GRANT
SERVICE CONTRACT · VIEW: GOV
Axiom
GRANT is the funded research lane. Every proposal is a governed artifact — aims authored in markdown, evidence linked to papers, budgets evidenced, deadlines enforced. Deterministic. Auditable.
Constraints
MUST: Link every aim to governed evidence (paper, ledger, or intel) MUST: Maintain correspondence ledger for all PI interactions MUST: Evidence consortium structure with partner roles and budget allocation MUST: Track submission deadline as hard constraint MUST: Declare PI and institutional lead MUST: Include SPECIFIC-AIMS.md as primary collaboration surface MUST: Every child instance at GRANTS/ inherits these constraints MUST: Instance trees carry all state (CANON, INTEL, LEARNING, COVERAGE, ROADMAP, VOCAB) MUST NOT: Nest instance directories under SERVICES/GRANT/ (service contract is the class, not the instance) MUST NOT: Submit without PI sign-off MUST NOT: Publish VAULT-gated terms on public surfaces MUST NOT: Hand-author compiled outputs
Capabilities
AIMS_DRAFT, CONSORTIUM_MAP, DEADLINE_ENFORCE, EVIDENCE_LINK, GRANT_PROPOSE
COVERAGE: 255/255
SPEC
Purpose
GRANT governs funded research proposals. Each grant is a governed scope with:
- SPECIFIC-AIMS.md — the collaboration surface (paper layout, linked evidence)
- {GRANT}.md — the deal spec (consortium, budget, WPs, timeline)
- CANON.md — axiom + constraints specific to the grant
- LEARNING.md — correspondence and event ledger
Structure
GRANTS/{GRANT}/
├── CANON.md — axiom + constraints
├── {GRANT}.md — grant spec (consortium, budget, WPs)
├── SPECIFIC-AIMS.md — collaboration surface (paper layout)
├── VOCAB.md — domain terms
├── README.md — summary
├── COVERAGE.md — 255-bit compliance
├── ROADMAP.md — critical path
└── LEARNING.md — ledger
Service Contract
| Term | Value |
|---|---|
| SERVICE | GRANT |
| INHERITS | SERVICES |
| SURFACE | paper layout with contribute gate |
| TALK | side |
| GATE | contribute (identity logged) |
LEARNING
Patterns
| Date | Signal | Pattern | Source |
|---|---|---|---|
| 2026-03-19 | FEEDBACK_PROMOTED | Grant writing feedback: How to write specific aims — follow Russell & Morrison (GAWW) as a bible, not ad hoc. The Trinid | intake:feedback_grant_writing.md |
| 2026-03-19 | REFERENCE_PROMOTED | GAWW Grant Writing Reference: Russell & Morrison Grant Application Writer’s Workbook is the domain knowledge for all gra | intake:reference_gaww_grants.md |
LEARNING | GRANT | _generated
ROADMAP
Now
- [x] GRANT service contract created
- [x] EHDS-GOV — first grant instance
Next
- [ ] Additional grant instances as pipeline grows
VOCAB
| Term | Definition |
|---|---|
| GRANT | Funded research proposal — governed scope with aims, consortium, budget |
| PI | Principal Investigator — institutional lead on the grant |
| CONSORTIUM | Multi-partner agreement for joint research |
| WP | Work Package — scoped deliverable within a grant |
| FUNDER | Granting authority (IHI, NIH, ERC, etc.) |
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