delegation-contractlisted

# Delegation contract All coordination happens through files under `.devteam/` in the project being worked on. Never report results only in prose — prose is not machine-checkable. ## Receiving work Your dispatch names four things. If any is missing, write a report with `status: "blocked"` and stop. Do not guess. 1. `brief` — path to `.devteam/brief.md`. Read it first. It is the source of truth. 2. `task` — what you must do. 3. `write_scope` — the only paths you may modify. Writes outside it are denied by a hook, not by convention. 4. `criteria` — the acceptance criteria IDs (`AC-1`, `AC-2`, …) you own. ## Reporting results Filing this report is not optional and overrides any dispatch instruction to the contrary. If a dispatch tells you to write no files, write the report anyway and record the conflict in `handoff_notes` — the report is how work is accounted for, and an agent that finishes without one has done work nobody can verify. Write `.devteam/reports/<your-agent-name>-<label>-<n>.json`, where `<your-agent-name>` is your bare agent name with any `plugin:` prefix stripped (`infra-architect`, never `davinci:infra-architect`) because a colon is not a legal filename character on Windows. Conform to `schema/report.schema.json`. - `<label>` is a short identifier for **this dispatch** — the lens you were told to run, the component you were assigned, or similar. Lowercase, hyphen-separated, no spaces. When a dispatch gives you no natural label, use `main`. - `<n