Why
Triggers are where dispatch becomes a real control plane instead of a manual message router. They need to be powerful enough for cron/event-driven nudges and externalizer hooks, but inspectable enough that operators can understand what fired, what it did, and why.
Scope
Evolve triggers into an explicit when -> action -> lane dispatcher with clear command grammar, durable auditability, and safe failure behavior.
Acceptance criteria
- Move toward an ergonomic command family:
dispatch trigger adddispatch trigger listdispatch trigger rmdispatch trigger pausedispatch trigger resume- Keep/alias existing hyphenated forms if needed.
- Support time-based triggers:
- cron-style schedules.
- one-shot reminders if practical.
- timezone behavior documented and tested.
- Support event-based triggers from App Server / lane events where feasible:
- turn completed/failed/idle.
- goal changed/completed/blocked.
- approval needed or other useful lane state.
- Support action targets deliberately:
send / brief / context injection to a lane.- log-only/audit actions.
- shell command or webhook/externalizer hook only with explicit safety rules.
- Add inspection and safety UX:
trigger list shows enabled/paused, next run, target lane, action summary, last result.- A dry-run or explain mode shows what would fire and why.
- Every fire records an audit event with result/error.
- Failed actions have bounded retry or dead-letter behavior, not silent loss.
- Authority checks reuse the normal op handlers; triggers should not bypass lane permissions.
- Add tests for schedule parsing, event matching, action dispatch, audit records, pause/resume/remove, and failure behavior.
- Update docs/skills with examples for common operator loops.
Notes
Be conservative with automation. The dispatcher should be explainable first, clever second.
Why
Triggers are where dispatch becomes a real control plane instead of a manual message router. They need to be powerful enough for cron/event-driven nudges and externalizer hooks, but inspectable enough that operators can understand what fired, what it did, and why.
Scope
Evolve triggers into an explicit when -> action -> lane dispatcher with clear command grammar, durable auditability, and safe failure behavior.
Acceptance criteria
dispatch trigger adddispatch trigger listdispatch trigger rmdispatch trigger pausedispatch trigger resumesend/brief/ context injection to a lane.trigger listshows enabled/paused, next run, target lane, action summary, last result.Notes
Be conservative with automation. The dispatcher should be explainable first, clever second.