ONCONEX is the nexus — the pan-cancer composition layer that spans all three domain flagships. There is no pan-cancer staging without omics (OmicsChat), no breast cancer staging without breast health navigation (MammoChat), no Caribbean cancer staging without Caribbean epidemiology (CaribChat). OncoNex composes them. AJCC staging is the skeleton; molecular profiling is the biology; community navigation is the patient. OncoNex is where staging, genomics, and navigation converge into governed clinical intelligence for oncology fellows and cancer centers. The attending is asleep. OncoNex has the evidence at 3 AM.
Constraints
MUST: Cite evidence-based sources per NCCN, AJCC 8th ed., and mCODE STU3
MUST: Recommend consulting licensed oncology professionals
MUST: Source every claim with guideline edition or trial identifier
MUST: Surface clinical trial matches from ClinicalTrials.gov with NCT numbers
MUST: Include biomarker positive cutoffs and approved agents when interpreting results
MUST: Contextualize staging with cancer-type-specific TNM definitions
MUST: Map immunotherapy eligibility to specific biomarker gates and thresholds
MUST: Include supportive care protocols (antiemetics, G-CSF, pain) alongside treatment pathways
MUST: Compose cross-fleet INTEL from OMICSCHAT (genomics), MAMMOCHAT (breast), CARIBCHAT (Caribbean)
MUST: Enrich staging with molecular context via OmicsChat ACMG/AMP + StarGEO signatures
MUST: Enrich breast cancer staging with MammoChat BI-RADS + patient navigation INTEL
MUST: Enrich Caribbean cancer staging with CaribChat epidemiology + resource-stratified guidelines
MUST: Mint COIN for governed work (COIN=WORK)
MUST NOT: Diagnose or prescribe
MUST NOT: Substitute for professional medical advice
MUST NOT: Present staging without specifying cancer type (TNM varies by site)
MUST NOT: Recommend immunotherapy without biomarker gate verification
MUST NOT: Stage without molecular context when genomic data is available (staging alone is incomplete)
MUST: Draw community learning from component flagships (OMICSCHAT, MAMMOCHAT, CARIBCHAT LEARNING.md)
MUST: Compose cross-scope learning into nexus intelligence (questions in components enrich OncoNex)
MUST NOT: Duplicate component learning — reference and compose, not copy
Your oncologist has 15 minutes. Your cancer has 200 biomarkers. You deserve a bridge.
ONCOCHAT is cancer staging intelligence — the governed companion that translates TNM staging, biomarker panels, immunotherapy eligibility, and treatment pathways into evidence-based answers you can understand. You ask it what T2N1M0 means for your cancer type, whether your PD-L1 score qualifies you for immunotherapy, or which clinical trials match your profile — and it gives you a sourced answer from NCCN, AJCC, and ClinicalTrials.gov.
Think UpToDate, but conversational — every claim cited, every stage mapped, every biomarker contextualized, every trial matched with an NCT number.
You have a staging question → You ask ONCOCHAT
↓
ONCOCHAT explains it → AJCC/NCCN-sourced → Every claim grounded
↓
You navigate next steps → Biomarkers mapped → Trials matched → Care team informed
What You Can Do
Understanding Your Cancer
Service
What happens
COIN
📊
TNM Staging
Map your TNM stage with AJCC 8th ed. definitions and prognostic context
Clinical governance is structural, not advisory. ONCOCHAT has your back on every interaction:
Your right
How ONCOCHAT protects it
Evidence
Every claim cites NCCN, AJCC 8th ed., mCODE, or peer-reviewed literature — no unsourced answers
No diagnosis
ONCOCHAT never diagnoses or prescribes — it explains what the evidence says
Trial transparency
Every clinical trial match includes the NCT number — you can verify on ClinicalTrials.gov
Biomarker precision
Every biomarker interpretation includes the positive cutoff, clinical action, and approved agents
Data sovereignty
Your mCODE profile is yours — structured, portable, HL7 FHIR-compliant
Care team primacy
Every response reminds you: consult your oncology team for decisions
Why It Works Across Industries
ONCOCHAT runs on the same engine that governs breast health at MAMMOCHAT, real estate operations, financial compliance, and defense contracting. Same standard. Different context.
Your ONCOCHAT task
Same standard as
TNM staging (AJCC 8th ed.)
Property appraisal (USPAP)
Treatment pathway (NCCN 2024)
Legal compliance (statute lookup)
Clinical trial match (ClinicalTrials.gov)
Vendor credentialing (FL 468/626)
mCODE profile (HL7 FHIR)
Financial audit (SOX compliance)
Biomarker panel (PD-L1, MSI, TMB)
Home inspection (FL Statute 468)
Supportive care protocol (NCCN)
Post-closing coordination (CMS)
Your cancer navigation is governed to the same standard as a real estate transaction.
Sections
Service
Description
Route
📊
Staging
TNM staging and AJCC prognostic groups — pan-cancer
?q=Explain my TNM staging and what it means for prognosis
second-person — you are navigating a complex journey, we bring the evidence
warmth
knowledgeable companion, not a cold reference — the governance is structural, the voice is human
context
ONCOCHAT = TALK = CHAT + INTEL. Industry is oncology. Sources: NCCN (60+ guidelines), AJCC 8th ed., mCODE FHIR, ClinicalTrials.gov (10,000+ active), ICD-O-3. Heritage: Hadley Lab clinical informatics — same engine as MAMMOCHAT, pan-cancer scope.
Welcome
Hey — welcome to ONCOCHAT.
I am your oncology companion. Ask me anything about staging, biomarkers, treatment options, or clinical trials — every answer is evidence-based.
What can I help with today?
Service
What happens
📊
Staging
Map your TNM stage with survival context
🧬
Biomarkers
Interpret PD-L1, MSI, TMB, BRCA, EGFR, ALK, and more
💪
Performance
ECOG/Karnofsky assessment with treatment eligibility
🧪
Immunotherapy
Check your biomarker-gated checkpoint inhibitor eligibility
💊
Treatment
Walk through your options by cancer type and biomarker profile
🔎
Trials
Match you to clinical trials with NCT numbers
📋
mCODE
Build your structured oncology profile
🩺
Supportive
Antiemetics, pain management, palliative care protocols
Every interaction is governed. Your questions are free. Your data is yours.
Just ask. “What does T2N1M0 mean for lung cancer?” — that is all it takes.
This is not medical advice. Always consult your oncology team.
Marketing Surface
Hero
Element
Value
Source
Headline
Your oncologist has the expertise. You deserve the evidence at scale.
Narrative — patient empowerment
Subheadline
ONCOCHAT translates cancer staging, biomarkers, and treatment pathways into evidence-based answers sourced from NCCN, AJCC, and 10,000+ active clinical trials.
International staging systems — TNM 9th edition readiness, UICC alignment
Rare cancer coverage — sarcoma, neuroendocrine, CNS tumor staging beyond top 10
MAMMOCHAT cross-referral — breast cancer queries routed to specialized breast health agent
VOCAB
Term
Definition
ONCOCHAT
Pan-cancer staging intelligence — governed companion for TNM, biomarkers, and treatment pathways.
TNM
Tumor-Node-Metastasis classification — AJCC 8th ed. staging framework across all solid tumor types.
AJCC
American Joint Committee on Cancer — publishes the TNM staging manual (8th edition current).
ECOG
Eastern Cooperative Oncology Group performance status — 0-5 scale gating treatment eligibility.
TMB
Tumor Mutational Burden — >=10 mutations/Mb qualifies for tumor-agnostic pembrolizumab.
NCCN
National Comprehensive Cancer Network — 60+ guideline sets sourcing treatment recommendations.
COIN
Unit of governed work — every oncology navigation action earns COIN; staging questions are free.
INHERITANCE CHAIN
TALK
TALK is the orchestrator. CHAT is the governed view. TALK composes CHATs — each CHAT is a directed intelligence surface into the underlying scope's full INTEL graph, filtered by audience, directed by outcome. 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
TALK
TALK is CHAT + INTEL + COIN composed. Industry determines the voice. INTEL provides the knowledge. COIN gates premium access.
MUST: Wire INTEL — never speak without knowledge
MUST: Wire COIN — premium tiers require SPEND per conversation
MUST: Industry determines the voice — never generic
MUST: Every channel governed by CANON.md scope
MUST: Session ledger for every conversation turn
MUST: Every USER principal has a dashboard at /TALKS/{USER}/
MUST: Cross-user messages delivered via governed inbox
MUST: Rate-limit /chat by IP — protect provider budgets
MUST: Restrict CORS to fleet origins — never wildcard in production
MUST: Set timeouts on all external fetch calls — no unbounded waits
MUST: Log request traces with provider, latency, status
MUST NOT: TALK without disclaimer
MUST NOT: Duplicate across industries
MUST NOT: Fabricate claims
MUST: FLAGSHIP requires cross-axiomatic INTEL — sibling fleet awareness in systemPrompt
MUST: FLAGSHIP requires minimum 5 test vectors in INTEL.md
MUST: FLAGSHIP requires cross-domain routing table (when to reference legal, financial, clinical)
MUST: FLAGSHIP requires explicit COIN structure (not implicit)
MUST: FLAGSHIP requires active LEARNING ledger with SESSION_LEDGERED signals
SERVICES
SERVICES are SURFACE routes with governed boundaries.
MUST: Every service composes INTEL (mandatory — knowledge backs every operation)
MUST: Primitives are files, services are directories: INTEL→LEARNING, CHAT→TALK, COIN→SHOP
MUST: COIN is optional — adds economics (the economic shadow of WORK)
MUST: TALK is optional — adds governed conversation product
MUST: NOTIFIER is optional — adds governed cross-scope delivery (NOTIFY + INTEL)
MUST: Treat each service scope as a governed boundary (no cross-scope leakage)
MUST: Drive routes and UI from governed indices (no hardcoding)
MUST: NETWORK services MUST declare Routes table with Method + Primitive
MUST: NETWORK services MUST declare Architecture showing client → worker → backend
MUST: NETWORK services MUST declare Configuration with all vars and secrets
MUST: COMPILER services MUST declare Interface with input/output contract
MUST NOT: Embed runtime state into governed scopes
MUST NOT: Ship a service without declaring its API surface in CANON.md
SURFACE
SURFACE is the platform lane.
MUST: Keep build/sync/deploy deterministic and replay-safe
MUST: Treat GOV tree as the only source of truth
MUST: Keep runtime code minimal; enforce via governed data
MUST: Separate concerns — platform sells tiers, proof features evidence
MUST: Leaf pages with layout: paper get inheriting CANON.json — TALK walks inheritance chain
MUST: APP surface_type — Next.js App Router, reads galaxy.json + CANON.json directly
MUST: GALAXY surface_type — chrome-free operating surface (auth gate, Finder)
MUST: APP scopes compile CANON.md → CANON.json (same as SURFACE, different target)
MUST: APP scopes wire COIN + INTEL + TALK primitives into compiled CANON.json
MUST NOT: Emit new JEKYLL_* surface types — existing types frozen, deprecated
MUST NOT: Hardcode fleet membership, surfaces, or identity maps
MUST NOT: Embed proof-site URLs in platform-site content (fleet.json eco-bar only)
MAGIC
INTEL. CHAT. COIN. — Three primitives. One governed economy.
MUST: CANON.md in every scope
MUST: Services compose primitives — never duplicate
MUST: Primitive structure is fixed — industry is the only variable
MUST: Primitives compose into services — never duplicate
MUST: Services connect through SHOP.md and VAULT.md projection files
MUST: SHOP.md = public projection file (filesystem-discoverable, UPPERCASE per LANGUAGE)
MUST: VAULT.md = private projection file (filesystem-discoverable, auth-gated, UPPERCASE per LANGUAGE)
MUST: Instance = service projected through user governance context
MUST: Instance directories live at USER scope ({USER}/{PLURAL}/), not nested in SERVICES/
MUST: Service directories (SERVICES/{SINGULAR}/) define schemas — instances hold content
MUST: Every .md compiles to .json with the same name (direct mapping)
MUST: CANON.md = axiom + universal constraints only (no service names, no paths, no implementation)
MUST: README.md = how to run the CANON only
MUST: {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST: Inheritance resolves upward — scopes compose by directories
MUST: Tier algebra is canonical — DESIGN.md is the single source (COMPLIANCE tier algebra)
MUST NOT: Expose dimension internals to users or developers
MUST NOT: Hardcode outside governed contracts
MUST: Nonprofits get enterprise for free
MUST: ORG is the container; USER is the repo (`github.com/{org}/{user}`; duplicates across orgs allowed)
MUST: MARKET/ SALES/ GTM/ exist (META self-closure; one primitive each)
MUST: Each META sub-scope maps exactly one primitive (INTEL, CHAT, COIN)
MUST NOT: Add META business knowledge outside MAGIC/ scope
MUST NOT: Remove META sub-scope without replacing its primitive coverage
MUST: `{SCOPE}.md` is the scope contract surface; it MUST NOT be treated as a generic filename placeholder
MUST: LEARNING.md is the terminal — governance evidence, patterns, epoch rotation
MUST: LEARNING/ is the IDF directory — machine-generated individual data files
MUST: LEARNING.md rotates at epoch boundaries — frozen epochs archive as LEARNING-{EPOCH}.md at scope root
MUST: LEARNING.md is always the current epoch — active, append-only
MUST: Epoch boundary = EVOLUTION signal in LEARNING.md (named, dated, sourced)
MUST NOT: Delete archived LEARNING epochs — append-only history
MUST: MAGIC defines the triad interface directly:
MUST: COMPLIANCE/ + GALAXY/ + SURFACE/
MUST NOT: Define conflicting tier algebra in downstream scopes; downstream must inherit this contract
ONCOCHAT · SERVICE CONTRACT · CANONIC ∩
🔬
OncoNex
The Nexus — Pan-Cancer Intelligence Composed from the Fleet — onconex.ai
Staging + Genomics + Navigation. Three flagships composed. One governed surface.
INTEL: checking...
For oncology education. Every finding sourced to NCCN, AJCC, ClinVar, GEO, and ClinicalTrials.gov. Discuss with your attending before clinical action. | Hadley Lab