# Architecture decision records: individual agents, ALZ-F01 Discovery Each record documents a change to the original requirements for ALZ-F01 Discovery: the ADO Feature 3214441, its stories 3214451–3214458, and the v1.1 story files (`drafts/cp1/agentic-landing-zone/stories/F01-discovery/` in the engineering hub workspace). These records apply to the **individual-agents pattern** in this Feature folder. The sub-agent pattern in `sub-agents/ALZ-F01: Discovery Workflow Agent/` keeps its own records, and the two patterns' decisions are separate. Which pattern is adopted has not been decided. Each agent's `docs/adr/README.md` lists the records that change its own story. **Status values:** - **Accepted:** decided by the product owner. - **Proposed:** built as a default and awaiting confirmation. | ADR | Decision | Status | Stories | |---|---|---|---| | [0001](0001.md) | Eight separate agents chained by the KAB workflow, with no orchestrator | Accepted | All | | [0002](0002.md) | Workflow hand-offs replace the `alz-run` tools | Accepted | All | | [0003](0003.md) | The MCP write tools are dropped; outputs go back in the reply | Proposed | DSC-03, 05, 06 | | [0004](0004.md) | The scan executor runs once per run and returns one finding per entry | Proposed | DSC-02 | | [0005](0005.md) | Inventory before CMDB reconciliation; the inventory gets CMDB records from `alz-inventory` | Proposed | DSC-03, 04 | | [0006](0006.md) | The critic's verdict is gated by human approval, not by code | Proposed | DSC-08 | | [0007](0007.md) | Agent names | Proposed | All | | [0008](0008.md) | Models: executors on `gpt-5.6-sol`, the critic on `gpt-5.4` (2026-11-03) | Accepted | All | | [0009](0009.md) | Deploy with kustomize; keys stay in Secrets | Accepted | — | | [0010](0010.md) | Step outputs travel through the workflow; there is no shared store | Proposed | All | | [0011](0011.md) | Uploaded files and project artifacts reach the planner and the inventory as text | Accepted | DSC-01, 03 | | [0012](0012.md) | The Discovery report comes from code, and the approval gate moves to it | Accepted | report (new) | | [0013](0013.md) | A `provider` input lets one workflow read the sample estate or a live cloud | Accepted | All | | [0014](0014.md) | A Well-Architected review step in Discovery, judged in code | Accepted | DSC-10 (new), report | | [0015](0015.md) | A live run's inventory is built in batches, at most three tries per batch; a batch that fails all three fails the step | Accepted | DSC-03 | | [0016](0016.md) | The run context file carries an intent, in the solution-architecture scope spec's format | Proposed | DSC-01, DSC-10, package, F02 | | [0017](0017.md) | A live run's scope is every resource under the scope root, planned and checked in code | Accepted | DSC-01, DSC-08 | | [0018](0018.md) | Uploaded CMDB exports are normalised by the model to our CI schema, and judged and reconciled in code | Accepted | DSC-01, DSC-03, DSC-04, DSC-08, report | | [0019](0019.md) | A live run's dependency graph is built in code: one graph of resource, external and CMDB CI nodes | Accepted | DSC-04, DSC-06, DSC-08, report | | [0020](0020.md) | One Discovery package for the Assessment workflow, with a manifest and a value scorecard, built in code | Accepted | package (new), F02 ASM-01 | | [0021](0021.md) | A live run's applications and asset owners are grouped in code: CMDB, then tag, then container, then a judged model proposal | Accepted | DSC-03, DSC-04, DSC-06, report, package, F02 ASM-01 | New records copy [template.md](template.md) and take the next number.