The task panel is the single place to see every matter step in the workspace at once, rather than opening matters one at a time. It is not a separate to-do store you keep in step with the work by hand: it is a live read over the matter engine, so the steps it shows are the real steps, with the real status, drawn from the one source of truth. Open it to answer the everyday question - across all the work in flight, what is active right now, and what is waiting.
What it does
A workspace-wide list of matter steps. A matter runs as an ordered pipeline of steps, and each step is a unit of work: a document to generate, data to gather, a gate to clear, a plain task. The task panel reads every one of those steps across the workspace into a single list, so you do not have to open each matter to see where its work stands. Each row shows the step’s title, the matter it belongs to, the step kind, and its status.
Computed live, never a copy. The list is read from the matter engine at the moment you open it, through the workspace-wide step read. It is not a second task table that someone has to keep current; it cannot drift out of step with the matters because it is the matters, projected into a list. The steps it shows are exactly the steps the matter pipeline holds.
Filter by status. Narrow the list to one status - pending, active, completed, skipped, or blocked - or leave it on all. Because a matter keeps a single active step at a time, filtering to active gives you, in one view, precisely what every matter in the workspace is currently waiting on, with no inference and no guessing.
Fenced to what you may see. The step read is permission-checked at the front door and scoped to the matters you are allowed to read, so the panel never surfaces a step from a matter outside your reach. The list you get is your list, fail-closed by construction, not a filter applied after the fact.
Open a step for its detail. Select a row and the panel shows that step’s full detail - its id, the matter, the step number in the pipeline, the step kind, and the status - read from the list already loaded rather than fetched again. The detail is everything the step record carries, surfaced honestly: the panel shows what the substrate holds, not fields it does not.
How you use it
Open the task panel. It loads the workspace’s matter steps into a single table - title, matter, step kind, and status - so you can take in the whole caseload’s work in one view instead of matter by matter.
Filter to what matters now. Set the status filter to active to see exactly what each matter is currently waiting on, to blocked to find work that has stalled, or to pending to see what is queued next. Leave it on all for the complete picture.
Open a step. Click a row to see that step’s detail - which matter it belongs to, where it sits in the pipeline, its kind, and its status. From the matter itself you then drive the step forward: activate the next one, skip one that does not apply, reopen one closed too soon, or send one back.
Stay told when work needs you. Your inbox carries the notices raised against your work, with an unread count per section, and you can mark items done as you clear them. Add a watch to follow a thing you care about, and you are told when it changes.
The kernel verbs behind it
Each goes through the one front door - permission-checked and audited before it runs. These are the verbs that back the panel and the work around it.
Reading the steps:
step.list- the workspace-wide matter-step read that fills the panel, filterable by matter or status and fenced to the matters you may read.
Moving a step:
step.activate- transition a pending step to active (the single-active-step cursor advance).step.skip- skip a step that does not apply to this matter.step.reopen- reopen a step that was closed too soon.step.reject- send a step back rather than accept it.
Being told, and following:
inbox.list- read your notifications, with the per-section unread count.inbox.get- open a single inbox item.inbox.mark- mark an inbox item done.notify.send- raise an outbound notice.notify.taxonomy- the fixed notification-kind taxonomy and per-kind suppression (the mute-matrix source).watch.add- follow a thing so changes reach you.watch.list- see what you are watching.watch.remove- stop following it.
The agent work-queue:
agenttask.list- read the queue of tasks the agents work from, with status and last error, for the operator console.
See the full set in the step verb reference.