Constraints & Guardrails¶

← Back to Mechanisms by Solution Family

Solutions that prevent unacceptable states or actions by encoding limits, invariants, preconditions, safe envelopes, or error-proofing rules.

212 mechanisms across 29 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.

Archetype Overview¶

This unusually large family has a compact overview for orientation. Each archetype name jumps to its fully visible section below.

Solution archetype	Mechanisms	Description
Access-Conditioned Bundle Decoupling	12	Prevent access leverage from forcing unwanted bundled acceptance by testing necessity, unbundling separable conditions, and preserving meaningful refusal, alternatives, or remedies.
Archetype Overmatching Guardrail	10	Prevent familiar archetypes from being forced onto cases that only superficially resemble them.
Balance Preservation	9	Preserve a desirable balance by preventing one part, value, workload, demand, or pressure from overwhelming the others.
Bounded Approximation	8	Use a simplified approximation when exactness is costly, while bounding the error enough for the decision.
Branching and Merging	8	Allow parallel versions or lines of work to diverge safely and then recombine through explicit merge rules.
Constraint Envelope Adjustment	0	Tighten, relax, or reshape the constraints defining a system's permissible action space to remove harmful freedom or restore needed flexibility.
Constraint Propagation and Decoupling	6	When constraints bind a problem into an unwieldy whole, propagate their implications first, then solve only the reduced and justified subproblems that remain.
Context-Preserved Meaning Capture	9	Record what happened together with the contextual cues, meanings, roles, and observer notes that make the event interpretable later.
Contradiction-Closure Proof	9	Prove a claim by showing that denying it makes the accepted system impossible or inconsistent.
Cross-Language Constraint Check	10	Check whether communication, interface, policy, or category assumptions survive movement across languages and communities before treating translation or localization as complete.
Decision-Procedure Boundary Mapping	5	Map whether a yes/no question can be decided by a finite total procedure before promising automation, certainty, or universal adjudication.
Emergency Authority Activation and Constraint	3	Activate extraordinary authority only under defined crisis triggers, keep it bounded by scope, time, oversight, and audit, then force reversion when the emergency condition ends.
Entropy Export	7	Preserve local order by moving disorder, waste, ambiguity, heat, or cleanup burden across a boundary to a governed sink with visible accountability.
Feasible-Alternative Comparator Calibration	8	Judge real options against reachable alternatives, not against perfection.
Function-Without-Intent Caution	8	Avoid assuming that because something has a function, it was intentionally designed for that purpose.
Geometric Primitives Vocabulary Constraint	7	Limit the available formal vocabulary to a small alphabet of primitive units, then create expressive range by composing, repeating, scaling, aligning, and transforming those units rather than adding new decorative forms.
Guarded State Transition	0	Allow state changes only when defined preconditions, invariants, or authority requirements are satisfied.
Hidden Path Discovery	8	Search for non-obvious routes around barriers that appear impossible from the ordinary path.
Invariant Guarding	8	Identify conditions that must always remain true and guard operations so those invariants are preserved.
Irreversible Commitment Management	9	Treat irreversible actions differently by adding prevention, deliberation, staging, consent, and compensation logic before commitment.
Latent Capacity Release Design	8	Remove a suppressing constraint in bounded stages so latent capacity can emerge without uncontrolled rebound, externality, or destabilization.
Necessary-Condition Closure Design	10	Make all non-substitutable success conditions explicit, verify each one, and treat the weakest missing condition as the blocker rather than averaging it away.
Nonactivating Occupancy Blockade	8	Block an unwanted trigger by safely occupying the recognition site with a nonactivating substitute that denies access without producing the response.
Physical-Constraint Design for Impossibility	0	Make the wrong action physically impossible, materially rejected, or harder than the correct action.
Reflexive Rule-Binding Governance	10	Keep authority inside the rule system by making every actor, enforcer, exception, and rule-change path subject to stated rules.
Self-Targeting Defense Guardrail	10	Keep defensive power from turning on legitimate self by separating identity judgment from damaging response, staging the response through reversible checks, and preserving a self-protection invariant.
Supernormal Cue Guardrail Design	10	Prevent engineered cues from exceeding the range where a responder can regulate proportionate response.
Tension–Resolution Cycle Design	12	Deliberately build, bound, sustain, and resolve a temporary instability so the resolution’s value is earned by the preceding tension without turning anticipation into harm.
Termination Condition Design	0	Define explicit stop conditions so processes, searches, arguments, reviews, escalations, or recursive actions do not continue indefinitely.

Access-Conditioned Bundle Decoupling¶

Prevent access leverage from forcing unwanted bundled acceptance by testing necessity, unbundling separable conditions, and preserving meaningful refusal, alternatives, or remedies.

12 mechanisms · View full solution archetype

