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.

1. Overview

Mandatory / Default Rule Design chooses the degree of force a rule should carry. It distinguishes a nonwaivable floor from a rebuttable presumption, a beneficial default, an opt-in offer, advisory guidance, and bounded discretion. The archetype is not simply about writing stricter or softer language. It designs the whole normative arrangement: who has authority, whose interests are protected, what choice remains legitimate, which departures affect others, how exceptions work, what evidence supports enforcement, and when the rule must be reconsidered.

The central error this pattern prevents is binary thinking. One system treats every desirable behavior as a mandate; another treats every preference as personal choice. Both miss the structure of the case. Some interests cannot safely be waived by the person making the choice because harm falls on workers, children, counterparties, future users, or the public. Other contexts contain legitimate preference diversity and reversible consequences, making compulsion unnecessary. Many cases need a hybrid: a mandatory outcome floor, default implementation, multiple compliant methods, and a bounded exception path.

A mature design therefore asks two questions separately. First, what must remain invariant? Second, how much freedom can remain around that invariant? The answer may be a universal prohibition, a targeted duty, a performance standard with safe harbors, automatic enrollment with meaningful exit, an opt-in offer, a rebuttable presumption, or guidance. The selected form is then supported with notice, transition, due process, monitoring, and sunset logic.

The pattern covers governance in law, organizations, markets, platforms, safety systems, public services, and professional practice. It remains a governance intervention even when defaults rely on behavioral inertia: inertia explains an effect, while this archetype justifies and bounds the rule’s normative force.

2. Why This Pattern Exists

Rules allocate risk, freedom, effort, and responsibility. Their force is never a cosmetic drafting choice. A mandate shifts the burden of justification to anyone seeking departure and authorizes enforcement. A default shifts attention and transaction costs while formally preserving choice. Opt-in makes inaction preserve the status quo. Advice leaves action with the recipient. Discretion transfers part of the decision to an official. Each form changes behavior and power even if its substantive recommendation is identical.

Institutions often choose among these forms by habit. Legal teams favor mandatory clauses because they appear clear. Product teams favor defaults because they increase uptake. Managers favor discretion because edge cases are difficult. Advocates favor opt-in because it sounds autonomous. These preferences can be reasonable, but none substitutes for analysis of severity, externality, reversibility, information, dependency, heterogeneity, and enforceability.

The pattern exists because freedom and protection are relational. Allowing one actor to opt out may expose another actor who never consented. Conversely, imposing one uniform method may burden people whose circumstances differ without improving anyone’s safety. A rule can be formally optional yet functionally compulsory when exit is hidden or costly. It can be formally mandatory yet practically arbitrary when evidence is unavailable and enforcement concentrates on visible, low-power actors.

Good rule design makes these effects explicit. It selects the least restrictive form that reliably protects the legitimate interest, and it adds institutional safeguards appropriate to the stakes. That discipline supports both effective protection and durable legitimacy.

3. Problem Signature

The pattern is indicated when the live dispute concerns the force of a norm rather than only its content. Participants may agree that an outcome is desirable while disagreeing about whether it should be required, presumed, recommended, or left to individual choice. They may also agree on a mandatory floor while disputing how much implementation flexibility, exemption, or review should remain.

Look for mismatches between stated form and lived effect. A default is suspect when most people cannot locate the alternative, when exit requires a different channel, when the alternative causes unrelated loss, or when supervisors can retaliate. A mandate is suspect when compliance evidence is vague, when equivalent methods are rejected without reason, when exceptions are available only through personal influence, or when widespread technical violation coexists with selective punishment.

Diagnose the harm pathway before the rule type. Identify the protected interest, the duty bearer, the beneficiary, affected third parties, severity, probability, timing, reversibility, and available repair. Then assess whether the chooser has adequate information and legitimate authority to accept the risk. Consent is weaker under dependency, urgency, market concentration, cognitive overload, or hidden downstream effects. The same surface choice may therefore support a default in one setting and a mandatory floor in another.

Competing diagnoses matter. If the force is already justified and only penalty severity is at issue, use proportionality calibration. If the main defect is invalid agreement, use informed-consent governance. If a physical interlock is the decisive solution, use constraint design for impossibility. If the sole objective is to make a beneficial routine easier, inertia harnessing is enough. Mandatory / Default Rule Design is primary only when selection and governance of normative force organize the intervention.

4. Intervention Signature

