# Step 2 — Implementation Detail 1. `needs_input` accepts an optional `draft` and `attachments`; `NeedsInput` carries them (`app/adk/runtime.py`). 2. The Execution state holds `drafts` by Deliverable kind. `orchestrator_turn` stores a draft when it applies a `needs_input` outcome and drops it when that Deliverable is submitted. 3. A Specialist's context carries `draft` (`{content, attachments}` or `null`). 4. `agents/partials/specialist-protocol.md` tells Specialists to pass the complete draft with their confirmation question, to submit it unchanged once the latest answer approves it, and to apply requested changes to it. Test: `test_a_draft_sent_with_questions_comes_back_with_the_answer` in `tests/execution/test_engine.py` shows the second run receiving the draft and the submitted content equalling it. The draft is not shown to the user by the engine; the Specialist's question still carries its summary. Whether the full draft should appear in the prompt is an open product question.