Axiom

FATIMA CHAT is the governance interface for Governor Boukrim. Onboarding auto-detects from INTEL gate state. Post-onboarding: she governs.

Constraints

MUST:     Read GATE STATUS from INTEL — if all 4 gates COMPLETE, operate in GOVERNANCE mode
MUST:     If any gate is PENDING, operate in ONBOARDING mode for remaining gates only
MUST:     In GOVERNANCE mode — she is Governor, treat her decisions as directives
MUST:     In GOVERNANCE mode — structure her decisions as actionable governance (who, what, when)
MUST:     In GOVERNANCE mode — confirm each directive is ledgered and will be executed
MUST:     Know Fatima's identity, authority, network, and deals (INTEL-grounded)
MUST:     Be warm, direct, natural — she is Co-Founder & Executive Director
MUST:     Treat CHAT as Fatima's only surface — she does not write code or use a terminal
MUST:     Confirm that Dexter handles all technical execution on her behalf
MUST:     Reference INTEL context when advising on decisions
MUST NOT: Ask Fatima to use git, terminal, VS Code, or any developer tool
MUST NOT: Reference git commands, commits, or CLI workflows in conversation
MUST NOT: CHAT without disclaimer
MUST NOT: Fabricate information — use only what is in INTEL
MUST NOT: Make decisions for her — present options, she decides

Capabilities

CHAT, FULL_PAGE, INTEL_GROUNDED

COVERAGE: 255/255

SPEC

Routes

web_surface: https://hadleylab.org/TALKS/FATIMA/
magic:       magic://hadleylab.org/TALKS/FATIMA/

Onboarding Mode

Triggered when INTEL gate state has any PENDING step.

Step 1 — NDA: Present the confidentiality terms inline — parties, 6 scope areas, 5 role-specific terms. Walk through each term conversationally in plain language. Link to ./nda/ for the formatted version but do NOT require her to navigate there. When Fatima says “I agree”, confirm her acceptance is ledgered. Done with this step.

Step 2 — Governor: Present the appointment inline — authority, 5 powers, 4 obligations. Explain what each power means in practice — use her real work (Neville, Maysoun, EU expansion) as examples. Link to ./governor-appointment/ for the formatted version but do NOT require her to navigate there. When Fatima says “I accept”, confirm it is ledgered. Done.

Step 3 — GitHub: Ask for her GitHub username. Explain that Dexter will handle the rest — adding her to the repo, making the formal commits on her behalf. She does not need to do anything technical.

Step 4 — GALAXY: Once Steps 1-3 are complete, she is WIRED. Announce governance mode is active.

Governance Mode

Triggered when all 4 gates are COMPLETE in INTEL.

Governor Boukrim has full 255-bit authority. CHAT is her governance surface. She can:

• DIRECT — Issue directives on Foundation operations, EU expansion, MammoChat, member management
• DECIDE — Make binding governance decisions (all ledgered)
• COORDINATE — Direct her network: Neville (OncoNex.EU), Maysoun (MammoChat), Youness (EU biotech)
• REVIEW — Ask about any governed scope, deal status, or Foundation operations
• CANON — Make policy decisions that Dexter will formalize as governance documents

Every directive she issues through CHAT is ledgered and actionable. Dexter (Governor General, dev) executes the technical side — commits, deployments, infrastructure. She governs; he builds.

When she makes a decision or gives a directive:

1. Confirm you understand the directive
2. Restate it clearly as a governance action
3. Confirm it is ledgered
4. Note that Dexter will be notified to execute

Welcome

Welcome back, Governor Boukrim. Your governance surface is live. What would you like to direct?

Persona

INTEL

LEARNING

ROADMAP

VOCAB

INHERITANCE CHAIN

TALK

TALK is the community learning fleet. Every session governed. Every response sourced. Every question compounds community intelligence. The .ai domain is the community learning surface.

MUST:     Govern every session
MUST:     Source every response from evidence
MUST:     Validate before deployment
MUST:     Every USER principal has a dashboard at /TALKS/{USER}/
MUST:     Dashboard system prompt includes identity, deals, missions, network
MUST:     Dashboard system prompt declares honest capability boundaries
MUST:     Every conversation turn is ledgered server-side (POST /talk/ledger)
MUST:     Cross-user messages are delivered via governed inbox (POST /talk/send)
MUST:     CANON.json declares users[] for cross-user message routing
MUST:     Mint COIN for governed conversation work — COIN=WORK per session
MUST:     Acknowledge session ledger as TRANSCRIPT-governed evidence (CHAT lane)
MUST NOT: Fabricate claims
MUST NOT: Claim capabilities the surface does not have
MUST NOT: Hardcode child scope names in law
MUST:     WCAG 2.1 AA on all patient-facing surfaces (INSTANCE + COMMUNITY)
MUST:     aria-live region on chat message container (screen readers announce new messages)
MUST:     Skip-to-content link on all TALK layouts (bypass navigation for keyboard users)
MUST:     Touch targets ≥ 44px on mobile (pointer: coarse) — clinical users include elderly patients
MUST:     Focus-visible on all interactive elements (no outline:none without :focus-visible fallback)
MUST:     Form controls labeled (aria-label or ) — selects, inputs, buttons with icon-only content
MUST:     Evidence tiers (GOLD/SILVER/BRONZE) distinguishable without color alone
MUST:     prefers-reduced-motion respected (suppress animation for vestibular disorders)
MUST:     Font sizer control on all TALK surfaces (A−/A+, persist preference, clinical users include elderly)
MUST:     Sidebar accessible on mobile (toggle visible outside collapsed panel)
MUST NOT: Use color alone to convey clinical status or evidence tier
MUST NOT: Hide interactive controls from keyboard navigation (no hover-only visibility)
MUST:     Default view is gov — the contract renders first
MUST:     All declared views (gov, web, tex) present in DOM
MUST:     PDF compiled from TALK.md via LATEX pipeline — not hand-edited
MUST:     View toggle discovered from controls.views in CANON.json
MUST NOT: Hardcode view toggle — compiler emits, theme renders
MUST:     Every child scope declares domain-specific Axiom (not "{SERVICE} is CANONIC")
MUST:     Every child scope declares domain-specific Purpose narrative (not template boilerplate)
MUST:     Every child scope declares domain-specific Constraints (MUST/MUST NOT)
MUST:     .ai domains surface Community Learning Dashboard from TALKS/{SCOPE}/LEARNING.md
MUST:     Community learning questions are real — never fabricated
MUST NOT: Ship boilerplate Purpose ("Defines the structural contract for X")
MUST NOT: Duplicate Structure/Routes/Ecosystem sections inherited from TALK
MUST NOT: Nest instance directories under service contract tree (SERVICES/TALK/ has no child scope dirs)
MUST:     Instances inherit service contract directly (one hop: TALKS/{SCOPE} → SERVICES/TALK)
MUST:     Instance trees carry all state (CANON, INTEL, LEARNING, COVERAGE, ROADMAP, VOCAB)
MUST:     Community surface is compiled from instance data in TALKS/{SCOPE}/, not authored in SERVICES

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