Skip to content

Governance & Accountability

← Back to Mechanisms by Solution Family

Solutions that allocate decision rights, oversight, responsibility, transparency, and consequences so power remains answerable and action-owned.

317 mechanisms across 36 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 archetypeMechanismsDescription
Accountability Chain Design6Trace responsibility from action or decision to owner, record, answerability forum, and repair consequence.
Adjudication Process Design8Resolve disputes by applying defined standards to evidence through an impartial process with remedy and review.
Alignment Governance and Dispute Resolution6Stabilize multi-actor systems by giving misalignments a legitimate forum, clear authority boundaries, and escalation/resolution paths before conflicts cascade.
Authority Legitimacy and Consent Foundations7Make authority acceptable by grounding it in a clear mandate, scoped consent or representation, demonstrated competence, fair process, and accountable review.
Authority Rotation and Term Limitation8Limit and rotate authority so power remains attached to a role, mandate, or process rather than consolidating around a person or faction.
Autonomous Action Zone Protection6Protect a bounded zone where a legitimate actor can make and execute in-scope decisions without needing permission from outside authorities.
Bounded Discretion Governance11Turn unavoidable rule gaps into accountable judgment spaces with clear purpose, boundaries, criteria, records, review, and drift controls.
Checks-and-Balances Architecture8Distribute power so one actor’s authority can be reviewed, limited, corrected, or blocked by another when unilateral action would create overreach risk.
Coercive Leverage Governance11Use explicit, bounded consequences to reshape another actor's choice set while preserving legitimacy, proportionality, verification, and an exit from coercive pressure when conditions are met.
Collective Memory Curation13Curate what a collective remembers, how it is contextualized, who may contest it, and when it must be revisited so memory supports identity and accountability without becoming erasure, propaganda, or an unusable archive.
Commitment Lifecycle Governance7Turn an intention or assertion into a safe basis for reliance by defining what is bound, who owns it, why it is credible, how performance is verified, how change is communicated, and how the commitment ends.
Commons Governance4Govern shared resources so individually rational use, neglect, or pollution does not destroy collective viability.
Conditional Authority Envelope Design8Give actors advance permission to act inside known conditions, with explicit limits, escalation triggers, and after-action accountability.
Conflict-of-Interest Mitigation9Prevent competing interests from compromising entrusted judgment through timely disclosure, independent assessment, proportionate mitigation, recusal or structural separation, verification, and remedy.
Decision Commitment and Closure9Close deliberation responsibly by naming the choice, authority, evidence threshold, reversibility, forgone alternatives, execution handoff, and conditions for reopening.
Decision Rights Clarification5Clarify who has authority to decide what, under which constraints, with which escalation paths.
Dependency Exposure12Reveal hidden dependencies so risks, obligations, failure paths, and coordination needs become visible before they cause failure.
Equity Adjustment7Adjust rules, resources, supports, or access conditions to account for materially different starting conditions or barriers.
Escalation Exit Gate5Define independent exit criteria before sunk costs make continuation feel obligatory.
Functional Vacancy Backfill12Treat an occupied but inactive authority role as functionally vacant once observable nonperformance thresholds are met, and activate bounded backfill channels.
Governance Exception Management12Govern departures from standing rules through explicit grounds, accessible review, reasoned and scoped decisions, expiry, cross-case monitoring, and feedback that changes a rule when exceptions reveal the baseline is wrong.
Informed Consent Governance9Ensure agreement is informed, voluntary, specific, revocable where appropriate, and granted by someone with authority to consent.
Mandatory / Default Rule Design9Decide which rules must bind, which should guide by default, and which require opt-out or exception paths by testing harm, rights, reversibility, information, heterogeneity, and enforcement capacity.
Network Effect Governance14Govern self-reinforcing network growth so shared value does not become harmful lock-in, exclusion, concentrated power, abuse, or systemic fragility.
Normative Assumption Explicitness8Make value judgments and ought-claims explicit before treating them as neutral facts.
Outcome Responsibility Attribution Calibration12Assign credit or blame only after separating outcome, causal contribution, control, duty, knowledge, and uncertainty.
Outside-Authority Influence Channel Mapping7Protect sovereignty by mapping how outsiders can still shape decisions through money, information, access, dependencies, relationships, reputation, or pressure despite lacking formal authority.
Procedural Fairness Design8Design decision processes so affected parties receive meaningful notice, voice, impartial treatment, evidence handling, reasons, and a path for review or remedy.
Proportionality Calibration7Scale response, restriction, remedy, or sanction to the severity, necessity, risk context, and affected interests of the case.
Reciprocity Protocol Design8Structure mutual obligations so exchange, cooperation, and trust remain balanced over time.
Regress Termination Rule10Set a principled stopping point for chains of justification, explanation, authority, or delegation so action can proceed without hiding foundational assumptions.
Responsibility Assignment for Action9Assign clear responsibility when group presence would otherwise diffuse action.
Rights–Freedoms Obligation Mapping8Map every asserted right or freedom to its bearer, counterpart relation, scope, justification, conflict, and remedy before deciding what must be protected, provided, permitted, restrained, or reviewed.
Shared or Not Yet Assigned2Mechanisms shared across, or not yet assigned to, a single primary solution archetype.
Traceability Linking7Create explicit links from sources, requirements, decisions, actions, or artifacts to their downstream consequences or implementations.
Transparency for Accountability16Expose who decided what, under which authority, using which reasons and evidence, with visible limits, questions, corrections, and remedy so disclosure produces accountability rather than noise.
Workaround Governance9Govern recurring deviations by learning why they exist, classifying their value and risk, and choosing a bounded path to formalize, tolerate, redesign, or eliminate them.

Accountability Chain Design

Trace responsibility from action or decision to owner, record, answerability forum, and repair consequence.

6 mechanisms · View full solution archetype

  • Accountability Matrix — Maps decisions, roles, accountable owners, contributors, consulted parties, and informed parties so responsibility is visible before action occurs.
  • Answerability Review Meeting — Creates a recurring or event-triggered forum where owners explain decisions, reviewers test reasoning, and repair commitments are assigned.
  • Corrective Action Register — Tracks repair tasks, responsible owners, due dates, dependencies, verification evidence, and closure status.
  • Escalation Record — Documents when an issue exceeded local authority, who escalated it, who accepted it, and what follow-up commitments resulted.
  • Incident Ownership Protocol — Assigns an incident owner, response authority, communications duty, repair tracking, and post-incident answerability process.
  • Postmortem Action Tracking — Turns lessons from an incident, failure, dispute, or review into assigned corrective actions with deadlines and closure checks.

Adjudication Process Design

Resolve disputes by applying defined standards to evidence through an impartial process with remedy and review.

8 mechanisms · View full solution archetype

  • Appeal or Review Window — Creates a bounded opportunity to challenge the decision based on specified review grounds.
  • Arbitration-like Process — Assigns an external or agreed decision maker to resolve a dispute under defined standards.
  • Disciplinary Board Review — Determines whether conduct violated a standard and what proportionate response or repair should follow.
  • Evidence Docket — Collects, organizes, timestamps, and bounds the evidence considered by the decision maker.
  • Grievance Panel — Uses multiple reviewers to assess a complaint, apply policy, and recommend or issue a remedy.
  • Hearing Process — Creates a live or asynchronous occasion to present evidence, respond to claims, and test contested accounts.
  • Moderation Appeal Process — Reviews contested platform enforcement decisions using evidence, rules, reasons, and remedy options.
  • Written Decision Notice — Communicates findings, standard applied, reasoning, remedy, and review options to relevant parties.

Alignment Governance and Dispute Resolution

