Explainer

Three Kinds of Reversibility

Technical, operational, and institutional reversibility are separate claims, and only the third decides whether a correction will ever be used.

Definition

Short definition

Two-to-four sentences you can drop into briefs or specs.

Technical reversibility means the mechanism works. Operational reversibility means the people and processes can absorb it being used. Institutional reversibility means the organization can survive having used it.

A correction that would cause unacceptable damage will not be exercised, and a correction that will not be exercised is not part of the control system. Each level needs its own evidence.

Canonical entry: Three Kinds of Reversibility in the glossary.

Architecture

Mechanism in Operation

Visual model of operational states, transitions, boundaries, and failure points.

Mechanism, drawn

The Three-Level Reversibility Ladder

A correction that would cause unacceptable damage will not be exercised, and a correction that will not be exercised is not part of the control system.

Level 3: Institutional Reversibility Can the organization survive having thrown the switch? Evidence: Priced withdrawal impact assessment · Contractual penalty review · Viable alternative market Where Systems Fail Switch exists, but pulling it is institutional suicide Level 2: Operational Reversibility Can staff and fallback procedures absorb the switch at production volume? Evidence: Production-volume withdrawal rehearsals · Manual backlog clearance rate · Staff readiness Rehearsal Gap Manual skills atrophied; backlog explodes 10x Level 1: Technical Reversibility Does the rollback switch or undo API technically execute? Evidence: Automated rollback tests in staging · Git / DB schema migrations · Snapshot restore Where Audits Stop "Rollback passed in CI" (Nominal reversibility)

Example

Example use case

A concrete scenario to ground the term in operations.

A hospital scheduling system passes its rollback test in staging, but a withdrawal rehearsal shows the clinic cannot process a day of referrals manually, and the contract carries an exit fee larger than the annual budget. Technical reversibility passes, the other two fail.

Implementation

Distinct implementation signals

Unique operational detail to help this concept stand on its own in policy, procurement, and review workflows.

What to check

Ask for evidence at each level separately: a rollback test against the current build, a rehearsal at production volume, and a priced withdrawal impact assessment covering contracts and commitments.

Common failure pattern

A passing rollback test is reported as reversibility. The switch works and nobody has ever thrown it, so the two levels that matter remain unmeasured.

Evidence to ship

Publish rollback success rate and restore time, backlog per hour of fallback operation from the last rehearsal, and the estimated institutional cost of withdrawal trended against exposure.

CTAs

Related artifacts

Standards, bindings, and evidence packs to move from concept to adoption.

Doctrine

Law VI: nominal is not operational reversibility

The invariant behind the three-level ladder and the standards that bind it.

Read the laws

Eval

Dependence and reversibility

Test the ladder against a real deployment, including a withdrawal rehearsal.

Open the suite

Taxonomy

Dependence: reversibility

The capability branch that carries owners and readiness for this work.

Open the branch

FAQ

Quick answers

Short replies for common implementation questions.

Can a system pass level three but fail level one?

Rarely, and it usually means the system is not load-bearing. The levels tend to fail from the top down, which is why teams that test only the mechanism report reversibility they do not have.

How often should a withdrawal be rehearsed?

On a stated cadence that survives busy quarters. A rehearsal cancelled for load is evidence about operational reversibility, and it should be recorded as such.