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>
35 lines
1.5 KiB
Markdown
35 lines
1.5 KiB
Markdown
# Plan Map
|
|
|
|
**Iteration:** 3, KAB layout
|
|
**Intent:** Make the deployed container run the hierarchical Execution engine, and house that engine in the KAB workflow-agent folder layout (`app/agent.py`, `app/main.py`, `app/a2a_server.py`, `app/states/`, `app/nodes/`, `app/workflows/`), with the iteration 1 pipeline first parked under `app/legacy/` (steps 2 to 6) and then deleted (step 7).
|
|
**Branch:** `feat/solution-architect-agent` (committed in `7ee49ab`, 2026-10-06)
|
|
**This directory covers:** steps 1 to 7
|
|
|
|
## Sources of truth
|
|
|
|
- `../README.md`: the old-to-new module path table.
|
|
- `../docs/KAB_WORKFLOW_AGENT_IMPLEMENTATION_GUIDE.md` and `../langgraph-workflow-agent/app/`, both relative to the repository root: the layout being matched.
|
|
- `docs/adr/0003-langgraph-holds-state-adk-agents-reason.md`: the engine the layout must keep unchanged.
|
|
|
|
## Status
|
|
|
|
| Step | What | Status |
|
|
|---|---|---|
|
|
| 1 | Container starts the Execution engine | complete |
|
|
| 2 | Legacy pipeline moved to `app/legacy/` | complete |
|
|
| 3 | Engine moved into the KAB folders | complete |
|
|
| 4 | Graph file split into nodes and wiring | complete |
|
|
| 5 | Refresh paths in the spec and ADR text | complete |
|
|
| 6 | Finish iteration 2's cleanup list | complete; two items carried forward in `steps/step-6.md` |
|
|
| 7 | Decide the future of `app/legacy/` | complete: deleted on the owner's instruction |
|
|
|
|
## Dependency graph
|
|
|
|
- Step 1: no dependencies
|
|
- Step 2: no dependencies
|
|
- Step 3: depends on step 2
|
|
- Step 4: depends on step 3
|
|
- Step 5: depends on step 4
|
|
- Step 6: depends on step 4
|
|
- Step 7: depends on step 6
|