Stabilize multi-actor systems by giving misalignments a legitimate forum, clear authority boundaries, and escalation/resolution paths before conflicts cascade.

6 mechanisms · View full solution archetype

  • Conflict Register — A living ledger of every raised misalignment and its lifecycle — one row per dispute tracked to closure, with recurrence flagged and resolved cases retained as searchable precedent.
  • Dispute Intake Form — A structured entry template that turns a raised grievance into a complete, routable case at the moment of filing — capturing the issue, the parties and their standing, the decision sought, evidence, and urgency.
  • Escalation Threshold Table — A pre-agreed rule table that maps observable conditions — blast radius, cost, precedent weight, contested authority, time pressure — to the level of forum that must handle a dispute, with a top row that trips an emergency override.
  • Governance Cadence Meeting — A recurring, fixed-rhythm forum where affected parties, evidence, and shared criteria meet on a schedule, giving routine misalignments a known place and time to be decided.
  • Review Board or Panel — An empaneled body chartered with a defined mandate and staffed for independence, convened to adjudicate a specific case or class of cases with authority and impartiality the routine forum lacks.
  • Ruling or Decision Memo — The written record that closes a dispute — stating what was decided, by whom, on what authority, with what reasoning, dissent, and obligations — and opens the timebound route to appeal it.

Make authority acceptable by grounding it in a clear mandate, scoped consent or representation, demonstrated competence, fair process, and accountable review.

7 mechanisms · View full solution archetype

  • Appeal or Review Forum — Provides a place where stakeholders can contest decisions, boundary drift, procedural defects, or conflicts of interest.
  • Charter or Mandate Document — Codifies the decision rights, scope, source of authority, and revision conditions for a role, body, project, or institution.
  • Consent Capture and Revocation Workflow — Records what has been agreed to, under what scope, and how consent can be renewed, limited, or withdrawn where appropriate.
  • Credentialing and Peer Review Process — Operationalizes competence-based authority by testing, certifying, or reviewing the decision-maker's relevant expertise.
  • Legitimacy Health Dashboard — Tracks signals of legitimacy erosion such as complaints, appeals, opt-outs, noncompliance, distrust, or jurisdictional disputes.
  • Participatory Consultation Process — Creates structured opportunities for affected parties to be heard before authority is exercised or renewed.
  • Public Reason-Giving Protocol — Requires decisions to include reasons, evidence, constraints, and appeal information so authority remains legible.

Authority Rotation and Term Limitation

Limit and rotate authority so power remains attached to a role, mandate, or process rather than consolidating around a person or faction.

8 mechanisms · View full solution archetype

  • Entrenchment Audit — Tests, after a handover, whether authority actually moved — probing for the shadow signals that show the old holder still runs the role in everything but name.
  • Fixed Term-Limit Clause — Writes a hard ceiling on cumulative tenure into the founding rules, so an office empties on schedule no matter how popular or entrenched its holder.
  • Handover Briefing and Transition File — Packages the open decisions, obligations, and tacit context of a departing authority into a transferable record and live briefing, so the role turns over without the institution restarting.
  • No-Consecutive-Terms Rule — Bars a holder from serving back-to-back terms, forcing at least one intervening holder before they may return, so the seat cannot be occupied continuously by the same person.
  • Rotating Chair Schedule — Passes a single high-discretion role — the chair, the convener, the agenda-setter — around a group on a published order, so no one member controls it for long.
  • Sortition or Lottery Rotation — Fills the role by random draw from a defined eligible pool, replacing contested selection with a lottery whose fairness is the source of its legitimacy.
  • Staggered Board-Term Calendar — Offsets the terms of many seats so only a fraction turn over at each interval, renewing a governing body continuously instead of resetting it all at once.
  • Sunseted Delegation Order — Grants authority with an expiry built in — a delegated or emergency power that lapses automatically when its triggering condition ends, so temporary control cannot harden into permanent.

Autonomous Action Zone Protection

Protect a bounded zone where a legitimate actor can make and execute in-scope decisions without needing permission from outside authorities.

6 mechanisms · View full solution archetype

  • Access and Credential Partition — Gives the autonomous actor independent access to tools and resources while blocking outsiders from routine unilateral override.
  • Autonomy Service-Level Agreement — Commits support functions to provide resources, approvals of infrastructure, and response times without converting support dependencies into authority dependencies.
  • Chartered Autonomy Mandate — Encodes the zone, internal authority, non-interference rule, exception thresholds, and accountability route in a charter, policy, constitution, bylaws, or mandate.
  • Emergency Override Protocol — Allows temporary external intervention only when predefined harm, rights, safety, legal, or systemic thresholds are met.
  • Post-Action Audit Trail — Records in-scope decisions, reasons, outcomes, and boundary claims for retrospective accountability rather than pre-approval.
  • Sovereignty Breach Report Channel — Lets actors report external interference, hidden vetoes, unauthorized preclearance demands, or insider overreach beyond the zone.

Bounded Discretion Governance

Turn unavoidable rule gaps into accountable judgment spaces with clear purpose, boundaries, criteria, records, review, and drift controls.

11 mechanisms · View full solution archetype

  • Appeal and Reconsideration Workflow — A defined route for an affected party to contest a discretionary decision and have it independently re-examined — with a good-faith safe harbor that shields sound judgment from being punished for an unlucky outcome.
  • Calibration Review Cycle — A recurring session where several decision-makers judge shared cases, compare results, and reconcile divergence — keeping their reading of the criteria aligned so like cases stay treated alike.
  • Case Rationale Form — A per-decision template that captures the case facts, the reasons for the judgment, and why the response was proportionate — turning a discretionary call into a reviewable record.
  • Comparator Case Library — A searchable store of past decided cases — facts, outcomes, and reasons — so a new discretionary call can be checked against, and kept consistent with, how like cases went before.
  • Discretion Audit Dashboard — An aggregate view of how discretion is actually being used across deciders and over time — surfacing drift, outliers, and consumption against caps before individual calls harden into a pattern.
  • Discretion Matrix — Maps each kind of case to how much latitude the decision-maker has — the outer limits, the hard prohibitions, and the point where the case must be handed up.
  • Exception Review Board — A standing panel with delegated authority that decides the hard, boundary-testing cases escalated to it — so the toughest exceptions are owned by a reviewable body, not made alone under pressure.
  • Guideline-with-Reasons Manual — The written doctrine that states why a discretion exists and which criteria to weigh — each paired with its reason, so judgment can extend faithfully to cases no rule anticipated.
  • Peer Case Conference — A recurring room where peers talk through live cases together — aligning judgment and building shared precedent in real time, through deliberation rather than a scorecard or an archive.
  • Structured Professional Judgment Tool — A structured instrument that walks one decider through a fixed set of factors and the case's own facts to reach a defensible, proportionate judgment — structured, but deliberately not reduced to a formula.
  • Waiver or Override Log — A running ledger of every time a rule or control was waived or overridden — what limit was crossed, by whom, and how often — so exceptions stay counted, capped, and impossible to quietly forget.

Checks-and-Balances Architecture

Distribute power so one actor’s authority can be reviewed, limited, corrected, or blocked by another when unilateral action would create overreach risk.

8 mechanisms · View full solution archetype

  • Audit Committee — A committee that reviews controls, records, risks, compliance evidence, or audit findings independent from operations.
  • Compliance Review — A structured check against governing standards, policies, laws, controls, or risk requirements.
  • Dual Approval — A workflow requiring two distinct approvals before a high-risk action can proceed.
  • Independent Review — A review conducted by an actor not controlled by the decision-maker or operating unit under review.
  • Maker / Checker Separation — A role design separating the actor who creates or initiates an action from the actor who verifies or approves it.
  • Oversight Board — A standing body with authority to review, question, recommend, reverse, or escalate actions by another actor.
  • Red-Team Challenge — A deliberate adversarial or skeptical review that probes assumptions, misuse routes, blind spots, or failure modes.
  • Veto Authority — A defined power to block, delay, or require revision of an action under specified conditions.

