Codex 2 — The Divisions

Five operating divisions, two offices. Every piece of work belongs to exactly one division and may serve others through declared interfaces.

I. Academy — the teaching division

Purpose. Cultivate capability through structured, assessed, lifelong education.

Produces. Curriculum, lessons, assessments, credentials, cohorts, faculty judgment, alumni. Consumes. Research findings (from the Research Institute), practice cases (Advisory), founder needs (Ventures), platform engines (Technology). Interfaces. Curriculum API, credential issuance, cohort enrolment, capability assessment feed. Current state. The most developed division: seven schools, deep curriculum trees, a Scholar area.

II. Advisory — the applied division

Purpose. Apply institutional knowledge inside real organizations.

Produces. Engagements, diagnostics, executive coaching relationships, implementation programs, anonymized practice cases. Consumes. Academy credentials (to staff engagements), research (to ground recommendations), Technology (delivery tooling). Interfaces. Engagement lifecycle API, advisor directory, client workspace, case contribution pipeline.

III. Research Institute — the knowing division

Purpose. Produce durable knowledge: publications, indexes, analysis, the annual report.

Produces. White papers, indexes, economic and technology analysis, capability measurement methodology. Consumes. Anonymized outcome data (Academy, Advisory), venture data, external sources. Interfaces. Publication API, index API, methodology registry, editorial pipeline.

IV. Ventures — the building division

Purpose. Develop founders and build enterprises that extend capability.

Produces. Incubated and accelerated companies, venture studio builds, the capital network, the investor portal, the alumni network. Consumes. Academy graduates, advisory expertise, research on market conditions. Interfaces. Founder intake, venture record, capital network directory, investor reporting.

V. Technology — the enabling division

Purpose. Build and operate CapabilityOS and everything the institution runs on.

Produces. CapabilityOS engines, the knowledge graph, dashboards, APIs, automation, internal tooling, security and reliability posture. Consumes. Requirements from every division; doctrine from the Codices. Interfaces. Every internal API boundary in Codex 5.

The Executive Office

Runs the institution day to day. Sets priorities, allocates capital and people, owns targets, and decides between options the Codices permit. It cannot amend doctrine.

The Stewardship Office

Guards the institution across generations. Holds the Codices, records amendments, and reviews any proposal that touches mission, member trust, data use, credential integrity, or reserves. Its power is a veto and a written record — not day-to-day management.

                 Stewardship Office  (guards doctrine, veto)
                          |
                  Executive Office   (runs the institution)
                          |
  +---------+---------+---------+---------+---------+
  | Academy | Advisory| Research| Ventures| Technology
  +---------+---------+---------+---------+---------+
                          |
                    CapabilityOS
              (shared engines + knowledge graph)

Rule against duplication

No division may build a capability another division already owns. Where two divisions need the same thing, it belongs to Technology as a shared engine, consumed through an interface.