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 stated time is a boundary, not a firing: the designated work is due by then, and work still unmet at the boundary is overdue and reported as such.
The registry's own words: 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.
Fire it — usage examples
“The venue quote is due Friday at 5.
sch:due”→ the deadline is recorded and confirmed as a boundary: “due by Friday 5 PM” — never as a firing (“will run Friday 5 PM”).
“The insurance paperwork is due on the 15th.
sch:du”→ the boundary is recorded; if the 15th arrives with the paperwork unfiled, it is reported overdue — not silently passed.
Said aloud: “Lingo, schedule due — the venue quote, Friday at five.”
→ the deadline stands as a boundary, confirmed in your own terms.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “schedule due”. Dictated directives fire deliberately, never by accident.
What the agent actually does
A deadline entry: the work, the boundary. Nothing executes at the boundary; the overdue report is the firing — it names the unmet work plainly. A deadline bounds work; it does not schedule the work itself.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-sch-due ↗.
When the host can't
No scheduling capability on this host: say so plainly and state the deadline that would have been recorded, as for sch:once. The deadline may still be tracked in the conversation's own terms, disclosed as conversation-only.
Conformance — “done when”
The deadline is recorded and confirmed as a boundary — 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.