feat: establish the Target architecture as a graph before code

Design is now approved before any infrastructure code is written (ADR-0005).
A new target-architect Specialist produces one graph of Elements,
Relationships and Checks; the diagram is rendered from it, deployment
guidance must account for every Check, and validation gives a verdict per
Check. Requirements, components, products and recommendations carry ids in
data files, and a submission with a gap in the Requirements chain is refused.

Also in this commit:
- Customer cases group Executions, with an intent history per case
- lesson candidates are captured when an Execution ends
- evaluation gains chain, verdict, judged and interactive checks, and
  per-case thresholds
- Terraform providers are cached between checks
- the requirements analyst proposes defaults instead of asking
- the legacy-baseline case and the checks that only read it are removed
- ADR-0006 (Change requests) accepted; ADR-0004 and ADR-0007 proposed
- plans for iterations 4 to 7 under .agents/plans/

Unproven with a real model: no evaluation run has completed on this design.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-07 13:59:09 +01:00
parent 7ee49ab352
commit e9246828b3
586 changed files with 5166 additions and 22432 deletions

View File

@@ -121,3 +121,19 @@ Every step ends with the full suite passing. Steps that change agent behaviour (
- **Where:** `providers/gcp.yaml`, `app/providers.py`, `app/workflows/deliverables.py`, `app/presentation.py`, `agents/iac-author.md`, `agents/validator.md`, `agents/design-advisor.md`.
- **Timing:** Build when a second Cloud provider is planned. ADR-0002 says no provider interface exists in code until then.
- **Acceptance criteria:** Pillar headings come from `pillar_skills`, guide sections from the bundle's `output_template`, and the IaC tool with its file contract from the bundle. `grep -rni "terraform" app/workflows app/nodes app/states` is empty, and no pillar or guide-section name appears as a literal in `app/workflows/deliverables.py`.
## Step 15: Group Executions by Customer case
- **Report ref:** none; requested by the owner on 2026-10-06
- **Capability:** Everything under `deliverables/` is grouped by Customer case, so a case ties each request to the artefacts generated for it.
- **Rationale:** Outputs were keyed only by Execution id. Nothing on disk said which customer workload an Execution belonged to or what it had been asked.
- **Where:** `app/states/execution_state.py` (the case id rule and the paths), `ExecutionEngine.start` in `app/agent.py`, `_write_outputs` in `app/nodes/execution_nodes.py`, `app/main.py`, `app/a2a_server.py`, `eval/solution_eval.py`, `CONTEXT.md`.
- **Acceptance criteria:** Every Execution's files are under `deliverables/cases/<customer_case>/executions/<execution_id>/`. Each has a manifest naming the case, the request and every file. Each case has an index of its Executions and their requests. A case id that is not a safe slug is refused before anything runs. A Customer case never feeds one Execution into another.
## Step 16: Cache Terraform providers between checks
- **Report ref:** none; requested by the owner on 2026-10-07 to shorten a run
- **Capability:** A provider is downloaded once and reused by every later `terraform validate` and `plan`.
- **Rationale:** Each check runs `terraform init` in a new scratch directory, so every call downloaded its providers again. The setting `TF_PLUGIN_CACHE_DIR` existed and was unset by default.
- **Where:** `TerraformRunner` in `app/tools/local.py`, `app/config.py`, `.env.example`.
- **Acceptance criteria:** The cache is on by default and can be disabled. A second check of the same configuration does not download the provider. Concurrent checks cannot corrupt the cache.