Files
gcp_solution_architecture_a…/.agents/plans/iter-04-learning-and-skills/steps/step-2.md
Jonathan Boniface e9246828b3 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>
2026-10-07 13:59:09 +01:00

1003 B

Step 2 — Implementation Detail

  1. needs_input accepts an optional draft and attachments; NeedsInput carries them (app/adk/runtime.py).
  2. The Execution state holds drafts by Deliverable kind. orchestrator_turn stores a draft when it applies a needs_input outcome and drops it when that Deliverable is submitted.
  3. A Specialist's context carries draft ({content, attachments} or null).
  4. agents/partials/specialist-protocol.md tells Specialists to pass the complete draft with their confirmation question, to submit it unchanged once the latest answer approves it, and to apply requested changes to it.

Test: test_a_draft_sent_with_questions_comes_back_with_the_answer in tests/execution/test_engine.py shows the second run receiving the draft and the submitted content equalling it.

The draft is not shown to the user by the engine; the Specialist's question still carries its summary. Whether the full draft should appear in the prompt is an open product question.