Challenge load ledger
Volume, response capacity, unanswered-challenge age, and the decisions each breach produced.
Challenge load ledger
Track challenge volume against response capacity, so sustained congestion triggers a resourcing or scope decision instead of a narrowing of who may challenge.
- 1 Evidence
- 2 Authority
- 3 Decision
- 4 Consequence
- 5 Challenge acts here
- 6 Reconsideration
- 7 Correction
Where it acts
At Challenge, one of the seven stages every consequential decision passes through. It counts challenges against the capacity to answer them, so congestion is met with staff or a smaller scope, not fewer people allowed to challenge.
Steps
Put the mechanism in motion
3 steps, in order. Check each one off as it is done; the records below show the work was done.
0 of 3 steps complete
Records this mechanism keeps
What a team running this mechanism keeps, and what each record is for.
Congestion decision log
For each breach: resourcing, scope reduction, or error-reduction chosen, with the record behind it.
Standing-stability note
Evidence that eligibility and admissibility were not adjusted in response to volume.
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-23 Challenge load ledger) - Challenge volume, response capacity, and unanswered-challenge age are tracked and reported together. - A sustained congestion breach triggers a recorded resourcing decision or a recorded scope reduction, never a narrowing of standing. Reference: https://ethotechnics.org/mechanisms/patterns/challenge-load-ledger
Product requirement
Product requirement (MEC-23) - The challenge dashboard shows volume against capacity, not volume alone. - Clock breaches surface as capacity events in the same tooling as operational incidents.
Audit evidence checklist
Audit evidence checklist (MEC-23) [ ] The ledger reports volume, capacity, and age as a series. [ ] Each recorded congestion breach links to a resourcing or scope decision. [ ] No eligibility criterion was changed in the same review window as a congestion breach without a recorded rationale.
Postmortem trigger
Postmortem trigger (MEC-23) Trigger review when unanswered-challenge age crosses the published threshold, or when standing or admissibility was narrowed within a window where congestion was breached.
Example usage
The queue that funded its own reviewers
One scenario with each part of the mechanism in place.
How it plays out
Challenges against an automated denial triple after a model change. The ledger breaches its threshold, and the recorded decision is two additional funded reviewers and a scope reduction on the denial class — not an admissibility bar. The standing register is unchanged; the model change is reconsidered under its policy review trigger.
Anti-patterns
Common failure cases and counterfactuals
Each case passes on paper and fails in operation. The counterfactual shows what would have worked.
Congestion as nuisance
Volume is treated as bad-faith filing, and the response is higher bars, longer clocks, or narrower eligibility.
Counterfactual: Volume is read as a capacity signal and answered with resourcing or scope decisions on the record.
Exception: Bad-faith volume exists; filter it per case through admissibility, never through the standing register.
The invisible queue
Challenges age silently because nothing reports unanswered age, so the system's own records hide the saturation.
Counterfactual: Unanswered-challenge age is a first-class metric with a breach threshold.
Exception: A dashboard that shows only throughput hides the queue; report what has not been answered.
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). Challenge load ledger (MEC-23). Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/challenge-load-ledger
MLA
Ethotechnics Institute. "Challenge load ledger (MEC-23)." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/challenge-load-ledger.
Chicago
Ethotechnics Institute. "Challenge load ledger (MEC-23)." Ethotechnics Institute. Oct 6, 2026. https://ethotechnics.org/mechanisms/patterns/challenge-load-ledger.
BibTeX
@misc{mechanism_challenge-load-ledger,
title={Challenge load ledger (MEC-23)},
author={Ethotechnics Institute},
year={2026},
howpublished={Ethotechnics Institute},
url={https://ethotechnics.org/mechanisms/patterns/challenge-load-ledger},
version={v1.2.1}
}
RIS
TY - WEB TI - Challenge load ledger (MEC-23) AU - Ethotechnics Institute PY - 2026 UR - https://ethotechnics.org/mechanisms/patterns/challenge-load-ledger ER -