STD-F — The Financial Standard

Subordinate to Codex 1, Codex 0 Chapter 15, Chapter 16, and Codex 8. See 00-index.md for authority, vocabulary, citation, and waiver rules, which this Standard does not restate.

1. Purpose

1.1 This Standard converts Codex 8's financial doctrine and Codex 0 Chapter 15's financial architecture into obligations a reviewer who did not do the work can verify: allocation order, reserve protection, revenue recognition, pricing discipline, the seven-axis evaluation, unit economics, concentration limits, procurement, capitalisation, reporting cadence, conflicts of interest, and the prohibition list.

1.2 A financial decision is not conformant because it produced a good outcome. It is conformant because it was made in the order, with the artefacts, and under the limits this Standard states, and a second person can confirm that from the record.

2. Scope and non-scope

2.1 In scope: any decision that commits, recognises, prices, allocates, or reports institutional capital, and any proposal for a new or changed revenue stream, price, vendor commitment, or build-versus-buy choice.

2.2 Out of scope: the revenue architecture's descriptive content (streams, dependencies, risks — Codex 0 §15.3–15.9), the reporting philosophy and metric definitions (Codex 0 Chapter 16, governed by STD-Q's reporting-adjacent obligations only where a report is the work product), and the mechanics of any specific accounting or billing tool. This Standard states the obligations those systems and decisions must satisfy; it does not specify their implementation.

2.3 Applies to every division and office, every AI system proposing or evaluating financial decisions (subject also to STD-I), and every contributor with authority to price, commit spend, or recognise revenue.

3. Normative clauses

3.1 Allocation priority

3.1.1 Capital must be allocated in this fixed order and no other: (1) operating expenses, (2) operating reserve, (3) research, (4) technology, (5) education, (6) innovation, (7) strategic investments, (8) institutional endowment (Codex 8, Article V; Codex 0 §15.12). This order is a hard institutional rule; no Standard, Codex, waiver, or emergency declaration may reorder it.

3.1.2 A funding proposal that allocates to a later category while an earlier category has a recorded unmet need must be rejected at proposal review, not corrected after funding.

3.1.3 Conformance is checked by inspecting the funding proposal's recorded allocation trace against the order in §3.1.1; the trace must name, for each category funded, whether all prior categories were satisfied first, or were explicitly deferred with a plan, an owner, and a date.

3.1.4 A single opportunity's apparent size or urgency must not be cited to justify reordering §3.1.1. A proposal that argues this must be rejected on that argument alone.

3.1.5 Strategic investments (category 7) must not be funded from the reserve (§3.2.2) nor against expected revenue (§3.8.2), and require Board approval and Stewardship Office assent (Codex 9, Article II). A draw against endowment principal (category 8) carries the review weight of §3.2.3 and additionally requires Board confirmation.

3.1.6 A proposal must state, for each allocation, at least one of the seven forms of capital it increases (Codex 8, Article III). An allocation naming none is expenditure, not strategy, and is refused at proposal review.

3.2 The reserve

3.2.1 The reserve is expressed in months of operating cost and its current floor value must be a matter of record, visible to the Executive Office and the Stewardship Office at all times.

3.2.2 The reserve must never be drawn for growth, expansion, or any new revenue stream's initial cost. A draw request citing an expansion purpose must be refused at the request stage.

3.2.3 The reserve floor may be lowered only by the Stewardship Office, in writing. The Executive Office may raise it unilaterally. A floor change without a Stewardship Office written record, where the change is a lowering, is non-conformant regardless of who executed it.

3.2.4 Any draw that takes the reserve below its floor is itself a Stewardship Office-reviewable event, carrying the same review weight as a proposed floor reduction (Codex 0 §15.11.5). Conformance is checked by confirming a Stewardship Office review record exists dated at or before the draw, not after.

3.2.5 Reserve adequacy (current months covered) must be reported at the cadence in §3.10 and included in the annual report without exception.

