Deferred-Action Checklist Marker¶
Artifact marker — instantiates Cue-Triggered Intention Execution
Parks a deferred action as a visible, unticked item on a checklist so it stays retrievable until it is explicitly closed off.
A Deferred-Action Checklist Marker is a single durable, visible entry on a list that holds a "do this later" until a review ritual resurfaces it and someone ticks it done. Its defining move is that the store is a persistent artifact you re-read, not a self-announcing event in the world and not a clock. The intention doesn't wait for something to happen; it waits for the checklist to be walked. What makes the marker work is that an un-ticked item is conspicuously incomplete — at the checklist's sign-off, an open box is an unmissable "you are not done yet." That is its whole leverage, and it is what separates it from cue-in-the-environment and time-fired siblings: the marker externalizes the record of intent into a list that is deliberately reviewed, and makes omission visible by leaving the box empty.
Example¶
A team is shipping a database migration and must temporarily disable a rate-limiter during the cutover, then re-enable it once traffic has drained. The re-enable step is exactly the kind of thing that gets forgotten in the relief of a successful migration. So it goes on the deployment runbook as an explicit line: [ ] Re-enable rate limiting on checkout-service (disabled in step 4). Through the migration nobody has to hold it in mind — it sits on the runbook, un-ticked, carrying its own context ("disabled in step 4"). At the post-cutover review the on-call engineer walks the runbook top to bottom, hits the open box, sees the intention it stored, performs it, and ticks it. Had they reached the runbook's end with that box still empty, the gap would have been obvious: a checklist is not signed off with open items. The action was retrieved not because an alarm fired, but because the list was read and the marker refused to disappear until closed.
How it works¶
- Write the payload into the item. The line states the deferred action in executable terms and carries enough context ("re-enable X, disabled in step 4") to act on cold.
- Leave it visibly open. The unticked box is the store: it persists on the artifact and signals incompleteness on every read, so the intention cannot quietly evaporate.
- Resurface at the ritual. The checklist's own review pass is the retrieval event — the item is found because the list is walked, not because it announced itself.
- Close by marking. Ticking (or annotating deferred/N-A) records the outcome and clears the item from the open set, so a still-open box at sign-off flags the omission.
Tuning parameters¶
- Item specificity — a terse tag versus a fully-contextualized instruction. More detail lets a different person close it cold, but bloats the list.
- Review cadence — how often the checklist is walked (per-deploy, daily stand-down, shift handover). Frequent reviews shorten the latency between intent and action but cost attention.
- Closure strictness — whether sign-off is blocked by open items or merely flags them. Hard blocks catch every omission but can wedge a process on a stale entry.
- Carry-over rule — whether an unclosed item rolls to the next checklist instance or must be explicitly re-parked, controlling how long a deferred action can drift.
When it helps, and when it misleads¶
Its strength is that it is nearly free, needs no infrastructure, and makes omission positively visible — the empty box is evidence. It shines when actions cluster around a recurring ritual (a deploy, a shift change, a close-of-day) that reliably brings the list back into view. The genre's canonical case for making the invisible-pending visible is the surgical and aviation checklist tradition.[n1]
Its failure mode is that the marker only fires if the list is actually read — a checklist that becomes rote, or is skipped under time pressure, buries its markers as surely as forgetting would. Over-long lists breed tick-without-reading; markers with no context become undecipherable months later. And unlike a timed or event cue, a checklist marker has no independent way to summon attention if the ritual lapses. The discipline is to keep lists short enough to be read honestly, block sign-off on open items where the stakes justify it, and route truly time-critical intentions to a firing cue instead of a passive marker.
How it implements the components¶
Deferred-Action Checklist Marker fills the record-and-close side of the machinery:
future_intention_payload— the item text names the deferred action in executable terms, with the context needed to perform it later.latent_intention_store— the persistent, visible checklist entry is the store, holding the intention without rehearsal until the review pass.action_closure_signal— ticking the box records execution and empties it from the open set, so an unclosed item at sign-off makes omission visible.
It manufactures no self-announcing cue and does no watching — the salient environmental trigger (cue_salience_amplifier) is Environmental Prompt Placement's, and continuous condition-watching (parallel_cue_monitor) is the daemon's; the marker simply waits to be re-read.
Related¶
- Instantiates: Cue-Triggered Intention Execution — it supplies the passive, list-based store whose retrieval is a review ritual rather than an event.
- Sibling mechanisms: Environmental Prompt Placement · Time-Based Reminder · Missed Trigger Review · Event-Based Reminder · Callback Registration · Event Listener or Monitoring Daemon · Cue Disambiguation Test · Execution Acknowledgement Loop
Editorial Notes¶
Form Classification¶
Form family: Interface, Display & Cue
Rationale: A visible unticked item carries an executable deferred action and context on the checklist until review resurfaces it and explicit marking closes it, so its operative form is a persistent action cue.
Nearest alternative: Record, Log & Register — Ticking or annotating records the outcome, but the mechanism works chiefly by keeping incompleteness perceptually present on every read.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Aviation safety cohered visible checklist items as durable, must-close controls against omitted deferred actions.
Related originating lineages:
- Medicine & Healthcare — Surgical safety independently institutionalized checklist sign-off for critical deferred steps.
Review resolution: Aviation safety cohered visible checklist items as durable, must-close controls against omitted deferred actions. The retained alternate lineages materially shaped the mechanism's form.
Attribution caveat: Aviation and clinical checklist traditions are both genuine lineages for the visible unclosed marker.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] The surgical- and aviation-safety checklist tradition — popularized for medicine in Atul Gawande's The Checklist Manifesto — works precisely by turning easily-forgotten steps into visible, must-close line items, so an omission shows up as an unchecked box rather than as silence. ↩