Access Dependency Heat Map — Ranks who is most exposed to an access tie — high dependence, few substitutes — so scrutiny, remedies, and unbundling effort land where refusal is least free.
Access-Condition Inventory Workshop — Surfaces every condition attached to a desired access — across contracts, interfaces, onboarding, renewals, and informal practice — into one reviewable list.
Appeal, Waiver, or Manual Access Channel — Gives an affected party a real route to contest, waive, or bypass a separable condition — and still reach essential access — while the tie is reviewed.
Bundle/Unbundle Menu — Presents the desired access and each attached condition as separately choosable, separately priced options, so a person can take what they need without the unrelated add-ons.
Coercion Safeguard Review — Tests whether an apparent acceptance is actually free — or is produced by dependence, scarce alternatives, authority pressure, or unacceptable loss on refusal.
Granular Opt-In Flow — Splits the single 'I agree' into separate, independently refusable consents, so accepting core access never silently carries optional data uses, communications, or add-ons.
Necessity/Proportionality Checklist — For each condition attached to access, forces a documented answer to whether it is truly necessary and whether a narrower or separable alternative would do — with a higher bar when the access is essential.
Purpose-Bound Security Condition Record — Records each security or safety condition that stays attached to access — its purpose, scope, evidence, expiry, and the less-restrictive alternatives weighed — and binds it to that purpose so a legitimate guardrail cannot quietly become an all-purpose leash.
Rebundling Drift Audit — Periodically re-checks a decoupled bundle to catch conditions that have crept back through defaults, pricing, renewal friction, degraded alternatives, or quiet policy edits.
Severability Clause and Review Rule — Builds in the right to sever or revise a disputed add-on condition — and a rule to revisit it — without collapsing the legitimate access or the whole relationship.
Standalone Base-Service Path — Guarantees a real, usable way to get the core thing on its own — at nonpunitive terms and without the optional conditions — so that refusing the add-ons is an actual option.
Take-It-or-Leave-It Term Audit — Stress-tests a nonnegotiable package for whether 'leave it' is a real choice — probing the affected party's dependency, hidden add-ons, excessive waivers, and the absence of any exit.

Archetype Overmatching Guardrail¶

Prevent familiar archetypes from being forced onto cases that only superficially resemble them.

10 mechanisms · View full solution archetype

Anti-Pattern Review — Checks the case against a catalog of the archetype's known look-alikes — situations that show the surface markers but carry a disqualifying feature — so a familiar-looking failure isn't mistaken for the pattern it mimics.
Case Comparison Matrix — Arrays the case's features against the candidate archetype and its nearest neighbors in one grid, so where the case actually lines up — and where it doesn't — is visible at a glance.
Counterexample Search Session — A time-boxed working session whose only job is to find cases that wore the same surface features yet turned out differently, testing whether the resemblance driving the match actually predicts the outcome.
Decision Confidence Label — Attaches a standardized confidence tag to the accepted match and ties each level to how far the decision may act, so a shaky pattern can't quietly license a confident action.
Differential Pattern Review — Holds the proposed archetype against its nearest rivals and asks which features would tell them apart, refusing the match until the evidence favors it over the alternatives.
Pattern Fit Checklist — Lists the structural features a named archetype requires and checks the case against them one by one, so a match must clear a fixed bar rather than a feeling of familiarity.
Pattern Fit Scoring Rubric — Scores a candidate match on weighted fit criteria to produce a graded degree-of-fit, turning 'it kind of resembles X' into a defensible number with its reasoning attached.
Precedent Distinction Memo — A short written record that names the precedent a case is being matched to and states, point by point, the material differences — so applying the precedent must survive an argument, not just an impression.
Red-Team Pattern Match Review — Assigns someone the explicit job of breaking the proposed match — arguing the case is not an instance of the archetype — so the pattern faces a dedicated adversary before it drives the decision.
Review Queue — Routes proposed archetype matches into review by stakes, holding the higher-consequence ones for scrutiny and escalation instead of letting every confident match act on itself.

Balance Preservation¶

Preserve a desirable balance by preventing one part, value, workload, demand, or pressure from overwhelming the others.

9 mechanisms · View full solution archetype

Balanced Scorecard Review — Tracks multiple value dimensions together so one metric, such as speed, cost, growth, or efficiency, does not silently overwhelm other required values.
Budget Balance Guardrail — Constrains spending or investment mix so immediate demand, favored categories, or politically salient projects do not consume all capacity.
Cap or Floor Rule — Sets maximum or minimum participation, budget, exposure, workload, risk, or representation levels to keep one element from dominating or disappearing.
Editorial or Deliberative Balance Rule — Ensures that relevant perspectives, issues, sources, or stakeholder positions are represented enough for a decision or publication to remain balanced.
Exception Expiry Marker — Attaches a deadline, review date, or reversal condition to justified temporary imbalances so exceptional concentration does not become permanent drift.
Redistribution Review — Reviews skew evidence and authorizes shifts in burden, resources, attention, authority, or representation when the balance band is exceeded.
Rotation or Turn-Taking Protocol — Alternates duties, speaking turns, attention, leadership, or scarce opportunities so repeated concentration does not harden into structural imbalance.
Skew Dashboard — Displays balance indicators such as load concentration, budget share, representation, attention share, or unresolved burden so imbalance becomes visible early.
Workload Rebalancing Routine — Periodically compares capacity and burden across teams, people, queues, or roles and moves work or support to prevent chronic overload.

Bounded Approximation¶

Use a simplified approximation when exactness is costly, while bounding the error enough for the decision.

8 mechanisms · View full solution archetype