3.3 Revenue recognition discipline

3.3.1 Revenue must be recognised only when delivery has occurred, per the class-specific rule below. A reviewer checks recognition by matching a recognised revenue line to a recorded delivery event, not to an invoice or a signed contract alone.

3.3.2 Memberships, subscriptions, retainers, coaching, platform licensing, SaaS, AI services, APIs, automation, institutional licences, publishing subscriptions, reports (subscription form): recognised ratably over the service period actually delivered, never in full at the point of sale or renewal.

3.3.3 Certifications: recognised at the point the credential is issued following a completed, unmodified assessment (Codex 0 §15.13.3), never at enrolment or payment.

3.3.4 Corporate and executive education, cohort and program delivery: recognised as sessions or milestones are delivered against the contracted scope, not on contract signature.

3.3.5 Consulting, advisory engagements, fractional leadership: recognised against delivered engagement milestones stated in the engagement scope, never on retainer receipt alone where the retainer funds future, undelivered work.

3.3.6 Licensing (research index, data, IP), revenue share, equity, capital network economics: recognised only on realized value (executed licence period elapsed, exit, dividend, or distribution actually received). Unrealized paper valuation must never be recognised as revenue (Codex 0 §15.7.6, §15.19.5).

3.3.7 Incubator, accelerator, studio participation economics: recognised on the same realized-value basis as §3.3.6; any near-term fee component (e.g., program fee distinct from equity) follows §3.3.4.

3.3.8 Speaking, one-off reports, project-based research: recognised on delivery of the named deliverable, not on booking.

3.3.9 A revenue class's registry or reporting entry must state its recognition basis in the terms of §3.3.2–3.3.8; an entry that states a more favourable (more front-loaded) basis than its actual delivery structure supports is non-conformant on its face (Codex 0 §15.9.2).

3.4 Pricing discipline

3.4.1 A price must not depend on a dark pattern to remain viable. Conformance is checked against the STD-X-governed interaction audit and the Codex 6 Rubric prohibited-pattern list (manufactured urgency, obstructed cancellation, loss-framed nudges, and the like); a price whose retention rate is shown to depend on any of these fails this clause regardless of revenue performance.

3.4.2 No penalty pricing on exit. A cancelling member or client must not be charged a fee, forfeiture, or rate change triggered by the act of leaving, beyond the ordinary unwinding of a usage-based charge already incurred.

3.4.3 Cancellation and refund terms must be published, in plain language, at the point of sale, and must be locatable by a current customer without contacting support. A reviewer checks this by finding the published terms independently, without asking the author where they are.

3.4.4 A price change must be communicated in advance of its effective date, with a stated effective date, and must never be applied retroactively to a commitment already made (Codex 0 §15.13.4). The minimum notice period for a recurring-revenue price increase is 30 days; for an enterprise or contracted stream it is the notice period stated in the contract or 30 days, whichever is longer.

3.4.5 Cancellation of any recurring stream must require no more effort than enrollment did (Codex 0 §15.13.2). Conformance is checked by a reviewer independently completing the cancellation flow and counting the steps against the enrollment flow's step count.

3.5 The seven-axis evaluation

3.5.1 No new revenue stream, priced feature, or material pricing change proceeds to commitment without a written seven-axis evaluation attached to its proposal or registry entry: revenue potential, implementation cost, maintenance cost, operational complexity, customer value, enterprise value, long-term strategic value (Codex 8; Codex 0 §15.15).

3.5.2 Each axis must be answered specifically, in writing. An axis marked "n/a" without a stated reason, or answered in a single vague sentence, is treated as unanswered, and the evaluation is treated as absent (Codex 0 §15.15.3).

3.5.3 Conformance is checked by confirming the evaluation exists, predates the commitment (approval or funding date), and is attached to the record a future reviewer will find — not reconstructed retroactively.

