The Debt Ledger

The Debt Ledger is the mechanism that tracks what you owe when you operate in Pressure State. Every time a gate is bypassed, every time a Provisional Commission runs without full Groundwork, every time a decision is made under pressure that deviates from Standard State protocols — the Debt Ledger records it.

This is not a guilt ledger. It is not a punishment mechanism. It is an accounting system for operational shortcuts that were taken deliberately and need to be resolved deliberately. The distinction matters because every organisation takes shortcuts under pressure. The ones that survive are the ones that track the shortcuts and pay them down. The ones that fail are the ones that take the shortcut, forget about it, and let the debt compound.

The concept borrows from technical debt in software engineering, but applies it to the full operating model. Technical debt is code you know needs to be refactored. Operational debt is governance you know needs to be completed. Both compound if ignored. Both are manageable if tracked.

Debt enters the Ledger through three mechanisms.

Gate Bypasses happen when a Post's gate is temporarily disabled for operational urgency. The scope gate is bypassed because the team needs the agent to handle something slightly outside its documented territory. The testing gate is bypassed because a new golden vector has not been built yet for an edge case that was just discovered. Each bypass is recorded with a reason, a date, and a resolution deadline — typically 14 days.

Provisional Commissions happen when a Post is deployed with incomplete Groundwork. Only scope.md and a Directive are required for a Provisional Commission. The remaining documents — contracts.md, testing.md, prompting.md — are owed. Each run of a Provisionally Commissioned Post generates a Debt entry because the Post is operating without full governance.

Skipped Gates happen when a gate is intentionally omitted from The Groundwork. This is rare and should require ops lead approval. The gate must be retrospectively applied or formally waived with documented reasoning.

The Debt Ledger is reviewed at every Survey — the quarterly planning session. The question is straightforward: what Debt have we accumulated, what have we paid down, and what is the plan for the remainder?

Organisations that do not track operational debt experience the consequences as surprise failures. An agent that was provisionally commissioned six months ago is still running without contracts.md. Nobody remembers it was provisional. The contracts were never written. The agent has been quietly expanding its behavior because there was never a frozen interface to constrain it. The first time someone notices is when the output breaks downstream.

Organisations that track the Debt experience the same situation as a line item in a quarterly review. "This Post has been Provisional for 90 days. The contracts.md is owed. Who is resolving this and when?" The outcome is different because the visibility exists.

The Debt Ledger is also the mechanism that prevents Pressure State from becoming permanent. When the organisation enters Pressure State, gates get bypassed and shortcuts get taken. The Debt Ledger ensures those shortcuts are tracked and resolved when the pressure eases. Without it, Pressure State quietly becomes the new normal, and the governance framework collapses under the weight of accumulated exceptions nobody is tracking.