Coercive Leverage Governance

Use explicit, bounded consequences to reshape another actor's choice set while preserving legitimacy, proportionality, verification, and an exit from coercive pressure when conditions are met.

11 mechanisms · View full solution archetype

  • Access Suspension or Permission Revocation — Withholds a privilege the target relies on — access, participation, standing — as a temporary, reversible consequence that lifts the moment a defined condition is met.
  • Audit and Enforcement Workflow — The adjudication engine that collects evidence, tests whether the condition is truly met and the consequence warranted, applies it consistently, and records the review so decisions can be checked.
  • Compliance Deadline Notice — A formal, on-the-record warning that states the required action, the evidence that will satisfy it, the consequence, and the deadline — giving the target a fair, time-boxed chance to comply before pressure escalates.
  • Conditional Release or Off-Ramp Protocol — The defined pathway by which a target under pressure earns its way back — through verified compliance, restitution, or a negotiated transition — so coercion always has a reachable exit.
  • Contract Penalty or Remedy Clause — Writes the consequences of breach into a binding agreement in advance — remedies, damages, holdbacks, termination rights — so the leverage is credible, pre-agreed, and bounded before any dispute.
  • Diplomatic or Trade Sanctions Framework — Applies conditional restrictions on a collective actor — a state, bloc, or organization — tied to a legitimate objective, anchored in shared authority, scoped to limit collateral harm, and built to de-escalate when conditions are met.
  • Graduated Sanction Matrix — A published, tiered schedule that maps violation severity, repetition, and remedy status to a bounded, proportionate consequence — so escalation is rule-governed rather than improvised.
  • Platform Moderation Strike System — Running software that detects rule violations, records strikes against a specific account, escalates restrictions as strikes accumulate, and gives the user notice and a route to appeal.
  • Regulatory Fine or License Condition — Backs a compliance demand with the force of law — a statutory fine or a condition on the license to operate — so the consequence is credible because a legitimate public authority stands behind it, and bounded because that same mandate limits it.
  • Restorative Compliance Agreement — A negotiated written path back — it names the repair owed to those harmed, the support needed to build real compliance, and the terms on which the consequence is retired and standing restored.
  • Safety Boundary Lockout — An automatic interlock that withholds access to a hazardous capability the instant an unsafe condition is detected, and releases only when the required safeguard is restored.

Collective Memory Curation

Curate what a collective remembers, how it is contextualized, who may contest it, and when it must be revisited so memory supports identity and accountability without becoming erasure, propaganda, or an unusable archive.

13 mechanisms · View full solution archetype

Commitment Lifecycle Governance

Turn an intention or assertion into a safe basis for reliance by defining what is bound, who owns it, why it is credible, how performance is verified, how change is communicated, and how the commitment ends.

7 mechanisms · View full solution archetype

  • Commitment Register — Holds every commitment and its current lifecycle state — proposed, active, amended, satisfied, breached, released — in one owned, queryable record, so no promise is silently forgotten and none lingers past its basis.
  • Contract Speech-Act Clause — A precisely worded clause that performs the act of binding — using operative language like 'shall' or 'hereby warrants' to turn a statement into an obligation and to mark exactly what is committed and what stays mere aspiration.
  • If-Then Revision Contract — Agrees in advance, in writing, that a specified trigger of evidence will produce a specified change to the commitment — so a live promise adapts by pre-set rule instead of by silent breach or fresh negotiation.
  • Precommitment Device — Makes a commitment credible by removing or raising the cost of the promisor's own future option to back out — binding the maker's future self rather than the counterparty.
  • Public Commitment — Puts a commitment on the record before an audience whose regard the promisor values, so backing out later carries a visible reputational cost.
  • Readback Confirmation — Closes the communication loop on a commitment by having the receiver repeat it back, so a gap between what was said and what was heard surfaces before anyone relies on it.
  • Warranty or Guarantee — Backs a commitment with a promised remedy — repair, replacement, or refund — that the promisor owes if the thing fails, so the promise costs the maker, not just the relying party.

Commons Governance

Govern shared resources so individually rational use, neglect, or pollution does not destroy collective viability.

4 mechanisms · View full solution archetype

  • Commons Charter — Writes a shared resource's unwritten norms into an explicit, ratified charter — defining the resource, who may use it, and where the rules can be found — so a commons becomes a referenceable institution instead of a folk memory.
  • Maintenance Rotation — Splits the recurring labor of upkeep into fair, tracked turns with real consequences for skipping — so shared maintenance rides on the many instead of collapsing onto a silent few.
  • Participatory Rulemaking — Gives the people bound by a shared resource's rules a real hand in making and revising them — so the rules earn legitimacy, adapt on a regular cadence, and carry a forum for hearing objections.
  • Replenishment Fund — Pools money from those who benefit from a shared resource and disburses it to restore and repair — with hardship waivers so paying in never becomes a gate — financing upkeep that volunteer labor alone can't sustain.

Conditional Authority Envelope Design

Give actors advance permission to act inside known conditions, with explicit limits, escalation triggers, and after-action accountability.

8 mechanisms · View full solution archetype

  • Delegated Authority Charter — Records the source, scope, and accountability of a delegation in a standing document — who holds the authority, over what domain, and to whom they answer.
  • Engagement Threshold Table — Converts severity or state tiers into a graduated ladder of proportional response, so a mild condition unlocks a light action and a severe one a stronger action.
  • Exception Escalation Form — A structured intake artifact an actor files when a case exceeds the envelope — capturing the case, the reason it breached a limit, and routing it up for a decision while leaving a record that can be reviewed or challenged.
  • Field Decision Card — A pocket-sized operational aid that compresses the envelope into a few cues an actor can read at a glance under pressure — recognize the condition, honor the hard limits, and know when to bail out to escalation.
  • Readback Authority Confirmation — A closed-loop confirmation in which the actor repeats back the authorization and their reading of it before acting, so the granter can catch a mishearing or a wrongly-assumed permission in time.
  • Rules-of-Engagement Matrix — A two-axis grid that maps each recognized condition to the actions permitted and the actions forbidden, so an actor can look up any situation and read off what they may and may not do.
  • Scenario Rehearsal Protocol — A structured program of practice scenarios that drills actors on recognizing trigger conditions and choosing between acting and escalating, keeping their judgment current before real cases arrive.
  • Temporary Authority Window — A delegation that is deliberately time-boxed — it grants an actor expanded authority over a defined window and then automatically expires, so the expanded permission cannot silently become permanent.

Conflict-of-Interest Mitigation

Prevent competing interests from compromising entrusted judgment through timely disclosure, independent assessment, proportionate mitigation, recusal or structural separation, verification, and remedy.