Begin with a force spectrum rather than a preferred answer. At minimum compare advisory guidance, opt-in, default with opt-out, rebuttable presumption, targeted mandate, universal mandate, and architectural constraint. Some options will be legally or ethically unavailable; recording why is part of the design.

Select force through a sequence of tests. Is the protected interest legitimate and within authority? Can departure create material nonconsensual harm? How severe, likely, and reversible is that harm? Can the affected person understand and validly choose? Do circumstances differ enough that one form will misfit many cases? Can compliance be verified accurately and proportionately? Would a weaker or more targeted rule control residual risk? Can exceptions be administered fairly? How quickly could the rule be changed if evidence shifts?

The output is an architecture, not a label. A mandatory layer states the irreducible outcome or prohibition. A default layer coordinates ordinary implementation. An opt-out or alternative layer preserves meaningful choice. An exception layer handles conflict, impossibility, hardship, and protected status. An evidence layer defines enforcement. A due-process layer corrects error. A transition layer avoids retroactive or impossible demands. A monitoring and sunset layer makes force adaptive rather than permanent by inertia.

The design is successful when people can tell which statements are duties, presumptions, defaults, options, and advice; when each form has an intelligible justification; and when real-world outcomes support continued use of that force.

5. Components

Protected-Interest and Harm Boundary

Defines the interest the rule protects, the harms it prevents, and the population to whom those harms can propagate. Separates a legitimate protective purpose from convenience, symbolism, or unsupported paternalism. In the assembled archetype this component precedes drafting and controls the legitimacy of everything downstream.

Design record. State the protected interest, affected parties, causal pathway, severity, and time horizon. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. A vague appeal to safety can make any preference appear mandatory. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Authority and Scope Record

Records who may set the rule, for whom, in which domain, and under what legal, contractual, or institutional authority. Prevents a substantively attractive rule from outrunning the decision-maker’s mandate. In the assembled archetype this component precedes drafting and controls the legitimacy of everything downstream.

Design record. Name the rulemaker, governed population, jurisdiction, delegated powers, and reserved powers. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. Authority inferred from custom can silently displace consent or higher-order limits. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Rule-Type Decision Matrix

Compares mandatory, default, opt-in, advisory, and discretionary forms against risk, rights, reversibility, information, and enforcement conditions. Makes the choice of normative force explicit and reviewable instead of burying it in drafting language. In the assembled archetype this component precedes drafting and controls the legitimacy of everything downstream.

Design record. Score the competing forms and record why the selected degree of force is necessary. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. A matrix can become decorative if evidence and thresholds are not documented. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Mandatory Floor

States the minimum obligation or prohibition that applies without individual waiver. Protects nonwaivable interests and blocks harmful races to the bottom. In the assembled archetype this component shapes the operational rule and the limits placed on affected parties.

Design record. Specify the regulated act, threshold, duty bearer, beneficiary, effective period, and consequence of breach. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. An overbroad floor suppresses legitimate variation and creates avoidable noncompliance. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Default Path

Provides the recommended or presumed option while preserving a genuine alternative. Reduces decision burden and coordinates ordinary cases without falsely converting convenience into command. In the assembled archetype this component shapes the operational rule and the limits placed on affected parties.

Design record. Make the default visible, explain its rationale, and ensure the alternative remains operational. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. A default becomes a hidden mandate when opting out is obscure, costly, stigmatized, or delayed. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Meaningful Opt-Out Path

Allows an authorized person to depart from a default through an understandable and usable process. Preserves autonomy where individualized choice is legitimate and external harms remain controlled. In the assembled archetype this component shapes the operational rule and the limits placed on affected parties.

Design record. Define who may opt out, required notice, timing, consequences, renewal, and revocation. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. Nominal choice is coercive when the path demands disproportionate time, disclosure, or loss. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Exception and Hardship Path

Handles cases in which a generally mandatory rule would impose conflict, impossibility, disproportionate burden, or protected hardship. Keeps a necessary floor from becoming brittle or unjust at the edge. In the assembled archetype this component shapes the operational rule and the limits placed on affected parties.

Design record. Define eligibility, evidence, temporary safeguards, decision authority, duration, and review. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. Discretion without standards invites unequal treatment, favoritism, and strategic pleading. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Rights, Burden, and Dependency Map

Maps liberties, claims, duties, dependencies, and distributional burdens created by each rule form. Reveals whose freedom is preserved by a default and whose safety or access depends on a mandate. In the assembled archetype this component shapes the operational rule and the limits placed on affected parties.

