Files
cp1-agents/individual-agents/ALZ-F01: Discovery Workflow Agent/docs/adr/0001.md
Jonathan Boniface 416c66ced4
All checks were successful
check agents / check (push) Successful in 10s
Add CP1 Discovery agents in both patterns
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>
2026-10-29 18:25:57 +00:00

1.0 KiB

0001. Eight separate agents chained by the KAB workflow, with no orchestrator

Status Accepted
Date 2026-10-29
Decided by Product owner (CP1)
Requirements changed None in the stories; this is the stories' own "no orchestrator" model, delivered the cp4-agents way

Decision

  • One declarative agent per ALZ-DSC story, in cp4-agents' shape and with no app/. Each calls its own read-only MCP tools.
  • The workflow wires them together (workflows/cp1-alz-discovery-individual.json): each step's inputs are named fields of earlier steps' outputs.
  • The orchestrator pattern stays separate in ../cp1-agents, so the two can be compared.

Consequences

  • The good: each agent can be deployed, evaluated and released on its own. Each has its own MCP identity, so per-agent allowlists hold, and no agent needs code.
  • The cost: the rules in the stories' pseudo-code are applied by each model, not by code, so the eval cases carry more weight. Nothing outside the workflow remembers a run (ADR 0010).