Specification sheet

MEC-12 Stoppability testing

Verify pre-deployment that systems can be halted by authorized stakeholders under defined conditions.

Where it fits

Filters and handoffs

Tagged for Governance, Policy with validator handshakes. Includes 3 steps, 3 reusable assets, and 4 snippet blocks.

Scholarly metadata

Authorship

Contact: research@ethotechnics.org

Publication details

  • Published: Dec 3, 2025
  • Last updated: Jan 9, 2026
  • Version: v1.1.0
  • DOI: Pending Zenodo deposit

License: CC BY-SA 4.0

Credit Ethotechnics Institute, include the page title + version, and link to the canonical permalink.

Archive snapshot: Wayback capture

Changelog

  • v1.1.0 · 2026-01-09 — Added citation metadata, mechanisms-level authorship details, and structured usage guidance.
  • v1.0.0 · 2025-12-03 — Initial public mechanisms release.

Copy citation (APA/BibTeX)

Cite this page Formats: APA, MLA, Chicago, BibTeX, RIS

Version

v1.1.0

Last updated

Jan 9, 2026

DOI

Pending Zenodo deposit

APA

Ethotechnics Institute Research Team. (2026). MEC-12 Stoppability testing. Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/stoppability-testing

MLA

Ethotechnics Institute Research Team. "MEC-12 Stoppability testing." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/stoppability-testing.

Chicago

Ethotechnics Institute Research Team. "MEC-12 Stoppability testing." Ethotechnics Institute. Jan 9, 2026. https://ethotechnics.org/mechanisms/patterns/stoppability-testing.

BibTeX

@misc{mechanism_stoppability-testing,
  title={MEC-12 Stoppability testing},
  author={Ethotechnics Institute Research Team},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/mechanisms/patterns/stoppability-testing},
  version={v1.1.0}
}

RIS

TY  - WEB
TI  - MEC-12 Stoppability testing
AU  - Ethotechnics Institute Research Team
PY  - 2026
UR  - https://ethotechnics.org/mechanisms/patterns/stoppability-testing
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 1 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.

Assets

Keep outputs reusable.

Link or copy these assets into design docs, runbooks, and briefs so the mechanism travels with the work.

Stoppability test plan

Defines scenarios, triggers, and expected time-to-halt targets.

Drill log

Records stoppability test outcomes and restoration steps.

Launch gate checklist

Confirms stoppability tests are complete before deployment.

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-12 Stoppability testing)
- Require stoppability drills before launch and after major changes.
- Publish time-to-halt targets and authorized halt owners.
Reference: https://ethotechnics.org/mechanisms/patterns/stoppability-testing

Product requirement

Product requirement (MEC-12)
- Stoppability tests log time-to-halt and restoration outcomes.
- Launch gates verify test completion and remediation.

Audit evidence checklist

Audit evidence checklist (MEC-12)
[ ] Drill logs include time-to-halt metrics and outcomes.
[ ] Authorized halt owners are documented.
[ ] Remediation actions are tracked to closure.

Postmortem trigger

Postmortem trigger (MEC-12)
Trigger review when stoppability tests are skipped or time-to-halt targets are missed.

Example usage

Pre-launch halt drill for automated approvals

A concrete scenario to help teams see how the pieces fit together.

How it plays out

A public benefits team runs a stoppability drill before release, measuring time-to-halt and verifying restoration steps before approving launch.

Anti-patterns

Common failure cases and counterfactuals

Use these to avoid superficial compliance and clarify what success requires.

Stoppability assumed, not tested

Teams rely on documentation without running drills.

Counterfactual: Stoppability drills run on a calendar and log outcomes.

False-positive warning: Simulated drills are acceptable if production tests are risky.

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.