Design record. Include direct, indirect, cumulative, and asymmetric effects across affected groups. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. Average burden can hide concentrated harm to people with less power or fewer alternatives. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Information and Consent Condition

Tests whether affected people can understand, evaluate, and validly choose among the available paths. Determines when an opt-out or opt-in regime can rely on choice and when informational asymmetry defeats it. In the assembled archetype this component shapes the operational rule and the limits placed on affected parties.

Design record. Assess notice, comprehension, voluntariness, specificity, capacity, and revocability. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. Disclosure alone does not cure manipulation, urgency, dependency, or incomprehensible complexity. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Enforcement and Verifiability Boundary

Defines what compliance can be observed, by whom, at what cost, and with what privacy or error limits. Prevents mandatory language from outrunning feasible, legitimate, and accurate enforcement. In the assembled archetype this component shapes the operational rule and the limits placed on affected parties.

Design record. Specify evidence, record retention, inspectors, error handling, and limits on surveillance. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. Unverifiable mandates produce selective enforcement and incentives to optimize appearances. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Least-Restrictive Alternative Record

Documents why weaker forms, narrower scope, or better defaults cannot adequately protect the stated interest. Constrains coercion by requiring necessity rather than mere usefulness. In the assembled archetype this component shapes the operational rule and the limits placed on affected parties.

Design record. Compare advice, disclosure, default, opt-in, targeted mandate, universal mandate, and physical constraint. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. A conclusory statement can launder a predetermined mandate without serious comparison. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Notice, Reason, and Transition Plan

Explains the rule, its force, its reasons, its effective date, and the path from prior practice. Allows governed parties to prepare, contest, and comply rather than being surprised by a new obligation. In the assembled archetype this component governs implementation, correction, and learning after adoption.

Design record. Provide plain-language notice, rationale, lead time, migration assistance, and legacy treatment. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. Immediate application can turn administratively easy rules into retroactive or impossible demands. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Review, Appeal, and Due-Process Channel

Provides an impartial route to challenge classification, evidence, denial of exception, or enforcement response. Corrects error and disciplines frontline discretion when the rule affects substantial interests. In the assembled archetype this component governs implementation, correction, and learning after adoption.

Design record. Separate initial decision, review authority, record, deadline, remedy, and anti-retaliation protection. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. An appeal controlled by the original decision-maker may exist on paper but not in substance. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Sunset and Reassessment Trigger

Schedules review or automatic expiry when evidence, context, technology, or risk changes. Prevents temporary emergencies and obsolete assumptions from hardening into permanent mandates. In the assembled archetype this component governs implementation, correction, and learning after adoption.

Design record. Set dates and event triggers, evidence owners, renewal criteria, and default outcome at expiry. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. Review without an expiry consequence encourages automatic renewal and institutional inertia. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

Compliance, Outcome, and Distribution Monitor

Tracks whether the rule changes behavior, protects the interest, shifts burdens, and creates evasion or exclusion. Closes the loop between normative design and real-world effects. In the assembled archetype this component governs implementation, correction, and learning after adoption.

Design record. Measure outcomes, compliance, error, burden, exception use, opt-out friction, and enforcement distribution. The record should identify evidence, accountable owner, affected groups, unresolved uncertainty, and the consequence of getting the classification wrong. It should be short enough to review but specific enough that a later decision-maker can distinguish changed evidence from changed preferences.

Boundary and test. High compliance can coexist with no benefit, hidden exit, inequity, or displacement into unmeasured channels. Reviewers should test the component against both a high-risk case and a legitimate-departure case. If it protects the former only by erasing the latter, scope is too broad. If it accommodates the latter while leaving the protected interest exposed, force is too weak or the exception is poorly bounded.

6. Mechanisms

Mechanisms implement the selected force. No mechanism proves that its own use is legitimate: an opt-out screen can support autonomy or hide coercion; a safe harbor can preserve innovation or entrench incumbents; a sunset can end obsolete authority or become a ritual prelude to automatic renewal. Selection therefore follows the diagnosed problem and inherits the parent safeguards.

Mandatory / Default Decision Matrix

Scores candidate rule forms against severity, externality, rights, reversibility, information quality, heterogeneity, and enforcement capacity. Use before drafting when stakeholders disagree about force. As a procedure, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. List forms from advisory through mandatory; define evidence and thresholds; compare burdens; record dissent and the selected form. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. Do not let numerical scores conceal rights-based limits or weak evidence. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

