Who moves a task
Why Sparrow documents the task status workflow but lets anyone make any move.
The task status workflow says who makes each move and what it needs. Sparrow doesn't enforce it: it accepts a move from any status to any other.
- Agents are you, to Sparrow. An agent signs in as the person who started it (Agents and the MCP server), so Sparrow can't tell its moves from yours. Only a machine credential, the landing automation's, is a different caller (ADR-0018).
- A refusal wouldn't stop an agent. It would stop you: the shortcuts people take, such as closing a task straight from Planning, or dragging a card to another column.
- Sparrow has declined to refuse before. ADR-0022 and ADR-0025 each weighed refusing moves and chose a rule that agents follow instead. ADR-0027 does the same for the whole workflow: a documented, tested table, with no enforcement.
- The history shows every move. Each task records every status it moved into, when, and by whom: the person's user ID, or the machine credential's. A move that departs from the workflow stays visible there, for the reviewer.
- People can take shortcuts. Reopening a task, correcting a status or skipping a column is yours to do. The workflow binds the agents and the landing automation, which make only the moves in the table.
The laws set what agents must do, such as who completes a merged task (How work reaches main); the workflow describes those laws and Sparrow's own behaviour in one place.