Command Explorer › sch: — when things happen › pause
sch:pause
Suspend an item until resumed — never deleted.
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 recurring or watched item stops firing until resumed. It is suspended, not deleted: its record, pattern, and history survive.
The registry's own words: Suspend a designated recurring or watched item: it stops firing until resumed. Resumption is by plain instruction (or by re-issuing the item); a paused item is never deleted and never fires while paused. The agent confirms what was paused.
Fire it — usage examples
“
sch:pausethe Monday numbers while I'm away.”→ the item stops firing; the confirmation says what was paused and that resumption is by plain instruction (“resume it”) or by re-issuing the item.
Quote a price watch's confirmation and reply: “
sch:pa— until I'm back.”→ that watch stops firing; its record and threshold survive untouched.
Said aloud: “Lingo, schedule pause — the Monday numbers.”
→ the item is suspended and confirmed as suspended, not deleted.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “schedule pause”. Dictated directives fire deliberately, never by accident.
What the agent actually does
A state change on the store entry: suspended. A paused item never fires and is never quietly deleted.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-sch-pause ↗.
When the host can't
No scheduling capability on this host: there are no scheduled items to pause; 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 is suspended and confirmed — or the no-match / ambiguity / inapplicable case is reported with nothing changed.
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.