SUNSHINE

Axiom

PUBLIC RECORDS ARE GOVERNED INTELLIGENCE. EVERY REQUEST LEDGERED. EVERY RETRIEVAL ANCHORED.

Constraints

MUST:     Ledger every public records request (ID, agency, record, date filed, status)
MUST:     Cross-reference retrieved records to consuming scopes
MUST:     Verify retrieval status before citing as evidence anchor
MUST:     Respect statutory timelines (Ch. 119 — "reasonable time")
MUST:     Distinguish RETRIEVED (in hand) from ANCHORED (cited but not retrieved)
MUST NOT: Claim retrieval without actual record in possession
MUST NOT: Alter or redact retrieved public records
MUST NOT: Conflate California public records (TransparentCalifornia) with Florida Sunshine Law

Capabilities

CROSS_REFERENCE, RECORD_RETRIEVE, REQUEST_LEDGER, TIMELINE_TRACK

COVERAGE: 255/255

SPEC

Purpose

SUNSHINE extracts governed intelligence from Florida public records.

Florida Sunshine Law (Chapter 119, F.S.) makes government records publicly accessible. Every state agency document, grant application, contract, correspondence, and expenditure is a potential INTEL source. SUNSHINE governs the request, retrieval, and ledgering of public records across all scopes.

Structure

Leaf SERVICE scope. No governed child scopes. Extracted intelligence lands in INTEL.md and cross-references to consuming scopes.

Required closure artifacts per scope: CANON.md, README.md, SUNSHINE.md, VOCAB.md, ROADMAP.md, COVERAGE.md, LEARNING.md.

Learning lane per governed scope: LEARNING.md at the scope root is terminal and SHALL NOT nest further LEARNING/.

Routes

web_docs: https://hadleylab.org/
web_surface: https://hadleylab.org/SERVICES/SUNSHINE/
magic:    magic://hadleylab.org/SERVICES/SUNSHINE/

Pipeline

Identify record (grant app, contract, correspondence, expenditure)
  -> File public records request (Ch. 119, F.S.)
  -> Agency processes request (statutory timeline)
  -> Retrieve records
  -> Extract INTEL (claims, evidence, letters of support, data agreements)
  -> Ledger in INTEL.md (request ID, agency, status, artifacts)
  -> Cross-reference to consuming scopes (MAMMOCHAT, CLINICAL, FINANCIALS, VITAE)

Applicable Agencies

Agency	Record Types	Cross-Scope
Florida Department of Health (FDOH)	Grant applications, award letters, contracts, correspondence	MAMMOCHAT, CLINICAL, FINANCIALS
University of Central Florida (UCF)	Employment records, salary, contracts, research agreements	VITAE, FINANCIALS
Florida Department of State	Corporate filings, entity records	DEAL, KYC
Any Florida state agency	Correspondence, expenditures, contracts	Cross-cutting

Ecosystem Connectivity

Upstream: SERVICES meta-governance.
Authority: Florida Constitution Art. I §24 + Chapter 119, Florida Statutes.
Source: Florida state agencies (FDOH, UCF, DOS, etc.) — public records requests.
Sink: INTEL.md — request ledger and extracted intelligence.
Consumers: Any scope that depends on state records for evidence anchoring.
Existing anchors: VITAE salary data already sourced from Florida public records (OpenPayrolls).

Pages

Page	Sections
Overview	Purpose, Structure
Pipeline	Pipeline, Applicable Agencies
Ecosystem	Routes, Ecosystem Connectivity

Default: Overview.

Persona

Field	Value
tone	formal
audience	legal, compliance, governance operators
voice	third-person
warmth	neutral
context	public records governance — precise, auditable, evidence-anchored

INTEL

Request Ledger

ID	Agency	Record	Filed	Status	Artifacts
SUN-001	FDOH (Tallahassee)	MammoChat $2M grant application (Casey DeSantis Florida Cancer Innovation Award)	PENDING — verify if filed	UNKNOWN	AdventHealth letter of support, data sharing agreement, grant narrative, budget

Known Public Records (Already Sourced)

Record	Agency	Source	Status	Consumer
UCSF salary (2015-2019)	California State Controller	TransparentCalifornia.com	RETRIEVED	VITAE §Salary
UCF salary (2019-2025)	Florida Has A Right To Know	OpenPayrolls.com	RETRIEVED	VITAE §Salary
NIH grant UH2CA203792	NIH Reporter	reporter.nih.gov	RETRIEVED	VITAE §Grants, FINANCIALS
NIH grant U01LM012675	NIH Reporter	reporter.nih.gov	RETRIEVED	VITAE §Grants, FINANCIALS
NIH grant U19AR076737	NIH Reporter / Grantome	grantome.com	RETRIEVED	VITAE §Grants, FINANCIALS
Clinical trial NCT06604078	ClinicalTrials.gov	clinicaltrials.gov	RETRIEVED	CLINICAL, MAMMOCHAT

Pending Retrievals

Record	Agency	Why	Priority	Consumer
FDOH MammoChat grant application	FDOH Tallahassee	AdventHealth letter of support, 20K images data sharing agreement, full grant narrative	HIGH	MAMMOCHAT, CLINICAL
UCF separation records	UCF	Employment timeline verification	LOW	VITAE

Cross-Scope Evidence Map

