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>
- Validator budget 15 to 30: recording verdicts in pieces for 100 Checks
used all 15 calls in one attempt.
- Plans record three runs on 2026-10-08:
case 02 completed at 100% with no Revision in 24 minutes;
case 03 completed at 100% with two Revisions of the design in 40 minutes;
case 04 (interactive) ended with warnings at 75%, on two router faults:
a reply that echoes the question is read as a change request, and the
router loops at the Revision limit. Neither is fixed here.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Increment 7 of .scratch/solution-architect-agent/spec.md.
- app/assembly.py: composition root building the engine from settings
and the provider bundle (roles, ADK runtime, MCP catalog, Terraform
tools, checkpointer, recorder).
- app/a2a: a2a-sdk 1.1 JSON-RPC server (v0.3 compatible) mapping tasks to
Executions; questions, Approvals and permissions pause as
input-required; Approvals accepted only as structured data; completed
tasks return the guide and code as artifacts; agent card derived from
the dependency graph.
- POST /generate runs a pre-approved Execution with the legacy keys.
- Specialist exceptions are relayed to the user; Orchestrator exceptions
fail the task. Engine accepts a caller-chosen execution id.
- Dockerfile installs checksum-verified Terraform and ships agents,
providers and skills; add mcp and a2a-sdk requirements.
- 17 new tests; full suite 206 passed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>