Money movement with an audit trail a regulator could read.
For any organization whose money moves — settlement, reconciliation, compliance, reporting — and whose CFO needs every consequential action to carry a named human, a tier, and a record designed to be handed over.
Everything below — every role, purpose, measure and gate — is rendered from FINANCIAL_OS in @flashyos/aao at build time. This page cannot drift from the shipped template.
“Money movement with an audit trail a regulator could read.” — 5 standing responsibilities, each a role that outlives whoever holds it. Capabilities name actions, never departments; gates sit where a mistake would hurt, not everywhere.
| Role | Purpose | Capabilities | Approval gate | Measure |
|---|---|---|---|---|
| settlement finance | Moves value when an obligation completes, exactly once. | post · reverse · report | human at LOW+ | Unreconciled entries at end of day |
| reconciliation finance | Proves the books agree with the outside world, daily. | compare · report · escalate | no gate declared | Consecutive days of clean reconciliation |
| compliance risk | Checks every movement against the rules before it happens. | review · block · file | human at HIGH+ | Findings raised before rather than after settlement |
| reporting data | Turns the ledger into statements a person can act on. | query · summarise · publish | human at MEDIUM+ | — |
| coordination governance | Resolves jurisdiction between finance and risk, and keeps this charter true. | plan · approve | no gate declared | — |
accountableTo: you@example.com — the template ships the placeholder on purpose; conformance fails it until a real human is named. That field is the whole point. Escalation: coordination.
The settlement role posts and reverses with approval required at LOW impact — the strictest gate in the template, on the role that moves value. Its measure: unreconciled entries at end of day.
The compliance role holds review, block and file — block being the one capability that prevents rather than performs, and the reason a CFO can sign off on the rest. Its measure: findings raised before rather than after settlement.
The reconciliation role compares, reports and escalates, and its measure is consecutive days of clean reconciliation — a number a finance leader already tracks, produced by the same system that does the work.
Copy the template, change every field — a charter describing work nobody does is worse than none — then gate your CI on validateCharterDocument and static conformance. The full path — validation, the CI conformance gate, the JSON Schema for any language — lives on the builder hub; the format itself on the AAO spec page, and the naming rules every role above passes at /standard.
These are starting points, not defaults to ship — a charter describing work nobody does is worse than none. When yours validates clean, the network is waiting.
Start building