Mechanism MEC-27

Protected disagreement

Separate an institutional error from a legitimate disagreement, and protect the losing side's capacity to challenge the next decision.

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

Where it acts

At Challenge and Reconsideration, two of the seven stages every consequential decision passes through. It classifies the claim before deciding it and keeps the losing side able to contest what comes next.

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.

Claim classification record

Whether the claim is an error or a disagreement, and the reasons.

Settlement record

The procedure, the decision, and the protections for the losing side.

Future-challenge check

The resources, information, organization, and standing the losing side retains.

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-27 Protected disagreement)
- Every challenge is classified as an error or a disagreement before the outcome is recorded.
- A disagreement settlement records what the losing side retains and how it can challenge again.
Reference: https://ethotechnics.org/mechanisms/patterns/protected-disagreement

Product requirement

Product requirement (MEC-27)
- The challenge record separates the claim type, the procedure, the decision, and the minority protections.
- A settlement cannot close without a future-challenge check.

Audit evidence checklist

Audit evidence checklist (MEC-27)
[ ] Each challenge is classified as an error or a disagreement.
[ ] Error outcomes record the remedy and the rule change.
[ ] Disagreement outcomes record the procedure and reasons.
[ ] The losing side retains resources, information, and standing to challenge again.

Postmortem trigger

Postmortem trigger (MEC-27)
Trigger review when a settlement leaves the losing side without the resources or standing to challenge a subsequent decision.

Example usage

A rent cap that protects tenants and small owners

One scenario with each part of the mechanism in place.

How it plays out

A city adopts a rent cap. Tenants gain security; small property owners face a real income loss. The process records both claims, adopts a transition support line for owners who qualify, and preserves their route to challenge the next housing rule. Neither side is removed from future politics, and the settlement does not pretend the conflict was an error.

Anti-patterns

Common failure cases and counterfactuals

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

Every loss is an error

Any burdened group is treated as the victim of a mistake, so every political loss becomes a correction claim and no decision can settle.

Counterfactual: Claims are classified, and legitimate disagreement is resolved through a procedure rather than a remedy.

Exception: A framework that cannot name a legitimate loss will call every loss a failure.

Settlement as elimination

The winning side keeps the outcome and strips the losers of the resources or organization they would need to challenge it.

Counterfactual: The settlement protects the losing side's future challenge capacity.

Exception: A decision that ends the opponent is not a settlement.

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). Protected disagreement (MEC-27). Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/protected-disagreement

MLA

Ethotechnics Institute. "Protected disagreement (MEC-27)." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/protected-disagreement.

Chicago

Ethotechnics Institute. "Protected disagreement (MEC-27)." Ethotechnics Institute. Oct 6, 2026. https://ethotechnics.org/mechanisms/patterns/protected-disagreement.

BibTeX

@misc{mechanism_protected-disagreement,
  title={Protected disagreement (MEC-27)},
  author={Ethotechnics Institute},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/mechanisms/patterns/protected-disagreement},
  version={v1.2.1}
}

RIS

TY  - WEB
TI  - Protected disagreement (MEC-27)
AU  - Ethotechnics Institute
PY  - 2026
UR  - https://ethotechnics.org/mechanisms/patterns/protected-disagreement
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.