Opt-Out Architecture

Makes departure from a default legible, timely, low-friction, and reversible where appropriate. Use when a recommended path should coordinate ordinary cases without binding everyone. As a workflow, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. Present notice at the decision point, offer a symmetric alternative, confirm consequences, record choice minimally, and support later revision. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. Audit dark patterns, repeated prompts, stigma, bundled consent, and service degradation. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

Exception Review Protocol

Applies defined grounds and safeguards to departures from an otherwise mandatory floor. Use when a mandate is necessary generally but edge conditions are predictable. As a protocol, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. Receive a minimal request, provide interim protection, apply published criteria, document reasons, set duration, and allow appeal. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. Avoid unlimited discretion, burdensome proof, public disclosure, and unequal access to advocacy. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

Least-Restrictive Alternative Screen

Tests whether a less coercive or more targeted rule can achieve the protected outcome with acceptable residual risk. Use before adopting or renewing a mandate. As a procedure, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. Generate alternatives, estimate effectiveness and burden, test targeted scope, identify residual harm, and explain rejection. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. A screen is invalid when only straw alternatives are compared. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

Mandatory Floor with Safe Harbor

Combines a nonwaivable outcome floor with approved methods that presumptively satisfy it. Use where outcomes must bind but implementation can vary. As a institution, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. State the floor, publish safe-harbor methods, permit equivalent evidence, update methods, and preserve enforcement outside the harbor. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. Safe harbors can freeze incumbent technology or become de facto exclusive mandates. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

Default Enrollment with Notice

Places eligible people on a beneficial path while giving timely, salient notice and a usable way to decline. Use where participation is broadly beneficial, choice remains legitimate, and inertia causes avoidable nonparticipation. As a procedure, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. Confirm eligibility, enroll, notify before consequences attach, provide immediate opt-out, and monitor differential friction. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. Enrollment without meaningful notice or exit is a concealed mandate. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

Tiered Compliance Rule

Varies normative force or implementation duties by risk, scale, capability, or affected population. Use when one universal form would be underprotective for high-risk cases and excessive for low-risk cases. As a institution, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. Define tiers using observable criteria, prevent strategic down-classification, provide transition rules, and review thresholds. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. Complex tiering can invite gaming, cliff effects, and unequal enforcement. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

Sunset Clause and Periodic Review

Ends or reauthorizes a rule on a defined schedule using updated evidence and burden data. Use when uncertainty, emergency conditions, or technological change makes permanence hard to justify. As a protocol, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. Set an expiry, evidence package, accountable reviewer, public reasons, renewal test, and fallback state. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. A review date without genuine expiry merely ceremonializes renewal. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

Pilot and Reversibility Test

Trials a proposed mandate or default at bounded scale to measure effects before durable adoption. Use when consequences are uncertain and temporary testing is ethically and operationally possible. As a experiment, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. Predefine scope, metrics, stop conditions, comparison, support, reversal plan, and decision criteria. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. Do not pilot irreversible harms or shift experimental risk onto people unable to refuse. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

Appeal and Waiver Process

Corrects misclassification, evidence error, and disproportionate application through an independent review path. Use whenever a rule can materially affect rights, access, livelihood, safety, or status. As a procedure, it should have a named owner, documented inputs, completion state, and audit trail appropriate to the stakes.

Operating sequence. Give notice and record access, accept accessible filings, separate reviewer, pause avoidable harm, issue reasons, and provide remedy. The sequence should state what happens when evidence is incomplete, deadlines are missed, or the participant cannot use the ordinary channel.

Guardrail. Nominal appeal fails when deadlines, cost, language, or retaliation make use unrealistic. Monitor both aggregate results and distribution across affected groups; apparently neutral friction or discretion can concentrate burden.

7. Parameters

Harm severity and reach. Higher severity, wider third-party exposure, and lower reversibility support stronger floors. Severity must be tied to a causal pathway, not an emotive label. Low-probability catastrophic risk may justify a targeted mandate, but uncertainty should also narrow scope and increase review.

Choice validity. Choice is stronger when notice is timely, information comprehensible, alternatives usable, dependency limited, and consequences reversible. Where choice is structurally compromised, opt-in or opt-out language may provide form without autonomy.

Heterogeneity. Variation in capacity, context, technology, or legitimate preference favors performance standards, tiers, defaults, equivalent methods, or exceptions. Heterogeneity does not defeat a mandatory outcome when the protected interest remains common.

