Files
gcp_solution_architecture_a…/.agents/plans/iter-04-learning-and-skills/steps/step-25.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

1.1 KiB

Step 25 — Implementation Detail

Built on 2026-10-08.

  1. _write_outputs takes the Execution's final status and its Ledger. end_with_warnings now calls it, as finalize does.
  2. execution.json gains status (completed or completed_with_warnings), warnings, phases (each Phase's status), and a status on every Deliverable: submitted, or draft when something it depends on was reopened after it was written.
  3. With no Deliverable at all nothing is written, and the case's history records no files, as before.
  4. The solution guide is written only when it exists; an Execution that stopped before packaging has none, and the manifest says so.

Not covered: an Execution whose process is killed. It never reaches either end node, so it still writes nothing. The evaluation's progress file (iteration 6 step 11) records its time and tokens, not its Deliverables.

Also on 2026-10-08, outside any step: the CI workflow installs requirements.txt and requirements-dev.txt before linting and testing. It installed only ruff, mypy and pytest, so its test step could not import the application.

Tests: tests/execution/test_engine.py, two updated.