A new Deliverable in the packaging Phase, produced by a delivery planner
after validation.
- The planner writes the plan as data: work packages that name the Elements
they deliver, and activities with days, what each follows, and whether the
team or the customer owns it.
- Code checks the plan against the design: every Element belongs to a work
package, and the activities can be scheduled.
- Code computes the schedule, with no more of the team's activities at once
than the team has people, and the critical path.
- Code writes the WBS dictionary (a work package is done when the Checks on
its Elements pass), the activity sequence and a timeline on a relative axis
from Day 0.
- The plan is checked against the delivery window from the agreed scope; over
it, the Deliverable says by how much and names the critical path.
- With a start date it also gives calendar dates and a Mermaid Gantt chart.
- The timeline is added to the solution guide, and the plan's length is in
execution.json and the packaging Approval.
Not run with real models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every Execution now begins by agreeing the scope, before requirements.
- A new Phase and Deliverable, produced by a scope analyst with two tools:
scope_read shows what is settled and what is not; scope_set records fields
with where each value came from (the request, the customer's answer, or an
assumption with its reason). Code checks each value against the catalogue.
- With someone present the analyst asks for what is missing; with nobody
present it assumes it, visibly. With no spec it drafts one from the request.
A value the customer stated in the file is changed only by their own answer.
- A submission cannot leave an essential field unknown. Code writes the
completed spec, the data every later Specialist reads, and the information
register, from what was recorded.
- The spec's status follows the Execution: under review, approved, then
locked as a Baseline. A Change request starts from the delivered scope.
- The requirements analyst derives from the agreed scope and no longer asks
for what it settles.
About 80 tests assumed requirements came first; tests/scoped.py runs scoping
ahead of a test's own script, and tests about order and counts are updated.
Not run with real models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reason sent back to the target architect says to read every Check against
it, and the IaC author records every Check that cannot be met in one
submission. Records the investigation of why the Target architecture is
revised: two causes, about half each (iteration 6 step 12).
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>
Case 04, the first interactive evaluation, stopped at 100 Orchestrator
turns on two router faults:
- A reply that quoted the agent's question back was judged on that question.
A reply now reaches the router with quoted questions and Q:/A: labels
removed, and the questions are given to the decider as background.
- At a Revision limit the reply was read as another change request for the
same Deliverable, and the refusal repeated. The user is now told once,
the reply is taken as the answer, that Deliverable is not reopened again,
and the Execution carries on with it as it stands.
- Any run that asks the user four times running with no work done in
between now ends with a warning.
The validator is told to confirm with the user in an interactive Execution.
Plans record the fixes and the rerun, which did not finish: both fixes
held, and a third fault appeared that is not fixed here. A scripted answer
restating a requirement, given to a draft-confirmation question, reopens
requirements.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>