Codex 0 · Chapter 02 — The Five Divisions
Chapter 02 of the institutional specification.
- Authority rank
- 2
- Version
- v2.0
- Adopted
- unrecorded
- Held by
- Stewardship Office
- System
- SYS-11
Source · docs/codices/CODEX-0/02-divisions.md · registered by rule
Specifies each operating division: mandate, products, inputs, declared interfaces, operating cadence, capacity model, failure modes, and the rule against duplication.
02.0 Purpose
To make ownership unambiguous. Every piece of work belongs to exactly one division. This chapter is the authority on which one, and on how work crosses a division line without either side reaching into the other.
02.1 Scope and non-scope
In scope. DIV-01 through DIV-05, their interfaces to each other, cadence, capacity, and failure modes.
Not in scope. The two offices (Chapter 03), engine internals (Chapter 05), workflow stages (Chapter 09), contract shapes (Chapter 10).
02.2 The division model
02.2.1 One owner
Every system, surface, entity, workflow stage, and revenue stream has exactly one owning division, recorded in the Registry. Shared ownership is not permitted; shared use is normal and happens through a declared interface.
02.2.2 Interfaces, not access
A division consumes another division's capability through a named API boundary (Chapter 10). No division reads another division's storage, imports its internal modules, or depends on its private data shapes.
02.2.3 The rule against duplication
Where two divisions need the same capability, it moves to DIV-05 Technology as a shared engine and both consume it. Building a second implementation is a defect, not a trade-off, and is refused at Registry entry.
02.2.4 Interface ownership
Each division names an interface owner accountable for the stability of the boundaries it publishes and for the migration of consumers when a boundary versions.
02.2.5 Division registry
A sixth division may be created without touching the other five: it takes a DIV- ID, declares mandate, products, inputs, boundaries, cadence, and capacity, and consumes CapabilityOS unchanged (§18).
02.3 DIV-01 Academy — the teaching division
Status. partial — the most developed division: seven schools, deep curriculum trees, an authenticated Scholar area.
02.3.1 Mandate
Cultivate individual capability through structured, assessed, lifelong education. The Academy is the division that turns knowledge into demonstrated capability.
02.3.2 Produces
| Product | Entity | Boundary |
|---|---|---|
| Curriculum: schools, programs, courses, modules, lessons | ENT-09 | API-03 |
| Enrolments and cohorts | ENT-10, ENT-11 | API-03 |
| Submitted work | ENT-17 | API-04 |
| Capability assessments | ENT-07 | API-04 |
| Credentials and their public verification | ENT-08 | API-05 |
| Faculty judgement and review records | ENT-17, ENT-19 | API-04 |
| Alumni and mentor eligibility | ENT-05 | API-02 |
02.3.3 Consumes
Research findings and the capability taxonomy (DIV-03, API-07, ENT-06); anonymized practice cases (DIV-02); founder capability needs (DIV-04); CapabilityOS engines ENG-01, ENG-02, ENG-03 and all platform boundaries (DIV-05).
02.3.4 Cadence
Curriculum is versioned, not edited in place. Cohorts run on a published calendar. Assessment turnaround is a published commitment. Credential standards are reviewed annually and changed only forward, never retroactively against issued credentials (§09).
02.3.5 Capacity model
The binding constraint is human review capacity, not content volume. Capacity is expressed as reviewable submissions per faculty member per period. Growth in enrolment without a matching growth in review capacity degrades credential integrity and is refused (§18).
02.3.6 Failure modes
| Failure | Consequence | Guard |
|---|---|---|
| Assessment softened to raise completion | credential meaning collapses | Codex 1 Art. VI(7); standard-setting separated from issuance (§08) |
| Curriculum outgrows review capacity | backlog, then silent auto-passing | capacity ceiling in §02.3.5 |
| Content authored in code only | no authoring tool, no versioning discipline | TOOL-01 named as reserved debt (§14) |
| Credential revoked without record | trust loss, no recourse | reversal path in §09 |
02.4 DIV-02 Advisory — the applied division
Status. reserved.
02.4.1 Mandate
Apply institutional capability inside real organizations and to individual executives, and return what is learned to the institution.
02.4.2 Produces
Engagements (ENT-12), organizational diagnostics, coaching relationships, implementation programs, and anonymized practice cases contributed to Academy and Research.
02.4.3 Consumes
Credentialed people to staff engagements (DIV-01, API-05); research to ground recommendations (DIV-03, API-07); ENG-08 Business and ENG-10 Advisory; delivery tooling TOOL-07.
02.4.4 Cadence
Engagements are time-bounded with recorded commitments, a risk register, and a closing outcome record. Anonymization of a case precedes any teaching or publication use, and requires client consent on the record.
02.4.5 Capacity model
Constrained by qualified advisor availability. An engagement may not be accepted without a named accountable advisor whose committed capacity is recorded.
02.4.6 Failure modes
Client concentration beyond the materiality threshold (§15); advisory recommendation presented as research finding; identifiable client material entering curriculum; advisory judgement substituted by an agent (§13).
02.5 DIV-03 Research Institute — the knowing division
Status. partial — public research and journal surfaces exist as editorial content; the pipeline and indexes are reserved.
02.5.1 Mandate
Produce durable knowledge: publications, indexes, analysis, the capability taxonomy, and the measurement methodology the institution reports against.
02.5.2 Produces
Publications (ENT-13), indexes and their versioned values (ENT-14), the capability taxonomy (ENT-06), methodology of record, and the analytical content of the annual report.
02.5.3 Consumes
Anonymized outcome data from DIV-01, DIV-02, DIV-04; external licensed sources; ENG-09 Research; ENG-01 Knowledge Graph.
02.5.4 Cadence
Question → registered methodology → sources → draft → editorial review → publication → graph linkage. Indexes publish on a stated schedule with a published correction procedure (§16).
02.5.5 Capacity model
Constrained by editorial review capacity. Unreviewed drafts are never published, and no publication date is committed before review capacity is allocated.
02.5.6 Failure modes
Publication without registered methodology; index revised silently instead of versioned; taxonomy changed without curriculum and credential impact review; sponsored research shaping conclusions rather than questions.
02.6 DIV-04 Ventures — the building division
Status. reserved — ecosystem and institutions surfaces exist as editorial content only.
02.6.1 Mandate
Develop founders and build enterprises that extend human capability, and connect them to capital.
02.6.2 Produces
Ventures (ENT-15), investments (ENT-16), founder development programs, the capital network, investor reporting, and the alumni founder community.
02.6.3 Consumes
Academy graduates and their credentials (API-05); advisory expertise (DIV-02); market and technology analysis (DIV-03); ENG-11 Venture, ENG-08 Business.
02.6.4 Cadence
Intake windows, a milestone cadence per venture, investment readiness reviews, and periodic investor reporting on a stated schedule.
02.6.5 Capacity model
Constrained by studio and mentor capacity per cohort, and by capital committed. Venture count never exceeds the mentor capacity recorded for the period.
02.6.6 Failure modes
Conflict of interest between institutional advice and institutional equity; founder selection drifting toward fundability over capability; investor reporting obligations exceeding reporting capability; venture failure treated as reputational risk rather than published learning.
02.7 DIV-05 Technology — the enabling division
Status. partial — identity, curriculum delivery, and progress exist; the engine set and boundaries are largely reserved.
02.7.1 Mandate
Build and operate CapabilityOS and everything the institution runs on, and hold the shared data model, permissions, reporting, and audit.
02.7.2 Produces
ENG-01..ENG-11; the shared entities of Chapter 07; API-01, API-02, API-09, API-10, API-11; internal tooling platform; the security, reliability, and accessibility posture.
02.7.3 Consumes
Requirements from every division, through named interface owners; doctrine from the Codices.
02.7.4 Cadence
Boundaries are stabilised before consumers integrate (§10). Changes ship behind versioned contracts. Access review, security review, and dependency review run on a stated periodic schedule (§16).
02.7.5 Capacity model
Constrained by engineering capacity and by the maintenance load of everything already shipped. New systems are costed on ten-year maintenance, not build (§15).
02.7.6 Failure modes
A division building around a boundary instead of waiting for it; unversioned breaking change; privileged tooling path around doctrine (§14); peripheral engine failure taking down the core (§17); accumulating unnamed debt.
02.8 Inter-division flows
| From → To | What flows | Through | Status |
|---|---|---|---|
| DIV-03 → DIV-01 | findings become curriculum | API-07, ENG-01, WF-03 | reserved |
| DIV-01 → DIV-02 | credentialed people staff engagements | API-05, WF-02 | reserved |
| DIV-02 → DIV-01 | anonymized real cases become teaching material | case contribution pipeline | reserved |
| DIV-02 → DIV-03 | field evidence | anonymized outcome feed | reserved |
| DIV-01 → DIV-04 | graduates enter founder development | WF-04 intake | reserved |
| DIV-04 → DIV-01 | founder needs shape curriculum | curriculum request pipeline | reserved |
| DIV-04 → DIV-03 | venture outcome data | anonymized outcome feed | reserved |
| DIV-03 → DIV-04 | market and technology analysis | API-07 | reserved |
| DIV-05 → all | engines, graph, dashboards, boundaries | Chapter 10 | partial |
| all → DIV-05 | requirements | interface owners (§02.2.4) | partial |
| all → DIV-07 | trust and commitment metrics | API-10 | reserved |
Each flow crosses one boundary, carries entities named in Chapter 07, and emits an audit record where it changes a person's standing (§09).
02.9 Interfaces
DIV-01: API-03, API-04, API-05. DIV-02: API-06. DIV-03: API-07. DIV-04: API-08. DIV-05: API-01, API-02, API-09, API-10, API-11. All divisions consume ENG-01..ENG-11 and none forks them (§05.2).
02.10 Invariants
- 1Exactly one owning division per Registry entry.
- 2No division reads another's storage or private modules.
- 3Duplication resolves upward into DIV-05, never sideways into a second build.
- 4A division's committed cadence is a public commitment and is reported against (§16).
- 5Capacity ceilings bind growth; enrolment, engagement, and venture counts never exceed recorded human capacity.
02.11 Prohibitions
- 1A division-private user table, role store, or Person record.
- 2Direct database access across a division line.
- 3Accepting work a division has no capacity to review or deliver.
- 4Presenting one division's output in another's register — advisory opinion as research, marketing copy as doctrine.
- 5Creating a new division to escape an existing division's constraints.
02.12 Open questions
- 1Advisory and Ventures conflict policy. Whether the institution may advise an organization it holds equity in, and under what disclosure, is undecided (§02.6.6).
- 2Case anonymization standard. The threshold at which an advisory case is genuinely non-identifying is unspecified (Chapter 16 aggregation thresholds are related but not sufficient).
- 3Faculty employment model. Whether faculty are employees, fellows, or credentialed contractors affects §02.3.5 capacity and Chapter 04 roles.
02.13 Governing Codices
Codex 2 (divisions), Codex 3 (shared engines), Codex 5 (boundaries), Codex 8 (capacity and cost), Codex 9 (ownership disputes).