Assumption Expiry Timer¶
Review trigger — instantiates Propositional Mode Governance
A date, event, or evidence trigger requiring an assumption to be renewed, tested, replaced, or retired.
An Assumption Expiry Timer treats an assumption as a loan against evidence and stamps it with a due date. Its one distinguishing move among its siblings is that it binds a firing condition to a single proposition held in the assumption mode — a calendar date, a triggering event, or the arrival of a piece of evidence — after which that assumption may no longer simply be relied on. When the timer fires, the proposition's licence to be used lapses until someone actively renews, tests, replaces, or retires it. The target is one specific decay: assumption hardening, the drift by which a provisional planning assumption becomes a settled fact through nothing more than repetition. A register can list an assumption forever; the timer is what makes it come due.
Example¶
A relief agency is standing up a food-distribution corridor into a flood-prone region. Early planning rests on a working assumption: "the northern road across the river will stay passable through the operation." It is not a fact — no one has surveyed the bridge this season — but the whole route plan leans on it. Rather than let it calcify, the planners set an expiry timer: the assumption fires for review at the first of two triggers — the seasonal monsoon onset (an event) or the arrival of a district engineer's bridge-condition report (evidence), whichever comes first. Weeks later the monsoon window approaches and the timer fires. The corridor lead cannot keep routing trucks north on autopilot; the assumption is suspended pending action. They renew it for two weeks against a fresh scout report, with a hard note that if the bridge is downgraded they will replace it with a river-barge leg. The timer is what stops a convenient early guess from silently becoming the operation's foundation after everyone has stopped questioning it.
How it works¶
The timer binds three things to one assumption that a plain list does not: a firing condition, a named owner, and a response menu. The firing condition is the mechanism's core — temporal ("re-confirm by 1 June"), event-based ("on the regulatory ruling"), or evidence-based ("when the pilot's first cohort reports"). On firing, the assumption's operating licence is provisionally withdrawn and routed to its owner, who must pick a licensed response: renew (with a re-stated basis), test (convert it toward a hypothesis under investigation), replace (swap in a better assumption), or retire (drop it and re-plan). Every firing and response is logged, so the assumption's history stays inspectable instead of dissolving into a thread.
Tuning parameters¶
- Firing-condition type — date, event, or evidence. Dates are predictable but arbitrary; evidence triggers fire exactly when they should but require you to be watching for the evidence.
- Default on firing — what happens if the owner does nothing: silent renewal (dangerous), forced suspension, or auto-escalation. A stricter default makes it harder to let an expired assumption keep running.
- Renewal cap — how many times an assumption may be renewed before retirement is forced. This is the anti-hardening dial: an uncapped renewal is just hardening with extra steps.
- Ownership granularity — one named owner per assumption versus a shared queue; a named owner is chased, a pile is not.
- Grace window — how long an assumption may keep operating after firing while its review is pending. Wider grace keeps work moving but reopens the drift the timer exists to close.
When it helps, and when it misleads¶
Its strength is that it converts a static caveat into a scheduled forcing function: the assumption cannot outlive its warrant unnoticed, because a date or event drags it back into the light. It is the epistemic analogue of a sunset clause — a provision that lapses unless it is deliberately renewed.[n1]
Its failure mode is timer theatre: renewals become a reflex stamp, the owner re-confirms without re-examining the basis, and the ritual of expiry replaces the substance of review — so hardening returns wearing a compliance badge. A classic misuse is setting the expiry so far out, or the grace window so wide, that the assumption is retired long after it has already misled the plan. The guarding discipline is the renewal cap plus a rule that each renewal must re-state the basis and what would falsify it — a quick informal self-check, not a rubber stamp — so every renewal is a fresh decision rather than an echo of the first.
How it implements the components¶
mode_transition_protocol— firing is a governed transition: the assumption moves to renewed, under-test, replaced, or retired, and the change, its reason, and its authoriser are recorded.obligation_register— each timer is a dated, owned obligation to revisit; the set of live timers is a queue of epistemic work with due dates.misuse_and_drift_guardrail— its whole reason for existing is to catch assumption hardening before a provisional premise sets into an unexamined fact.
It does not map which operations each mode licenses (licensed_operation_matrix) — that is Mode-Operation Matrix — nor does it gate a claim's promotion by binding it to evidence (formal_proof_or_model_binding), which is Hypothesis Promotion Gate, its nearest twin: the gate blocks a hypothesis from rising to accepted status until evidence lands, whereas the timer forces an assumption already in use back down for re-examination when its trigger fires.
Related¶
- Instantiates: Propositional Mode Governance — the timer supplies the time-and-trigger dimension that keeps assumptions from hardening.
- Sibling mechanisms: Axiom Boundary Statement · Claim Status Labeling Standard · Decision Memo Epistemic-Mode Section · Epistemic Mode Linter · Epistemic Status Ledger · Hypothesis Promotion Gate · Mode-Operation Matrix · Premise Discharge Checklist · Proposition Lifecycle Board
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: A date, event, or evidence condition fires against a live assumption, provisionally withdraws its operating licence, and routes it to its owner for renewal, testing, replacement, or retirement, so its operative form is runtime control.
Nearest alternative: Rule, Policy & Commitment — The expiry condition is a standing rule, but automatic trigger execution and routing when state changes make the deployed mechanism a controller.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Automatic lapse unless an explicit renewal occurs is the defining logic of a legal sunset provision, here transferred to planning assumptions.
Related originating lineages:
- Futurism & Strategic Foresight — Assumption-based planning supplies signposts and deliberate renewal when load-bearing assumptions change.
- Organizational & Management Science — Management practice supplies the assumption register, ownership, and recurring operational review context.
Review resolution: Congressional Research Service descriptions of sunset provisions confirm automatic expiration at a specified time, while RAND assumption-based planning supplies monitored load-bearing assumptions and signposts. The lapse-and-renew core therefore makes law and governance primary, with foresight and management materially formative.
Attribution caveat: The timer is an Encyclopedia synthesis: its lapse rule is legal, while its monitored object and renewal workflow come from planning practice.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- Congressional Research Service — Program Administration Sunset Provisions
- RAND — Assumption-Based Planning and Army Planning
Notes¶
An assumption that survives its final renewal should not simply expire into nothing — the honest terminal outcomes are retire and re-plan or test and promote. A timer that only ever offers "renew" has quietly become a hardening machine; the response menu, not the clock, is what makes it governance.
[n1] A sunset clause (or sunset provision) is a law or rule written to lapse automatically on a set date unless it is actively re-enacted — the legislative device that forces periodic re-justification rather than letting a measure persist by inertia. The expiry timer applies the same logic to a proposition's epistemic standing. ↩