9 mechanisms · View full solution archetype

  • Blind Trust or Divestiture Plan — Removes beneficial control of a persistent financial interest — by sale, relinquishment, or independent blind management — so it can no longer pull on an office holder's judgment.
  • Conflict Management Plan — Assembles a matter-specific bundle of proportionate controls — with owners, evidence, and an expiry — when no single measure covers all the influence paths but full disqualification is unnecessary.
  • Conflict-of-Interest Disclosure Register — A secure, purpose-limited standing record that links covered people to their disclosed interests, keeps it current through event-driven updates, and protects the sensitive data it holds.
  • Gift and Outside-Activity Approval Workflow — A thresholded preapproval gate for gifts, hospitality, outside employment, and board seats — deciding, before the benefit is accepted, whether it creates a reportable or disqualifying conflict.
  • Independent Conflict Review Panel — A standing or ad hoc body — protected in appointment, funding, and evidence access — that resolves the senior, disputed, and institutional conflicts a line manager cannot judge independently.
  • Information Firewall — Technically and procedurally isolates privileged information from a conflicted actor and their proxies — with monitored, logged exceptions — so an interest cannot exploit or shape it even without a formal decision.
  • Post-Decision Conflict Audit — Risk-based retrospective testing of past decisions — disclosures, access, communications, and outcomes — to catch undisclosed conflicts, control failures, and institutional patterns after the fact, and to trigger remedy.
  • Pre-Decision Conflict Screen — A hold point before a decision or assignment that matches the participants against disclosed interests and the matter's affected parties, flagging conflicts before the decision proceeds.
  • Role Separation and Decision Transfer — Reassigns duties, reporting lines, or approval rights so an incompatible pair of loyalties no longer sits inside one role — transferring each excluded right to a competent, independent alternate.

Decision Commitment and Closure

Close deliberation responsibly by naming the choice, authority, evidence threshold, reversibility, forgone alternatives, execution handoff, and conditions for reopening.

9 mechanisms · View full solution archetype

  • Decision Clock — Makes the closure deadline, elapsed deliberation time, delay cost, and pending prerequisites visible while the decision is still open.
  • Decision Record Log — Preserves why a decision was made — its rationale, assumptions, recorded dissent, and the strongest rejected alternatives — so later reviewers can reconstruct and calibrate.
  • Execution Handoff Checklist — Confirms a closed decision reaches an accountable executor with resources, a start condition, first actions, dependencies, and communication in place.
  • Go/No-Go Commitment Gate — Tests closure readiness, authority, reversibility, and execution capacity at a defined decision event and issues a single binding go or no-go.
  • Option Comparison Matrix — Arrays the live options against declared criteria to compress evidence into a side-by-side comparison, without implying the weights are objective facts.
  • Precommitment Challenge Session — Gives a designated challenger or affected party a bounded, licensed opportunity to attack the leading option's assumptions and resurface alternatives before closure.
  • Reopen Trigger Monitor — Tracks the assumptions, thresholds, safety boundaries, and external changes that were pre-declared as grounds to reopen a closed decision.
  • Reversibility and Exit Check — Classifies reversal costs, locates points of no return, and confirms a rollback path and the emergency authority that can invoke it before commitment.
  • Signed Commitment Authorization — Provides explicit, traceable evidence that the authorized actor or body actually closed the decision and bound the system to one option.

Decision Rights Clarification

Clarify who has authority to decide what, under which constraints, with which escalation paths.

5 mechanisms · View full solution archetype

  • Authority Boundary Review — Periodically compares actual decision delays, conflicts, overrides, exceptions, and outcome quality against the current rights map, and fires a revision where the two have drifted apart.
  • Decision Registry — A searchable system of record for decision rights — look up any decision category and get its current owner, approval requirements, threshold, and escalation path on demand.
  • Delegation Charter — A standing document that grants a bounded envelope of authority to one delegate — a role, team, project, or unit — stating what it may decide alone, the limits on that autonomy, and where cases outside the envelope must go.
  • Governance Charter — A constitution for a collective decision body — a committee, board, council, or steering group — defining which decision categories it owns, who sits on it in what role, how it decides by vote or consent, and how it resolves authority conflicts.
  • RACI / RAPID-Style Tool — Assigns a single, unambiguous participation label — recommend, decide, approve, consult, or inform — to each role for a given decision, prying apart the roles that ambiguity collapses together.

Dependency Exposure

Reveal hidden dependencies so risks, obligations, failure paths, and coordination needs become visible before they cause failure.

12 mechanisms · View full solution archetype

  • Architecture Dependency Review — A gate placed before migrations, launches, and deprecations that forces the technical, data, and operational dependencies a proposed change would touch into the open before the change ships.
  • Assumption Log — Makes the unstated premises a plan silently rests on into an explicit, revisable list — each with its confidence and a trigger to revisit it when reality drifts.
  • Contract and SLA Review — Reads the contracts and service-level agreements behind external providers to expose what is actually guaranteed, what happens on breach, and how little recourse the fine print really leaves.
  • Critical Dependency Dashboard — A live board that watches the handful of highest-criticality dependencies and lights up the moment one degrades, drifts stale, or nears a deadline — turning a one-time map into continuing observability.
  • Dependency Graph — Draws the system's depends-on relations as nodes and directed edges so concentration, chains, and single points of failure become visible at a glance.
  • Dependency Registry — The durable system of record for dependencies — one governed entry per dependency carrying its owner, its criticality, and its next review date, so nothing important stays unowned or unrevisited.
  • Dependency Review Workshop — Puts maintainers, users, and domain experts in one room to surface the dependencies that live only in people's heads — the tacit handoffs and workarounds no document records — and to claim owners for them on the spot.
  • FMEA Dependency Table — Adapts failure mode and effects analysis to dependencies — scoring each one's failure by severity, likelihood, and detectability to produce a ranked, mitigation-prioritized list rather than a flat inventory.
  • Impact Analysis — Traces the blast radius of one specific dependency failing or changing — what breaks first, who is hit, how fast, and what substitutes remain — turning a depends-on relation into a concrete consequence.
  • Software Bill of Materials — A machine-generated, itemized inventory of every software component and version inside a build — direct and transitive — so a vulnerability, license, or end-of-life question can be answered from a record instead of a scramble.
  • Supply Chain Mapping — Traces physical dependencies upstream through multiple supplier tiers — parts, materials, facilities, transport routes, geographies — to reveal the hidden convergence that a direct-vendor view can never see.
  • Vendor Risk Map — Connects each external provider to the services, data, and outcomes riding on it, rates the consequence of its failure, and names an owner and a fallback — turning a vendor list into a governed risk picture.

Equity Adjustment

Adjust rules, resources, supports, or access conditions to account for materially different starting conditions or barriers.

7 mechanisms · View full solution archetype

  • Accessibility Change — Changes the physical, digital, procedural, linguistic, sensory, or temporal environment so more participants can access the same opportunity or process.
  • Accommodation Process — Provides a structured way to request, assess, approve, implement, and review individualized adjustments without treating the request itself as a favor.
  • Barrier Removal Workflow — Identifies recurring barriers and redesigns processes, environments, forms, interfaces, schedules, or requirements so fewer individual exceptions are needed.
  • Differentiated Support Pathway — Routes participants to different levels or types of support while aiming at a shared standard or fair access outcome.
  • Hardship Exception Review — Reviews whether a standard rule should be modified for unusual hardship while preserving the rule's legitimate purpose and preventing favoritism.
  • Needs Assessment Rubric — Structures how decision-makers assess need, barrier severity, available supports, and relation to the preserved standard.
  • Targeted Resource Allocation — Directs support, funding, attention, staff time, or capacity toward participants or contexts facing materially greater barriers.

Escalation Exit Gate

Define independent exit criteria before sunk costs make continuation feel obligatory.

5 mechanisms · View full solution archetype

  • Funding Tranche Review — Releases resources in conditional increments, so each new slice of funding must be re-earned by fresh evidence and the most that can be lost before the next look is capped at the current tranche.
  • Independent Project Audit — Puts a live commitment in front of reviewers with no stake in the original bet, to test its assumptions, remaining value, and sunk-cost reasoning from the outside — diagnosing, not deciding.
  • Pivot Gate — Preserves the middle path between continuing blindly and cancelling outright: when the bet is invalidated, force a named broken assumption, a new falsifiable hypothesis, an owner, and a fresh gate.
  • Post-Investment Review — Runs after a committed effort ends or pauses, converting the time and money already spent into reusable lessons and a dignified way to have stopped.
  • Stage-Gate Review — Places an authorized, independent gate at each phase boundary, so passage to the next phase is never automatic but re-earned against current evidence.

