Reopen Trigger Monitor¶
Metric or dashboard — instantiates Decision Commitment and Closure
Tracks the assumptions, thresholds, safety boundaries, and external changes that were pre-declared as grounds to reopen a closed decision.
The Reopen Trigger Monitor is a standing watch that begins after a decision has closed. It holds a short list of pre-declared conditions — the specific assumptions, thresholds, and external facts whose violation was named at closure as legitimate grounds to reopen — and it watches them for as long as the commitment is live. Its defining idea is that reopening should fire on predeclared evidence, not on any fresh objection: an alarm, not a debate. That makes it the mechanism that holds the archetype's hardest balance — keeping a commitment stable enough to execute while leaving a narrow, bounded route back to deliberation when the factual basis genuinely breaks. It guards against two opposite failures at once: frozen error (ignoring disconfirming evidence) and reopening churn (letting every implementation gripe restart the argument).
Example¶
A drug's treatment protocol has been approved for a trial and execution is underway. At closure, the committee wrote down exactly what would justify reopening the protocol: an adverse-event rate above a set threshold, enrollment falling short of the assumption the dosing schedule relied on, or a newly published external trial contradicting a key safety premise. A Data Safety Monitoring Board holds those as a live watch-list.[n1] Each item has a data feed and an owner. When one investigator lobbies to change the protocol because a patient complained, the monitor's answer is procedural, not political: that complaint matches no predeclared trigger, so it is logged but does not reopen the decision. Months later the adverse-event feed crosses its threshold — a real trigger trips — and the protocol returns to deliberation with the specific violated assumption already on the table. The monitor's discipline is that only a tripped trigger reopens; everything else is noise it records without acting on.
How it works¶
The monitor is built by reading the rationale and assumption record produced at closure and lifting from it the load-bearing assumptions — the ones that, if false, would change the choice. Each becomes a watched item with three parts: a trigger condition stated as a testable threshold, a data source that tells whether it has tripped, and an owner accountable for watching it. The board then runs continuously: unmet triggers stay green; a tripped one fires an alarm that routes the decision back to its authority for a bounded review. Requests to reopen that cite neither a trigger nor genuinely new evidence are logged and declined by default. The monitor thus converts the vague standing question "should we revisit this?" into a small set of yes/no conditions.
Tuning parameters¶
- Trigger sensitivity — how tight the thresholds are set. Tight triggers catch drift early but risk churn; loose ones stabilize execution but risk freezing past a real break.
- Watch-list scope — how many assumptions are monitored. Watching everything drowns the signal; watching only the two or three decisive assumptions keeps the alarm meaningful.
- Monitoring cadence — continuous instrumentation versus scheduled review. Safety-critical triggers warrant live feeds; slow-moving ones a periodic check.
- Ownership — whether each trigger has a named watcher. Unowned triggers are the ones that silently fail to fire.
- Sunset — when the monitor is retired because the commitment horizon has passed and further watching is just overhead.
When it helps, and when it misleads¶
Its strength is that it makes a commitment corrigible without making it fragile: execution proceeds on the assumption that the basis holds, and the system only pays the cost of reopening when a named condition says the basis has broken. Stopping rules in clinical and safety contexts are the mature form of this idea — thresholds fixed in advance so that the decision to halt is not re-argued under pressure.[n2]
Its failure mode is mis-set triggers in either direction, and the subtler misuse is reversibility theater: a monitor that exists to look corrigible but whose triggers are written so vaguely or so tightly that they can never actually fire, leaving frozen error dressed as governance. The guarding discipline, straight from the archetype's invariants, is that triggers must be predeclared at closure — not invented afterward to justify reopening a decision someone simply came to dislike.
How it implements the components¶
reopening_trigger— the monitor is this component operationalized: the predeclared conditions, their data feeds, and the alarm that routes a tripped one back to deliberation.rationale_and_assumption_record— it reads the closing assumptions and watches each load-bearing one for violation, giving that record an active afterlife.
It implements nothing about the still-open decision: the pre-closure gauges closure_readiness_threshold, evidence_sufficiency_rule, and decision_expiry_or_review_date belong to Decision Clock, its pre-closure twin. The clock counts down to closure; the monitor wakes only once closure has happened.
Related¶
- Instantiates: Decision Commitment and Closure — the monitor keeps a closed commitment corrigible through bounded, predeclared reopening.
- Consumes: Decision Record Log supplies the assumption record from which the watch-list is built.
- Sibling mechanisms: Decision Clock · Go/No-Go Commitment Gate · Option Comparison Matrix · Precommitment Challenge Session · Decision Record Log · Signed Commitment Authorization · Execution Handoff Checklist · Reversibility and Exit Check
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: Reopen Trigger Monitor operates as ongoing observation, sensing, or alerting that detects and surfaces state without itself executing the response because it tracks the assumptions, thresholds, safety boundaries, and external changes that were pre-declared as grounds to reopen a closed decision.
Independent corroboration: The frozen evidence defines Reopen Trigger Monitor as 'Tracks the assumptions, thresholds, safety boundaries, and external changes that were pre-declared as grounds to reopen a closed decision', so its operative form is Monitoring, Sensing & Alerting.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Predeclared conditions for revisiting a decision are characteristic of organizational governance and decision management.
Related originating lineages:
- Systems Thinking & Cybernetics — Continuous comparison of external state against thresholds supplies the monitoring logic.
Review resolution: Both blind reviewers agree that organizational_management is the primary historical origin. Explicit reconciliation of origin mode disagreement adopts reviewer_a's evidence: Predeclared conditions for revisiting a decision are characteristic of organizational governance and decision management. The selected record uses alternates=systems_cybernetics, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; the other review proposed alternates=systems_cybernetics, origin_mode=single_lineage, and domain_reach=multi_domain. The selected combination better preserves the mechanism-specific formative lineages and calibrated scope; broader present-day use is not treated as proof of additional historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] A Data Safety Monitoring Board is an independent committee in clinical trials that watches accumulating safety data against predefined criteria and can recommend pausing or stopping a trial. It is a real-world instance of watching predeclared conditions rather than re-litigating a decision on demand. ↩
[n2] Stopping rules are thresholds fixed before a process begins that determine when it must halt — used precisely so the halt decision is not re-argued, under pressure, at the moment it matters. ↩