Files
gcp_solution_architecture_a…/.agents/plans/iter-06-target-architecture-graph/MAP.md
Jonathan Boniface 654370bb46 feat: all four evaluation cases pass; intake, checklist review, thresholds
Case 04 (interactive)
- A scripted answer may name who it is for, so facts written for
  requirements discovery are not given to a Specialist confirming a draft.
- A reply that restates what the agreed requirements already say is read
  as an answer, not a request for changes.
- With a user present, a first submission is refused until the user has
  been shown a draft of that Deliverable (CONFIRM_DRAFTS).

Routing and reviews
- Intake: a message that starts something is read first. A question is
  answered and starts nothing; a change to delivered work starts as a new
  request with a note, until Change requests are built.
- Requirements and recommendations list what infrastructure code can show
  (conditions) apart from what it cannot (outside_code); the latter needs
  no Check and validation proposes nothing for it.
- A requirements review, "names no products", behind its own switch (off).
- Each pillar advisor reviews its pillar's checklist; the engine writes the
  reviews into the design recommendations. The judged checklist check went
  from 9-45% a pillar to 100% in one run of case 04.

Evaluation
- Per-case thresholds for Revisions, seconds and tokens, set from every
  completed run on this build.
- A progress file after every agent run, so an interrupted run keeps its
  time and tokens.
- eval/calibrate_judge.py with a 32-question set awaiting a person's
  labels. Unlabelled: Jev stable at 1.00, Gemini 0.92, agreeing on 0.91.

Smaller
- An Execution that ends with warnings writes its Deliverables, with the
  warnings and each status in the manifest.
- CI installs the application's dependencies before linting and testing.
- A load-balancer pattern in the IaC patterns Skill.

Plans record nine runs of 2026-10-08. Iteration 6 is complete.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 09:32:57 +01:00

4.8 KiB

Plan Map

Iteration: 6, the Target architecture graph Intent: Establish the Target architecture as one explicit graph of Elements, Relationships and Checks before any infrastructure code is written, and derive and check every later Deliverable from it, so that the outcome is understood before code exists and validation has a fixed bar. Status: complete. Steps 1 to 10 built; all four cases, the interactive one included, completed twice with real models on 2026-10-08 and the thresholds are set (steps/step-11.md) This directory covers: steps 1 to 11

Order of work

Build this iteration before the remaining steps of iteration 4 (10 to 14) and before iteration 5. It changes Deliverables, Phases and the validation format that those steps build on. The effects on them are listed at the end of this file.

Sources of truth

  • docs/adr/0005-the-target-architecture-is-an-explicit-graph.md: the decision, its three points to confirm, and the rejected alternatives. Status proposed.
  • CONTEXT.md: Target architecture, Element, Relationship, Check, Requirements chain. Use these words; "Dependency" stays the link between Deliverables.
  • iter-04-learning-and-skills/steps/step-8.md, "The evaluation run of 2026-10-06": the evidence. Three validation passes gave 4, 7, then 5 different findings on the same Terraform.
  • docs/adr/0002-*.md: the graph's format and how to write it are behaviour, so they live in a Skill; the engine only checks the result.

The flow this iteration builds

flowchart TD
    REQ([Workflow request]) --> R[Requirements]
    R --> D[Technical decomposition]
    D --> A1{{Approval: requirements discovery}}
    A1 --> PS[Product selection]
    PS --> DR[Design recommendations]
    R --> DR
    PS --> TA
    DR --> TA[Target architecture: Elements, Relationships, Checks]
    TA --> A2{{Approval: design}}
    A2 --> DESC[Architecture description]
    A2 --> IAC[Deployment guidance]
    TA -.rendered by code.-> DIA[Architecture diagram]
    IAC --> A3{{Approval: implementation}}
    DESC --> A3
    A3 --> VAL[Validation: a verdict per Check]
    VAL -->|a Check fails| IAC
    VAL -->|the graph is missing something| TA
    VAL -->|every Check passes| A4{{Approval: validation}}
    A4 --> G[Solution guide]
    G --> A5{{Approval: packaging}}

Status

Step What Size Status
1 Accept ADR-0005 S complete: accepted 2026-10-07
2 Identify requirements, components and recommendations by id M complete
3 The graph: format, parsing and structural rules M complete
4 The Target architecture Deliverable, its Specialist and its Skill M complete; unproven with a real model
5 Completeness: the Requirements chain is a submission rule M complete
6 Split the solution architecture Phase: design, then implementation M complete
7 The diagram is rendered from the graph S complete
8 Deployment guidance implements the graph M complete
9 Validation gives a verdict per Check M complete
10 Revision routing: the code or the graph S complete; routing unproven with a real model
11 Evaluation: prove the loop converges M complete: all four cases pass, each run twice on 2026-10-08; thresholds set (steps/step-11.md)

Size: S under a day, M a few days.

Dependency graph

  • Step 1: no dependencies
  • Step 2: depends on step 1
  • Step 3: depends on step 1
  • Step 4: depends on step 3
  • Step 5: depends on step 2, step 4
  • Step 6: depends on step 4
  • Step 7: depends on step 4
  • Step 8: depends on step 5
  • Step 9: depends on step 8
  • Step 10: depends on step 6, step 9
  • Step 11: depends on step 7, step 10

Steps 2 and 3 can be built side by side, as can 6 and 7.

Effects on other iterations

  • Iteration 4 step 1 (findings.json): replaced by the verdicts of step 9 here. The free-form finding list goes.
  • Iteration 4 step 4 (contracts): the diagram's contract goes with the diagrammer; the decomposition's component table becomes data in step 2 here.
  • Iteration 4 step 6 (Orchestrator step order): rewritten by step 10 here.
  • Iteration 4 step 7 (lesson candidates): finding candidates become failed Checks and proposed additions.
  • Iteration 4 step 8 (evaluation): no_blocking_findings is rewritten against verdicts; the unset thresholds are set by step 11 here.
  • Iteration 4 step 11 (IaC patterns Skill): its patterns should be keyed by the product of an Element.
  • Iteration 4 step 13 (trim Specialist context): mostly achieved here, since later Specialists work from the graph. Re-scope it after step 11.
  • Iteration 5 step 5 (finding-to-Deliverable routing): no longer needed; a failed Check already names what it applies to.
  • Iteration 5 step 4 (semantic checks at submission): can judge whether each Check is verifiable as written.