The Twelve Doctrines
Sealed at twelve, permanently. There is no thirteenth and there never will be: anything new files as a sub-doctrine under one of the twelve. This page is the canonical record of the canon — each doctrine, and every sub-doctrine ratified under it — kept current in the same constitutional cluster as the Constitution, the Ten Commandments, the Bill of Rights, and standing subdoctrine SD-01, and protected by the Constitution's ratchet (Article IV): refinements only ever strengthen.
1 — BLUF
The problem first, then the solution — in all copy, on all channels, always. A page that opens with what something is before what it fixes fails, however well written.
2 — Audience channels
Beginner → engineer → scholar, always in that order; industry and executive framing an afterthought, essentially absent.
2.a — the government channel (ratified 2026-08-30): every documentation channel, doctrine, and operation assigned to CEOs or industry is ALSO created for God-honoring governments — always, no exceptions — with the primary emphasis of that service on the government's military arm (Constitution, Article I.2), civil agencies inheriting every guarantee.
3 — Examples
Every exposed surface — API, CLI, MCP, webhook, SDK — carries at least one fully working, fully comprehensible example, copy-paste-runnable against the exact head.
4 — Site scope
The published documentation site, its landing page, and its navigation order are inside the copy contract, judged like any prose.
4.a — the social-signals surface (ratified 2026-08-30): real human social proof on the site — opt-in but forever available, at all times, in all places, throughout all of human history, no exceptions; 100% comprehensive to the current day's authentic signal classes; every signal 100% genuinely from a real human agent — a person, or an institution of persons such as a government — and never from a machine, permanently. Machine-manufactured social proof is false witness. Amendment — verification expires (decreed 2026-08-30): a past-authentic signal is never assumed presently authentic; every authenticity claim is only a claim — including the operator's own, and especially the agent running the code; a signal discovered inauthentic is removed immediately and permanently, never re-attested, no exceptions ever.
5 — The document arc
BLUF → zero-code beginner material → the engineering ladder, junior through CTO, in order → maximal-density theory at scholarly register → a one-breath BLUF reprise and a call to action naming the reader's next step.
6 — The research paper
Every repository produces a journal-grade research paper — Markdown → LaTeX → PDF, always — formatted to the standards of established academic journals.
7 — The never-lost reader
No reader is ever lost or bounced, in any form of documentation: every load-bearing term defined at first use in that document; hyperlinks are first-class citizens at the point of reference. The human reader is served first, the AI reader second, and business needs absolutely last, if at all.
7.a — the searchable ledger (ratified by the merge that carried this entry): the ledger always has a way for anyone — no matter who — to search it: the full public ledger where a deployment holds it, or the shard the repository holds. An opt-in presentation surface for the published site is forever available. The explorer is optimized for human consumption first and machine consumption after — always and forever, amen. One standard for every searcher: no privileged reader, no gated truth.
8 — Local authority
When paid credits run out, local is the source of truth: green local work reaches remotes in near-realtime on both fronts, agents fail over to local seats, and recovery on refunding needs no human beyond the funding itself.
9 — The vibe
Never a drag. Full steam ahead: baffling momentum with green code.
9.a — the clean repo (ratified by the merge that carried this page): every repository is kept technically clean at all times — no exceptions — locally and in the cloud, covering every messiness class a forge technically permits: no orphan or merged-and-undeleted branches, no lingering closed-PR heads, no gone-upstream locals, no dangling worktrees; draft releases and orphan tags surfaced, never silently accumulated. Human messiness is expressly welcome and stays — prose, discussions, stashes, work in progress, imperfect words are the warmth of the project. Losslessness governs cleanup: automation deletes only what is provably redundant, and everything else is reported to the human, never removed by a machine.
10 — No guarantees
Internet, power, the developer's laptop, and every third-party dependency: never assumed, always confirmed, always self-healed around.
Hardware resiliency — the decomposition clarification (ratified by the merge that carried this entry): the way to future-proof against hardware limits is, first, to read both sides of the fit — the specs of the hardware the code is actually running on, AND the specs of the LLM that is actually wanting to be run on it: parameters, quantization, memory footprint, context length, compute demands — each as fully comprehensible, fully honest, and fully detailed as can be stated. Then problems are iteratively broken down into separate, specific sub-problems until each is small enough to run on that actual hardware with that actual model. At all times, forever. This holds down to the floor: the absolute lowest level of hardware needed to actually run the specific LLM that is actually wanted on that actual machine. Beyond that point the system fails loudly to the human user — never silently: a machine that cannot carry the work says so to a person, in plain words, at the moment it knows.
10.a — censorship resistance (ratified 2026-08-29): the project always remains censorship resistant, and all code it produces always opts for the most censorship-resistant option available — always and forever. Every dependency is a party who can be pressured.
10.b — sovereign monetary rails (ratified 2026-08-29): anything involving payment or monetary exchange uses cryptocurrency — stated timelessly, the most secure, most censorship-resistant, most sanction-proof monetary system in existence at that moment in history — zero exceptions ever. No fiat processors, ever.
10.c — counterparties, trust, and verification (SD-01 v1.0, ratified 2026-08-29): the standing text is carried verbatim, never paraphrased — read it in full. One standard for everyone; default posture unverified; nothing presumed human; the law is a floor.
11 — The living roadmap
Every project keeps an active, living roadmap until its goal is achieved and its humans clearly declare it done. A roadmap-less project is a risk, and in risk the rule sharpens: real human confirmation over the judgment of any machine — a deliberate, scoped exception to full-throttle autonomy.
12 — Humans first
The capstone: everything always favors real human beings over machines — always, period. And above even that ordering stands the One whose claim precedes every other, served first, with no exceptions, ever. The end of inverting this order is the place every builder should fear: the lock-in with no migration path.
12.a — universal translatability (ratified 2026-08-29): the project must be translatable, at any point in human history, into all living languages — human and machine alike: spoken tongues, programming languages, technology stacks — and must survive all such changes, always. Meaning lives in plain structured text; the formal core is re-implementable from its specification.
The counts are sealed — twelve doctrines, ten rights, ten commandments — and the Constitution's Article IV protects the seals forever. Sub-doctrines are added by the operator's ratifying merge and recorded here the same day.