Functional Vacancy Backfill

Treat an occupied but inactive authority role as functionally vacant once observable nonperformance thresholds are met, and activate bounded backfill channels.

12 mechanisms · View full solution archetype

  • Acting Sponsor Rotation — Covers an absent authority by cycling the acting role through a standing roster on a fixed cadence, so coverage is continuous and no single stand-in accumulates entrenchable power.
  • Auto-Escalation Workflow — An automated pipeline that, the moment a decision is deemed stalled, fires a last re-engagement attempt to the absent authority and then routes the decision onward — keeping affected stakeholders notified at every hop.
  • Decision Stall Register — A running ledger of decisions left unresolved under a nominally-present authority, turning scattered 'still waiting on them' complaints into dated, per-function evidence of a failing role.
  • Decision Timeout Rule — A bright-line deadline that deems a decision stalled once it sits unresolved past a preset clock, converting open-ended waiting into an automatic, pre-agreed trigger for backfill.
  • Deputy Sponsor Charter — A standing charter that pre-names a deputy and pre-loads their authority envelope, so decision rights held in escrow spring to the deputy the moment the sponsor goes dark — no scramble, no improvised legitimacy.
  • Functional Vacancy Declaration — The formal, recorded act that reclassifies a still-occupied authority role as functionally vacant, dissolving the nominal occupancy that was keeping every substitute channel illegitimate.
  • Governance RACI With Backups — A responsibility chart that pre-names, for every decision a role owns, both its primary holder and a standing backup — so the map of who-may-act already exists before anyone goes absent.
  • Interim Authority Letter — A signed instrument that grants a named substitute bounded authority to act in the role's place — scope, duration, and limits spelled out — and stands as the public record that the backfill is legitimate.
  • Post-Backfill Authority Review — The closing review that decides a backfill's fate — hand the seat back, formalize the deputy, replace or redesign the role, or shut the backfill down — so temporary cover never hardens into shadow governance.
  • Sponsor Health Check — A periodic diagnostic that reads a sponsor's actual decision output — latency, closure, blocked substitutes — to tell a nominally-filled seat that still works from one that has gone functionally vacant.
  • Sponsor Re-Engagement Notice — A formal, on-the-record prompt to a disengaged role-holder to resume the function — a documented last chance to re-engage before any backfill is activated.
  • Two-Key Escalation Panel — A standing panel that can resolve a stalled decision only when two authorized members sign off together — so interim power is exercised, but never by one hand alone.

Governance Exception Management

Govern departures from standing rules through explicit grounds, accessible review, reasoned and scoped decisions, expiry, cross-case monitoring, and feedback that changes a rule when exceptions reveal the baseline is wrong.

12 mechanisms · View full solution archetype

  • Controlled Exception Register — The system of record that holds every active and historical exception's status, dates, scope, conditions, dependencies, and privacy tier so no departure becomes an untracked shadow rule.
  • Emergency Exception Log and Ratification Queue — Captures an already-taken urgent departure the instant it happens and drives it into a bounded queue for prompt confirmation, modification, or revocation by the proper authority.
  • Exception Access and Status Channel — The public-facing front door that publishes who may request an exception and how, takes in requests through accessible channels, and shows each requester their status, reasons, and review rights without exposing protected details.
  • Exception Comparator Memo — A single-case template that pulls up materially similar prior approvals and denials and forces the decision-maker to state whether this case follows, distinguishes, narrows, or departs from them — and why.
  • Exception Eligibility Screen — A pre-merits checklist that tests a request against recognized grounds, exclusions, sufficiency, ordinary alternatives, and nonwaivable floors, and routes it to the correct decision authority before any judgment on the merits.
  • Exception Expiry and Revalidation Calendar — A forward-scheduled workflow that fires notice, evidence requests, and owner tasks ahead of each exception's expiry, drives a renew-or-revert decision, and flags when repeated renewals should trigger rule review.
  • Exception Request and Evidence Dossier — A structured intake template that captures, for one request, the exact rule being departed from, the claimed ground and material facts, proportionate evidence, affected parties, the precise scope asked for, urgency, and confidentiality needs.
  • Exception Review Panel or Designated Officer — The human decision authority — a scoped panel or officer with the competence, independence, recusal, and escalation rules to actually grant or deny an exception and own the reasoned outcome.
  • Exception Saturation and Distribution Dashboard — A live analytic view over the exception population that shows volume, recurring grounds, concentration, access and outcome gaps, renewal churn, and where saturation crosses the threshold that should trigger rule review.
  • Reasoned Waiver or Variance Certificate — The authoritative decision document that states the approved or denied departure, its rationale, its exact scope and conditions, its duration and reversion terms, the deciding authority, and its precedential status.
  • Rule-Revision Referral and Response Packet — A referral document that packages the portfolio evidence of a saturated exception pattern and compels the authorized rule owner to record a time-bounded response: investigate, clarify, tier, amend, retire, or justify continued exception handling.
  • Sampled Exception Consistency Audit — A retrospective, sampled review that pulls materially comparable decided exceptions — including adverse ones — and tests whether like cases were treated alike, reasons held up, scope was proportionate, and access was equitable across subgroups.

Ensure agreement is informed, voluntary, specific, revocable where appropriate, and granted by someone with authority to consent.

9 mechanisms · View full solution archetype

  • Assent / Consent Distinction — Splits one 'yes' into two: the affected person's affirmative participation and the authorized actor's binding permission — and defines what happens when they diverge.
  • Consent Form — The signed artifact that fixes the disclosed terms, the bounded scope agreed to, and a durable, provable record of who authorized what and when.
  • Consent Renewal Prompt — A change-triggered workflow that re-discloses what shifted and asks the person to affirmatively re-agree to the updated scope before the new use begins.
  • Data Consent Settings — A standing, self-service control surface where a user can grant, narrow, revoke, or inspect specific data permissions at any time — and the toggle actually changes what the system does.
  • Granular Permission Dashboard — A single review surface that lays out every permission a person has granted — split by purpose, actor, and duration — so the whole consent landscape can be inspected and spotted for staleness at a glance.
  • Informed Consent Conversation — A two-way dialogue that co-produces and live-tests understanding — through questions, teach-back, and deliberation — before any agreement is sought.
  • Opt-In Flow — A pre-entry interface gate that presents one permission request with its material terms at the threshold of a feature, and requires an affirmative choice against a genuine, equally-weighted decline.
  • Research Consent Protocol — An oversight-governed protocol spanning the full arc of research participation — standardized disclosure, voluntary enrollment, documented consent, and a penalty-free right to withdraw.
  • Withdrawal Procedure — The end-to-end workflow that executes a person's decision to take back or narrow an existing permission — receiving it, propagating the stop downstream, and stating what can and cannot be undone.

Mandatory / Default Rule Design

Decide which rules must bind, which should guide by default, and which require opt-out or exception paths by testing harm, rights, reversibility, information, heterogeneity, and enforcement capacity.

