Codex 0 · Chapter 15 — The Financial Architecture
Chapter 15 of the institutional specification.
- Authority rank
- 2
- Version
- v2.0
- Adopted
- unrecorded
- Held by
- Stewardship Office
- System
- SYS-05
Source · docs/codices/CODEX-0/15-finance.md · registered by rule
This chapter specifies how Anabasis earns, allocates, and protects capital so that money remains a means of institutional independence and never becomes the mission's substitute.
15.0 Purpose
15.0.1 Capital exists to sustain and extend the mission (Codex 8). This chapter makes that purpose architectural: it specifies the six revenue streams by ID, the limits that prevent any one of them from controlling the institution, the reserve policy, the reinvestment order, pricing doctrine, cost discipline, the mandatory feature-evaluation artefact, and what is permanently outside the market.
15.0.2 An institution designed to operate for a hundred years (Codex 1, Article VII) cannot depend on a single customer, product, or funder. This chapter is the architecture of that independence.
15.1 Scope and non-scope
15.1.1 In scope: purpose of capital, REV-01..REV-06 in full, diversification and concentration limits, reserve policy, reinvestment order, pricing doctrine, cost discipline, the seven-axis feature evaluation, and non-monetizable domains.
15.1.2 Out of scope: annual reporting format and capability metrics (Chapter 16), the internal tooling used to run finance operations (Chapter 14, TOOL-10), and governance procedure for amending reserve floors (Codex 9). This chapter states the rules those systems execute and report against.
15.1.3 Applies to every revenue-generating or cost-incurring decision across all five divisions and both offices.
15.2 Purpose of capital
15.2.1 Revenue is a means of institutional independence. An institution that depends on a single customer, product, or funder is not free to hold its principles when that dependency is threatened (Codex 8).
15.2.2 Capital is never the measure of the institution's success. The measure is the positive difference made in people's lives (Codex 8, "the measure of success"). Financial results are reported alongside, never instead of, capability outcomes (Chapter 16 §16.2).
15.2.3 A financial decision that improves the current year at the cost of the institution's tenth year is rejected on its face, regardless of its size (Codex 8, rule 7).
15.3 The revenue architecture
15.3 REV-01 — Individual membership and tuition
15.3.1 What is sold. Access to Academy curriculum, credentialing pathways, and membership-tier capability tools.
15.3.2 To whom. Individual members and scholars (Codex 4 user types), self-enrolled through SURF-15.
15.3.3 Recurrence. Recurring (subscription or term-based membership), the institution's most direct claim to independence because it does not depend on any single institutional counterparty.
15.3.4 Unit economics shape. Low marginal cost per additional member once curriculum exists; the shape favours scale, provided curriculum quality and assessment integrity are not diluted to serve volume (Codex 1, Article VI.7).
15.3.5 Dependencies. SURF-15 intake, API-04 Progress & Assessment, TOOL-04 Admissions.
15.3.6 Risks. Price sensitivity at scale; the temptation to soften assessment to reduce churn (prohibited absolutely, Codex 1, Article VI.7); support-cost growth outpacing membership growth if tooling lags.
15.4 REV-02 — Enterprise cohorts and programs
15.4.1 What is sold. Contracted delivery of Academy curriculum and diagnostics to a client organization's employees or members, as a cohort.
15.4.2 To whom. Enterprise clients and partner institutions (universities, governments), via Codex 4's Organization and Partner membership types.
15.4.3 Recurrence. Contracted recurring, typically multi-year, renewed on demonstrated capability movement rather than automatically.
15.4.4 Unit economics shape. Higher per-contract revenue with higher delivery and account-management cost; margins depend on reusing existing curriculum rather than bespoke authoring per client.
15.4.5 Dependencies. WF-05 (enterprise client to cohort), TOOL-09 Partner & Enterprise Console, API-03/06/10.
15.4.6 Risks. Client concentration (governed by §15.4 limits below); scope creep into bespoke, non-reusable delivery that erodes the unit-economics shape; procurement and security-review cycles lengthening sales timelines.
15.5 REV-03 — Advisory engagements
15.5.1 What is sold. Consulting, executive coaching, and enterprise advisory delivered by credentialed Advisors, staffed from the Academy-to-Advisory pipeline (WF-02).
15.5.2 To whom. Organizations and executives (Enterprise client, Organization).
15.5.3 Recurrence. Project and retainer; less recurring by nature than REV-01/02, which is why diversification against it matters (§15.7).
15.5.4 Unit economics shape. Labour-intensive, margin tied directly to advisor utilization and engagement scope discipline; does not scale by volume alone.
15.5.5 Dependencies. WF-02, TOOL-07 Engagement Management, API-06.
15.5.6 Risks. Revenue volatility tied to engagement pipeline; advisor capacity constraints; reputational exposure if engagement commitments are not tracked and honoured (DASH-04).
15.6 REV-04 — Research subscriptions and indexes
15.6.1 What is sold. Access to publications, sponsored research findings, and licensed index data.
15.6.2 To whom. Institutional subscribers, sponsors, and organizations licensing index data for their own use.
15.6.3 Recurrence. Recurring (subscription and licensing), with occasional project-based sponsored research.
15.6.4 Unit economics shape. High fixed cost to produce rigorous research and maintain index methodology; low marginal cost to distribute once produced — a compounding system per Codex 8's preference.
15.6.5 Dependencies. API-07 Publication & Index, TOOL-05 Editorial Pipeline, TOOL-06 Index Management.
15.6.6 Risks. Sponsor influence compromising research independence (mitigated by editorial separation, Codex 3, Codex 7); index methodology drift undermining credibility if not versioned and published per Chapter 16 §16.3.
15.7 REV-05 — Venture equity and studio outcomes
15.7.1 What is sold. Equity stakes and studio participation economics from ventures built and capitalised through the Ventures division.
15.7.2 To whom. Not sold to a customer in the ordinary sense; realized through eventual venture outcomes (exit, dividend, or ongoing equity value) accruing to the institution and co-investors.
15.7.3 Recurrence. Long-horizon, non-recurring by nature — capital is committed for years before any return, if any materializes.
15.7.4 Unit economics shape. Power-law: most ventures return little or nothing, a few return disproportionately; must never be relied upon for operating cash flow (§15.6.5 below and Codex 8 rule 4).
15.7.5 Dependencies. WF-04 (founder intake to venture to capital), TOOL-08 Venture Pipeline, API-08.
15.7.6 Risks. Illiquidity; long feedback loops that obscure whether the venture program is working; the temptation to report unrealized paper value as if it were operating revenue (prohibited — Chapter 16 requires honesty about what is realized versus projected).
15.8 REV-06 — Licensing of CapabilityOS to partner institutions
15.8.1 What is sold. Licensed access to CapabilityOS engines and APIs for partner institutions to run their own capability programs on the institution's infrastructure.
15.8.2 To whom. Partner institutions (universities, governments, allied organizations) meeting the "third-party integration only through published API boundaries" expansion point (Codex 0 §15.6).
15.8.3 Recurrence. Recurring (platform licensing).
15.8.4 Unit economics shape. The most compounding of all six streams: each licensee amortizes CapabilityOS's fixed build cost further without materially increasing its own marginal cost, provided API boundaries are stable (Codex 5).
15.8.5 Dependencies. All of API-01..API-11, stabilised, per the registry's explicit gate ("recurring; depends on API-01..11 stabilised").
15.8.6 Risks. Cannot be sold before the underlying APIs are stable and versioned (Codex 5); premature licensing against an unstable boundary creates support burden that outweighs the revenue; multi-tenant data isolation must be airtight before any partner is onboarded.
15.9 Standing rules across all six streams
15.9.1 No stream is introduced without a seven-axis evaluation (§15.9 below) and a Codex 10 Institutional Critic review recorded in DECISIONS/ (Codex 0 Part II §10).
15.9.2 Every stream's registry entry states its recurrence class plainly; a stream may not be represented internally or externally as more recurring than its actual structure.
15.10 Diversification and concentration limits
15.10.1 No single division's revenue may be allowed to determine the institution's survival. The Executive Office sets a materiality threshold for maximum division share of total revenue and reviews it annually; the Stewardship Office reviews the threshold itself, not just compliance with it.
15.10.2 No single client (enterprise, partner institution, or sponsor) may exceed a materiality threshold set by the Executive Office and reviewed by the Stewardship Office. Breach of the threshold triggers a diversification plan, not a one-time waiver.
15.10.3 Concentration is assessed both by revenue share and by dependency depth — a client that is small in revenue but structurally hard to replace (e.g., sole distribution channel) is treated as concentrated even below the revenue threshold.
15.10.4 Vendor and model-provider concentration (Chapter 13 §13.11.4) and single-technology-platform concentration (Codex 7) are reviewed under the same discipline as customer concentration, because dependency on a critical supplier is symmetrical in risk to dependency on a critical customer.
15.10.5 The diversification requirement is a standing constraint on the Executive Office's capital allocation decisions (Codex 0 §3), not a one-time design goal met at founding and then ignored.
15.11 Reserve policy
15.11.1 A named operating reserve, expressed in months of operating cost, is maintained at all times. The reserve exists to let the institution honour its commitments — payroll, credential integrity, member service continuity — through a revenue shock without compromising doctrine under pressure.
15.11.2 The reserve floor is set by the Executive Office and may only be lowered by the Stewardship Office in writing (Codex 8 rule 3) — the Executive Office may raise it, but lowering it requires the higher authority's assent, because the reserve is a trust instrument as much as a financial one.
15.11.3 The reserve is never spent on growth. A funding need for expansion is met from surplus after the reserve floor is intact (§15.12), from dedicated capital raised for that purpose, or it is not met.
15.11.4 Reserve adequacy (current months of cost covered) is reported to the Stewardship Office on a fixed cadence and is part of the annual report's financial section (Chapter 16 §16.2).
15.11.5 A reserve draw-down below the floor is itself a Stewardship Office-reviewable event, triggering the same review weight as a proposed floor reduction.
15.12 The allocation path (reinvestment order)
15.12.1 Every dollar entering the institution follows one fixed path, never re-ordered for a single opportunity however attractive (Codex 8, Article V):
Revenue → Operating Expenses → Operating Reserve → Research → Technology →
Education → Innovation → Strategic Investments → Institutional Endowment15.12.2 Operating expenses. The cost of honouring existing commitments — payroll, delivery, security, service continuity — is met first. An institution that cannot keep today's promises has no standing to fund tomorrow's.
15.12.3 Operating reserve. Surplus restores or maintains the reserve floor (§15.11) before any discretionary category is funded.
15.12.4 Research, technology, education. These three constitute mission capacity: the capability that directly increases human capability development (Codex 1, Article II). They are funded in the stated order where they compete for the same surplus, and each records its unmet need where it is deferred.
15.12.5 Innovation. New programs, new engines, and new seams between divisions are funded only after mission capacity's recorded needs are met or explicitly deferred with a plan, an owner, and a date.
15.12.6 Strategic investments. External positions, acquisitions, capital-network participations, and partnerships requiring capital are funded only after Innovation, never from the reserve, and never against expected rather than earned revenue (§15.14.2). Each requires Board approval and Stewardship Office assent (Codex 9, Article II).
15.12.7 Institutional endowment. Surplus remaining after every category above flows to the Endowment (Codex 8, Article VII), whose principal is not an operating resource. A draw against principal carries the review weight of a reserve floor reduction and requires the Stewardship Office's written assent and Board confirmation.
15.12.8 A proposal to fund a later category while an earlier category has a recorded unmet need is refused at proposal review regardless of the later opportunity's apparent size or urgency, consistent with Codex 8, Article V. Reordering may not be authorised by emergency powers (Codex 9, Article IV.4).
15.12.9 The pre-2026 three-step order (reserve → mission capacity → expansion) is superseded by §15.12.1 and is a strict refinement of it, not a reversal: the same priorities remain, expressed at the granularity the allocation trace must now record (DECISIONS/0007).
15.13 Pricing doctrine
15.13.1 Legible pricing. A member or client can understand what they pay for, in plain terms, without needing to parse tiers designed to obscure true cost (Codex 8 rule 6).
15.13.2 Frictionless cancellation and export. Cancellation of any recurring stream (REV-01, REV-02, REV-04, REV-06) requires no more effort than enrollment did, and a departing member or client can export their own data (credentials, progress records, portfolio) in a usable form. Friction engineered into cancellation to suppress churn is a dark pattern and prohibited under Codex 1, Article VI.1.
15.13.3 No pay-to-pass credentials. A credential's issuance is never conditioned on payment beyond the ordinary cost of the program that led to it; nobody buys their way past an assessment standard. This restates and binds Codex 1, Article VI.7 into the pricing model specifically: price may gate access to instruction and support, never gate the truth of what a credential certifies.
15.13.4 Pricing changes are communicated in advance, with an effective date, never retroactively applied to a commitment already made to a member or client.
15.14 Cost discipline for engineering and operations
15.14.1 Engineering and operational cost decisions follow Codex 7's principles (modularity, build-once, configuration over custom code) as financial discipline, not only as code quality: a duplicated system built by a second division is a cost-discipline failure as much as an architecture failure (Codex 0 §2, "rule against duplication").
15.14.2 Recurring operational cost (hosting, vendor contracts, on-call staffing) is committed against recurring revenue already earned, never against expected future revenue (Codex 8 rule 4, "protect cash flow").
15.14.3 A feature or system that creates ongoing operational cost without meaningful strategic value, as determined by the seven-axis evaluation (§15.15), is refused outright rather than deferred to a future budget cycle where it quietly persists.
15.14.4 Where a cheaper implementation is deliberately chosen over a more complete one, the trade is named in writing: what was given up, and what future work repays it (Codex 7, "technical debt"; Codex 8 rule 5).
15.15 The seven-axis feature evaluation
15.15.1 Every feature or system proposal — in engineering, tooling, or a new revenue stream — records a written evaluation on seven axes before approval. This evaluation is a required artefact, not an optional justification; a proposal without it is not ready (Codex 8, "feature evaluation").
15.15.2 The seven axes and the question each answers:
| Axis | The question |
|---|---|
| Revenue potential | Does it earn, enable earning, or protect existing revenue? |
| Implementation cost | People and time to build it properly, not minimally. |
| Maintenance cost | What it costs to keep correct, secure, and current for ten years. |
| Operational complexity | New moving parts, vendors, on-call surface, human review load. |
| Customer value | What a member or client can now do that they could not before. |
| Enterprise value | Whether it survives procurement, security review, and reporting scope. |
| Long-term strategic value | What it makes possible in five years that is otherwise closed. |
15.15.3 An evaluation that cannot be written honestly — where an axis is skipped or answered vaguely to push a proposal through — is itself grounds for rejecting the proposal, independent of the axes' content.
15.15.4 The evaluation is attached to the proposal's registry entry or decision record so that a future reviewer can see what was known and weighed at approval time, not only the outcome.
15.15.5 Evaluations are revisited when a system's actual cost or value diverges materially from what was projected, feeding the annual accounting workflow (WF-07).
15.16 What is never monetized
15.16.1 Member data is never sold, rented, or brokered, under any packaging or euphemism (Codex 1, Article VI.2; Codex 8 rule 5).
15.16.2 Member attention is never sold or arbitraged — no advertising against member attention, no engagement-optimized feed monetized by a third party (Codex 8 rule 5).
15.16.3 Credential integrity is never for sale — no pay-to-pass, no softened assessment to raise completion or renewal figures (§15.13.3, Codex 1, Article VI.7).
15.16.4 Trust itself is never monetized: no practice that trades a member's or client's trust for growth is acceptable at any revenue level (Codex 8, "the measure of success").
15.16.5 Research independence is never for sale: a sponsor of REV-04 research may fund a question, never dictate a finding (§15.6.6, Codex 3).
15.17 Interfaces
15.17.1 Each REV- stream's dependencies name the WF-, API-, and TOOL- entries it relies on; a stream's registry entry is the authoritative interface list.
15.17.2 Reserve status, reinvestment allocation, and feature evaluations surface through TOOL-10 Reporting Studio (Chapter 14 §14.16) into the annual report (Chapter 16 §16.2).
15.18 Invariants
15.18.1 The reserve floor is never spent on growth and is lowered only by the Stewardship Office in writing.
15.18.2 Surplus is allocated in the fixed order: reserve, mission capacity, expansion.
15.18.3 No revenue stream launches without a seven-axis evaluation and a recorded Codex 10 review.
15.18.4 No single client or division exceeds its reviewed materiality threshold without triggering a diversification plan.
15.19 Prohibitions
15.19.1 No sale, rental, or brokerage of member data under any revenue stream.
15.19.2 No credential issuance conditioned on payment beyond the ordinary program cost.
15.19.3 No cancellation or data-export friction engineered to suppress churn.
15.19.4 No expansion funded ahead of an intact reserve floor or unmet mission-capacity need.
15.19.5 No unrealized venture value (REV-05) reported as if it were realized operating revenue.
15.20 Open questions
15.20.1 The exact numeric materiality thresholds for client and division concentration (§15.10) are reserved pending Executive Office proposal and Stewardship Office review.
15.20.2 The reserve floor's initial value in months of operating cost is reserved pending the Executive Office's first published operating budget.
15.20.3 Whether REV-06 licensing requires a distinct multi-tenant data-isolation review beyond the standing API-stability gate is open pending the first partner-institution proposal.
15.21 Governing Codices
15.21.1 Codex 8 (financial doctrine, source of the rules elaborated here). Codex 1, Article VI (non-negotiables on data, manipulation, credential integrity). Codex 9 (amendment procedure for reserve-floor changes and stream approval). Codex 10 (Institutional Critic review required before a new stream). Codex 0 Part II §10 (REV- registry). Chapter 16 of this Codex (financial reporting alongside capability outcomes).