3.5.4 An evaluation is revisited, and a fresh written comparison recorded, when actual cost or value diverges materially from the original evaluation's projection (Codex 0 §15.15.5).

3.6 Unit economics before scaling

3.6.1 Before any revenue stream, product, or feature is scaled beyond its initial cohort, pilot, or client set, a written unit-economics statement must exist recording: marginal cost per additional unit, current gross margin at pilot scale, and the shape of cost as volume grows (favourable, flat, or unfavourable).

3.6.2 A stream whose unit economics are unfavourable at scale (cost grows with or faster than volume) must not be scaled on the strength of top-line revenue growth alone; the scaling proposal must name the mitigation or the ceiling at which scaling stops.

3.6.3 Conformance is checked by finding the unit-economics statement dated before the scaling decision, and confirming the scaling decision's proposal references it.

3.7 Concentration limits

3.7.1 No single revenue stream may exceed the materiality threshold set by the Executive Office and reviewed by the Stewardship Office without a recorded diversification plan naming the target share, the timeline, and the owner (Codex 0 §15.10.1).

3.7.2 No single client, enterprise account, partner institution, or sponsor may exceed its reviewed materiality threshold without the same recorded diversification plan (Codex 0 §15.10.2). Breach triggers the plan; it is not resolved by a one-time waiver.

3.7.3 A client or vendor that is small in revenue share but structurally difficult to replace (sole channel, sole model provider, sole data source) must be assessed as concentrated by dependency depth even where its revenue share is below threshold (Codex 0 §15.10.3–15.10.4).

3.7.4 Conformance is checked quarterly by comparing each stream's and each client's current share against its threshold in the concentration exposure report (Codex 0 §16.3, "Concentration exposure").

3.8 Procurement and vendor commitment

3.8.1 A recurring vendor or platform commitment must not be entered without a written exit-cost assessment: cost and time to migrate off the vendor, data portability, and contractual termination terms.

3.8.2 A vendor commitment must not be funded against expected future revenue; it is funded against revenue already recurring and earned (Codex 8 rule 4; Codex 0 §15.14.2).

3.8.3 Vendor and model-provider concentration is reviewed under §3.7's discipline, not as a separate lesser standard (Codex 0 §15.10.4).

3.8.4 Conformance is checked by locating the exit-cost assessment in the procurement record before the contract's execution date.

3.9 Capitalisation versus expense

3.9.1 Build work is capitalised only where it produces a durable, reusable asset (a shared engine, a platform capability, a licensable system) with a stated useful life; work that produces a one-off, non-reusable deliverable for a single client is expensed against that engagement.

3.9.2 A capitalisation decision must be recorded at the time the work is proposed, stating the useful life assumed and the reusing consumers expected, not decided retroactively to improve a reporting period's appearance.

3.9.3 Where a cheaper, less complete build is chosen over a fuller one, the trade is named in writing: what was given up and what repays it (Codex 8 rule 5; Codex 0 §15.14.4). This is the financial-side instance of the named-debt rule that STD-Q §7 governs generally.

3.10 Financial reporting cadence and contents

3.10.1 Financial reporting follows the cadence fixed in Codex 0 §16.6: weekly operational figures held internally; monthly divisional figures to the division lead and Executive Office; quarterly institutional figures (reserve adequacy, concentration exposure, commitment-kept rate) to the Executive Office and Stewardship Office; annual figures published per Codex 0 §16.5.

3.10.2 Every financial report at every cadence states, for each figure: the period covered, the definition applied, and whether it is realized or projected. A figure without these three is not a report (Codex 0 §16.3.3).

3.10.3 The annual report's financial section must include reserve adequacy, any concentration breach, and — where applicable — a named account of any reserve draw-down below floor, in the same unsoftened terms Codex 0 §16.5.2.1(4) requires of capability metrics.

3.11 Conflict of interest and related-party rules

