Making things
Tasks
NowA task is a unit of intent with a status and an owner — the atom of tracking, findability, and review, and the thing that replaces the chat transcript.
What a task contains
Task
├─ Intent the request, verbatim ("Create a landing page for X")
├─ Context refs what it was scoped to: selection, frame, file, docs
├─ Owner you · a teammate · an agent
├─ Plan items the checklist the owner derives — each checkable
├─ Activity the work log, CI-log style, collapsed by default
├─ Artifacts frames, files, flow nodes, reports it touched
├─ Outcome "1 page, 4 sections · 3 files · preview ready"
└─ Review attribution + Accept / Revert-batch / comment
Status lifecycle
draft → queued → running → needs-input → needs-review → done (plus archived). needs-input is an agent question waiting on you; needs-review never blocks other work but sits at the top of the agenda until you look.
Three densities, one object
The same task renders as a block in the thread (intent, owner, live plan items, then the receipt), a row in the agenda (status dot, title, owner, age, receipt), and a card on the board. Click any of them to open the full task dashboard — header, Conversation, Changes, and Activity. The thread is just one section of it.