Command Explorer › sch: — when things happen › snooze
sch:snooze
Defer an item to a later time, unchanged otherwise.
In the sch: domain
sch:once — One action, once, at the stated time.sch:again — The action, repeated on the stated pattern.sch:remind — At the time, you are nudged — the agent does no work.sch:watch — When the event occurs, the action runs — no clock.sch:due — A deadline: a boundary, not a firing.sch:snooze — Defer an item to a later time, unchanged otherwise.sch:pause — Suspend an item until resumed — never deleted.sch:stop — Cancel an item outright: it will not fire again.What it does
A designated scheduled item moves to a later time; everything else about it is unchanged.
The registry's own words: Defer a designated scheduled item: move it to a later time — the time this message states, or the host's stated default defer when none is stated. The item itself is otherwise unchanged. The agent confirms the item's new time.
Fire it — usage examples
Quote the confirmation of tomorrow's 9 AM check and reply: “
sch:snooze— push it to Monday.”→ that item moves; the reply confirms it and its new time.
“Push the Monday report by a day.
sch:snooze”→ the recurring item's next firing defers — and the confirmation states whether the pattern shifted with it.
Said aloud: “Lingo, schedule snooze — the nine o'clock check, to Monday.”
→ that item moves; the confirmation names it and its new time.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “schedule snooze”. Dictated directives fire deliberately, never by accident.
What the agent actually does
The item's time is edited in the scheduling store; the item itself is otherwise untouched. No time stated → the host's stated default defer applies, and the agent says that is what it did.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-sch-snooze ↗.
When the host can't
No scheduling capability on this host: there are no scheduled items to defer; say so plainly. If no item matches the designation, change nothing and say so; if several match, name them and ask.
Conformance — “done when”
The designated item sits at its new time and the confirmation states it — or the no-match / ambiguity is reported with nothing moved.
Persistence class: content-write. Execution report in the reply: required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.