All checks were successful
check agents / check (push) Successful in 10s
ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight individual declarative agents (individual-agents/), with their KAB workflow exports. Shared check, render and import scripts, the alz-discovery-sample MCP server, the crucible-kab-dev deploy profile, deployment docs, platform issue reports and the source material. Agent steps time out at 20 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
0004. Discovery runs as four phases, one request each
| Status | Proposed |
| Date | 2026-10-29 |
| Decided by | Built as a default; awaiting product owner confirmation |
| Requirements changed | ALZ-F01 flow (planner → executors → critic as one continuous run) |
Context
A request is bounded to 25 minutes and a model-call budget, and nothing carries over to the next request. A whole estate doesn't fit in one request. The KAB workflow format passes only workflow inputs and earlier steps' outputs to a step, with no constant per step.
Decision
Four workflow steps call the same agent: plan, collect, analyse and critique. Each phase reads what earlier phases stored. Step 1 sends no phase, and every later step sends the previous step's next_phase. With no phase, the agent uses the run's last recorded outcome: a new run is planned, and a failed or halted phase stops the chain. The critique step asks the Engagement Lead to approve.
Consequences
- Each phase gets its own budget and its own artifacts, so provenance is per phase.
- No scan-batch loop: the workflow format has none, so collect runs every batch unless a request names one.
- A failed phase must be rerun by name, which is deliberate.