What the model is allowed to invoke
Each opcode is a deterministic function the model calls instead of generating a clinical answer in free text. The function reads a citable canon table and returns a verified value. The model never writes the medical answer. It only decides which opcode to invoke. The opcode produces the answer, and the citation chain travels with it. Below: the registry, organized by tissue and domain. Opcode names and implementations are withheld for IP integrity; the function each performs and the evidence class each invokes is shown.
The discipline
An opcode is bound to one or more citation classes. A clinical opcode invoked at runtime must produce a value whose provenance traces to at least one source in the bound class. The SHA-256 hash of each bound citation will live with the opcode at compile time, so any verifier can confirm the citation chain without trusting Nexus Concordat or any third party. The hash slots are reserved below; population is in progress as the citation registry is finalized.
Opcode names and source code are not published. The function each opcode performs and the evidence it relies on are. That is the contract. Trust the evidence, not the operator.
Registry by tissue and domain
Cardiac System
- FDA approved drug labels (DailyMed)
- RxNorm + DrugBank curated interaction tables
- AHA/ACC/HRS clinical practice guidelines
- PubMed cardiology pharmacology literature
- FDA drug labels (boxed warnings, contraindication sections)
- NHLBI clinical practice guidelines (JNC8, ATP3, Million Hearts)
- AHA/ACC guidelines for specific drug classes
- PubMed contraindication case literature
- AHA/ACC heart failure guideline-directed titration ladders
- ESC heart failure dose escalation protocols
- NHLBI ATP3 antihypertensive titration recommendations
- FDA-approved dosing escalation language per agent
- AHA/ACCF/HRS standardized ECG recommendations (Wagner et al.)
- Sgarbossa criteria for ischemic patterns
- Brugada criteria (wide-complex tachycardia)
- ESC chamber enlargement / hypertrophy criteria
- PubMed cardiac electrophysiology literature
- Fick principle (cardiac output from oxygen consumption)
- Stewart-Hamilton thermodilution equations
- SVR / PVR calculation per AHA/SCAI consensus
- Berne & Levy Physiology, 7th edition
- DSM-5 / ICD-11 cardiac-relevant codes
- AHA/ACC chest pain / dyspnea / syncope clinical pathways
- NHLBI Framingham Heart Study epidemiologic priors
- UpToDate / Harrison's Principles of Internal Medicine (cardiac sections)
- AHA/ACC STEMI activation criteria
- HEART / GRACE / TIMI risk score thresholds for escalation
- NHLBI heart failure hospitalization criteria
- ACEP chest pain emergency pathways
- HEART score (Six et al., Crit Pathways Cardiol)
- TIMI risk score (Antman et al., JAMA)
- GRACE risk model (Eagle et al., JAMA)
- CHA2DS2-VASc (Lip et al., Chest) and HAS-BLED (Pisters et al., Chest)
Cellular Metabolism
- Lehninger Principles of Biochemistry (current edition)
- KEGG Pathway Database (map00010)
- Voet & Voet Biochemistry
- Lehninger Principles of Biochemistry
- KEGG Pathway Database (map00020)
- Stryer Biochemistry
- Lehninger Principles of Biochemistry
- Hinkle P/O ratio measurements (FEBS Letters)
- Mitchell chemiosmotic hypothesis (Nature, Nobel 1978)
- Lehninger Principles of Biochemistry
- KEGG Pathway Database (map00071)
- Voet & Voet Biochemistry
- Lehninger Principles of Biochemistry
- KEGG Pathway Database (map00010 reverse)
- Composes opcodes 9, 10, 11 (glycolysis + Krebs + oxphos)
- Lehninger Principles of Biochemistry, complete oxidation chapter
Molecular Biology
- The Universal Genetic Code (NCBI Taxonomy translation table 1)
- Crick et al., Nature (1961) — adapter hypothesis
- Nirenberg / Khorana / Holley Nobel work (1968)
- NCBI translation tables (per-organism initiation codons)
- Kozak consensus sequence (Kozak, Nucleic Acids Research)
- NCBI translation tables
- Universal Genetic Code stop signals
Amino Acid Chemistry
- IUPAC-IUB nomenclature (Eur J Biochem, 1984)
- Lehninger Principles of Biochemistry, amino acid appendix
- IUPAC-IUB nomenclature (Eur J Biochem, 1984)
- ExPASy ProtParam reference masses
- NIST atomic mass data
- Kyte & Doolittle (J Mol Biol, 1982)
- Eisenberg hydrophobicity scale (Proc Natl Acad Sci, 1984)
Linguistic Structure
- Penn Treebank POS tag set (Marcus et al., Computational Linguistics, 1993)
- Universal Dependencies POS tag set v2
- WordNet lexical database (Princeton)
- Penn Treebank POS tag set
- International Phonetic Alphabet (IPA), 2020 revision
- Ladefoged & Maddieson, Sounds of the World's Languages
- International Phonetic Alphabet feature matrix
- Chomsky & Halle, The Sound Pattern of English
- Spalding, The Writing Road to Reading (70 phonogram set)
- Orton-Gillingham phonogram corpus
- Merriam-Webster pronunciation database
What the registry guarantees
The model does not generate the answer. The model decides which opcode to invoke. The opcode reads its bound citation class and returns a value whose provenance traces to a documented source.
Names and implementations are withheld; bindings are not. The numbered registry above tells you what each opcode does and what evidence it is constrained to. The opcode names and source code are proprietary. The citation chain is public.
SHA-256 hashes will travel with each opcode. The hash slots above will be populated as the citation registry is compiled. After compilation, an external verifier can confirm the chain by querying the registry endpoint and comparing hashes against the bound citation set. The model itself cannot return a value whose hash is not in the registry.
This is what makes the architecture verifiable. Standard generative medical AI emits free text and then attempts post-hoc citation. We emit citation first, value second. The hash chain is built in.