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>
Design is now approved before any infrastructure code is written (ADR-0005).
A new target-architect Specialist produces one graph of Elements,
Relationships and Checks; the diagram is rendered from it, deployment
guidance must account for every Check, and validation gives a verdict per
Check. Requirements, components, products and recommendations carry ids in
data files, and a submission with a gap in the Requirements chain is refused.
Also in this commit:
- Customer cases group Executions, with an intent history per case
- lesson candidates are captured when an Execution ends
- evaluation gains chain, verdict, judged and interactive checks, and
per-case thresholds
- Terraform providers are cached between checks
- the requirements analyst proposes defaults instead of asking
- the legacy-baseline case and the checks that only read it are removed
- ADR-0006 (Change requests) accepted; ADR-0004 and ADR-0007 proposed
- plans for iterations 4 to 7 under .agents/plans/
Unproven with a real model: no evaluation run has completed on this design.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Increment 5 of .scratch/solution-architect-agent/spec.md, test-first.
- agents/*.md: provider-neutral role files for the Orchestrator, nine
Specialists and the pillar advisor, with a shared Specialist protocol.
- app/agents/roles.py: load and validate role files; Skills, MCP
servers and models come from the provider bundle.
- app/agents/adk_runtime.py: AgentRuntime on google-adk 2.9 with a
per-run LlmAgent, role-scoped SkillToolset (no run_skill_script),
step budgets, early stop on turn-ending tools, LiteLLM models.
- app/execution/pillars.py + toolkit.py: design advisor fans out to one
advisor per WAF pillar in parallel.
- Specialists receive every earlier-Phase Deliverable as input.
- Bundle gains role_skills, pillar_skills and -latest Gemini aliases;
pin google-adk[extensions]==2.9.0.
- 37 new tests; full suite 158 passed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Increment 3 of .scratch/solution-architect-agent/spec.md, test-first.
- app/execution/deliverables.py: four Phases, nine Deliverables and
their Dependencies declared once, plus per-kind contracts (required
headings, attachments) checked by check_submission.
- app/execution/ledger.py: pure Ledger enforcing both acceptance
thresholds, Phase Approvals (including pre-approved mode and change
requests), Revision cascade with withdrawn Approvals, the revision
cap with escalation and user override, attempt numbers that reject
stale submissions, an ordered event log, and dict round-tripping.
- 37 new tests; full suite 102 passed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>