Algorithmic Relaxation — Relaxes exact optimization or constraint satisfaction so a usable answer can be produced within time, computation, or information limits.
Back-of-Envelope Estimate — Produces a rough calculation quickly by using simplifying assumptions, rounded values, and transparent arithmetic to check scale or feasibility.
Policy Pilot — Treats a limited rollout as an approximate test of a broader policy or operational intervention.
Prototype Test — Uses a partial or low-fidelity implementation as an approximation of later system behavior.
Rough Order-of-Magnitude Estimate — Approximates by powers of ten or broad scale classes when exact values are unavailable or unnecessary.
Sensitivity Probe — Varies key assumptions or inputs to see whether the approximate conclusion changes materially.
Simplified Simulation — Simulates a reduced version of the system that captures enough behavior to guide the decision.
Surrogate Model — Uses a cheaper model to stand in for a more expensive, slower, or inaccessible model while tracking where the substitute is valid.

Branching and Merging¶

Allow parallel versions or lines of work to diverge safely and then recombine through explicit merge rules.

8 mechanisms · View full solution archetype

Collaborative Draft Merge Workflow — Combines divergent document, legal, curriculum, or design drafts by comparing edits, preserving rationale, and resolving incompatibilities.
Design Variant Merge Review — Evaluates parallel design tracks, selects compatible elements, and integrates them into a coherent design direction.
Integration Test Suite — Runs automated or structured tests to detect whether separately developed changes still work together after recombination.
Merge Conflict Board — Gives persistent cross-functional or cross-authority conflicts an explicit forum for resolution before integration.
Negotiation Redline Merge — Tracks divergent contract or agreement drafts and merges accepted language while surfacing unresolved conflicts.
Policy Pilot Reintegration Review — Reviews locally piloted rules or practices and decides which elements should be merged into the general policy baseline.
Pull Request or Merge Request — Creates a reviewable merge proposal with diffs, comments, approvals, checks, and an explicit integration decision.
Version-Control Branching Workflow — Implements branches, commits, diffs, merge commits, conflict detection, and history tracking for code, documents, data, or configuration.

Constraint Envelope Adjustment¶

Tighten, relax, or reshape the constraints defining a system's permissible action space to remove harmful freedom or restore needed flexibility.

0 mechanisms · View full solution archetype

No mechanism currently instantiates this archetype as its primary archetype.

Constraint Propagation and Decoupling¶

When constraints bind a problem into an unwieldy whole, propagate their implications first, then solve only the reduced and justified subproblems that remain.

6 mechanisms · View full solution archetype

Backward Deadline Pass — Propagates a deadline or milestone constraint backward through a task network to derive local windows and slack.
Constraint Dependency Matrix — Tabulates which constraints touch which variables, resources, tasks, or subsystems so propagation paths are visible.
Cut-Set or Separator Analysis — Identifies edges, variables, interfaces, or boundary conditions whose resolution separates the network into subproblems.
Domain Reduction Pass — Iteratively narrows possible values, options, quantities, or time windows by applying propagated constraints.
Gauge-Fixing Choice — Chooses a representative frame, normalization, baseline, or reference condition that removes redundant degrees of freedom.
Recomposition Consistency Test — Tests whether independently produced local solutions still satisfy the original global constraints when combined.

Context-Preserved Meaning Capture¶

Record what happened together with the contextual cues, meanings, roles, and observer notes that make the event interpretable later.

9 mechanisms · View full solution archetype

Analytic Memo — Captures the researcher's evolving interpretation in dated memos that keep observed evidence, participant meaning, and observer inference visibly separate.
Artifact Metadata Capture — Attaches provenance and setting to a captured artifact so the object stays interpretable once it leaves the moment it documents.
Codebook Loss Note — Records what a coding scheme discards when local categories are translated into external codes, so the loss travels with the coded data.
Contextual Inquiry Note — Captures situated work by observing a person in their own environment and asking why in the moment, preserving the roles and reasoning behind what they do.
Ethnographic Fieldnote Protocol — A disciplined routine for turning fleeting field observation into durable written record before memory flattens the scene.
Interpretation Recovery Review — Hands the record to someone who was not there and checks whether they can reconstruct its meaning without inventing the missing context.
Member Check Session — Takes provisional interpretations back to the people who were studied and asks whether the account rings true from the inside.
Observation Vignette Template — A fixed template for rendering one observed scene as a compact standalone narrative organized around why it mattered.
Scene-Setting Ledger — A structured checklist that inventories the setting of an observation — time, place, material environment, who was present, and what was notably absent.

Contradiction-Closure Proof¶

Prove a claim by showing that denying it makes the accepted system impossible or inconsistent.

9 mechanisms · View full solution archetype

Assumption Ledger — A running two-column register that keeps temporary assumptions apart from accepted premises and tags each derived line with what it depends on, so nothing sneaks into the conclusion.
Case-Split Elimination Table — Lays the supposition's exhaustive, mutually exclusive cases in a table and drives each row to contradiction, so the negation survives in no case and the claim closes.
Contradiction Search Checklist — A diagnostic list of the standard forms impossibility takes, run against a supposition to find, name, and validate a genuine contradiction rather than a mere surprise.
Minimal Unsat Core Analysis — Shrinks an unsatisfiable constraint set to a minimal subset whose members truly clash, so the impossibility is pinned to a few named premises rather than blamed on the whole system.
Natural Deduction Proof Tree — A rule-typed derivation in which every inference cites a named rule and the falsum node is reached, so the contradiction and its dependence on the assumption are mechanically visible.
Peer Proof Review — A human referee scrutinizes a finished indirect proof for scope drift, hidden premises, and circularity, and records whether a direct or constructive proof would serve better.
Proof Assistant Script — Encodes an indirect proof as code checked by a trusted kernel, so every inference and the discharge are mechanically verified and each classical axiom is forced into the open.
Reductio Proof Template — A fill-in-the-blanks scaffold for indirect proof: state the claim, assume its exact negation, drive to absurdity, then discharge the assumption to close the claim.
Unsatisfiability Certificate — A machine-checkable artifact showing the search for a satisfying model is exhausted with none found, certifying that no countermodel exists within the encoding.