3.11.1 A related-party transaction (a vendor, client, or counterparty in which a decision-maker or their immediate family holds a financial interest) must be disclosed in writing before the commitment is made, not after.

3.11.2 A person with a disclosed related-party interest must not be the sole approver of that transaction; a second, disinterested approver must sign.

3.11.3 A conflict of interest touching reserves, pricing of a member-facing product, or a credential-adjacent transaction requires Stewardship Office assent, per the waivers-and-assent rule in 00-index.md §4.4.

3.11.4 Conformance is checked by finding the disclosure record dated before the transaction and the second approver's signature on it.

3.12 The prohibition list

3.12.1 No sale, rental, or brokerage of member data under any revenue stream, packaging, or euphemism.

3.12.2 No engagement-driven revenue: no pricing or compensation structure that rewards time-on-platform, session count, or attention capture rather than delivered capability or delivered service.

3.12.3 No revenue recognised before delivery, per the class rules of §3.3.

3.12.4 No obstructed cancellation: no flow, fee, dark pattern, or required contact-support step inserted to suppress a cancellation that could otherwise be self-served (§3.4.5).

3.12.5 No hidden fees: every charge a customer will incur must appear before the point of payment, not disclosed for the first time on an invoice or statement.

3.12.6 A single instance of any clause in §3.12 blocks the work regardless of its revenue contribution, and may not be waived (00-index.md §4.1).

3.13 Treasury and endowment

3.13.1 The Treasury must be managed for liquidity, capital preservation, operational continuity, and risk management, in that order (Codex 8, Article VI). Any position taken for return beyond those four objectives requires a written investment policy approved by the Board (Codex 9, Article II).

3.13.2 Treasury and endowment positions must be reported at realized value. Unrealized gain must never be recognised as revenue (§3.3.6), counted toward reserve adequacy above cost, or cited as capacity to fund an allocation category.

3.13.3 Endowment principal must not be treated as an operating resource. A draw against principal requires a Stewardship Office written record and Board confirmation, both dated at or before the draw, and must be named in the following annual report.

3.13.4 The Endowment must never be drawn, or its accounting altered, to conceal an operating deficit. Conformance is checked by confirming the operating result is reported independently of any endowment movement in the same period.

3.14 The Impact Ledger

3.14.1 The financial report and the capability report must be published together, in the same publication, for the same period (Codex 8, Article XII; Codex 0 §16.5). Publishing either alone is non-conformant.

3.14.2 Conformance is checked by confirming both reports exist in the published annual report and that neither was withheld, deferred, or summarised in place of the other.

4. Governing Codex clauses

4.1 Codex 8 — The Financial Doctrine, in full: Articles I–XII, particularly the seven forms of capital (III), the five revenue engines (IV), the allocation path (V), treasury policy (VI), the endowment (VII), the capital network (X), the Impact Ledger (XII), "never monetize trust," and the seven-axis evaluation.

4.2 Codex 0 Chapter 15 — the six revenue streams (REV-01..REV-06), diversification limits (§15.10), reserve policy (§15.11), reinvestment order (§15.12), pricing doctrine (§15.13), cost discipline (§15.14), the seven-axis evaluation (§15.15), and what is never monetized (§15.16).

4.3 Codex 0 Chapter 16 §16.3 (institutional metric set, including reserve adequacy and concentration exposure) and §16.5 (annual report mandatory contents), for the reporting obligations this Standard cites rather than restates.

4.4 Codex 9 — The Governance Doctrine, Article II (decision rights over treasury, endowment, and strategic investments), Article IV (emergency powers may not reorder allocation), and Article VII (conflict of interest).

4.5 Codex 1, Article VI (non-negotiables: no dark patterns, no data sale, credential integrity), which this Standard's pricing and prohibition clauses bind into financial practice specifically.

5. Conformance checklist