9 mechanisms · View full solution archetype

  • Appeal and Waiver Process — Corrects misclassification, evidence error, and disproportionate application through an independent review path.
  • Default Enrollment with Notice — Places eligible people on a beneficial path while giving timely, salient notice and a usable way to decline.
  • Exception Review Protocol — Applies defined grounds and safeguards to departures from an otherwise mandatory floor.
  • Mandatory / Default Decision Matrix — Scores candidate rule forms against severity, externality, rights, reversibility, information quality, heterogeneity, and enforcement capacity.
  • Mandatory Floor with Safe Harbor — Binds a nonwaivable outcome floor while pre-approving named methods that presumptively satisfy it, keeping an equivalence path open.
  • Opt-Out Architecture — Makes departure from a default legible, timely, low-friction, and reversible where appropriate.
  • Pilot and Reversibility Test — Trials a proposed mandate or default at bounded scale to measure effects before durable adoption.
  • Sunset Clause and Periodic Review — Ends or reauthorizes a rule on a defined schedule using updated evidence and burden data.
  • Tiered Compliance Rule — Varies normative force or implementation duties by risk, scale, capability, or affected population.

Network Effect Governance

Govern self-reinforcing network growth so shared value does not become harmful lock-in, exclusion, concentrated power, abuse, or systemic fragility.

14 mechanisms · View full solution archetype

  • API Governance Policy — Governs how third parties build on an operator's API — access tiers, stability guarantees, deprecation notice, and security rules — so an ecosystem can depend on an interface that won't shift without warning.
  • Appeal and Dispute Process — Gives a participant hit by a suspension, delisting, or access denial a real channel to contest it before a reviewer who didn't make the original call — with a path back if it was wrong.
  • Competition or Antitrust Remedy — An externally imposed constraint on a dominant network — behavioral or structural — that maps where concentration has become coercive and compels changes like non-discrimination, unbundling, or interoperability.
  • Data Portability Rule — Requires that a participant can export their own data — and, where it applies, their reputation and connections — in a usable, machine-readable format, so leaving costs no more than the network's value honestly justifies.
  • Federation Protocol — Lets independent operators run their own nodes and still interoperate, so the network's value survives without any single hub owning the participants or the rules.
  • Governance Board or Council — A standing body with defined authority to set rules, review changes, and adjudicate disputes for a network — seated and constrained so no single operator or faction can steer it alone.
  • Interoperability Mandate — Requires a dominant operator to expose defined, compatible interfaces so participants aren't trapped behind one gatekeeper and value can flow across competing providers.
  • Moderation and Abuse Response — Detects harms that network scale amplifies — fraud, harassment, spam, manipulation — and responds with proportionate, reviewable action fast enough to matter.
  • Open Standard — A shared, openly-specified technical rule any implementer can build to, so compatibility — the thing that makes the network valuable — belongs to no single vendor.
  • Platform Access Rule — Defines the published conditions under which each side can join, list, sell, or build on a platform — and be removed — so access turns on stated criteria rather than the operator's discretion.
  • Rate Limit or Throttle — Caps how fast a given actor can hit the network so abuse, overload, or attack degrades gracefully instead of taking the shared system down — a blunt, reversible safety valve.
  • Service-Level Commitment — A published, accountable promise about uptime, notice, support, and interface stability, so participants who build livelihoods on the network can depend on it not degrading without warning.
  • Switching Support Tooling — The concrete utilities that make leaving actually work — export tools, migration assistants, adapters, and transition guides — turning a portability right into a path someone can walk.
  • Transparency Report — Publishes what the network's control points actually did — access decisions, enforcement, appeals, outages, and rule changes — on a fixed cadence, turning private governance into a checkable public record.

Normative Assumption Explicitness

Make value judgments and ought-claims explicit before treating them as neutral facts.

8 mechanisms · View full solution archetype

  • Decision Record — Stores the chosen value assumptions, decision rationale, rejected alternatives, and review triggers so the decision remains accountable over time.
  • Ethics Checklist — Prompts reviewers to ask value, harm, consent, fairness, transparency, and responsibility questions. It implements the archetype only when answers are recorded and contestable.
  • Metric Value Review — Examines what a metric rewards, ignores, normalizes, or sacrifices, especially when the metric is treated as objective evidence of success.
  • Model Card Value Section — Adds explicit value assumptions, intended uses, excluded uses, affected groups, and evaluation priorities to technical documentation for AI or analytic systems.
  • Policy Rationale Statement — Records the values, affected parties, evidence, alternatives, and reasons behind a policy or governance decision.
  • Stakeholder Deliberation — Creates a forum where affected parties and decision makers can compare normative claims, contest assumptions, and clarify acceptable tradeoffs.
  • Value Audit — Reviews a policy, model, metric, or process to identify hidden value priorities, displaced alternatives, affected parties, and unsupported legitimacy claims.
  • Values Statement — Names organizational or project values that can anchor later rationale. It is only a mechanism; the archetype requires linking those values to actual decision assumptions and tradeoffs.

Outcome Responsibility Attribution Calibration

Assign credit or blame only after separating outcome, causal contribution, control, duty, knowledge, and uncertainty.

12 mechanisms · View full solution archetype

  • Attribution Uncertainty Label — Stamps each attribution with how strongly the evidence actually backs it — from established down to unsupported — so confident-sounding blame or credit cannot outrun its proof.
  • Blame–Credit Apportionment Table — Turns the separate per-agent findings into explicit proportional shares of credit and blame that sum to the whole — no scapegoat carrying all of it, no residue vanishing into 'the system.'
  • Causal Contribution Timeline — Reconstructs the outcome as a time-ordered chain of actions, omissions, warnings, and conditions, so causal contribution is read from the actual sequence rather than from whoever is most visible at the end.
  • Counterfactual Control Test — Asks whether an agent actually had a feasible, foreseeable alternative that would likely have changed the outcome — the line between real control and mere presence at a result driven by luck.
  • Credit Contribution Register — Logs who actually enabled an outcome — including the invisible, upstream contributors — so recognition tracks real contribution instead of proximity to the finish line.
  • Just Culture Review — Sorts an adverse outcome into blameless error, at-risk behavior, and reckless choice, and matches the response to the conduct rather than to how bad the harm happened to be.
  • Omission–Commission Parity Check — Holds a duty-bound failure to act to the same standard as a visible action, so blame doesn't fall only on whoever did something.
  • Outcome Responsibility Review Panel — Convenes a procedural forum where high-stakes or contested attributions are argued, evidenced, and open to challenge before responsibility is fixed.
  • Responsibility Attribution Matrix — Cross-tabulates each candidate agent against contribution, control, duty, and knowledge, then applies an explicit weighting rule to turn the grid into a graded, comparable responsibility reading.
  • Responsibility Diffusion Check — Tests whether 'the system,' 'the team,' or 'the process' has been used to dissolve responsibility until no agent or duty remains answerable — and forces an explicit partition back.
  • Role–Duty Mapping — Lays out, before any verdict, which agents held which duties, authority, and expected actions — the outcome-blind baseline every later attribution step is measured against.
  • Scapegoat Screening Review — Checks whether a salient, low-power, or last-in-chain actor is absorbing more blame than their actual contribution and the available evidence support.

Outside-Authority Influence Channel Mapping

Protect sovereignty by mapping how outsiders can still shape decisions through money, information, access, dependencies, relationships, reputation, or pressure despite lacking formal authority.

7 mechanisms · View full solution archetype

  • Conflict-of-Interest Disclosure Review — A procedure that requires decision participants to disclose their outside interests, then checks the disclosures for undisclosed or asymmetric conflicts before a decision proceeds.
  • External Influence Channel Matrix — A single actor-by-channel grid that inventories every route through which outside parties can shape a protected decision — turning vague suspicion into an enumerated catalog.
  • Funding Conditions Register — A standing ledger of every funding source's attached conditions — grant terms, gift restrictions, sponsorship clauses — logged with owner, sovereignty risk, and review date so money-borne strings stay governable.
  • Influence-Response Decision Tree — Routes each mapped influence channel through a branching test — legitimate input or de facto override? — to the proportionate response the situation warrants.
  • Recusal and Firewall Protocol — Once a conflict is identified, removes the conflicted party from the decision and walls the channel off from it — redrawing the boundary of who may touch the protected decision.
  • Refusal-Cost Scenario Test — Stress-tests each dependency by simulating a flat refusal and pricing the consequence, exposing which outside actors the decision owner cannot actually afford to say no to.
  • Relationship Interlock Diagram — Draws the network of board seats, advisory roles, employment history, and personal ties linking a decision body to outside actors, so influence that travels through relationships becomes a visible graph.