Cross-Language Constraint Check¶

Check whether communication, interface, policy, or category assumptions survive movement across languages and communities before treating translation or localization as complete.

10 mechanisms · View full solution archetype

Back-Translation Review — Translates adapted content back into the source language to reveal meaning loss, added claims, altered obligations, or missing qualifications.
Bilingual Reviewer Panel — Uses reviewers with source and target language competence plus domain knowledge to detect false equivalence and missing local context.
Cross-Cultural Copy Review — Reviews examples, metaphors, idioms, politeness cues, cultural references, and tone for target-community interpretation and access risk.
Internationalization Check — Checks whether the underlying product or content system can support different scripts, text expansion, number/date formats, plural rules, sorting, and locale-specific conventions.
Language Accessibility Review — Checks whether target-language content is usable by intended audiences with different literacy levels, disabilities, education levels, or access channels.
Localization Review — Reviews a message, interface, form, policy, or document for target-language fit, nontransferable assumptions, and adaptation requirements before release.
Multilingual UX Audit — Evaluates whether interface text, layout, forms, navigation, errors, help content, and accessibility affordances work across language contexts.
Pseudo-Localization Test — Simulates text expansion, special characters, script variation, and layout stress to reveal interface assumptions before real translation.
Terminology Crosswalk Document — Documents source terms, target candidates, definitions, examples, non-equivalent cases, prohibited literal translations, and domain constraints.
Translation Testing — Tests whether translated outputs preserve intended meaning, required action, user rights, warnings, and operational consequences.

Decision-Procedure Boundary Mapping¶

Map whether a yes/no question can be decided by a finite total procedure before promising automation, certainty, or universal adjudication.

5 mechanisms · View full solution archetype

Decidability Triage Worksheet — Walks a team, at design time, through the questions that reveal whether a yes/no problem can be a real decision procedure — and where it can't, routes it to a declared fallback.
Decision-Procedure Specification — Pins down, in writing, the algorithm a decision rests on: exactly which inputs it accepts, what each output means, that it always halts, and why its answers are correct.
Fallback Mode Register — A living ledger of every case the procedure cannot cleanly decide, paired with the named fallback it is routed to — bounded search, heuristic, semi-decision, approximation, human review, or scope renegotiation.
Reduction Boundary Map — Locates a new yes/no question by mapping it onto problems whose difficulty is already known — decidable, undecidable, complete-for-a-class, or merely bounded — so you inherit the verdict instead of re-deriving it.
Termination & Totality Proof Review — Stress-tests a proposed procedure against two claims: that it halts for every input in scope, and that when it halts it returns one of the answers it is allowed to return.

Emergency Authority Activation and Constraint¶

Activate extraordinary authority only under defined crisis triggers, keep it bounded by scope, time, oversight, and audit, then force reversion when the emergency condition ends.

3 mechanisms · View full solution archetype

Crisis Declaration Protocol — The switch-flipping ritual that turns emergency mode on: verify the trigger is genuinely met, confirm the authorized declarer, stamp the moment, and broadcast it to everyone who must act on it.
Emergency Action Log — A contemporaneous, tamper-evident running record of every exceptional action taken while emergency mode is on — binding each act to its actor, authority, tier, and time so overreach can be told from justified response.
Emergency Authority Matrix — A pre-authored lookup table whose rows are severity tiers and whose cells say what powers each tier unlocks, how they are bounded, and which limits never relax at any level.

Entropy Export¶

Preserve local order by moving disorder, waste, ambiguity, heat, or cleanup burden across a boundary to a governed sink with visible accountability.

7 mechanisms · View full solution archetype

Archival Offloading Policy — Moves inactive-but-still-valuable records out of active systems into a governed archive with a named custodian, a retention-and-disposition clock, and a working retrieval path — so working space stays lean without the data being abandoned.
Chargeback or Quota System — Meters and prices each source's use of a shared sink — through internal chargebacks or hard quotas — so downstream burden lands back on the source's own ledger and stops feeling free.
Error Quarantine Queue — Diverts invalid, ambiguous, or risky items out of a trusted flow into a holding buffer at the trust boundary, where they wait to be inspected, replayed, or retired — protecting integrity without silently deleting the evidence.
Externalized Burden Register — A standing ledger that records what disorder was exported, where it went, who now bears its cost, and what obligation remains open — keeping exported burden traceable and its externalities visible after they cross the boundary.
Heat Dissipation Design — Engineers the physical route that carries heat out of protected equipment into a thermal sink, sized against the sink's real capacity so the escaping disorder never exceeds what the surrounding environment can safely absorb.
Outsourced Cleanup Contract — Binds a third-party sink owner, by contract, to remediate an exported burden to a defined standard and report back — so cleanup responsibility is transferred with legal teeth rather than merely dumped.
Waste Stream Protocol — Sorts residue by type at the point of export and routes each kind down its own defined handling path, so mixed waste is separated into governed streams instead of collapsing into a single undifferentiated dump.

