| 1 | # Collaboration modes and execution facts |
| 2 | |
| 3 | The composer offers Plan and Goal. There is no selectable quality floor. |
| 4 | Ordinary requests end when the model ends normally; pending todos and missing |
| 5 | checks do not cause host-generated continuation. |
| 6 | |
| 7 | ## Plan |
| 8 | |
| 9 | Plan previews work for approval. Before approval, the host blocks writes, |
| 10 | including Yolo, proxy tools and subagents. After approval, the model implements |
| 11 | the plan and feedback, updates todos, and judges completion. Acceptance notes |
| 12 | are task instructions; no sequential evidence signoff is required. |
| 13 | |
| 14 | ## Goal |
| 15 | |
| 16 | An active, armed Goal is continued by the runtime idle driver after every |
| 17 | normally completed top-level turn. No per-turn `continue` vote exists. |
| 18 | `update_goal(complete)` commits the model's completion declaration and |
| 19 | `update_goal(blocked)` stops continuation after the automatic-round minimum. |
| 20 | There is no independent completion evaluator. Restored and forked Goals are |
| 21 | always disarmed. Cancellation, queued user input, pending interaction, |
| 22 | persistence errors and explicit budgets retain their boundaries. |
| 23 | |
| 24 | Plan, Goal, permission, sandbox, and the task contract are independent states. |
| 25 | Read only, Workspace write, and Full access keep their public meanings. The tool |
| 26 | catalog stays stable so the prompt cache stays warm. The Harness minimal preset |
| 27 | is not a task complexity mode. |
| 28 | |
| 29 | ## Permissions and results |
| 30 | |
| 31 | Read only / Workspace write / Full access, sandbox restrictions and explicit |
| 32 | prohibitions remain action controls. They do not certify task quality. Tool results retain actual failures, |
| 33 | exit codes and interruptions. Checks that precede later edits are stale. |
| 34 | Model completion declarations and execution facts are distinct; unfinished |
| 35 | todos are not automatically marked complete. |
| 36 | |
| 37 | Plan mode is a workflow instruction, not a permission boundary. Writes stay |
| 38 | hard-blocked until the plan is approved, even under Full access. `complete_step` waits |
| 39 | for approval. |
| 40 | |
| 41 | See [execution semantics and migration](EXECUTION_MODEL_SIMPLIFICATION.md) and |
| 42 | [task instructions](TASK_CONTRACT.md). Tool ordering and serialization stay |
| 43 | stable within a version; historical provider-visible messages are not rewritten. |
| 44 |