Decisions compound.

Every consequential decision changes the conditions under which future decisions get made. It forecloses options, creates dependencies, sets precedents, and allocates attention. That's not a side effect — it's the primary long-run consequence, and it usually dwarfs the direct one.

Which means organizations accumulate decision debt the way codebases accumulate technical debt. Shortcuts in how decisions get made — unclear ownership, unstated assumptions, horizons that stop at the current quarter — don't fail immediately. They compound quietly, and the interest comes due later, paid by people who weren't in the room.

Here's the distinction the whole argument turns on: decision quality is not decision integrity. Quality asks whether this call was sound — right information, right analysis, right judgment. Integrity asks whether this call holds together with everything upstream and downstream of it: whether it honors the constraints it inherited and whether it's honest about the constraints it creates. An organization can be full of high-quality decisions and still be drowning in decision debt. That was exactly the situation I watched unfold.

Decision Risk deserves its own layer.

We've professionalized nearly every risk that matters to a large institution — credit, market, operational, technology, model, third-party. Each has owners, appetite statements, and controls. But the risk that a series of individually sound decisions compounds into an unsound position has no name, no owner, and no framework. It shows up in the post-mortem, never in the register.

I've started calling it Decision Risk, and I think it's the most under-managed risk in modern organizations — and getting worse. AI is collapsing the cost of analysis, which means decision velocity is going up everywhere. More decisions, made faster, by more actors, with fewer natural pauses. Compounding accelerates with volume. The organizations that thrive won't just make better individual calls; they'll manage the integrity of the whole decision system.

What a decision should pass before it ships.

The practical core of Decision Integrity is five tests. None require a committee. All require honesty.

Taking on decision debt isn't the sin. Hiding it is.

None of this argues for slow decisions or decision-by-committee. Speed matters, and sometimes the right call is to knowingly take on decision debt — lock in a vendor before the strategy is settled, ship the interim architecture, accept the precedent. Engineering teams do this with technical debt all the time, and the good ones do it well because they do it in the open: the shortcut is named, logged, and scheduled for repayment.

Decision debt deserves the same treatment. The failure mode isn't the shortcut. It's the unrecorded shortcut — the constraint nobody wrote down, discovered two years later by a team that can't understand why their options are so narrow. Deliberate debt is a tool. Silent debt is a trap.

Leaders are judged on the decision systems they leave behind.

We evaluate leaders on results, and results matter. But results are partly luck and often lag. The more durable measure is what a leader does to the organization's capacity to decide well after they're gone: whether ownership is clear, whether assumptions get written down, whether debt is deliberate, whether the decisions they made left the option space wider or narrower for the people who follow.

That's the discipline I'm calling Decision Integrity. This note plants the flag; the full framework is in the works — how to score it, how to review for it, and what a decision-mature organization looks like in practice. If this names something you've lived, I'd like to hear the story.

Evidence computed, not assembled.

The alternative is to move the point of control from the review meeting to the runtime. Concretely, that means three things.

Controls become versioned, testable code. A control that lives in a policy document is an intention. A control expressed as policy-as-code executes on every relevant action, cannot be skipped by busy humans, and carries a version history the second line can challenge line by line.

Every execution self-evidences. When the control runs in the path of the work, the evidence of its operation is generated at the moment of execution — signed, immutable, mapped to the obligation it satisfies. Nobody assembles an evidence package before an exam. The evidence already exists.

Exposure is computed continuously. Residual risk stops being a rating negotiated in a workshop twice a year and becomes a number derived from live control performance, with drift visible the day it starts, not the quarter it's discovered.

None of this weakens governance. It's the same obligations with stronger answers — and it's the only architecture I can see that lets a regulated institution adopt autonomous systems honestly, because it's the only one where the control layer runs as fast as the thing being controlled.

The dual rail: run both, retire one on evidence.

You don't get to flip a switch on this, and you shouldn't ask anyone — least of all your second line or your examiners — to take a new system on faith. The transition I'd run is a dual rail over eighteen to twenty-four months: the traditional KRI and attestation rail keeps operating exactly as it does today, while the runtime rail comes up beside it, domain by domain.

The quiet weapon is the reconciliation log. For every domain on both rails, you record where the runtime evidence and the traditional artifacts agree and where they diverge, and you disposition every divergence. When reconciliation holds for consecutive cycles, you've built the evidentiary case to retire the manual rail for that domain — on data, not on trust. The transition has an owner and an end state. A permanent dual system is a failure, not a compromise.

Where to start matters. I'd begin on the agentic estate itself: it's where the gap between change velocity and assessment cadence is widest, and no legacy KRI regime has earned incumbency there. Prove the spine on the sharpest edge — a live inventory of agents and their permissions, autonomy tiers that are earned through evidence gates rather than granted by calendar, and one existing committee metric rendered directly from runtime data with full lineage. Ninety days to first value, then expand deliberately.

Same obligations. Stronger answers.

For institutions under heightened supervisory standards, this is not a workaround — it's strengthened compliance. The examiner conversation changes from "show me your testing" to "here is the decision log."

Where this goes wrong — named in advance.

I have more credibility proposing this if I name its failure modes myself. There are four I watch.

Start where the gap is sharpest.

If you run technology or technology risk inside a regulated institution, the question in front of you isn't whether autonomous systems arrive — they're already in your pipelines. The question is whether your control environment governs them or merely documents them after the fact.

My argument: pick the domain where the gap between change velocity and assessment cadence hurts most. Codify your top controls as policy. Instrument the evidence at execution. Run the dual rail, keep the reconciliation log, and let the data retire the old system domain by domain. Ninety days to the first control that proves itself in production. Everything after that is expansion.

Risk management at the speed of the business used to be an aspiration. For autonomous systems, it's the entry fee.