Feasible-Alternative Comparator Calibration¶

Judge real options against reachable alternatives, not against perfection.

8 mechanisms · View full solution archetype

Best Feasible Alternative Test — Applies the rule that an option is validly rejected only if some feasible alternative beats it on net — not because it falls short of an ideal.
Comparison-Class Review Memo — Records, for a given decision, what comparison class each objection actually used and flags where a comparator drifted between aspiration, diagnostic, and decision roles.
Defect/Disqualifier Sort — Separates each shortfall into a residual defect to carry forward as a tradeoff versus a hard-constraint violation that genuinely disqualifies.
Feasibility Sensitivity Probe — Perturbs the feasibility and cost assumptions to see whether the winning option and its dominance ranking survive — or hang on one fragile estimate.
Feasible Option Inventory — Turns 'compared to what?' into an explicit, bounded list of the options that could actually be chosen or built under the real constraints.
Ideal Comparator Filter — Catches comparators that have smuggled in perfection and quarantines them, so a real option is never rejected for failing to match something no one could have chosen.
Shared-Burden Comparison Table — Forces every option onto the same dimensions under the same constraints, so none gets to be abstract and exempt from burdens the others carry.
Status Quo Costing Sheet — Refuses to treat 'do nothing' as free — prices the status quo as a real option with ongoing costs, residual risks, and forgone value.

Function-Without-Intent Caution¶

Avoid assuming that because something has a function, it was intentionally designed for that purpose.

8 mechanisms · View full solution archetype

Attribution Check — Prompts decision makers to separate current effect, original cause, actor intent, foreseeable harm, maintenance choices, and accountability claim.
Current Use Mapping — Maps current users, beneficiaries, maintainers, constraints, and harms so an originally unintended function is still evaluated for present-day consequences.
Design History Review — Examines design records, implementation decisions, roadmaps, and change logs to determine whether current use aligns with documented design intent.
Evidence Threshold Table — Defines what evidence is required for claims such as “intended,” “designed for,” “repurposed,” “emergent,” “negligently maintained,” or “functionally beneficial.”
Functional Analysis — Identifies what a pattern currently does for different actors or systems, while treating function as an observation rather than proof of intent.
Institutional Genealogy — Traces how a rule, practice, category, or institution developed over time so current function is not mistaken for original purpose.
Intent Audit — Reviews records, incentives, choices, and communications for evidence that a function was deliberately pursued or knowingly maintained.
Root-Cause Explanation Review — Checks whether a causal explanation has collapsed into a purpose-like story without specifying the mechanism that produced the observed function.

Geometric Primitives Vocabulary Constraint¶

Limit the available formal vocabulary to a small alphabet of primitive units, then create expressive range by composing, repeating, scaling, aligning, and transforming those units rather than adding new decorative forms.

7 mechanisms · View full solution archetype

Grid and Alignment System — A modular grid, spacing scale, and alignment framework that governs where primitives sit and how much room they get, producing rhythm and coherence without ever introducing a new form.
Icon Construction Template — A construction recipe — keyline grid plus a fixed build sequence — for drawing any new icon out of the primitive alphabet so the whole family stays visibly related.
Parametric Module Library — A library that generates allowed variants from primitive units and bounded parameters.
Primitive Grammar Style Guide — The governing rulebook for a primitive vocabulary — the composition grammar, palette and cross-domain rules, and the process for admitting new variants that turn a set of approved forms into an enforceable design language.
Primitive Sufficiency Review — A structured test of whether the current primitive alphabet and grammar can express every distinction the work actually requires — before scarcity forces a one-off exception.
Shape Alphabet Sheet — A reference artifact showing approved primitive forms, allowed variants, and disallowed near-forms.
Vocabulary Drift Audit — A recurring review that checks whether shipped artifacts still obey the approved primitive grammar, or have quietly drifted back toward one-off forms.

Guarded State Transition¶

Allow state changes only when defined preconditions, invariants, or authority requirements are satisfied.

0 mechanisms · View full solution archetype

No mechanism currently instantiates this archetype as its primary archetype.

Hidden Path Discovery¶

Search for non-obvious routes around barriers that appear impossible from the ordinary path.

8 mechanisms · View full solution archetype

