- An Execution's files are written as each Deliverable is submitted, marked
in_progress, so a killed process or one waiting for its user leaves them on
disk. A write removes files an earlier write left that it no longer has.
- A question about delivered work is answered from that Execution's solution
guide by the reply writer; a question about the service is answered as
before. Nothing is started for either.
- Lessons: prove writes only for lessons the Skill holds; the Skill records
the vendored Skill versions the lessons were read against, status names any
that changed, and a test fails until they are reviewed.
- Four more code patterns: Firestore, BigQuery, Eventarc and GKE.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A caller restates a request to say how requirements have changed, naming a
completed Execution of the same Customer case as the Baseline.
- app/baseline.py reads a Baseline from its files and refuses one that
does not exist, did not complete or belongs to another case, before
anything runs or is recorded. A Baseline is never modified.
- Requirements carry a change (unchanged, added, changed, removed) and a
reason. Submission is refused when a Baseline requirement disappears, an
id is reused, or an unchanged requirement's text differs. A removed
requirement stays on record and asks nothing downstream.
- Each Specialist starts from its delivered version; the graph and the code
are its working copy, and the description is carried over when the
design's shape is the same.
- app/workflows/changes.py compares versions by id and traces what each
changed requirement reaches; anything else that changed is listed as
unrequested. Approvals show the change for their Phase, and changes.json
is written with the full Deliverables.
- Intake no longer starts a message read as a change: it names the
Execution to give as the Baseline.
- A fifth evaluation case runs a request and then a change to it, with
four checks that the change is recorded, reaches Checks, stays contained
and costs less than its Baseline.
Tested with scripted agents only; no Change request has run with real
models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>