Manual sections
Audit Exhaust
Traceability as a byproduct.
Audit Exhaust is not documentation-as-a-ritual. It is traceability-as-a-byproduct.
Traceability as a byproduct.
- Where ambiguity gets in
- After: history nobody can reconstruct
- In the tunnel
- The trail you leave behind
- Enforced by
- The Runtime
The Default Exhaust of Good Work
If you can't reconstruct what happened, governance didn't happen. The minimum audit exhaust required for every project includes:
- Scope artifact exists (Card/Charter).
- Lens Output exists (GapScore/Maturity/Path).
- Decisions are recorded where work lives.
- Deviations are recorded and signed off.
- Change Forum outputs are recorded and trade-offs are traceable.
The test
Could someone who was not in the room reconstruct what was decided, by whom and why, from the records alone?
Calibration Governance
The Governance OS has two forms of calibration. They are entirely separate mechanics.
Project Calibration
Happens inside the Accelerator at phase transitions (via Change Forum Gates). Its purpose is to re-confirm reality, formalize trade-offs, and prevent silent scope expansion. This is mandatory per project.
OS Calibration
Changes the OS itself (tokens, thresholds, maturity mapping). Owned strictly by the OS Custodian. Never happens per-project. Never happens mid-flight.