Dispatch, receipts, and acceptance
Two destinations
Pick where the work lands:
| Destination | Best for |
|---|---|
| Project root | Work inside a project, with its files, project memory, and rules; best for repositories and real folders |
| Standalone workspace (no project) | A temporary workspace; best for one-off analysis, a quick script, or tidying files |
Three ways to dispatch
- Just say it: “Check the clauses in this contract and get it to me before end of day.” MateBot records an item and dispatches it.
- Promote the item to a board card: use “⋯ → Promote to board card” on the item row, pick a project; the card enters the backlog for dispatch to an agent or expert.
- Project coordinator session: one session owns the whole project board — splitting cards, dispatching, and accepting. MateBot keeps only the item and the receipts.
Receipts
When the executor finishes, it returns a structured receipt: result, deliverables, and what needs your acceptance. The receipt is a task capsule in chat; open it to jump to the execution session.
- Result: done, partially done, blocked, failed, and so on — reported as it actually went
- Deliverables: files, diffs, and links come back with the receipt; view them in the artifacts panel
- Needs acceptance: the points you must confirm, written out clearly, before it comes back to you
Out-of-scope work is handed back
If a request doesn’t belong to the item, the executor hands it back with a reason instead of widening scope. You see the reason in the item, then decide whether to re-dispatch, add instructions, or open a separate item.
Acceptance
- An item enters Awaiting acceptance; it counts as done only once you confirm. Only you can reopen a Done item.
- If it isn’t right, say what’s wrong. The follow-up returns to the original execution session with its context intact.
- Deleting a session doesn’t delete the item; it only invalidates the binding. When needed, reopen the item and rebind it from the main link.
The board is read-only for MateBot
MateBot has read-only access to the board: it can see card status and leave comments, but it doesn’t create or change cards. Cards are created by you via “Promote to board card” on the item row, or by the project coordinator session or an execution session.
When work is stuck
| Ledger label | What to do |
|---|---|
| Waiting for your answer | The executor asked a question: open the linked session and answer |
| Waiting for your approval | A high-risk action needs approval: approve in the conversation or notification |
| Blocked | Missing file, permission, or dependency: read the reason in the receipt, fix it, re-dispatch |
| Failed | The run errored: open the session, read the log, fix it, retry |
How this splits with the board
The board is the project’s execution surface: cards have scheduling, review, branches, and worktrees. MateBot is the personal surface: it only guarantees that the work has an owner, a receipt, and an acceptance step. The two connect through “promote item to board card” and “write the card result back to the item after completion.”