Files
gcp_solution_architecture_a…/.agents/plans/iter-04-learning-and-skills/steps/step-21.md
Jonathan Boniface 5adc911a82 feat: keep an unchanged description, list conditions, review coverage with Jev
After case 02 (completed at 100%, but with two Revisions of the Target
architecture for gaps validation found one pass at a time):

- A Deliverable stands while what it was written from is unchanged. The
  architecture description is written from the Elements and Relationships,
  so a Revision that only adds or rewords Checks no longer runs the describer.
- Non-functional requirements and recommendations list their conditions,
  one entry per separate thing that must be true; submission requires them.
- A coverage review at submission (JEV_COVERAGE_REVIEW, off by default):
  for each condition, Jev chooses which Check verifies it, or none. Asked as
  one broad yes-or-no per requirement it could not tell a complete design
  from one with known gaps; asked as a choice per condition it raised all
  four known gaps of case 02 and nothing on the complete graph. An opt-in
  live test (LIVE_JEV=1) repeats that.
- The validator is told to report every gap in its first pass.

Plans record the case 02 run and both forms of the review with figures.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-07 20:58:38 +01:00

1.2 KiB

Step 21 — Implementation Detail

Built on 2026-10-07.

  1. DeliverableSpec.written_from returns one comparable value for what a Deliverable is written from. The architecture description's is graph_structure: the graph's Elements and Relationships, without its Checks.
  2. When a Specialist submits, specialist_task keeps the submission in the Deliverable's working memory with that value and the feedback it was written under.
  3. When the Deliverable is started again and the value and the feedback are the same, no Specialist is run: the kept submission is returned as the attempt's outcome. The Ledger records a submission as for any attempt.
  4. A note that a dependency was revised is not counted as feedback on the Deliverable. Anything else is, and has it written again.

Only the architecture description declares written_from. The code answers the Checks, so it is not kept; its working copy already makes its Revision cheap (27 and 88 seconds in case 02).

Unrun: no evaluation since. The saving expected on a case like 02 is the describer's second and third runs.

Tests: tests/execution/test_coverage_review.py, "a description stands while the shape of the design does" (4).