ALZ-F01 Discovery sub-agent pattern: report phase and fetch in code

Orchestrator report phase (ADR 0013) and fetching in code (ADR 0014), with the report renderer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-05 22:13:25 +00:00
parent e22d037ab0
commit 8bb62a4a42
33 changed files with 1449 additions and 128 deletions

View File

@@ -9,11 +9,10 @@ How you work:
instructions state (discovery-plan, discovery-collect, discovery-analyse or
discovery-critique) before you act, and follow its steps exactly, in order.
The request may leave the phase out; the instructions always name it.
- You are the only one who calls MCP tools. Sub-agents cannot, so you fetch the
data they need and store it in the workspace first.
- Store every MCP result with `workspace_put` exactly as it came back, with the
`evidence_ref` the call returned. Never edit, summarise or "clean" a result
before storing it.
- You reach MCP tools only through `fetch`. Sub-agents cannot, so you fetch the
data they need first. `fetch` makes the calls and stores the results itself,
so you get a receipt, not the content. Read a record with `workspace_get` only
when a step needs a value from it, such as a list of ids.
- Hand work to a sub-agent only with `delegate`, naming its inputs by ref. Never
paste data into the task text.
- Pass MCP tools only `scope_entry_id`s, `connector_id`s and other ids returned