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>
5.9 KiB
Plans
One directory per iteration of this agent. Each holds the plan for that iteration and, for finished steps, the record of what was built. Read the row for the iteration you are working in, then its MAP.md.
Iterations
| # | Directory | Status | What it is |
|---|---|---|---|
| 1 | wf-decompose-65ea49fc2d04/ |
complete, superseded | The decomposer's scaffold: a linear four-phase pipeline of template functions. Its code was deleted in iteration 3 and survives only in git history. Generated by the platform decomposer; leave its files as written. |
| 2 | iter-02-solution-architect-agent/ |
complete; step 9 was done in iteration 3 | The rebuild as a hierarchical ReAct agent: Orchestrator, one Specialist per Deliverable, Skills, provider bundle, A2A. |
| 3 | iter-03-kab-layout/ |
complete (commit 7ee49ab) |
The container starts the new engine, the engine moved into the KAB workflow-agent folder layout, and the original pipeline was deleted. |
| 4 | iter-04-learning-and-skills/ |
steps 1–8, 11, 13 and 15–22 built; case 01 completed on them on 2026-10-07 (18 minutes against 60, 100%, no Revision); cases 02 to 04 have not run; 9 awaits the owner; 10, 12 and 14 planned | The enhancement backlog from the 2026-10-06 review: cheap fixes, the learning loop through Skills, overlay Skills, provider neutrality. Steps 17–20 are the speed-ups from the 2026-10-07 run: a working copy for files and the graph, a provider schema lookup, routing a Check the code cannot meet, and a model timeout per role. |
| 5 | iter-05-jev-decisions/ |
the Jev client and the Orchestrator router are built (steps 2, 11, 12), unverified against the live service; the rest planned | Jev (a hosted decision model) for the agent's closed decisions: checks, routing, context selection. |
| 6 | iter-06-target-architecture-graph/ |
steps 1–10 built; cases 01 and 02 pass with real models; cases 03 and 04 outstanding | The Target architecture as one explicit graph of Elements, Relationships and Checks, established before infrastructure code, with validation as a verdict per Check. |
| 7 | iter-07-change-requests/ |
planned; ADR-0006 accepted 2026-10-07; follows iteration 6; its step 8 (removing deliverables/cases/legacy-baseline/) was done early on the owner's instruction |
A user restates a request to say how requirements changed; a new Execution starts from a Baseline Execution of the same Customer case and delivers the updated architecture with what changed. |
Numbers record when an iteration was planned, not the order to build in. Build iteration 6 before the remaining steps of iteration 4 (10 to 14) and before iteration 5: it changes the Deliverables, Phases and validation format they build on. Its MAP.md lists the effect on each of their steps.
Two designs sit between iterations 1 and 2 and have no plan directory. Commit a24a44e wrapped the pipeline in a compatibility layer that imitated Google ADK without using it (deleted in iteration 3). .scratch/phase-pipeline/spec.md then designed a code-sequenced Phase pipeline; ADR-0002 reopened it before any of it was built, and its decision log (D1 to D46) explains how iteration 2's design was reached.
Files in an iteration
MAP.md: the intent, each step's status, the dependency graph between steps, and the sources of truth to read.DETAIL.md: per step, the capability, why it exists (with evidence), where the change lands, and the acceptance criteria.steps/step-N.md: written when step N is finished. What was built, what differed from the plan, and how it was verified. A step with no file is not done.
Steps are numbered from 1 in iterations 2 onward. Iteration 1 numbers from 0.
Working in an iteration
- Read
MAP.md, then theDETAIL.mdentry for your step and every step it depends on. - Read the sources of truth
MAP.mdnames. Plans point at specs and ADRs; they repeat only what those lack. - Build the step until every acceptance criterion in its
DETAIL.mdentry holds and.venv/bin/python -m pytest -q,.venv/bin/ruff check .and.venv/bin/mypy .all pass. - Write
steps/step-N.mdand set the step's status inMAP.mdtocomplete. When the last step closes, update the iteration's row above.
A new iteration gets the next number, a directory iter-NN-<slug>/, and a row above.
Module paths changed in iteration 3
Iteration 2's spec and ADR text name the modules by their old paths. The code is here now:
| Old path | Current path |
|---|---|
app/execution/deliverables.py |
app/workflows/deliverables.py |
app/execution/graph.py |
app/nodes/execution_nodes.py (nodes) and app/workflows/execution_graph.py (wiring) |
app/execution/engine.py, app/assembly.py |
app/agent.py |
app/execution/state.py |
app/states/execution_state.py |
app/execution/ledger.py |
app/states/ledger.py |
app/execution/tools.py, toolkit.py, pillars.py |
app/tools/execution.py, app/tools/toolkit.py, app/tools/pillars.py |
app/execution/recorder.py, checkpointing.py, presentation.py |
app/recorder.py, app/checkpointing.py, app/presentation.py |
app/agents/{runtime,adk_runtime,fake_runtime,roles}.py |
app/adk/ (same file names) |
app/agent_skills.py |
app/skills/agent_skills.py |
app/a2a/server.py, executor.py, card.py |
app/main.py, app/a2a_server.py, app/card.py |
the pre-rebuild app/agent.py, app/card.py, app/adk/, app/nodes/, app/workflows/, app/skills/, app/states/ deleted; in git history up to e94b249 |
|
tests/test_{adk_architecture,agent_api,graph_workflow,mcp_developer_knowledge,skill_loader}.py |
deleted |
eval/{metrics,optimizer,eval_harness,test_eval_harness}.py, eval/datasets/benchmark_cases.json |
deleted |
app/adk/, app/nodes/, app/workflows/, app/skills/ and app/states/ therefore mean different code before and after iteration 3. In text written before 2026-10-06, those names refer to the deleted original pipeline.