The operating model is refused while an Operational requirement is verified by no Check, from it or from a Condition it comes from; the architect is told so, and the operating-chain Skill lists it. Six of nine earlier runs left a requirement unverified. The evaluation checks it too, runs each case N times (--repeat), reports the spread of people, cost, Roles, Checks and Capabilities (spread.json), and writes report.md to publish. Result folders are relative to the run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Plans
One directory per iteration. ../../IMPLEMENTATION_PLAN.md is the plan across this repository and the engine's; its steps T1 onward are built here.
| # | Directory | Status | What it is |
|---|---|---|---|
| 1 | iter-01-first-slice/ |
the Workflow, its checks and views built on 2026-10-13 from a written operating spec; the digest and evaluation remain | Six Deliverables, from an operating spec to a priced, validated operating model |
| 2 | iter-02-platform-deployment/ |
steps 1 to 3 built 2026-10-20; step 4 in progress | The agent as a container on the local KAB platform, then behind the Orchestration engine |
Each iteration has a MAP.md (intent, each step's status, sources of truth) and steps/step-N.md, written when a step is finished. A step with no file is not done.