Procedural Fairness Design

Design decision processes so affected parties receive meaningful notice, voice, impartial treatment, evidence handling, reasons, and a path for review or remedy.

8 mechanisms · View full solution archetype

  • Appeals Process — A structured procedure for challenging a decision and seeking reconsideration or correction.
  • Decision Notice — A notice document or message explaining a pending or completed decision and available process rights.
  • Grievance Process — A workflow for raising fairness complaints, process defects, retaliation concerns, or unresolved harms.
  • Hearing Procedure — A structured meeting or written equivalent where parties present evidence, respond to claims, and receive a decision.
  • Moderation Appeal — A platform-specific workflow for challenging content, account, or community enforcement decisions.
  • Ombuds Channel — An accessible independent or semi-independent channel for navigating process, raising fairness concerns, or seeking informal resolution.
  • Review Panel — A group or designated body that reviews decisions, evidence, process defects, or appeals.
  • Transparent Decision Record — A record of decision standard, evidence considered, rationale, participation, and review status.

Proportionality Calibration

Scale response, restriction, remedy, or sanction to the severity, necessity, risk context, and affected interests of the case.

7 mechanisms · View full solution archetype

  • After-Action Proportionality Review — Reviews whether the response produced intended safety, fairness, deterrence, repair, or learning without excessive collateral burden.
  • Disciplinary Guideline — Provides recommended response ranges for workplace, school, professional, or community discipline without replacing judgment and review.
  • Moderation Strike System — Implements scaled platform responses for repeated or severe violations, provided it preserves context, appeal, and de-escalation.
  • Proportional Remedy Menu — Offers repair options calibrated to harm type and scale, such as apology, correction, restitution, access restoration, remediation, or redesign.
  • Response Matrix — Maps severity, recurrence, intent, impact, and context to response ranges so decision-makers can see the proportional response band.
  • Risk-Based Enforcement Protocol — Allocates enforcement intensity according to severity, likelihood, exposure, and urgency while preserving checks against bias and overreach.
  • Sanction Matrix — Lists sanction levels by conduct category or severity. It is a mechanism under this archetype, not the archetype itself.

Reciprocity Protocol Design

Structure mutual obligations so exchange, cooperation, and trust remain balanced over time.

8 mechanisms · View full solution archetype

  • Benefit-Sharing Arrangement — Routes a defined share of the value that cooperation creates back to the contributors whose inputs made it, sized by a fairness formula agreed before the value exists.
  • Contribution Norms — Regulates give-and-take through unwritten, internalized expectations — enforced by approval and disapproval rather than any ledger or contract — and tolerant of rough rather than exact balance.
  • Cooperative Agreement — A charter for a member body that ties belonging to duties and benefits — defining who counts as a member, what membership obligates and entitles, and how one joins, pauses, or leaves.
  • Exchange Protocol — Carries a single exchange from ask to settled through defined steps — request, offer, acceptance, fulfillment, confirmation, return — with a confirmation gate that flags anything left unreturned.
  • Mutual Aid Rules — An explicit rule set for a help network under generalized reciprocity — you help whoever needs it and draw help when you need it — with rules for who belongs, how help is recognized, and how the network is protected from extraction.
  • Partnership Agreement — A written, signed record of the reciprocal duties between two (or a few) independent parties — what each owes, by when, and how disputes get repaired — binding named counterparts to each other.
  • Reciprocity Log — A running record of who contributed what — and who benefited — that makes imbalance visible and remembered so it can be noticed and discussed, without minting credits or enforcing any rule.
  • Time Bank or Credit System — Turns a contribution into a transferable credit you earn by giving and spend by receiving, so deferred, generalized reciprocity settles across a whole network over time — the credit itself does the remembering and enforcing.

Regress Termination Rule

Set a principled stopping point for chains of justification, explanation, authority, or delegation so action can proceed without hiding foundational assumptions.

10 mechanisms · View full solution archetype

  • Axiom Set — Terminates proof regress by declaring a fixed set of statements as primitive — accepted without further justification — and bounding the formal system in which they hold.
  • Burden-of-Proof Rule — Allocates who must justify what, and to what standard, before a claim is accepted or reopened — so a support chain closes by a fixed rule of responsibility rather than by whoever argues longest.
  • Decision Closure Criteria — Converts abstract 'enough support' into a concrete, decision-class checklist that says when a specific decision may be closed and acted on.
  • Evidence Sufficiency Rubric — Grades whether a body of evidence is strong, diverse, and relevant enough that the chain of 'but what backs that?' can stop — calibrated to the evidentiary regress specifically.
  • First-Principles Statement — Names the base premises a group will reason up from for one specific decision, and flags what those premises leave uncertain, so the chain of 'why' bottoms out at a chosen, visible foundation.
  • Five Whys with Stop Rule — Follows a causal 'why' chain down to the first level where a durable action can be taken, then stops on a named rule rather than chasing causes forever.
  • Governance Authority Chain — Defines who holds legitimate authority to finally close recursive approvals or appeals, within what scope, and what it takes to appeal — so an escalation chain terminates by mandate, not by exhaustion or raw power.
  • Research Stopping Rule — Sets in advance when data collection, literature search, or analysis has done enough for its purpose — by information saturation, a preset threshold, or a resource limit — so inquiry ends before it either never closes or is cut off arbitrarily.
  • Review Trigger Register — A living list of the events, thresholds, and failures that would reopen a closed decision — each with an owner who must act — so closure stays provisional and revisitable rather than permanent.
  • Timeboxed Inquiry Record — Caps an open-ended investigation at a fixed time or resource budget and records what was learned, what remains unresolved, and the scope the cap applies to — so inquiry closes on the deadline without hiding its gaps.

Responsibility Assignment for Action

Assign clear responsibility when group presence would otherwise diffuse action.

9 mechanisms · View full solution archetype

  • Emergency Role Assignment — Pre-assigns named people to named emergency roles ahead of time, keyed to a trigger and an urgency tier, so that when an incident hits nobody burns seconds deciding who acts.
  • Explicit Task Assignment — Turns a shared concern or a meeting's agreed outcome into a single named next-action owner with an expected update — the smallest act that keeps responsibility from dissolving into the group.
  • Incident Commander Role — Names one person to hold coordinating command for the duration of an active incident — directing responders, keeping the shared status picture, and owning the response until it is resolved or handed off.
  • On-Call Ownership — Puts a named responder on the hook for a defined time window — with a backup and a severity ladder — so recurring alerts and requests never depend on who happens to be around.
  • Public Commitment Board — A shared, visible surface that shows who owns each active item and what state it is in, so coverage and gaps are legible to the whole group at a glance — without becoming a surveillance tool.
  • RACI-Like Ownership Matrix — A grid mapping every task against every party, marking who is Responsible, Accountable, Consulted, and Informed — disambiguating overlapping roles across a whole effort, and kept current so it does not ossify into fiction.
  • Runbook With Named Owner — A documented procedure that pairs the step-by-step for a recurring situation with the named role authorized to run it, so the instructions and the person cleared to act arrive together.
  • Shift Handoff Check — A structured checkpoint at the boundary between two shifts that transfers unresolved state, active blockers, and pending obligations to the incoming owner, so nothing silently drops when responsibility changes hands.
  • Single-Threaded Owner — Assigns one person — not a committee — to carry a cross-functional effort through ambiguity end to end, with the authority to make calls across team boundaries until it is done or escalated.