Externality and affected-party distance. The more departure shifts risk to people who cannot negotiate or observe it, the less individual choice can carry the decision. Map downstream and cumulative effects, not only immediate parties.

Evidence and enforcement capacity. A rule that cannot be observed accurately invites selective enforcement. Increase force only when evidence, error correction, privacy limits, and institutional capacity can support it. Otherwise redesign the outcome, narrow scope, or use nonpunitive assistance.

Opt-out friction. Measure time, steps, channel changes, disclosure, stigma, delay, repeated solicitation, and service degradation. A low aggregate opt-out rate is not evidence of preference unless friction and comprehension are known.

Exception width and duration. Narrow grounds protect the floor but may punish legitimate hardship. Broad discretion adapts but increases inconsistency and capture. Use published categories, temporary safeguards, expiry, reasons, and distribution review.

Transition horizon. Stronger or more technically demanding rules require notice, lead time, support, legacy treatment, and staged enforcement. Immediate effect is justified only when delay itself creates the protected harm and compliance is feasible.

Review cadence and sunset default. Stable, well-evidenced floors may use periodic review. Emergency, experimental, or technology-sensitive rules need event triggers or automatic expiry. Always name the fallback state at sunset.

8. Invariants

The protected interest and the authority to protect it remain explicit. “Safety,” “quality,” “fairness,” or “best practice” cannot stand alone as authorization. The rule applies no more force than the evidence and rights structure justify.

A mandatory floor is precise enough to distinguish violation from disagreement about preferred method. If methods can vary while preserving the outcome, equivalence remains possible. When methods cannot vary, the record explains the dependency.

A default remains genuinely defeasible. Notice appears before material consequences, the alternative is understandable and operational, and exit does not require accepting unrelated loss or retaliation. People can later revise the choice when reversibility is part of the justification.

Exceptions do not silently become the ordinary policy, and the ordinary policy does not erase edge cases. Grounds, evidence, interim protection, duration, reasons, and appeal remain defined. Comparable cases receive comparable treatment, with distribution audits where discretion is substantial.

Enforcement stays within a minimum-necessary evidence boundary. Records are correctable and purpose-limited. High-power actors and low-visibility violations are not exempt simply because enforcement is easier against visible individuals.

Material decisions receive notice, reasons, and review. Temporary rules have real review or expiry. Outcome and burden evidence can reduce as well as increase normative force.

9. Outcomes

The immediate outcome is categorical clarity. Governed parties know which elements bind, which are presumed, which remain optional, who may decide, and how departure works. Drafting, operations, and enforcement use the same categories.

Protective effectiveness should improve because mandatory force is concentrated where weak forms cannot control serious nonconsensual harm. At the same time, unnecessary compulsion declines because ordinary preference diversity, reversible decisions, and equivalent methods remain defeasible.

Legitimacy improves when reasons connect rule form to evidence, exceptions are accessible, enforcement is consistent, and appeals can correct error. Legitimacy is an operational outcome: it affects voluntary compliance, reporting, cooperation, and whether people evade or exit the system.

Innovation and contextual fit can improve when outcome floors replace method mandates and safe-harbor or equivalence paths remain open. Administrative burden may also decline when defaults handle ordinary cases while review capacity focuses on material exceptions.

Monitor adverse outcomes. A higher participation or compliance rate can conceal misunderstood defaults, coercive dependency, service exclusion, surveillance, or displacement. Report outcomes together with friction, hardship, exception, error, appeal, and distribution measures.

10. Tradeoffs

Protection and autonomy are not a single slider. Stronger rules can preserve the autonomy of people protected from others’ conduct, while weaker rules can preserve the chooser’s flexibility. Make each affected party visible before describing a change as freedom-enhancing.

Uniformity improves clarity and equal treatment but can misfit heterogeneous conditions. Tiering and exceptions improve fit but add classification disputes and discretion. Prefer a common outcome floor with varied methods when verification supports it; use tiers only where observable risk differences justify their complexity.

Defaults reduce cognitive burden and coordinate expectations, yet they allocate the cost of attention to anyone who differs. This cost is not trivial where language, disability, digital access, fear, or dependency affects exit. Symmetric channels and active monitoring reduce but do not eliminate the tradeoff.

