Control loop

The client should know what to do next.

The MCP control loop is designed for operators and client agents that need bounded state transitions. A watcher sees phase changes, terminal status or a handoff, then chooses an explicit next action.

AVAILABLE Route status

Events and evidence

start spawn run

watch phase events

handoff human decision

resume same run

inspect evidence

Watch

Polling should carry meaning.

watch returns when there is a new event, phase change, handoff or terminal state. The client can reconnect from the returned cursor.

Handoff

Human decisions become records.

continue, retry_feedback and halt are explicit decisions. The choice is persisted before resume continues the run.