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
The designated action is performed once, at the time your message states. Nothing is performed now.
The registry's own words: One-shot: the agent performs the designated action once, at the time this message states (an absolute time or a delay — the time itself rides in the prose; the token fixes the type). Nothing is performed now; the agent records the item and confirms what will happen and when.
Fire it — usage examples
“Check whether the venue replied tomorrow at 9 and summarize it for me.
sch:once”→ a one-shot item is recorded, and the reply confirms what will happen and when. Nothing is checked now.
“In two hours, ask me how the draft reads.
sch:once”→ a relative time works the same way.
Said aloud: “Lingo, schedule once — check the venue reply tomorrow at nine.”
→ the one-shot is recorded and confirmed: what, and when.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “schedule once”. Dictated directives fire deliberately, never by accident.
What the agent actually does
An entry in the scheduling store: action, time, type one-shot. At the time, the agent performs the action under the same approval rules as a live request — an action approval would refuse then is not promised now.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-sch-once ↗.
When the host can't
No scheduling capability on this host: say so plainly, state in the reply the item that would have been set (action and time) so the user can place it in their own tools, and never claim a scheduled item exists.
Conformance — “done when”
The item is recorded with action and time, and the confirmation states both — or the missing capability / unidentifiable designation is reported with nothing recorded.
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.