Safe harbors provide certainty and reduce enforcement disputes, but approved methods can become incumbent protection. Equivalence review preserves innovation but demands technical capacity and can create delay. Publish criteria, deadlines, and reasons, and update approved methods.

Exceptions preserve justice but can undermine predictability and create moral hazard. The response is not zero discretion; it is structured discretion with accessible application, interim safeguards, bounded evidence, duration, reasons, and audit.

Sunsets preserve adaptability but can destabilize investment and make protection depend on recurring political attention. Match the review mechanism to uncertainty: stable outcome floors may persist while implementation details update more often.

11. Failure Modes

Hidden mandate. A rule called a default uses obscure notice, repeated pressure, different-channel exit, delay, stigma, or loss of unrelated service. Repair it through friction measurement, channel symmetry, clear consequences, and anti-retaliation protection. If no genuine exit can be offered, name and justify the mandate.

Underprotective choice. The system treats consent as sufficient even though departure imposes risk on third parties, dependents, workers, or future users. Identify who cannot authorize whose exposure and establish a narrow nonwaivable floor.

Preferred-method mandate. A regulator or organization mistakes familiar practice for the only acceptable outcome. Reframe the duty as a performance floor, add safe harbors, and permit equivalent evidence unless method dependence is demonstrated.

Exception capture. Waivers are formally available but usable mainly by people with lawyers, insider knowledge, time, or status. Simplify the process, provide assistance, minimize disclosure, separate review, and audit grants and denials by relevant group.

Selective enforcement. A vague or expensive evidence standard concentrates attention on visible, compliant, or low-power actors. Redesign for observable outcomes, constrain discretion, sample across risk, publish enforcement distribution, and drop rules that cannot be enforced fairly.

Permanent emergency. Temporary necessity becomes institutional habit. Use automatic expiry, a named fallback, updated evidence, burden review, and explicit reauthorization. Renewal must be a new decision, not administrative continuation.

Compliance theater. Actors satisfy paperwork while protected outcomes do not improve. Link measures to the harm pathway, sample actual results, track substitution and exit, and revise or remove low-value requirements.

Mandate fragmentation. Each unit adds individually reasonable requirements whose cumulative burden becomes incoherent. Maintain a rule inventory, map dependencies and conflicts, consolidate evidence requests, and review total burden.

Default discrimination. One default assumes resources, language, identity, technology, or family structure that does not fit many participants. Evaluate differential outcomes and friction, create accessible alternatives, and reconsider whether a single default is appropriate.

12. Variants

Safety-Critical Mandatory Floor. Use this form where departure can create severe, nonconsensual, or hard-to-reverse harm. Scope the floor to the protected outcome, retain equivalent methods when possible, provide hardship handling that does not expose others, and attach sunset review where uncertainty is material.

Welfare-Preserving Default with Opt-Out. Use this form where the recommended path benefits most people but preferences legitimately vary. Make notice salient, exit symmetric and nonpunitive, and later revision possible. Audit comprehension and differential friction rather than inferring preference from inertia.

Outcome Floor with Method Safe Harbor. Use this hybrid where the end must bind but multiple implementations can satisfy it. Approved methods provide certainty; an equivalence path prevents the harbor from becoming an exclusive technology mandate.

Adaptive Mandate with Sunset. Use this temporal form when delay creates harm but evidence or conditions are changing. Define expiry, fallback, renewal criteria, monitored burdens, and who owns the reassessment. The variant is not a license for indefinite emergency authority.

These variants stay under one parent because each selects and governs normative force using the same protected-interest, necessity, choice-validity, exception, enforcement, and review logic. Promote one only if evidence shows a cross-domain intervention with components and mechanisms not adequately represented by the parent.

13. Boundaries and Neighbor Distinctions

inertia_harnessing explains how existing momentum, habit, routine, and default paths can carry desired behavior. It can implement a default selected here, but it does not decide whether an interest is waivable, whether external harm justifies a floor, or how exceptions and enforcement should work.

informed_consent_governance determines whether agreement is informed, voluntary, specific, authorized, and revocable. It is essential when choice carries the rule. This archetype asks the prior governance question: may individual agreement legitimately waive the interest, or must some floor remain binding?

autonomy_supportive_constraint_design preserves meaningful choice within necessary limits. It overlaps in values but focuses on the experience and structure of constrained choice. Mandatory / Default Rule Design focuses on the legal or institutional status of the norm and the architecture connecting force to authority, evidence, exception, and review.