• [ ] The funding decision's allocation trace matches the order in §3.1.1, with each prior category's need stated as met or explicitly deferred with a plan. (yes/no/n-a-because)
• [ ] No reserve draw was made for growth or expansion purposes. (yes/no/n-a-because)
• [ ] Any reserve floor lowering carries a Stewardship Office written record. (yes/no/n-a-because)
• [ ] Any draw below floor carries a dated Stewardship Office review. (yes/no/n-a-because)
• [ ] The revenue's recognition basis matches its class rule in §3.3 and is stated in its registry or reporting entry. (yes/no/n-a-because)
• [ ] No price depends on a dark pattern verified against the Codex 6 Rubric prohibited list. (yes/no/n-a-because)
• [ ] No exit penalty exists; cancellation and refund terms are published and independently locatable. (yes/no/n-a-because)
• [ ] Any price increase carries advance notice meeting or exceeding the stated minimum, with no retroactive application. (yes/no/n-a-because)
• [ ] A written seven-axis evaluation exists, predates commitment, and every axis is answered specifically. (yes/no/n-a-because)
• [ ] A unit-economics statement exists and predates any scaling decision. (yes/no/n-a-because)
• [ ] Stream and client concentration are within threshold, or a diversification plan with owner and timeline is recorded. (yes/no/n-a-because)
• [ ] Any recurring vendor commitment carries a written exit-cost assessment predating execution. (yes/no/n-a-because)
• [ ] Capitalised work states its useful life and expected reusing consumers at proposal time. (yes/no/n-a-because)
• [ ] Any cheaper-build trade is named in writing with what repays it. (yes/no/n-a-because)
• [ ] Financial reports at every cadence state period, definition, and realized-versus-projected status for each figure. (yes/no/n-a-because)
• [ ] Any related-party transaction carries a dated disclosure and a disinterested second approver. (yes/no/n-a-because)
• [ ] No item on the §3.12 prohibition list is present. (yes/no/n-a-because)
• [ ] Each allocation names at least one of the seven forms of capital it increases. (yes/no/n-a-because)
• [ ] Any strategic investment carries Board approval and Stewardship Office assent, and was not funded from reserve or expected revenue. (yes/no/n-a-because)
• [ ] Treasury and endowment positions are reported at realized value only. (yes/no/n-a-because)
• [ ] Any endowment principal draw carries a dated Stewardship Office record and Board confirmation. (yes/no/n-a-because)
• [ ] The financial report and capability report were published together as the Impact Ledger. (yes/no/n-a-because)

6. Interfaces to other Standards

6.1 STD-Q — a financial or pricing change's definition of done (STD-Q §5, work class "financial or pricing change") requires this Standard's checklist as a precondition to sign-off.

6.2 STD-X — pricing surfaces and cancellation flows are also scored under the Codex 6 Rubric for dark-pattern and interaction defects; §3.4.1 and §3.4.5 depend on that scoring.

6.3 STD-D — money and time representation in any schema recognising revenue (§3.3) follows STD-D's data-modelling rules for currency, precision, and period boundaries.

6.4 STD-I — an AI system proposing a price, evaluating a revenue stream, or drafting a seven-axis evaluation is bound by STD-I's human-checkpoint rule; the evaluation's approval is never delegated to the AI that drafted it.

6.5 STD-R — sponsored research revenue (§3.3.6, §3.3.8) is additionally bound by STD-R's editorial-independence rules where a sponsor funds a finding.

7. Open questions

7.1 The numeric materiality thresholds for stream and client concentration (§3.7) are set by the Executive Office and reviewed by the Stewardship Office; this Standard binds the process, not a specific number, pending Codex 0 §15.20.1's resolution.

7.2 The reserve floor's initial value in months of operating cost is pending the Executive Office's first published operating budget (Codex 0 §15.20.2); this Standard's obligations bind regardless of the floor's numeric value.

7.3 Whether REV-06-style platform licensing requires a distinct capitalisation treatment beyond §3.9's general rule is open pending the first partner-institution licensing proposal.