Standing missions: responsibilities on a schedule
Missions are now charters a team owns continuously — checked on a schedule, discharged with only the work that's needed. Plus schedule triggers for workflows, agent steps, and an Automation page for every clock in your deployment.
Until today, nothing in a Vocion deployment ran on a clock. The daily briefing was "daily" because someone clicked it. This release makes time a first-class trigger — and sharpens what a mission is along the way.
Missions are responsibilities, not projects
We'd been modeling missions as one-off assignments: brief in, plan out, done. But the missions that matter in a real deployment — "no conversation movement goes unrecorded," "no lead goes cold" — don't end. They're standing responsibilities a team owns.
So a mission is now a charter with an optional schedule:
goal: No lead or open deal ever goes cold.
schedule: "0 15 * * 1-5" # daily check-in, weekdays (UTC)
The litmus test: if the steps are the same every run, it's a workflow on a schedule; if discharging it takes judgment about what's needed this time, it's a mission.
On each tick, the team's lead gets the charter and a check instruction: review the current state, do only what's needed right now — search, run skills, queue proposed CRM updates for approval — and report. If nothing needs doing, say so in a paragraph and stop. No planner, one agent pass, cheap enough to run hourly. Manual briefs still work for ad-hoc planned work.
The boundary between the two work modes is now crisp: in a workflow the author decides the steps; in a mission the team decides. A mission can invoke workflows; a workflow can borrow an agent.
Workflows get clocks, events — and agents
trigger: {type: schedule, cron}— workflows now run on a cron, backed by Temporal Schedules and reconciled idempotently byworkspace:apply(edit the cron, re-apply, done).agentsteps — a fixed procedure can dispatch one step to a full agent (retrieval, subagents, proposed actions) and interpolate its answer downstream: fixed where you want determinism, open-ended where you need judgment.
One page for every clock
Dashboard → Automation lists everything that runs without a human pressing a button: mission schedules, scheduled workflows, event subscriptions, and source-sync crons — each shown as human-readable text ("12
PM, Monday through Friday (UTC)"), with next fire time and a link to the thing itself.