proportionality_calibration scales restriction, remedy, response, or sanction to severity and necessity. It informs the decision matrix and enforcement ladder, but it does not by itself choose among advisory, opt-in, default, rebuttable, or mandatory forms.

physical_constraint_design_for_impossibility changes the environment so prohibited action cannot occur. That may be appropriate when enforcement is too late or human error unacceptable. It is distinct because normative compliance, opt-out, evidence, and appeal no longer perform the decisive control function.

procedural_fairness_design supplies notice, voice, impartiality, reasons, and review across many decisions. It supports high-stakes application here, but this archetype’s distinctive intervention is selecting and layering normative force.

14. Examples

Employment benefits. An employer automatically enrolls eligible workers in a retirement plan because delay and inertia cause under-saving, while financial preferences vary. Notice arrives before deduction, explains the rate and consequences, and offers a same-channel opt-out or rate change. The employer measures comprehension and exit friction across language and access groups. This is a legitimate default, not a savings mandate.

Industrial exposure. A safety authority requires a nonwaivable exposure ceiling because workers and nearby people cannot individually authorize all downstream harm. Facilities may use listed controls or demonstrate equivalent protection. Temporary exceptions require interim safeguards, reasons, expiry, and independent appeal. The outcome binds; methods remain flexible.

Data security. A regulator sets a baseline protection floor for sensitive records, adds higher duties for risk tiers, and recognizes multiple audited frameworks. Small low-risk entities receive transition support rather than exemption from the outcome. Evidence standards, breach reporting, and appeals are defined. The design avoids both voluntary guidance that leaves third parties exposed and one technology mandate that freezes practice.

Emergency reporting. During an emerging hazard, an agency imposes time-bounded reporting because delay impairs collective response. The mandate covers only material events, minimizes data, and expires after ninety days unless new evidence meets published renewal criteria. The fallback is a narrower default reporting protocol. Renewal considers burden and distribution, not only submission counts.

Professional competence. A licensing body establishes a competence floor but allows examination, supervised practice, and portfolio evidence as safe-harbor routes. Applicants with documented barriers can seek adjusted process without waiving competence. Denials receive reasons and independent review. The mandatory interest is public reliance; the method is defeasible.

15. Non-Examples

Preselecting a harmless interface theme to reduce clicks is default design or inertia harnessing; no significant governance choice among waivable and nonwaivable interests is present.

Asking a patient to sign a dense form without assessing comprehension is an informed-consent failure. It may reveal a rule-force problem if an institution wrongly treats consent as waiving a protected floor, but disclosure repair is the immediate intervention.

Installing an interlock that prevents a machine from operating while open is physical constraint design. A policy requiring the interlock may be governed by this archetype, but the interlock itself works by impossibility rather than normative choice.

Raising a fine after repeated violations is proportionality calibration or graduated response when the mandatory duty is already justified and settled. The current archetype becomes primary only if the force, scope, waiver, or exception structure is being reconsidered.

Publishing “mandatory” guidance without authority, observable evidence, or a review route is not an instance of the archetype. It is an assertion of force without the architecture that could make it legitimate or effective.

A manager allowing favored employees to ignore a policy informally is not flexible rule design. It is unstructured discretion and unequal application. Defeasibility requires explicit grounds, accessible process, reasons, and comparable treatment.

16. Review and Open Questions

Frozen reconciliation strongly supports a distinct draft. mandatory_default_rule_design is a high-fit, promote-first Batch 048 candidate, and its governance cluster is explicitly marked “do not overmerge.” The cluster’s procedural-fairness anchor does not absorb the rule-force decision. The accepted direct source inertia_harnessing is established as a behavioral momentum pattern but has no components or mechanisms and cannot carry the governance architecture documented here.

Human review should test the boundary around “default.” In law and institutional design, default can mean a defeasible rule that applies unless parties validly alter it; in behavioral design, it can mean a preselected option. The draft intentionally covers both only where the higher-level intervention is selection of normative force. If future usage becomes confusing, the primary name could shift toward “Binding / Defeasible Rule Design” while retaining mandatory/default aliases.

Review should also test safe-harbor placement. A mandatory outcome with flexible methods is common across regulation, security, safety, and professional standards. It remains a variant here because its decision logic is a hybrid force architecture. Promotion would require evidence that equivalence assessment, assurance, and update mechanisms form a broader standalone pattern.

