The CodicesThe library
The dependency map.
Doctrine only holds if the chain of authority is explicit. Higher wins: a Standard cannot loosen a Codex, a decision record cannot amend the Constitution, and code cannot outrank any of them.
CODEX 1 — THE CONSTITUTION
|
CODEX 0 — THE BLUEPRINT ---- PART II: THE REGISTRY
|
CODICES 2..11 — DOMAIN DOCTRINE
|
STANDARDS — STD-A D S I X R F Q
|
DECISION RECORDS
|
src/Document by document
- Governs
- 0 · Codex 0 — The Master Blueprint of Anabasis
- 2 · Codex 2 — The Divisions
- 3 · Codex 3 — CapabilityOS
- 4 · Codex 4 — People, User Types, and Permissions
- 5 · Codex 5 — Shared Data Model and API Boundaries
- 6 · Codex 6 — Experience Doctrine
- 7 · Codex 7 — Engineering Doctrine
- 8 · Codex 8 — The Financial Doctrine
- 9 · Codex 9 — The Governance Doctrine
- 10 · Codex 10 — The Institutional Critic
- 11 · Codex 11 — The Institutional Systems Architecture
- STD · The Institutional Standards of Anabasis
- STD-R · STD-R — The Research Standard
- Governed by
- 1 · Codex 1 — The Constitution of Anabasis
- 9 · Codex 9 — The Governance Doctrine
- 0003 · 0003 — The Institutional Registry becomes the mandatory pre-implementation artefact
- 0004 · 0004 — Codex 0 becomes a specification book; Codex 6 gains a UX rubric
- 0006 · 0006 — The Institutional Systems Architecture
- 0007 · 0007 — The Financial Doctrine and the Governance Doctrine
Governs- 0 · II · Codex 0, Part II — The Institutional Registry
- STD · The Institutional Standards of Anabasis
- 0 · index · Codex 0 — The Master Blueprint of Anabasis
- 0 §01 · Codex 0 · Chapter 01 — The Institution
- 0 §02 · Codex 0 · Chapter 02 — The Five Divisions
- 0 §03 · Codex 0 · Chapter 03 — The Executive and Stewardship Offices
- 0 §04 · Codex 0 · Chapter 04 — People
- 0 §05 · Codex 0 · Chapter 05 — CapabilityOS
- 0 §06 · Codex 0 · Chapter 06 — The Knowledge Graph (ENG-01)
- 0 §07 · Codex 0 · Chapter 07 — The Data Model
- 0 §08 · Codex 0 · Chapter 08 — Permissions
- 0 §09 · Codex 0 · Chapter 09 — Cross-Division Workflows
- 0 §10 · Codex 0 · Chapter 10 — API Boundaries
- 0 §11 · Codex 0 · Chapter 11 — Surfaces
- 0 §12 · Codex 0 · Chapter 12 — Dashboards
- 0 §13 · Codex 0 · Chapter 13 — AI Agents
- 0 §14 · Codex 0 · Chapter 14 — Internal Tooling
- 0 §15 · Codex 0 · Chapter 15 — The Financial Architecture
- 0 §16 · Codex 0 · Chapter 16 — Reporting and Measurement
- 0 §17 · Codex 0 · Chapter 17 — Platform Architecture and Engineering
- 0 §18 · Codex 0 · Chapter 18 — Scale and Expansion
- 0 §19 · Codex 0 · Chapter 19 — Glossary
- 0 §20 · Codex 0 · Chapter 20 — The Twelve Institutional Systems
- 0 §21 · Codex 0 · Chapter 21 — Institutional Memory and the Institutional Lifecycle
- 11 · Codex 11 — The Institutional Systems Architecture
- 2 · Codex 2 — The Divisions
- 3 · Codex 3 — CapabilityOS
- 4 · Codex 4 — People, User Types, and Permissions
- 5 · Codex 5 — Shared Data Model and API Boundaries
- 6 · Codex 6 — Experience Doctrine
- 7 · Codex 7 — Engineering Doctrine
- 8 · Codex 8 — The Financial Doctrine
- Governed byGoverns
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governs
- Binds nothing directly.
- Governed by
- Governed by
- Governed byGoverns
- 0 · Codex 0 — The Master Blueprint of Anabasis
- 10 · Codex 10 — The Institutional Critic
- 0001 · 0001 — The Codices are the supreme authority of the project
- 0002 · Decision 0002 — Institutional UX doctrine, feature evaluation, and the Institutional Critic
- 0003 · 0003 — The Institutional Registry becomes the mandatory pre-implementation artefact
- 0004 · 0004 — Codex 0 becomes a specification book; Codex 6 gains a UX rubric
- 0005 · 0005 — The Institutional Standards: the third doctrinal layer
- 0006 · 0006 — The Institutional Systems Architecture
- 0007 · 0007 — The Financial Doctrine and the Governance Doctrine
- 0008 · 0008 — The eight-layer institutional architecture, and Creation as the sixth capability
- 0009 · 0009 — The database is the Academy catalog; the TypeScript curriculum is no longer served
- TEMPLATE — a Codex
- Governs
- Governs
- Binds nothing directly.
- Governs
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governs
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governs
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governed byGoverns
- Binds nothing directly.
- Governed by
- Nothing above it.
Governs- Binds nothing directly.
- Governs
- Binds nothing directly.
Registry classes
Every entry in the Registry names one governing Codex and one system. The classes below are the seams through which the institution grows.
- The eight-question record0 entries
- 0. Institutional systems — `SYS-`12 entries
- 1. Divisions and offices — `DIV-`7 entries
- 2. CapabilityOS engines — `ENG-`11 entries
- 3. API boundaries — `API-`11 entries
- 4. Cross-division workflows — `WF-`7 entries
- 5. Canonical entities — `ENT-`19 entries
- 6. AI agents — `AGT-`14 entries
- 7. Dashboards — `DASH-`10 entries
- 8. Internal tooling — `TOOL-`11 entries
- 9.1 Institutional surfaces9 entries
- 9.2 Academy surfaces7 entries
- 9.3 Member surfaces (authenticated)5 entries
- 10. Revenue streams — `REV-`6 entries
- 10a. Financial and governance instruments — `FIN-` and `GOV-`11 entries