Error Prevention & Correction¶

← Back to Mechanisms by Solution Family

Solutions that remove opportunities for mistakes, detect invalid states, repair deviations, or make failures easier to reverse.

29 mechanisms across 4 solution archetypes in this solution family. A mechanism inherits the primary family of the archetype it instantiates; family is about the move the solution makes, not the domain where it originated.

Change-Scoped Revalidation¶

After a change, re-derive only the facts inside a justified affected closure, retain the rest by a defeasible persistence presumption, and test that the boundary did not leak.

7 mechanisms · View full solution archetype

Boundary Escape Sampling — Spot-checks a random sample of items presumed unaffected by a change, re-deriving each, to estimate whether the scope boundary actually held.
Cache Invalidation Review — Walks the store of previously-derived results after a change and rules, item by item, which are now stale and must be recomputed versus which may still be trusted.
Change Impact Report — A shareable summary that states a proposed change and lists the downstream artifacts, obligations, tests, and owners it touches, so reviewers can see the blast radius before approving.
Dependency Closure Traversal — Walks the dependency graph outward from a change to compute the transitive set of everything reachable — the affected closure — in an order safe to revalidate in, halting where a stop condition holds.
Persistence Exception Register — Records each fact deliberately carried forward unchecked after a change — with its owner, its confidence, and the condition that would force a recheck — so the persistence presumption is explicit and accountable rather than silent.
Selective Revalidation Worklist — Turns the affected set into an ordered, scheduled to-do list of exactly which items to re-derive after a change — in dependency order, at a cadence matched to the change rate — and nothing outside it.
Truth-Maintenance System — An automated engine that records why each derived fact is believed and, when a premise changes, retracts and re-derives exactly the dependent facts — stopping where independent support still holds.

Deterioration Monitoring¶

Track slow degradation signals so maintenance, repair, renewal, or replacement occurs before failure becomes visible, expensive, or catastrophic.

8 mechanisms · View full solution archetype

Condition-Monitoring Sensor — Instruments an asset so its physical condition streams as a continuous quantitative signal, turning slow wear into a live trend that surfaces long before failure.
Cultural Health Survey — Periodically asks the people inside an organization to report on collaboration, morale, and norms, converting a diffuse sense of how things feel into tracked, comparable signals of cultural decline.
Health-Scoring Dashboard — Rolls many condition signals up into per-item health scores on a live display, so a whole portfolio can be ranked, watched for trend, and triaged at a glance.
Infrastructure Condition Assessment — Sends an expert to rate a single physical asset against a standardized condition rubric, producing a defensible condition state, a repair priority, and an estimate of how much service life remains.
Preventive Inspection — Sends a trained person, on a deliberate schedule, to examine an asset for early signs of trouble and log what they find, catching decline before the user does and turning findings into work orders.
Quality Drift Monitoring — Watches a system's outputs against a reference of acceptable quality and tracks how far they have drifted, firing a threshold when accuracy, usefulness, or fairness has slid too far to ignore.
Technical Debt Tracking — Keeps an explicit, itemized ledger of the shortcuts, deferrals, and known-bad structure accumulating inside a system, each entry traced to its cause, so invisible internal decay becomes a visible inventory.
Trust-Erosion Metric — Combines a few trust-sensitive signals into a single tracked index, watching its trajectory and firing escalation as an institution slides toward the point where legitimacy fails.

Self-Checking Operation¶

Make the operation prove or test its own acceptability before its output can propagate.

8 mechanisms · View full solution archetype

Constraint Gate Enforcement — Stations an admissibility rule at the operation's boundary so an output that violates a declared constraint is rejected before it can enter or commit.
False-Alarm Recalibration — Feeds the log of false alarms and misses back into the check itself, retuning its criterion and thresholds so the gate stays trustworthy as the operation changes.
Immediate Feedback Routing — Surfaces the check's verdict to the operator at the instant of the slip and routes them straight to the fix, so errors are corrected while the context is still fresh.
Independent Recomputation — Re-derives the same result by a deliberately different method and compares the two derivations, so a mistake in either path shows up as a disagreement.
Invariant Checking — Makes an operation test its own result against a property that must always hold, so an internally inconsistent output flags itself before it can propagate.
Physical Impossibility Design — Shapes the hardware so the wrong action simply cannot be performed — the part won't seat, the plug won't fit — making a whole class of slip physically impossible.
Redundancy-Based Error Detection — Attaches an independently-derived second encoding to an output and compares the two, so corruption reveals itself as a mismatch — and, when the code is rich enough, can be corrected in place.
Safe-Commit Hold — Holds an operation's output in a non-propagating pending state until it is cleared or approved, so nothing downstream can consume it until it is known good.

Standardization-and-Simplification¶

Make the correct action easier and the wrong action less available by replacing needless variation with a small, clear, maintained standard.

6 mechanisms · View full solution archetype

Controlled Vocabulary and Label Set — A governed set of terms, labels, abbreviations, codes, or field names used consistently across a workflow.
Order Set or Protocol Bundle — A predefined bundle of fields, sequence, defaults, and checks for recurring high-risk actions such as medical orders, service workflows, or approvals.
Part Family Rationalization — A method for reducing near-duplicate physical components, units, materials, or SKUs to a smaller approved set.
Point-of-Use Kit or Layout — A standardized physical or digital arrangement that presents only the needed items in a consistent location and order.
Standard Work Instruction — A concise, controlled description of the approved steps, sequence, roles, and conditions for a repeatable task.
Template and Form Library — A controlled set of approved forms, schemas, templates, or field layouts for recurring communication and documentation tasks.