Analogical Path Transfer — Imports a route structure that already works in another domain, then tests whether the two problems share the deep structure the transfer relies on before adopting it.
Clinical Alternative Pathway Review — When a standard care pathway is contraindicated or unavailable, reviews evidence-based alternatives against the patient's therapeutic goal and their path-specific risks, then selects a safe substitute.
Indirect Negotiation Route — Reopens a socially deadlocked issue by routing it through a trusted intermediary and a changed sequence rather than head-on, while guarding against coercion or exclusion and holding a fallback in reserve.
Lateral Reframing Workshop — A facilitated session that changes the framing, scale, or actor boundary of a stuck problem to make non-obvious routes visible, then harvests multiple candidate paths.
Legal or Regulatory Pathway Search — Classifies which constraints in a rule system are absolute versus procedurally waivable, then finds a legitimate alternative pathway — waiver, exemption, or demonstration route — that respects the rule's purpose.
Route-Finding and Topology Search — Maps the network, space, or dependency graph as a topology and searches it for a route around a blocked edge, keeping a fallback path in reserve.
Sandbox or Pilot Pathway — Runs a candidate hidden path inside a bounded, reversible enclosure with a limited blast radius, so its feasibility can be measured before the full system is exposed to it.
Workaround Discovery — Surfaces an improvised route that keeps a blocked process delivering its essential function, then integrates the informal fix into sanctioned practice before it hardens into a shadow process.

Invariant Guarding¶

Identify conditions that must always remain true and guard operations so those invariants are preserved.

8 mechanisms · View full solution archetype

Contract Check — Attaches preconditions, postconditions, and state assumptions to a boundary and evaluates them at runtime, so a transition is refused the moment it would break the contract.
Database Constraint — Encodes a record invariant — uniqueness, referential integrity, a balance rule — directly in the data schema so the store itself rejects any write that would break it.
Integrity Monitor — Watches live state for violations, near misses, and bypasses and records them, surfacing invariant breaks that slipped past the guards so they can be governed.
Invariant Test Suite — Expresses declared properties as executable assertions and exercises common, rare, and regression cases offline, so a change that would break the invariant fails before it ships.
Policy Guardrail — Routes, refuses, or demands evidence for decisions that might violate a rule, right, or separation-of-duties requirement, with scoped exceptions and a named owner.
Rollback Transaction — When a change fails its invariant check partway through, returns the system to a known-good state instead of leaving a partial or invalid result committed.
Safety Interlock — Makes a hazardous action physically impossible unless every enabling safety condition is true, holding the system in a safe default state until they are.
Two-Person Rule — Requires two authorized people to independently confirm a high-risk transition before it proceeds, so no single actor can break the invariant alone.

Irreversible Commitment Management¶

Treat irreversible actions differently by adding prevention, deliberation, staging, consent, and compensation logic before commitment.

9 mechanisms · View full solution archetype

Destructive Action Confirmation — Inserts deliberate friction at the exact instant of an unrecoverable action, showing the operator what will be destroyed and forcing a conscious confirmation before the point of no return.
Environmental Impact Gate — Blocks a habitat-altering project until its ecological and community consequences are scoped, independently reviewed, and paired with a binding mitigation plan before ground is broken.
Informed Consent Protocol — Ensures the person who will bear an irreversible effect understands its permanence and alternatives, voluntarily authorizes it, and has that authorization recorded as the basis for the commitment.
Irreversible Deployment Gate — A blocking pre-release checkpoint that refuses to run a one-way production action until its rollback residue is assessed and the true point of no return is marked and acknowledged.
Legal Finality Review — A pre-signature review that tests exactly which rights, claims, and future options a legal instrument surrenders forever, routes high-finality ones to independent counsel, and records the basis for signing.
Major Migration Approval Workflow — Sequences a large one-way migration into approved waves, gating each wave behind rollback-residue assessment and accountable sign-off so the whole system is never cut over at once.
Remediation or Compensation Plan — Names and assigns the residual obligations owed for harm that cannot be undone — restitution, repair, aftercare, and ongoing monitoring — so accountability survives after the irreversible act.
Sandbox Simulation or Pilot — Buys knowledge about an irreversible action without incurring its finality — by rehearsing it in a replica or a bounded low-stakes trial where mistakes carry no permanent exposure.
Staged Rollout or Canary Release — Exposes a risky change to a small live cohort first, watches monitored signals, and widens only if they stay healthy — so real-world blast radius is capped while evidence accrues.

Latent Capacity Release Design¶

Remove a suppressing constraint in bounded stages so latent capacity can emerge without uncontrolled rebound, externality, or destabilization.

8 mechanisms · View full solution archetype

Adaptive Reconstraint Protocol — A live feedback rule that re-imposes the released constraint — fully or partially — the moment monitored rebound crosses a trigger, then logs the episode to tune the next release.
Pilot Constraint Lift — Lifts the suppressing constraint on one small, real slice of the system to measure whether the hypothesized latent capacity actually emerges — attributed against matched controls.
Post-Release After-Action Review — A structured backward-looking review held after a release completes — comparing what was predicted to what happened and converting the gap into a reusable lessons record.
Progressive Threshold Raise — Turns a single quantitative limit upward in small, feedback-gated increments — each step held until the system settles and cleared of overshoot before the next raise.
Release Timing Gate — Decides WHEN a release may proceed by testing a conjunction of readiness preconditions against the live window — holding until conditions align, not merely until a date arrives.
Sandbox Release Trial — Rehearses the full constraint release inside an isolated, non-production replica so rebound, overshoot, and externalities can be provoked and the rollback path proven — with zero real-world exposure.
Staged Rule Relaxation — Removes a categorical rule one clause at a time in a planned sequence — decomposing the constraint into separable permissions and lifting the safest, most reversible first.
Temporary Safeguard Net — Erects a temporary backstop that absorbs the harms of release while the system finds its new equilibrium — sized to the reviewed harms, and withdrawn once the system self-stabilizes.