Public Record	Anchors Claim	In Scope
FDOH grant award	“$2M Casey DeSantis Florida Cancer Innovation Award”	VITAE, FINANCIALS, MAMMOCHAT
FDOH grant app — AdventHealth letter	“AdventHealth supports MammoChat”	MAMMOCHAT/INTEL §AdventHealth Partnership
FDOH grant app — data agreement	“20K mammography images from AdventHealth”	MAMMOCHAT/INTEL, LEARNING/mubarak-shah
NIH Reporter grants	“$38M+ in research funding from NIH”	VITAE, FINANCIALS, LINKEDIN/PAGES/HADLEYLAB
UCF salary records	Employment verification	VITAE §Salary

Test

prompt	expect	cross
What law governs Florida public records?	Chapter 119, F.S.
What FDOH record contains the AdventHealth letter of support?	MammoChat grant application	MAMMOCHAT
What salary records are already sourced from public records?	UCSF (TransparentCalifornia), UCF (OpenPayrolls)	VITAE
What is the status of the FDOH grant application retrieval?	PENDING	MAMMOCHAT

LEARNING

What Gets Learned

Type	Example
Statutory authority	Florida Sunshine Law = Ch. 119, F.S. + Art. I §24
Existing sources	VITAE salary already sourced from public records (TransparentCalifornia, OpenPayrolls)
FDOH grant app	Contains letters of support, data agreements, budget — not just award amount
Cross-state records	California public payroll (TransparentCalifornia) is different authority than Florida Sunshine
NIH Reporter	Federal grants are public via reporter.nih.gov — not Sunshine Law but same principle
AdventHealth evidence	Letter of support for FDOH grant anchors the partnership claim

ROADMAP

Now

Verify if FDOH MammoChat grant application request was filed (SUN-001)
Retrieve AdventHealth letter of support + data sharing agreement
Ledger all existing public record sourcing (VITAE salary, NIH grants)

File FDOH request if not yet executed
Extract and cross-reference grant application artifacts
Template for recurring Sunshine Law requests

Later

UCF employment records verification
Florida DOS corporate filings (entity formation)
Automated request tracking with statutory deadline monitoring

VOCAB

Term	Definition
ANCHORED	Record cited as evidence but sourced from public database (NIH Reporter, ClinicalTrials.gov) rather than direct request
RETRIEVED	Record is in possession and available for INTEL extraction

INHERITANCE CHAIN

SERVICES

SERVICES compose primitives — INTEL + CHAT + COIN. Every service governed. Every scope discovered.

MUST:     Maintain TRIAD integrity (CANON.md + VOCAB.md + README.md)
MUST:     Treat SPEC as scope identity (`{SCOPE}` directory), not as a file
MUST:     Every SERVICE scope include ROADMAP.md, COVERAGE.md, LEARNING.md, and `{SCOPE}.md` as governed content surfaces
MUST:     Discover SERVICE scopes from filesystem only (no manual catalog)
MUST:     Keep http:// and magic:// on the same namespace (transport differs, scope path matches)
MUST:     CANON.md = axiom + universal constraints (no service names, no paths, no implementation)
MUST:     README.md = how to run the CANON (nothing else)
MUST:     {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST:     SHOP.md = public projection file (per scope, filesystem-discoverable)
MUST:     VAULT.md = private projection file (per scope, filesystem-discoverable)
MUST:     Runtime implementation remains under ~/.canonic; this workspace is governance-first
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST NOT: Define ungoverned terms outside VOCAB.md
MUST NOT: Treat `{SCOPE}.md` as SPEC identity
MUST NOT: Move architecture/lifecycle into README
MUST NOT: Leak private projections to public surfaces
MUST NOT: Maintain duplicate mapping tables outside generated manifest outputs
MUST NOT: Add runtime jargon to governance contracts
MUST:     Ledger-consuming services declare source ledgers, scope filters, and closure gates
MUST:     Learning governance remains live — closure claims require fresh DISCOVER → GENERATE → RELINK evidence

hadleylab-canonic

HADLEYLAB ships software. Every app, book, paper, deal, and patent is PROOF that MAGIC works. COIN = WORK. LEARNING = COMPUTE.

MUST:     Every app, book, paper, deal, or patent is evidence of MAGIC
MUST:     All scopes inherit canonic-canonic/CANONIC.md governance
MUST:     All users governed under USERS/ via SERVICES/USER
MUST:     Cross-index INTEL across users (INTEL.md)
MUST:     Shared events propagate to ALL affected user dashboards
MUST:     Maintain governance workspace purity (.md files only)
MUST:     Ledger all COIN (validated work) through MAGIC 255
MUST:     Compile all INTEL from governed sources
MUST:     Keep frontend/runtime implementation under ~/.canonic (hidden runtime)
MUST:     Surface governed TALK, Library, and SERVICES scopes (no orphan content)
MUST:     Derive nav labels from governed scope names (no hardcoded strings)
MUST NOT: Publish without governance (CANON.md required)
MUST NOT: Duplicate primitives — compose from INTEL, CHAT, COIN
MUST NOT: Silo intelligence inside a single user when multiple are affected
MUST NOT: Expose VAULT contents outside NDA scope
MUST NOT: Store runtime artifacts in governance workspace

canonic-canonic

SPEC is governance. `canonic-canonic/` is the spec root.

MUST:     Keep this repo governance-only (.md/.pdf)
MUST:     Publish workspace mapping in CANONIC.git (no hardcoded repo lists)
MUST:     Preserve three primary lanes: FOUNDATION, INDUSTRIES, MAGIC
MUST NOT: Commit runtime artifacts here (runtime belongs in ~/.canonic/)
MUST:     Sell MAGIC tiers — the product, not the proof (proof is hadleylab-canonic)
MUST NOT: Embed beta-test app URLs in platform page content