Command Explorer › sch: — when things happen › watch
sch:watch
When the event occurs, the action runs — no clock.
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
No clock: when the designated event occurs — a reply arrives, a value crosses a threshold, a state changes — the agent performs the designated action.
The registry's own words: 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.
Fire it — usage examples
“When the venue replies, tell me right away and draft a response.
sch:watch”→ the watch is recorded, and the reply confirms what is being watched for, on what source, and what will happen when it occurs.
“Watch the rent listings — if a two-bedroom under $1,800 shows up in the east end, tell me the same day.
sch:wa”→ a watch with the threshold recorded; the confirmation names the source and the threshold it will fire on.
Said aloud: “Lingo, schedule watch — when the venue replies, tell me.”
→ the watch is recorded and confirmed: the event, and the action.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “schedule watch”. Dictated directives fire deliberately, never by accident.
What the agent actually does
A watch entry: event, source, action. It fires once per occurrence unless your prose says otherwise (“every time” vs “the first time”). A watch on an event that has already occurred at recording time is reported as such, not fired silently.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-sch-watch ↗.
When the host can't
No event-watching capability on this host: say so plainly, and state the watch that would have been set. Never present periodic checking as event-watching, and never claim to be watching what the host cannot observe.
Conformance — “done when”
The watch is recorded with its event, source, and action confirmed — or the gap 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.