Necessary-Condition Closure Design¶

Make all non-substitutable success conditions explicit, verify each one, and treat the weakest missing condition as the blocker rather than averaging it away.

10 mechanisms · View full solution archetype

All-Conditions Checklist — Operationalizes the necessary-condition set as a checklist where every hard requirement must be satisfied or handled explicitly.
Blocker Register — Records missing, weak, unknown, stale, or waived conditions and their decision path.
Condition Coverage Test Suite — Tests whether declared conditions hold across relevant cases, sites, configurations, or environments.
Dependency Closure Map — Maps upstream ownership and dependencies for every necessary condition.
Go/No-Go Condition Review — Reviews each hard condition independently before proceeding with a high-consequence action.
Limiting-Factor Board — Displays the current binding condition or shortest required input and tracks remediation.
Preflight Review — Runs a time-sensitive all-condition check before a high-consequence action.
Readiness Gate Scorecard without Averaging — Displays condition status without collapsing hard blockers into a composite score.
Red-Team Precondition Challenge — Challenges omitted, assumed, unverifiable, or falsely green preconditions before commitment.
Weakest-Link Postmortem — Traces a failure to the absent or weakest necessary condition and updates the condition set.

Nonactivating Occupancy Blockade¶

Block an unwanted trigger by safely occupying the recognition site with a nonactivating substitute that denies access without producing the response.

8 mechanisms · View full solution archetype

Active-Site Inhibitor — Places a blocker at an active site to prevent substrate occupation and transformation.
Competitive Receptor Antagonist — Uses a nonactivating ligand to occupy a receptor so an agonist cannot trigger the downstream response.
Confirmation Interstitial Hold — Holds a potentially destructive action in a reversible non-submitting state until explicit release or cancellation.
Decoy Sink Endpoint — Provides a nonproductive endpoint or route that absorbs unwanted requests without executing the protected function.
Defensive Identifier Reservation — Reserves a name, domain, handle, package, slot, or identifier so a harmful claimant cannot occupy it later.
Maintenance Hold or Dummy Slot — Places an inert hold in a schedule, queue, or resource calendar to block unsafe activation during a protected window.
Mutex or Lock Token — Uses an exclusive token or lock to occupy a resource-control point until safe release.
Precommitment Blocker — Occupies a future cue, routine, or choice slot with a voluntary safe commitment.

Physical-Constraint Design for Impossibility¶

Make the wrong action physically impossible, materially rejected, or harder than the correct action.

0 mechanisms · View full solution archetype

No mechanism currently instantiates this archetype as its primary archetype.

Reflexive Rule-Binding Governance¶

Keep authority inside the rule system by making every actor, enforcer, exception, and rule-change path subject to stated rules.

10 mechanisms · View full solution archetype

Amendment and Notice Protocol — Forces every change to a rule through a fixed, published pathway with advance notice, so rules cannot be quietly rewritten mid-case or applied backward.
Emergency Powers Sunset Clause — Grants extraordinary authority only with a built-in expiry date, so an emergency power dies automatically unless it is openly re-authorized.
Equality Before Rules Test — Probes whether the same rule produces the same outcome across identity, rank, and status — including for the powerful — by comparing matched cases that differ only in who the actor is.
Independent Review Board or Court — Stands up a body structurally separate from the rule-maker that can hear challenges, judge the authority against its own rules, and issue a binding ruling the authority cannot itself overturn.
Policy-as-Code Guardrail — Compiles the rules into an automated check that every action must pass at execution time, so even privileged operators and self-modifying processes cannot act outside the rule without a signed, logged exception.
Public Rule Registry — Maintains a single authoritative, openly readable catalog of the operative rules and exactly who they govern, so the rule in force is knowable in advance rather than held privately by the enforcer.
Recusal and Conflict Screening — Checks each decision-maker for a personal stake in the matter before they act, and removes the conflicted one from the decision, so the enforcer is held to the same impartiality standard they impose on others.
Rule Application Audit Log — Records, for every action taken, which specific rule authorized it and who invoked it — including the actions of the powerful — leaving a reviewable trace that no decision was rule-free.
Supremacy Clause — Declares, in the founding rule itself, that the rules outrank and bind every entity inside a named domain — expressly including the rule-makers and enforcers — so no actor holds standing authority above them.
Waiver Register — Keeps a standing, public ledger of every exception, waiver, and override granted against the rules — who got it, on what authority, and for how long — so deviations are visible and countable rather than quiet favors.

Self-Targeting Defense Guardrail¶

Keep defensive power from turning on legitimate self by separating identity judgment from damaging response, staging the response through reversible checks, and preserving a self-protection invariant.

10 mechanisms · View full solution archetype