Additional examples should examine family law, consumer protection, platform governance, education, public health, and financial regulation, especially cases where individual choice affects third parties or where dependency weakens consent. Reviewers should look for counterexamples that expose overreach as well as underprotection.

Acceptance should remain conditional on canonical-prime validation, collision review, component/mechanism reuse review, and governance-domain expert review. The draft introduces no proposed primes. All variant source primes are canonical. Its recommended disposition is a distinct second-wave full archetype, not a merge into inertia harnessing, informed consent, proportionality, or procedural fairness.

Common Mechanisms

• Appeal and Waiver Process
• Default Enrollment with Notice
• Exception Review Protocol
• Least-Restrictive Alternative Screen
• Mandatory / Default Decision Matrix
• Mandatory Floor with Safe Harbor
• Opt-Out Architecture
• Pilot and Reversibility Test
• Sunset Clause and Periodic Review
• Tiered Compliance Rule

Compression statement

Define the protected interest and authority; compare advisory, opt-in, default, targeted mandate, universal mandate, and physical-constraint forms; choose the least restrictive form that reliably controls nonconsensual harm; make defaults and exits genuine; bound exceptions and enforcement; provide notice, appeal, transition, monitoring, and sunset review.

Canonical formula: legitimate_rule_force = protected_interest + valid_authority + necessity_test + meaningful_choice_where_possible + bounded_exception + verifiable_enforcement + review_and_sunset

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (6)

• Autonomy: A unit's behavior is governed by its own internal rules or chosen reasons rather than external direction, defined by the inner-versus-outer authority asymmetry over a scoped domain.
• Consent: Voluntary agreement.
• Constraint: Limits possibilities to guide outcomes.
• Mandatory vs. Default Norms: Binding vs flexible rules.
• Optionality: The asymmetric value of having a choice—bounded downside, unbounded upside—without obligation to act.
• Rule of Least Power (Minimum Sufficient Capability): Choose the least expressive mechanism that still solves the problem, because unused capability is structural debt that weakens analyzability and safety.

Also references 8 related abstractions

• Accountability: Responsibility for actions.
• Bounded Rationality: Limited decision capacity.
• Externality: Spillover effects.
• Fairness: Judging whether an allocation or procedure treats comparable parties impartially according to a defensible standard, given that multiple such standards can conflict.
• Legitimacy: Accepted authority.
• Procedural Fairness (Due Process): Due process.
• Proportionality: Match response to scale.
• Risk: Exposure to a known distribution of possible outcomes.

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Safety-Critical Mandatory Floor · risk or failure variant · recognized

Use a nonwaivable minimum where individual departure creates severe, nonconsensual, or difficult-to-reverse harm.

• Distinct from parent: Makes the mandatory side of the spectrum structurally primary.
• Use when: Failure can seriously harm third parties or dependent persons; Detection or repair after the fact would be inadequate.
• Typical domains: public health, industrial safety
• Common mechanisms: least restrictive alternative screen, statutory floor and safe harbor, appeal and waiver process

Welfare-Preserving Default with Opt-Out · governance variant · recognized

Use a salient beneficial default while preserving a practical, informed, and nonpunitive exit.

• Distinct from parent: Makes default-path integrity and opt-out symmetry the primary design problem.
• Use when: Most people benefit from the recommended path; Individual preferences legitimately differ and external harms are controlled.
• Typical domains: retirement savings, privacy preferences
• Common mechanisms: opt out architecture, default enrollment with notice

Outcome Floor with Method Safe Harbor · implementation variant · recognized

Mandate a protected outcome while allowing approved or equivalently verified methods of compliance.

• Distinct from parent: Separates mandatory performance from flexible implementation.
• Use when: The outcome must be protected but methods differ by context; Reliable verification can compare alternative implementations.
• Typical domains: building codes, data security
• Common mechanisms: statutory floor and safe harbor, tiered compliance rule

Adaptive Mandate with Sunset · temporal variant · recognized

Adopt a time-bounded mandate under elevated risk and automatically reconsider its force as evidence changes.

• Distinct from parent: Makes transition between mandate and default a designed lifecycle.
• Use when: Delay creates material harm but evidence or context is changing; A reversible bounded intervention is possible.
• Typical domains: emergency governance, technology regulation
• Common mechanisms: sunset clause and periodic review, pilot and reversibility test

Near names: Binding vs. Defeasible Rule Design, Mandate / Default Calibration, Normative Force Selection, Mandatory / Optional Rule Architecture, Waivable / Nonwaivable Rule Design.