Rights–Freedoms Obligation Mapping

Map every asserted right or freedom to its bearer, counterpart relation, scope, justification, conflict, and remedy before deciding what must be protected, provided, permitted, restrained, or reviewed.

8 mechanisms · View full solution archetype

  • Claim–Liberty Classification Tree — Routes each ambiguous 'right' phrase through ordered yes/no questions to a single position type — claim, liberty, power, or immunity — before any detailed mapping begins.
  • Counterparty Obligation Register — Turns each recognized claim into a line item with a named duty-owner, a service level, the capacity behind it, and an enforcement hook — so no obligation floats unassigned.
  • Hohfeldian Relation Matrix — Lays every asserted position into a grid of its jural correlative and opposite, so a claim with no matching duty cell — or a liberty mistaken for a claim — becomes visible at a glance.
  • Least-Restrictive Alternative Screen — Requires reviewers to consider whether a less restrictive but still effective response would achieve the same purpose.
  • Permission–Entitlement Crosswalk — Maps technical permissions against substantive entitlements to catch capabilities with no claim behind them and claims the system cannot actually execute.
  • Proportionality Balancing Record — Records the reasoned weighing of a constraint's burden against its justified purpose, preserving the evidence, the value judgments, and the dissent behind the call.
  • Remedy Traceability Review — Follows a breach from detection through notice, review, state-change, and restoration to confirm the remedy can actually change the outcome — not just explain it.
  • Rights-Conflict Scenario Table — Runs concrete combinations of actors, conditions, and scarce resources to reveal which rights collisions are real and which dissolve once scope is fixed.

Shared or Not Yet Assigned

Mechanisms shared across, or not yet assigned to, a single primary solution archetype.

2 mechanisms

  • Graduated Sanctions — Implements proportionality by sequencing responses from warning or coaching through stronger sanctions as severity or recurrence increases.
  • Recusal Protocol

Traceability Linking

Create explicit links from sources, requirements, decisions, actions, or artifacts to their downstream consequences or implementations.

7 mechanisms · View full solution archetype

  • Audit Trail Record — Records who created, changed, approved, accessed, or retired each record and link, and when, in an append-only tamper-evident history — so the traceability system itself can be reviewed and trusted.
  • Citation Chain — Links each claim to the specific sources that support it with a typed support relation, so a reader can walk from an assertion back to the evidence it actually rests on.
  • Data Lineage Record — Follows a data value back through every source, join, and transformation that produced it and forward to everything that now depends on it, pinning each step to the pipeline version and the steward who owns it.
  • Decision Log — Captures each significant decision as a linked record — its rationale, the alternatives weighed, who approved it, and the artifacts it affects — so a choice can later be traced back to why it was made and forward to what it touched.
  • Source Control Linkage — Captures trace links as a byproduct of version control — pinning each commit, pull request, and release to the issue, requirement, or review that justified it.
  • Test Coverage Link — Links each requirement, behavior, or risk to the test that verifies it, turning an untested promise into a gap the links make visible.
  • Traceability Dashboard — Watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done.

Transparency for Accountability

Expose who decided what, under which authority, using which reasons and evidence, with visible limits, questions, corrections, and remedy so disclosure produces accountability rather than noise.

16 mechanisms · View full solution archetype

  • Audit Trail Export — Emits the ordered, timestamped record of who did what to which record, in a portable form an outside reviewer can ingest and verify independently.
  • Authority and Delegation Register — The canonical, traceable map of who is authorized to make which decisions and to what limit — and from which grant that authority flows.
  • Conflict-of-Interest Disclosure — Makes a decision-maker declare the relationships and incentives that could skew their judgment, so a specific decision can be checked for independence.
  • Correction and Retraction Notice — Publicly links a corrected or withdrawn record to what was wrong, what changed, and who is affected — without erasing the original from the trail.
  • Evidence Disclosure Packet — Assembles the underlying evidence a decision rests on into one sourced, indexed bundle, released so an outsider can check the factual basis for themselves.
  • Freedom-of-Information Response Workflow — Turns a member of the public's right-to-know into a delivered record: a request pipeline with a statutory clock, exemption tests, and redaction before release.
  • Independent Oversight Portal — Gives an external overseer a standing, credentialed channel to look directly into an organization's records and live cases — without asking permission each time.
  • Meeting and Vote Record — Records who was in the room, what was moved and decided, and how each member voted — turning a closed-door decision into an attributed, reviewable event.
  • Plain-Language Transparency Report — Rewrites already-disclosed records into a short, plain-language account a non-expert can actually read, so the disclosure reaches the people it is meant to make power answerable to.
  • Process Status Dashboard — Shows each item's current stage in a process, continuously refreshed, so anyone affected can see where a decision stands without having to ask.
  • Public Comment & Question Channel — Gives any affected party a visible, tracked way to ask a consequential question or contest a decision — and routes a substantiated challenge toward correction.
  • Public Decision Log — A durable, itemized public record of which decisions and actions were taken and when, each entry pinned to its authoritative source version.
  • Reason-Giving Template — A required structure that makes every decision state its grounds — the criterion applied, the material facts, and the conclusion — in a form a reviewer can check.
  • Redaction & Withholding Ledger — Logs every redaction or withholding as an itemized entry — what was withheld, under which authority, and when it will be released — so concealment is itself on the record.
  • Rule & Criteria Register — Publishes the current rules, standards, and criteria a body decides by, with version history, so decisions can be checked against a rulebook that isn't secret.
  • Transparency Impact Review — Periodically asks whether all the disclosure is actually producing accountability, and at what burden, rather than just accumulating published volume.

Workaround Governance

Govern recurring deviations by learning why they exist, classifying their value and risk, and choosing a bounded path to formalize, tolerate, redesign, or eliminate them.

9 mechanisms · View full solution archetype

  • Benefit-Preserving Transition Plan — A staged migration that supplies the workaround's legitimate function through a safer route before the deviation is restricted or removed.
  • Linked Root-Cause Repair Ticket — A funded, tracked change item that binds a tolerated workaround to repair of the formal source condition, so the underlying gap gets resources instead of remaining a footnote.
  • Multi-Path Disposition Matrix — A structured grid comparing formalization, controlled tolerance, source redesign, replacement, and elimination across evidence, benefit, hazard, equity, reversibility, and cost.
  • Nonpunitive Workaround Review — A facilitated, protected review that reconstructs a recurrent deviation with the practitioners who use it and the parties who bear its consequences, assigning an owner and a route to contest.
  • Practitioner Counterfactual Walkthrough — A case-based, step-by-step comparison of the official path against the workaround, walked with the practitioner, to reveal the demand the deviation answers and the function it supplies.
  • Recurrence and Displacement Dashboard — A monitoring view that tracks whether a workaround recurs, mutates, relocates, or shifts its burden onto other groups after a disposition is applied.
  • Structured Workaround Registry — An access-controlled system of record that stores each workaround case and its evidence under retention and identity-minimizing rules, so the portfolio is visible without becoming a list of people to punish.
  • Temporary Deviation Permit — A time-limited written authorization specifying who may run a workaround, under what scope and safeguards, until when, and the conditions that force an immediate stop.
  • Workaround Failure-Mode and Effects Review — A structured review of how a workaround and each proposed disposition can fail locally and downstream, classifying the effects and specifying the compensating controls that catch them.