ALZ-F01 Discovery: package step, value scorecard, application grouping, cases

- New cp1-discovery-package-agent (ADR 0020): one package per reviewed run, every part
  hashed (sha256 over canonical JSON), with a manifest and a value scorecard.
- Applications grouped CMDB -> tag -> resource group with a judged model fallback (ADR 0021):
  CMDB 0.7.0 carries ownership, dependency mapping 0.6.0 groups, report 0.9.0 shows them.
- Critic 0.6.1 accepts the producers' enums; build_workflow.py refuses a consumer enum
  narrower than its producer's.
- Code hooks, sub-agents and tests for the inventory, CMDB, dependency, planner and critic
  agents; the report and Well-Architected review agents; ADRs 0012-0021.
- Workflow cases with value bars and run limits; run evaluation and usage collection scripts;
  the run context template and the field-by-field review for ADR 0016.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-05 22:13:25 +00:00
parent f659564208
commit 9e503885cc
211 changed files with 18170 additions and 158 deletions

View File

@@ -21,9 +21,19 @@ Each agent's `docs/adr/README.md` lists the records that change its own story.
| [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 | 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.