Rehearsal plan
Scope, window, participants, and the measures to be taken during the exercise.
MEC-15 Withdrawal rehearsal
Run the workflow without the system on a schedule and measure what withdrawal would actually cost at the technical, operational, and institutional levels.
Permanent link /mechanisms/patterns/withdrawal-rehearsal
Where it fits
Filters and handoffs
Tagged for Governance, Policy with validator handshakes. Includes 3 steps, 3 reusable assets, and 4 snippet blocks.
Copy citation (APA/BibTeX)
Cite this page Formats: APA, MLA, Chicago, BibTeX, RIS
APA
Ethotechnics Institute Research Team. (2026). MEC-15 Withdrawal rehearsal. Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/withdrawal-rehearsal
MLA
Ethotechnics Institute Research Team. "MEC-15 Withdrawal rehearsal." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/withdrawal-rehearsal.
Chicago
Ethotechnics Institute Research Team. "MEC-15 Withdrawal rehearsal." Ethotechnics Institute. Jan 9, 2026. https://ethotechnics.org/mechanisms/patterns/withdrawal-rehearsal.
BibTeX
@misc{mechanism_withdrawal-rehearsal,
title={MEC-15 Withdrawal rehearsal},
author={Ethotechnics Institute Research Team},
year={2026},
howpublished={Ethotechnics Institute},
url={https://ethotechnics.org/mechanisms/patterns/withdrawal-rehearsal},
version={v1.1.0}
}
RIS
TY - WEB TI - MEC-15 Withdrawal rehearsal AU - Ethotechnics Institute Research Team PY - 2026 UR - https://ethotechnics.org/mechanisms/patterns/withdrawal-rehearsal ER -
Specification overview
At-a-glance details for planning and handoffs.
Capture the scope, assets, and validator handshakes before diving into the steps.
Spec essentials
What ships with this mechanism
- 3 steps with checklist-ready owners.
- 3 reusable assets for briefs and runbooks.
- 4 reuse-ready snippet blocks.
- 3 glossary anchors for shared terms.
Filters & validators
Where this spec sits in the system
Tagged in 2 filters with 2 linked validators.
Glossary anchors
Link back to the definitions.
Jump to the glossary terms that frame this mechanism.
Steps
Put the mechanism in motion.
Start with the field cues, then use the assets to keep the work legible.
3 steps with checklist-ready owners, plus linked assets for handoffs.
0 of 3 steps complete
Assets
Keep outputs reusable.
Link or copy these assets into design docs, runbooks, and briefs so the mechanism travels with the work.
Three-level reversibility readout
Cost and time to restore recorded separately for technical, operational, and institutional withdrawal.
Preserved capacity list
The staffing, tooling, and knowledge that must be maintained for withdrawal to stay possible, with owners.
Reuse-ready snippets
Copy policy, audit, and incident language.
Use these snippets in requirements, audits, and postmortems with the mechanism permalink.
Policy requirement
Policy requirement (MEC-15 Withdrawal rehearsal) - Rehearse operating the workflow without the system on a published schedule. - Record cost, expertise available, and time to restore at the technical, operational, and institutional levels. Reference: https://ethotechnics.org/mechanisms/patterns/withdrawal-rehearsal
Product requirement
Product requirement (MEC-15) - The system supports a rehearsal mode that suspends automated handling for a defined scope and window. - Rehearsal outcomes are recorded against the dependency record for the workflow.
Audit evidence checklist
Audit evidence checklist (MEC-15) [ ] Rehearsals ran on schedule with a defined scope and window. [ ] Results state cost, expertise available, and time to restore at all three levels. [ ] Preserved capacities have named owners and review dates.
Postmortem trigger
Postmortem trigger (MEC-15) Trigger review when a rehearsal is skipped, or when it shows the workflow can no longer be run without the system.
Example usage
A week of manual triage
A concrete scenario to help teams see how the pieces fit together.
How it plays out
A claims team runs one region manually for a week each quarter, finds that throughput halves and that only two reviewers still hold the rules, and funds a training rotation as a preserved capacity.
Anti-patterns
Common failure cases and counterfactuals
Use these to avoid superficial compliance and clarify what success requires.
The switch exists
A documented kill switch is treated as proof of reversibility, though nobody has run the workflow without the system in years.
Counterfactual: Withdrawal is rehearsed on a schedule and the cost of doing it is measured.
False-positive warning: A rehearsal can be scoped to a slice of traffic; what it may not be is hypothetical.
Rehearsal without a record
The drill happens but produces no measurement, so nothing can be compared to last year.
Counterfactual: Each rehearsal records cost, expertise, and restore time against the dependency record.
False-positive warning: Qualitative findings are useful, but at least one comparable measure has to survive the exercise.
Validators
Pair validators with this mechanism.
Use these tools to size risk and keep the stewardship path visible.
Validator
Maintenance Simulator
Tabletop simulation that plays through outages, maintenance windows, and handoffs to stress-test coverage.
Validator
Technical Capacity Forecaster
Charts compound decay against refusal windows to spot saturation risk across a 24-month horizon.