Regress Termination Rule¶
Essence¶
Regress Termination Rule is the intervention pattern for deciding where a potentially endless chain of support should stop. It is useful when every answer invites another prior question: why accept this evidence, why trust that authority, why use that value, why stop at that cause, or why act before every assumption is proven.
The archetype does not pretend that foundations are absolute. It creates local, explicit, accountable closure. A team can say: for this decision, under these stakes, we will accept this assumption, authority, evidence standard, or principle as enough; here is what remains uncertain; and here is what would reopen the chain.
Compression statement¶
When inquiry can continue indefinitely because every reason, cause, authority, or norm requires a prior one, Regress Termination Rule maps the chain, names the relevant link type, defines a context-appropriate stopping criterion, records accepted assumptions and uncertainty residue, and specifies when inquiry must reopen.
Canonical formula: open_ended_support_chain + decision_need -> mapped_regress + explicit_base_or_sufficiency_rule + assumption_record + uncertainty_residue + reopening_condition
When to Use This Archetype¶
Use this archetype when a live decision or explanation is blocked by recursive demands for prior support. It fits governance decisions, policy rationales, research thresholds, incident analysis, strategy assumptions, formal modeling, and ethical or legal reasoning where complete justification is impossible inside the current frame.
It is especially useful when the group has confused responsible due diligence with infinite deferral. It is also useful when decisions are already being closed implicitly by fatigue, deadline, seniority, or institutional habit and those hidden foundations need to become visible.
Do not use it merely because a process needs a stop condition. A workflow timeout, algorithmic base case, convergence threshold, or project deadline may need Termination Condition Design or Convergence Criteria Design instead. This archetype applies when the chain being stopped is a chain of reasons, explanations, authorities, or norms.
Structural Problem¶
The structural problem is an unbounded support chain. A claim depends on a reason; the reason depends on a prior premise; the premise depends on a further source; the source depends on a deeper authority, cause, definition, or value. The chain can continue indefinitely.
Without a termination rule, two bad outcomes become likely. The first is paralysis: no decision is ever justified enough to act. The second is hidden closure: action proceeds anyway, but the actual stopping point is power, fatigue, urgency, or an unstated assumption. In both cases, accountability suffers. Either no one can act, or no one can inspect why action was allowed.
The underlying tension is that responsible reasoning requires support, while practical action requires closure. Regress Termination Rule resolves this tension by making the stopping point explicit, scoped, and reopenable.
Intervention Logic¶
The intervention begins by naming the focal claim or decision. This keeps the inquiry from expanding into every adjacent philosophical or operational question.
Next, the regress chain is mapped. The chain may involve evidentiary links, causal links, authority links, definitional links, feasibility links, or normative links. Distinguishing link types matters because each type requires a different base. Evidence questions need evidentiary sufficiency. Authority questions need legitimate jurisdiction. Normative questions need declared value sources or procedures. Causal questions need an actionable explanatory level.
The team then identifies candidate bases or sufficiency standards. These might be accepted axioms, first principles, burden-of-proof rules, evidence thresholds, legal authority, stakeholder ratification, risk standards, or bounded inquiry budgets. The threshold is calibrated to the stakes: irreversible and high-harm decisions demand stronger justification than reversible exploratory decisions.
Finally, the team records the stopping criterion, accepted assumptions, uncertainty residue, and reopening conditions. Closure is not treated as final truth. It is treated as a justified local base for action.
Key Components¶
Regress Termination Rule converts an open-ended chain of demands for prior support into a bounded, transparent, and reviewable decision base. The work begins by anchoring the inquiry: the Claim Under Justification names exactly what is being held open so the conversation does not drift into every adjacent question. The Regress Chain makes the sequence of support demands visible, showing whether the group is asking for prior evidence, deeper cause, higher authority, or more fundamental value. The Link Type Distinction prevents answering the wrong kind of question — authority cannot settle evidence, evidence cannot settle a value premise — by classifying each link in the chain. The Foundational Assumption names the premise the group is willing to treat as a provisional base, making it visible and contestable rather than buried.
The middle components fix the place to stop and calibrate how stringent that stop must be. The Stopping Criterion declares what counts as enough for the current purpose, whether a legal standard, evidence threshold, or stakeholder approval. The Sufficiency Threshold tunes that criterion to stakes: reversible exploratory decisions can use lighter thresholds, while irreversible or rights-affecting decisions require stricter ones. The Assumption Record documents the accepted base, why it was accepted, what depends on it, and who owns later review — the accountability artifact that makes closure inspectable. The Decision Scope Boundary keeps the closure local: this base is for this decision, this horizon, this risk class, not for all future uses.
The final components keep closure honest by acknowledging what was left unresolved and how it might reopen. The Uncertainty Residue names the doubts that remain after closure, allowing action to proceed without pretending deeper questions have disappeared. The Reopening Condition specifies what would force the group to revisit the closed chain — new evidence, changed stakes, observed failure, legal change. The Burden of Reopening allocates who must provide what reason to challenge the closure once action has moved forward, preventing both endless relitigation and rigid refusal to reconsider.
| Component | Description |
|---|---|
| Claim Under Justification ↗ | This component identifies the exact claim, decision, or action being held open. Without it, participants may keep changing the subject. The archetype works best when the group can name what needs justification now. |
| Regress Chain ↗ | The regress chain is the visible sequence of support demands. It shows whether the group is asking for prior evidence, deeper cause, higher authority, clearer definition, stronger feasibility proof, or more fundamental value justification. |
| Link Type Distinction ↗ | Link Type Distinction prevents the group from answering the wrong question. Authority cannot substitute for evidence unless the issue is legitimately procedural. Evidence cannot settle a value premise by itself. A causal explanation cannot automatically justify an ought-claim. |
| Foundational Assumption ↗ | A foundational assumption is a premise accepted provisionally as a base for current action. It is not sacred. Its value is that it is visible, named, and contestable rather than hidden inside a decision. |
| Stopping Criterion ↗ | The stopping criterion defines what counts as enough for the current purpose. It might be a legal standard, an evidence threshold, a risk threshold, a stakeholder approval condition, an accepted axiom, or a practical due-diligence rule. |
| Sufficiency Threshold ↗ | The sufficiency threshold calibrates the strength of the stopping criterion. Reversible low-stakes decisions can use lighter thresholds. Irreversible, safety-critical, public, or rights-affecting decisions require stricter thresholds. |
| Assumption Record ↗ | The assumption record documents the accepted base, why it was accepted, what depends on it, what remains weak, and who owns future review. It is the accountability artifact of the archetype. |
| Reopening Condition ↗ | A reopening condition defines what would make the group revisit the closed chain. New evidence, changed stakes, an observed failure, affected-party challenge, legal change, or contradiction may all reopen the decision. |
| Burden of Reopening ↗ | Burden of reopening defines who must provide what reason to challenge the closure after the decision has moved forward. It prevents both endless relitigation and rigid refusal to reconsider. |
| Decision Scope Boundary ↗ | The decision scope boundary keeps local closure from becoming universal certainty. The rule should say what the closure is for: this decision, this time horizon, this risk class, this model, or this governance context. |
| Uncertainty Residue ↗ | Uncertainty residue names the doubts that remain after closure. It lets action proceed without pretending that deeper questions have disappeared. |
Common Mechanisms¶
| Mechanism | Description |
|---|---|
| First-Principles Statement ↗ | A first-principles statement names the base premises the group will reason from. It implements the archetype only when paired with scope, sufficiency, uncertainty, and reopening logic. Otherwise it is just a statement of belief. |
| Assumption Log ↗ | An assumption log records accepted assumptions, dependencies, review owners, and reopening triggers. It is a mechanism for preserving accountability after the regress has been locally closed. |
| Burden-of-Proof Rule ↗ | A burden-of-proof rule allocates responsibility for justification. It answers questions such as: who must prove that the claim is safe, fair, legal, feasible, or worth reopening? |
| Decision Closure Criteria ↗ | Decision closure criteria turn abstract sufficiency into practical checks. They help a team decide whether enough support has been gathered for the decision class. |
| Evidence Sufficiency Rubric ↗ | An evidence sufficiency rubric calibrates the quality, quantity, diversity, and relevance of evidence. It is especially useful when the regress is evidentiary rather than procedural or normative. |
| Axiom Set ↗ | An axiom set is a formal base for reasoning. In mathematics, specification, modeling, or architecture, the axiom set can terminate proof regress by declaring what is accepted as primitive for the system. |
| Governance Authority Chain ↗ | A governance authority chain defines who can close recursive approvals or appeals. It must be legitimate, scoped, and reviewable; otherwise it becomes simple power assertion. |
| Research Stopping Rule ↗ | A research stopping rule defines when enough data collection, literature review, or analysis has been completed for a purpose. It is a mechanism, not the archetype itself, because it applies the pattern inside research. |
| Five Whys with Stop Rule ↗ | Five Whys can expose deeper causes, but without a stop rule it can create endless explanatory regress. The mechanism implements the archetype only when it names the actionable level and review trigger. |
| Review Trigger Register ↗ | A review trigger register preserves reopenability. It lists the events, evidence, or failures that would invalidate the current base or require renewed inquiry. |
Parameter / Tuning Dimensions¶
The main tuning dimension is depth of inquiry: how far back the chain must be traced before closure is acceptable. High-stakes or poorly understood decisions need more depth.
Another dimension is sufficiency strength: how much support is enough. This depends on harm, reversibility, urgency, public accountability, legal duties, and confidence in evidence.
A third dimension is scope of closure. Closure can apply to a single experiment, one product release, a policy cycle, a legal classification, a model version, or a whole governance standard. Narrow closure is safer when uncertainty is high.
A fourth dimension is reopenability. Some decisions should reopen easily when new evidence appears; others need stability and require a stronger burden of reopening.
A fifth dimension is authority distribution. Closure can be made by an individual owner, a peer review group, a community process, a formal board, or a legal standard. The correct distribution depends on legitimacy and stakes.
Invariants to Preserve¶
The first invariant is explicitness: the base assumption or sufficiency standard must be named.
The second invariant is scope limitation: the stopping rule closes the chain for a particular purpose, not for all possible purposes.
The third invariant is contestability: relevant actors must be able to inspect and challenge the rationale through a defined path.
The fourth invariant is reopenability: new evidence, changed stakes, or observed failure can reopen the chain.
The fifth invariant is uncertainty honesty: remaining doubts are recorded instead of erased.
Target Outcomes¶
A good application produces actionable closure. The decision can move forward because the group knows what counts as enough.
It also produces transparent foundations. The premises, standards, authorities, and values beneath the decision are visible rather than tacit.
It reduces performative delay. Requests for more support must connect to declared criteria rather than functioning as indefinite obstruction.
It improves legitimacy because affected or accountable actors can see what was accepted, what remains uncertain, and how the decision may be revisited.
Tradeoffs¶
The core tradeoff is closure versus truth-seeking. Stopping enables action, but it can truncate inquiry. The mitigation is proportional sufficiency plus reopening conditions.
Another tradeoff is stability versus responsiveness. If closure reopens too easily, action destabilizes. If it reopens too rarely, the foundation becomes dogma. Burden-of-reopening rules manage this tension.
There is also a transparency burden. Recording assumptions, support chains, and uncertainty takes effort. The level of documentation should scale with risk.
Finally, authority can produce clarity but also exclusion. If authority terminates a chain, its legitimacy and appeal boundaries must be explicit.
Failure Modes¶
Arbitrary closure happens when the chain stops because people are tired, senior leaders demand action, or time runs out. The mitigation is a written stopping criterion and assumption record.
Dogmatic foundation happens when a provisional assumption becomes unquestionable. The mitigation is scope limitation and reopening triggers.
Infinite deferral happens when no sufficiency threshold is ever accepted. The mitigation is a burden-of-proof rule and proportional evidence standard.
Wrong link type happens when the group uses the wrong base for the question. Authority does not settle empirical evidence; data alone does not settle values. The mitigation is link-type distinction.
Overbroad closure happens when a local stopping rule is treated as global truth. The mitigation is a decision scope boundary.
Hidden value foundation happens when normative premises are disguised as neutral facts. Pair with Normative Assumption Explicitness when this risk appears.
Neighbor Distinctions¶
Termination Condition Design stops processes, workflows, searches, or recursive operations. Regress Termination Rule stops chains of justification, explanation, authority, or norm support.
Convergence Criteria Design asks whether an iterative process has stabilized enough. Regress Termination Rule asks what foundation or sufficiency standard can end a support chain.
Satisficing Threshold Design defines good-enough action under bounded rationality. Regress Termination Rule may use satisficing logic, but only when the problem is recursive justification.
Foundational Assumption Audit would test the validity and consequences of existing assumptions. Regress Termination Rule sets and governs assumptions as stopping points for live decisions.
Normative Assumption Explicitness surfaces hidden ought-claims. Regress Termination Rule addresses the further problem that every ought-claim can invite a deeper why.
Variants and Near Names¶
Justificatory Regress Termination applies to endless demands for reasons or evidence. Explanatory Regress Termination applies to endless causal or interpretive why-chains. Authority Regress Termination applies to recursive approval or appeal chains. Normative Regress Termination applies to values and ought-claims. Reopenable Foundational Closure emphasizes the review conditions that keep a base assumption accountable over time.
Near names include justification stop rule, explanation stop rule, regress closure rule, foundational assumption rule, first-principles statement, assumption log, burden-of-proof rule, research stopping rule, and termination condition. Most of these are mechanisms or components unless the full intervention pattern is present. termination_condition is recorded as a proposed prime in this draft because it appears prime-like in roadmap controls but is not canonical.
Cross-Domain Examples¶
In public policy, a team may accept a defined evidence threshold and public-value premise for a staged rollout while documenting what would trigger reversal or redesign.
In incident analysis, investigators may stop at the actionable control layer while recording deeper systemic contributors for separate governance review.
In product strategy, a team may proceed from a provisional market assumption after defined discovery work, then reopen if launch signals contradict the assumption.
In legal compliance, a process may define final internal authority for a classification and the evidence required to reopen it.
In formal modeling, a team may define accepted axioms and boundary assumptions before running proof or simulation work.
Non-Examples¶
A philosophical debate about whether foundations exist is not this archetype unless it produces an operational stopping rule for a decision.
A meeting ending because time ran out is not this archetype. The clock stopped, not the regress.
A manager refusing further questions is not this archetype. Suppression is not accountable closure.
A model stopping after numerical convergence is usually Convergence Criteria Design or Termination Condition Design, unless the issue is why that convergence is sufficient for action.