Mechanism MEC-26

Effective corrective power

Test correction as a chain from detection to enforcement, and map the route to the decision point that sets a binding constraint.

  1. 1 Evidence
  2. 2 Authority
  3. 3 Decision
  4. 4 Consequence
  5. 5 Challenge acts here
  6. 6 Reconsideration
  7. 7 Correction acts here

Where it acts

At Challenge and Correction, two of the seven stages every consequential decision passes through. It follows a correction from detection through enforcement and maps the route to the decision point that sets the constraint.

Steps

Put the mechanism in motion

4 steps, in order. Check each one off as it is done; the records show the work was done.

Records this mechanism keeps

What a team running this mechanism keeps, and what each record is for.

Corrective power chain map

The five conditions, the owner of each, and the record that shows it.

Constraint map

The binding constraint, the decision point that sets it, the standing at each node, the route, and where it stops.

Enforcement receipt

Who implemented the remedy, when, and what changed.

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-26 Effective corrective power)
- Each consequential decision class names the five conditions and the record that shows each one.
- A challenge that cannot be remedied locally records the constraint map and the decision point that sets it.
Reference: https://ethotechnics.org/mechanisms/patterns/effective-corrective-power

Product requirement

Product requirement (MEC-26)
- The challenge record carries detection, standing, agenda, decision, and enforcement status.
- The constraint map is visible to the challenger, not held only by the deciding body.

Audit evidence checklist

Audit evidence checklist (MEC-26)
[ ] The five conditions are recorded for each decision class.
[ ] The first broken link is named with its record.
[ ] The constraint map records the decision point that sets the constraint.
[ ] One live challenge was followed to enforcement.

Postmortem trigger

Postmortem trigger (MEC-26)
Trigger review when a challenge is closed without a record of which condition failed, or when a remedy is recorded as complete before enforcement is confirmed.

Example usage

A scheduling challenge that reaches the budget

One scenario with each part of the mechanism in place.

How it plays out

A worker contests a shift schedule. The local manager cannot change staffing because the budget is set above the department. The claim reaches the budget owner with standing, and the recorded remedy is a staffing line, not a case-by-case exception. The chain is recorded from detection to enforcement.

Anti-patterns

Common failure cases and counterfactuals

Each case passes on paper and fails in operation. The counterfactual shows what would have worked.

Challenge theater

A route exists and stops at standing, so the institution can say it offers a challenge without ever changing a rule.

Counterfactual: The chain is tested to enforcement, and the first broken link is named.

Exception: A challenge route is not a correction pathway until someone can follow it to a changed state.

Reachability as deferral

A claim is referred with no named decision point, no standing, and no answer date, which converts the referral into an indefinite wait.

Counterfactual: The map names the decision point that sets the constraint, the standing it grants, and the date by which it must answer.

Exception: A referral without a decision-maker is a way of closing a claim without deciding it.

Diagnostics for this mechanism

Tools that size the risk this mechanism addresses.

Diagnostic

Delegation audit

Walks a team through one workflow against six questions and returns an exposure score, the permissions nobody can justify, and whether its decisions can be undone. Start here when the system keeps no decision records yet; use the record conformance checker once it does.

Cite this page · v1.2.1 · updated Oct 6, 2026 · CC BY-SA 4.0

APA

Ethotechnics Institute. (2026). Effective corrective power (MEC-26). Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/effective-corrective-power

MLA

Ethotechnics Institute. "Effective corrective power (MEC-26)." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/effective-corrective-power.

Chicago

Ethotechnics Institute. "Effective corrective power (MEC-26)." Ethotechnics Institute. Oct 6, 2026. https://ethotechnics.org/mechanisms/patterns/effective-corrective-power.

BibTeX

@misc{mechanism_effective-corrective-power,
  title={Effective corrective power (MEC-26)},
  author={Ethotechnics Institute},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/mechanisms/patterns/effective-corrective-power},
  version={v1.2.1}
}

RIS

TY  - WEB
TI  - Effective corrective power (MEC-26)
AU  - Ethotechnics Institute
PY  - 2026
UR  - https://ethotechnics.org/mechanisms/patterns/effective-corrective-power
ER  -

Authorship

Contact: hello@ethotechnics.org

Publication details

  • Published: Dec 3, 2025
  • Last updated: Oct 6, 2026
  • Version: v1.2.1

License: CC BY-SA 4.0

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

Archive: Wayback Machine history

Latest change

v1.2.1 · Oct 6, 2026 — Rewrote the copy of MEC-01 to MEC-12 in plain sentences. A halt is described as containment while the rule is fixed and people are restored, upheld appeals are counted against the rule in MEC-06 and MEC-08, and MEC-04 is renamed Hard clock.

Earlier versions (3)
  • v1.2.0 · Oct 1, 2026 — Filed every mechanism under the six safeguards, led the starters and role paths with challenges that reach the rule, and added that obligation to MEC-06.
  • v1.1.0 · Jan 9, 2026 — Added citation metadata, mechanisms-level authorship details, and structured usage guidance.
  • v1.0.0 · Dec 3, 2025 — Initial public mechanisms release.