Reversibility Horizon Review¶
Test / assessment — instantiates Malleability Window Governance
Assesses when rollback, redesign, migration, exit, or compensation will become harder than continuation.
The Reversibility Horizon Review is a forward-looking assessment that estimates when — on the current trajectory — rollback, redesign, migration, exit, or compensation will become harder than simply carrying on, and stress-tests whether the exit route is actually executable before that moment arrives. It looks ahead at the closing of the window, not back at lock-in already formed. Its defining discipline is refusing to accept "reversible" as a claimed property: it converts reversibility into a dated, tested quantity by projecting the horizon and then drilling the rollback pathway to prove it works. A route that exists only on an architecture diagram is treated as no route at all.
Example¶
A national government is migrating civil records to a single cloud vendor. The review projects the reversibility horizon: as more agencies build workflows on vendor-proprietary services, the cost of extracting the data and rebuilding elsewhere climbs steadily. It estimates that at roughly eighteen months, exit cost will exceed the cost of staying — after that, the government is effectively captive. Then it tests the rollback pathway: is there a funded, owned, tested export-and-rebuild process? There is not — only a contractual clause asserting the data is portable. The review's recommendation is timed to the horizon: build and drill a real migration capability now, while still on the malleable side of the crossing, rather than discovering at month twenty that reversibility was fictional.
How it works¶
- Projects the trajectory forward. It models how switching cost rises along the current path and locates the crossing where reversal exceeds continuation.
- Distinguishes reversible-on-paper from reversibly-executable. A rollback is credited only if the pathway has owners, funding, a migration plan, and a tested process.
- Reports time-to-horizon. The output is a date (with a band), so action can be scheduled ahead of the window's close rather than triggered by its arrival.
- Re-runs as the trajectory shifts. New contracts or network effects move the horizon, so the estimate is refreshed, not frozen.
Tuning parameters¶
- Projection horizon — how far ahead to model. Longer projections give more warning but rest on shakier assumptions.
- Executability bar — tabletop review versus a live rollback drill. A real drill is convincing but expensive and disruptive.
- Pathway coverage — which exit routes (rollback, redesign, migration, compensation) are tested. Broader coverage is thorough but slower.
- Confidence band — how wide an uncertainty range the horizon date carries. Wider bands are honest but harder to act on.
When it helps, and when it misleads¶
Its strength is turning "reversibility" from a comforting adjective into a dated, drilled fact — the direct antidote to symbolic reversibility, where everyone agrees rollback is possible and no one has tried it. Its failure mode is treating the horizon estimate as precise, or declaring a rollback "possible" on the strength of a plan never executed; hysteresis[n1] is the physical intuition for why the return path rarely retraces the outbound one and usually costs more. A classic misuse is announcing a comfortably distant horizon to justify deferring the exit investment — the very investment the review exists to prompt. The guarding discipline is to drill the rollback, carry an honest band on the horizon date, and re-run the review whenever the trajectory changes.
How it implements the components¶
reversibility_horizon_marker— projects and dates the point after which reversing exceeds continuing, refreshed as the trajectory moves.rollback_and_redesign_pathway— tests whether the exit or redesign route is actually executable — owned, funded, drilled — before the horizon closes.
It forecasts when reversibility will close and whether the exit route works, not the lock-in a trial has already produced — measuring accrued dependency lock_in_cost_monitor and checking whether a trial stayed inside sandbox_boundary belong to its hazard-twin Post-Pilot Lock-In Audit.
Related¶
- Instantiates: Malleability Window Governance — the review is how the archetype's "reversibility before scale" invariant is dated and tested.
- Consumes: Collingridge Curve Workshop draws the first prospective horizon this review then monitors and re-dates against real evidence.
- Sibling mechanisms: Adaptive Stage-Gate Protocol · Collingridge Curve Workshop · Deployment Impact Dashboard · Exit and Interoperability Rule · Pause or Moratorium Trigger Protocol · Post-Pilot Lock-In Audit · Regulatory or Operational Sandbox · Stakeholder Harm Reporting Channel · Sunset Clause with Renewal Hearing
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Reversibility Horizon Review operates as an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution because it assesses when rollback, redesign, migration, exit, or compensation will become harder than continuation.
Independent corroboration: The frozen evidence defines Reversibility Horizon Review as 'Assesses when rollback, redesign, migration, exit, or compensation will become harder than continuation', so its operative form is Analysis, Modeling & Optimization.
Nearest alternative: Assessment, Review & Assurance — Reversibility Horizon Review includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Lifecycle engineering provides the clearest formative model for reviewing when rollback, redesign, or migration becomes more costly and less feasible than continuation. Strategy, switching-cost economics, foresight, and systems lock-in independently extend the horizon concept to institutional and social choices.
Related originating lineages:
- Economics & Finance — economics_finance contributes cost, allocation, repeated-game, expectation, and risk-analysis traditions to the mechanism’s formative or independently convergent form; that contribution does not displace the primary engineering_design lineage.
- Futurism & Strategic Foresight — futurism_foresight contributes horizon scanning, scenario timing, lock-in, and anticipatory decision practice to the mechanism’s formative or independently convergent form; that contribution does not displace the primary engineering_design lineage.
- Organizational & Management Science — organizational_management contributes decision records, operating routines, knowledge reuse, and institutional learning to the mechanism’s formative or independently convergent form; that contribution does not displace the primary engineering_design lineage.
- Systems Thinking & Cybernetics — systems_cybernetics contributes feedback, perturbation, dynamic role change, and interconnected risk behavior to the mechanism’s formative or independently convergent form; that contribution does not displace the primary engineering_design lineage.
Review resolution: The blind reviewers disagreed on primary lineage (organizational_management versus engineering_design); authoritative or primary research supports engineering_design as the best historical origin. Lifecycle engineering provides the clearest formative model for reviewing when rollback, redesign, or migration becomes more costly and less feasible than continuation. Strategy, switching-cost economics, foresight, and systems lock-in independently extend the horizon concept to institutional and social choices. The cited NASA Systems Engineering Handbook: Design Solution Definition; NASA Systems Engineering Handbook: Cost-Effectiveness Considerations directly supports the defining operation used in that choice. All independently supported contributing domains are retained without an arbitrary cap, while domain_reach=universal records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
- NASA Systems Engineering Handbook: Design Solution Definition
- NASA Systems Engineering Handbook: Cost-Effectiveness Considerations
Notes¶
[n1] Hysteresis — a system's state depends on its history, so the path back is not the reverse of the path in and often costs more. It is the physical analogue of why reversal grows harder over time, and why this review dates the horizon and drills the return route rather than assuming symmetry. ↩