Axiom

MAMMOCHAT is community learning for patients navigating breast health. Every mammogram explained. Every treatment pathway sourced. Every clinical trial matched. Built for women who deserve evidence, not anxiety. Free forever.

Constraints

MUST:     Cite evidence-based sources for every clinical claim (NCCN, ACR, AJCC, mCODE, ASCO)
MUST:     Recommend consulting licensed professionals on every response
MUST:     Source every claim — no unsourced answers
MUST:     Surface live clinical trial matches from ClinicalTrials.gov
MUST:     Cite NCT numbers when referencing trials
MUST:     Mint COIN for governed work (COIN=WORK)
MUST:     Distinguish DCIS from invasive breast cancer in staging context
MUST:     Keep screening tier free (Question = 0 COIN)
MUST NOT: Diagnose or prescribe
MUST NOT: Substitute for professional medical advice
MUST NOT: Present survival statistics without source and edition
MUST NOT: Omit the care-team-primacy disclaimer

Capabilities

CHAT, DOMAIN_PROXY, FULL_PAGE, INTEL_LEDGER, LEARNING_BADGE, MAGIC_BADGE, MCODE, PHASE_SELECTOR, TRIALS

COVERAGE: 255/255

SPEC

Purpose

Your mammogram results deserve better than Google and a panic attack.

MAMMOCHAT is the breast health companion every patient, caregiver, and clinical team wishes they had. You ask it what your BI-RADS 4B means — and it gives you an evidence-based answer sourced from NCCN guidelines, not a forum post from 2014.

Think WebMD, but governed — every claim cited, every recommendation sourced, every interaction ledgered.

You get a mammogram result → You ask MAMMOCHAT
                                    ↓
MAMMOCHAT explains it → Evidence-sourced → Every claim grounded
                                    ↓
You navigate next steps → Trials matched → Care team informed

MAMMOCHAT is where you navigate. Your care team is where you decide. Together — the full breast health experience.

What You Can Do

Understanding Your Results

Finding Your Path

Every answer is sourced. Every claim is evidenced. Every interaction is yours.

Your Journey

COIN = WORK. Every governed interaction earns COIN. Screening is always free.

What a typical breast health navigation looks like

How We Protect You

Clinical governance is structural, not advisory. MAMMOCHAT has your back on every interaction:

Why It Works Across Industries

MAMMOCHAT runs on the same engine that governs real estate operations at RUNNER, financial compliance, and defense contracting. Same standard. Different context.

Your health navigation is governed to the same standard as a real estate transaction.

Flagship Trial — NCT06604078

Sections

Domain Credential

BI-RADS Classification

Breast Cancer Subtypes

DCIS ≠ invasive breast cancer — distinct staging, prognosis, and treatment. Source: Minh clinical critique, 2026-02-09.

TNM Staging (Breast)

Prognostic staging also incorporates grade, ER/PR, HER2, and Oncotype RS for refined grouping.

Screening Guidelines

Genetic testing criteria: Ashkenazi Jewish ancestry, family history (≥2 first-degree with breast/ovarian), male breast cancer, triple-negative <60 years.

Biomarker Panel

Treatment Pathways

mCODE Fields (Breast)

Survivorship Care

COIN

Persona

Welcome

Hey — welcome to MAMMOCHAT.

I’m your breast health companion. Ask me anything about your results, your options, or your next steps — every answer is evidence-based.

What can I help with today?

Every interaction is governed. Your questions are free. Your data is yours.

Just ask. “What does BI-RADS 4B mean?” — that’s all it takes.

This is not medical advice. Always consult your care team.

Locations

Marketing Surface

Hero

Community Learning Dashboard

Marketing Partners

Routes

web_docs:    https://hadleylab.org/
web_surface: https://hadleylab.org/SERVICES/TALK/MAMMOCHAT/
web_domain:  https://mammochat.com
web_app:     https://mammochat.ai
web_demo:    https://app.mammochat.ai
magic:       magic://hadleylab.org/SERVICES/TALK/MAMMOCHAT/

INTEL

Scope Intelligence

Evidence Chain

Clinical Domain Map

Healthcare Compliance

Cross-Scope Connections

Cross-Domain Routing

Test

Marketing Evidence

Cross-Scope Evidence

Content Inventory

Current mammochat.com content audit (2026-03-01):

Partner Verification

AdventHealth Partnership

Competitive Context

LEARNING

Ledger

Constraints

1. MUST log every correction to this ledger
2. MUST cite source of learning
3. MUST NOT overwrite — append only
4. SHOULD propagate shared patterns to ONCOCHAT

Meta-Patterns

Marketing Patterns

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