Window Expiry Rule¶
Procedure — instantiates Kairotic Window Alignment
Declares when evidence, attention, permission, or readiness has aged out and the prepared action must be revised or withheld.
A window expiry rule declares the moment at which a prepared-but-unfired action's basis — its evidence, attention, permission, or the receiver's readiness — has aged out, so the action must be revised, re-authorized, or withheld rather than sent stale. Its defining idea is that readiness has a shelf life, and firing a prepared action after its window has closed is worse than not firing at all. The rule is forward-looking about a not-yet-sent action's validity. It is not the post-response refractory hold, and it does not make the initial launch call; it kills or revives a prepared action whose moment may have passed.
Example¶
A newsroom holds a prepared exclusive under embargo — a data-driven story cleared to publish the instant a regulator's ruling drops. The expiry rule specifies the closing conditions in advance: if the ruling leaks elsewhere first, if the key source withdraws consent, or if seventy-two hours pass with no ruling, the prepared package is no longer valid as written. When a rival breaks the core fact early, the embargoed window has closed[n1] and the expiry rule fires: the "exclusive" framing is withheld, and the prepared fallback — a reaction-and-analysis angle — is substituted. The window's expiry, and the trigger that caused it, are written to a register so the next embargo is bounded more realistically. The arc: closing conditions set at preparation time → a decay signal arrives (a leak) → the window is declared shut → the action routes to its fallback → the outcome is logged.
How it works¶
- Defines closing conditions up front. Expiry is specified when the action is prepared, not improvised after the fact.
- Watches for aging on four axes — evidence, attention, permission, and receiver readiness.
- Triggers a fallback, not just a stop. On expiry the rule routes to revise / re-authorize / withhold, so an aged action has somewhere to go.
- Records the expiry to memory so shelf-life estimates for future windows improve.
Tuning parameters¶
- Shelf-life length — how long a prepared action stays valid; generous risks staleness, tight risks discarding a still-live action.
- Expiry-axis weighting — which of evidence / attention / permission / readiness dominates the decay judgment.
- Fallback aggressiveness — revise-and-resend versus withhold entirely.
- Re-authorization cost — how much fresh sign-off a revived action must earn before it can fire.
- Decay-versus-noise sensitivity — how much confirming evidence is required before a dip in attention or readiness counts as true expiry rather than momentary fluctuation; touchy settings retire live actions, sluggish ones let stale ones through.
When it helps, and when it misleads¶
Its strength is that it is the main guard against late arrival — a technically good action sent after the receiver has already chosen, adapted, or normalized the problem, when it becomes noise or even backfires. It also protects the preparer: by naming the closing conditions up front, it prevents the sunk-cost reflex to fire a package simply because so much work went into it.
Its failure mode is symmetric: an over-tight expiry discards actions that were still live (a still-open window mistaken for closed), wasting the preparation; an over-loose one lets stale actions leak out. The classic misuse is invoking expiry to quietly kill an action someone simply no longer wants to send — laundering a preference as a deadline. The guarding discipline is to base expiry on observable decay (a leak, withdrawn consent, a locked-in decision), log every expiry with the trigger that fired it, and keep the fallback path genuinely prepared so expiry is a switch, not a dead end.
How it implements the components¶
kairotic_window_definition— it supplies the closing half of the window definition: the explicit conditions under which the window is declared shut.fallback_timing_path— on expiry it routes the action onto its fallback (revise / re-authorize / withhold) rather than firing it stale.window_memory_register— each expiry and its cause are recorded, sharpening future shelf-life estimates.
It does not implement closing_and_refractory_signal or quiet_period_and_recovery_spacing — that's Cooldown After-Action Rule, which protects a receiver who has just responded; expiry instead retires a *not-yet-fired action whose basis has decayed.*
Related¶
- Instantiates: Kairotic Window Alignment — the expiry rule supplies the closing-condition-and-fallback logic that keeps stale actions from being sent.
- Consumes: Readiness Signal Dashboard supplies the decay signals the rule watches for.
- Sibling mechanisms: Cooldown After-Action Rule · Launch-or-Hold Gate · Prebrief and Activation Cue · Critical-Moment Playbook · Event-Triggered Outreach Workflow · Just-in-Time Intervention Protocol · Readiness Signal Dashboard · Stakeholder Pulse Check · Timing After-Action Review
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Window Expiry Rule operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it declares when evidence, attention, permission, or readiness has aged out and the prepared action must be revised or withheld.
Independent corroboration: The frozen evidence defines Window Expiry Rule as 'Declares when evidence, attention, permission, or readiness has aged out and the prepared action must be revised or withheld', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Control, Automation & Runtime — Window Expiry Rule includes features of a live operational control that automatically routes, enforces, adapts, or responds during execution, but its defining operation is a standing rule, threshold, contractual commitment, or policy constraint governing future conduct.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Window expiry rule is rooted in organizational management's workflow, staffing, review, and coordination tradition; historically that field developed the defining operation described here: declares when evidence, attention, permission, or readiness has aged out and the prepared action must be revised or withheld.
Related originating lineages:
- Law & Governance — Legal doctrine, regulatory governance, and procedural accountability has a distinct contributing or parallel lineage for the mechanism's defining operation: declares when evidence, attention, permission, or readiness has aged out and the prepared action must be revised or withheld.
- Library & Information Science — Library and information-science stewardship has a distinct contributing or parallel lineage for the mechanism's defining operation: declares when evidence, attention, permission, or readiness has aged out and the prepared action must be revised or withheld.
- Systems Thinking & Cybernetics — Systems science's feedback, boundaries, stocks, flows, and regulation tradition supplies an independent formative lineage for the mechanism's window expiry rule logic.
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
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] Embargo — a journalistic agreement fixing the earliest time a story may be published; its value is entirely time-bound and collapses the moment a competitor breaks the fact or the agreed release passes. It is a concrete case of a window whose closing condition retires a prepared action. ↩