Appeal and Rapid Restoration Workflow — Gives a wrongly-engaged legitimate party a fast, independent path to contest the action and have the harm reversed before it hardens into permanent loss.
Engagement Kill Switch — A single, always-reachable control that halts an in-progress defensive response the moment it is caught engaging protected self, before the damage spreads further.
False-Positive Harm Budget Dashboard — Meters the running cost of wrongful self-engagements against a pre-set allowance, weighting each by harm intensity, so the defense's autoimmune damage is priced and capped.
Graduated Response Matrix — A lookup table that maps classifier confidence and self-status ambiguity against response harm, so uncertain judgments are routed to weaker, more reversible actions.
Post-Incident Autoimmune Review — Treats each confirmed false self-engagement as a coupled classifier-actuator design failure and feeds it back into thresholds, self-boundaries, and permissions.
Protected-Self Allowlist with Expiry — A maintained registry of known-legitimate self entities that shields them from defensive harm, with mandatory expiry so stale entries cannot outlive their trust.
Quarantine-Before-Destroy Rule — A hard rule that any destructive defensive action must first pass through a reversible holding step, so a false positive is recoverable instead of permanent.
Self-Status Cross-Check — Before acting on a threat flag, independently corroborates whether the target is really protected self using signals disjoint from the classifier that raised the alarm.
Shadow Mode and Canary Enforcement — Runs a new or changed defense in observe-only shadow, then on a small canary slice, measuring would-be self-engagements before it is trusted to act at full scale.
Two-Key High-Harm Engagement — Requires two independent authorities to concur before an irreversible defensive action fires, so no single classifier or operator can unilaterally harm protected self.

Supernormal Cue Guardrail Design¶

Prevent engineered cues from exceeding the range where a responder can regulate proportionate response.

10 mechanisms · View full solution archetype

Context Reinsertion Prompt — Shows the cost, quantity, source, delay, or comparison baseline a cue strips away, placing the missing information right beside the cue that would otherwise dominate the response.
Cue Intensity Cap Protocol — Sets a maximum allowed value for how strong a single cue may be — its salience, urgency class, sensory loading, or social-proof prominence — measured against a calibration range.
Cue-Hijack Red-Team Review — Tasks an adversarial reviewer with actively finding ways a design could capture attention, appetite, fear, or reward-seeking beyond user intent, focusing on vulnerable slices.
Default-Off High-Stimulation Setting — Keeps especially vivid, autoplaying, variable-reward, or urgent cue modes switched off out of the box, so they turn on only when a user or governing actor intentionally enables them.
Frequency Cap and Cooldown — Limits how many times a cue may be shown in a window and inserts a quiet period before it can be repeated, refreshed, or re-escalated.
High-Arousal Content Throttle — Reduces the distribution, ranking boost, or autoplay escalation of live content whose cue profile provokes disproportionate arousal relative to its substantive value.
Recovery Interval Enforcement — Makes the system compel the responder to rest after high-intensity cue contact — enforced session stops, rotation, or exposure spacing that the user cannot simply dismiss.
Salience Normalization Test — Compares decisions made under amplified versus normalized cue presentation to measure whether a choice depends on exaggerated salience rather than substantive value.
Supernormal Cue Audit — Systematically reviews a product, environment, or interface against a checklist of known cue channels, flagging any that exceed a natural or validated calibration range.
Variable-Reward Schedule Limit — Restricts intermittent, surprise, or loot-like reward loops when their unpredictability is what drives compulsive checking, redirecting toward predictable or earned reinforcement.

Tension–Resolution Cycle Design¶

Deliberately build, bound, sustain, and resolve a temporary instability so the resolution’s value is earned by the preceding tension without turning anticipation into harm.

12 mechanisms · View full solution archetype

Adaptive Release-Timing Protocol — Releases the resolution at the adaptively-chosen moment — reading live anticipation and readiness rather than a fixed schedule — so the payoff lands when tension has peaked but before it curdles.
Cadence Break and Restoration — Establishes a steady rhythm, deliberately breaks it to open a tension, then restores the cadence so the return itself is the resolution.
Countdown and Completion Cue — Makes anticipation visible and bounded with a ticking countdown toward a known moment, and marks the finish with an unmistakable completion cue.
Harmonic Suspension and Resolution — Creates a felt instability by suspending an expected resolution, then discharges it with a resolving move so the arrival feels earned.
Post-Resolution Debrief — After the cycle closes, tests whether the resolution's value was actually earned by the preceding tension — and feeds that verdict into how future cycles are spaced.
Productive-Struggle Pause and Reveal — Holds people in a bounded, productive struggle — capped so it never tips into demoralization — before the reveal, so the answer lands on prepared ground.
Progressive Reveal Sequence — Unveils a whole in an ordered run of partial disclosures, so each reveal pays off the last hold and opens the next.
Real-Time Dropout or Distress Monitor — Watches the audience live for the moment productive tension tips into disengagement or genuine distress, so the cycle can be eased or aborted before it harms.
Staged Commitment Release — Delivers the resolution as a sequence of gated, reversible increments, so each stage locks in value and can be halted before the next is risked.
Tension-Curve Rehearsal — Runs the planned tension curve in a sandbox on stand-in audiences first, to find where it drags, breaks, or fails to pay off before it goes live.
Tension-Curve Storyboard — Lays out the intended arc — baseline, rising beats, peak, release, aftermath — as a panel-by-panel plan before anything is built or run.
Unresolved-Question Hold — Poses a question and deliberately refuses to answer it, holding the open loop at the right intensity until its answer will land hardest.

Termination Condition Design¶

Define explicit stop conditions so processes, searches, arguments, reviews, escalations, or recursive actions do not continue indefinitely.

0 mechanisms · View full solution archetype

No mechanism currently instantiates this archetype as its primary archetype.