Command Explorer › sch:
Directive Shorthand 3.2 · Domain · Time
sch: — when things happen
Eight directives for timing: one per fundamental type of scheduling — one-shot, recurring, reminder, event-triggered, deadline — plus the lifecycle operations over all of them.
The sch: directives
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 this domain governs
When things happen — the timing of the agent's future actions, reminders, watches, and deadlines. sch: governs timing only: it designates when, while the work itself is specified in the message's prose and judged, when the item fires, under the host's ordinary approval rules. A sch: token never widens what may be done when the item fires.
Every token in this domain completes the same silent instruction — set when it happens … — written in the specification, never typed by the user. The prefix names the thing the phrase governs; the name after the colon qualifies it.
The domain's rules
- Never stacks. Each scheduled item is a distinct object, not a quality of one reply — one token records one item or performs one lifecycle operation. A message that needs two writes two tokens.
- The token fixes the type. The time, pattern, event, and action ride in the message's prose — exactly as
mem:'s content does. The confirmation restates them as recorded: that restating is how a fuzzy designation gets caught before it runs. - Every item is recorded and confirmed in the reply: what will happen, and when — in your terms, not a storage format.
- The payload split. Every type has the agent acting at the time — except
remind, which has the human nudged and the agent doing no work.
The directives
| Token | Axis | Shortest | Level | Meaning |
|---|---|---|---|---|
| sch:once | Type | onc | 2 | 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. |
| sch:again | Type | ag | 2 | Recurring: the agent performs the designated action repeatedly, on the pattern this message states in prose (daily, every Monday, each hour — the pattern rides in the prose; the token fixes the type). The agent records the recurring item and confirms the pattern it recorded. |
| sch:remind | Type | re | 2 | Reminder: at the time this message states, the user is notified — reminded — and the agent performs no work. This is the domain's payload split: every other sch: type has the agent acting at the time; sch:remind has the user nudged. Timing and recurrence ride in the prose; the token fixes the payload. |
| sch:watch | Type | wa | 2 | Event-triggered: no clock. When the event this message designates occurs — a reply arrives, a value crosses a threshold, a state changes — the agent performs the designated action. The event and the action ride in the prose; the token fixes the trigger type. The agent records the watch and confirms what it is watching for. |
| sch:due | Type | du | 2 | Deadline: the time this message states is a boundary, not a firing. The designated work is due by then; nothing executes at the boundary — instead, work still unmet at the boundary is overdue and is reported as such. The agent records the deadline and confirms what is due and by when. |
| sch:snooze | Lifecycle | sn | 2 | 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. |
| sch:pause | Lifecycle | pa | 2 | 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. |
| sch:stop | Lifecycle | st | 2 | Cancel a designated scheduled item outright: it will not fire again. Cancellation is confirmed in this reply; if the designation is ambiguous, ask rather than cancel the wrong item. |
Each directive page carries the detail: fired examples (typed, reply-targeted, and spoken), what the agent actually does under the hood, the honest fallback when a host lacks the capability, and the conformance test the directive must pass.