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:
@@ -59,7 +59,7 @@ Sub-agents cannot hold MCP tools, so the orchestrator makes every call itself. A
|
||||
|---|---|
|
||||
| `app/artifacts.py` | Imports uploads and project artifacts into the workspace (plan phase only): files read only from the executions volume, size-capped, provenance kept in a separate record sub-agents never get. |
|
||||
| `app/workspace.py` | Write-once records under `$EXECUTION_STORAGE_ROOT/alz-discovery/<engagement>/<run>/`, chained in `manifest.jsonl`. These are the data, context and memory the phases and sub-agents share. |
|
||||
| `app/tools.py` | `workspace_put` / `workspace_get` / `workspace_list`, and `delegate`, which hands work to a sub-agent and stores its reply with a hash. |
|
||||
| `app/tools.py` | `fetch` / `workspace_get` / `workspace_list`, and `delegate`, which hands work to a sub-agent and stores its reply with a hash. |
|
||||
| `app/rules.py` | The story files' rules as code: plan checks, match score, record confidence, ghost action, roll-up, edge score, node metrics, overlaps, bottlenecks, coverage. |
|
||||
| `app/business_logic.py` | `pre_process` binds the run, infers the phase and refuses a phase whose predecessor hasn't run. `post_process` rebuilds the reply from the workspace and enforces the verdict. |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user