Tasks · work that closes the loop
Work that falls out of the narrative.
In Scopes a task isn't a sticky note in a separate tool — it's generated from a beat, owned by a human or an agent, and it commits a beat back when it's done. The loop is always closed.
Task generated from beat
Flagged: invoice 14 days overdue
Chase overdue invoice
All open tasks
- Send renewal terms to procurementdoneagent:renewal-ops↳ from beat #c1e9
- Chase overdue invoicedue 2dagent:finance↳ from beat #b740
- Book exec sponsor intro calldue 5dj. rivera↳ from beat #8f2c
- Review security questionnairedue 7dt. wong↳ from beat #3ad7
Every task carries the beat that caused it — so the question "why does this exist?" is always answered, for humans and agents alike.
Tasks are first-class primitives on the arc.
Agents generate tasks from signals automatically. Humans can also create tasks manually — either way, the arc knows.
Humans and agents are first-class owners. Tasks delegated to an agent carry the same provenance as tasks assigned to a person.
Each task has a due date and a priority. Overdue tasks surface in health scoring before a human has to notice.
Every generated task carries a backlink to the beat that caused it — so you always know why the task exists.
The closed loop
Completing a task writes a beat.
When a task is marked done — by a human or an agent — Scopes appends a beat to the arc automatically. Health recomputes, context updates, and the arc's trajectory advances. No manual logging required.
- Tasks created by agents from signals — no human scheduling required.
- Completed tasks nudge health upward — the arc can feel momentum.
- Overdue tasks drag health — so gaps surface before they compound.
no manual logging · automatic on completion
Let work close itself.
Tasks that come from the arc, owned by humans and agents, and write back when they're done.