The general `deliverables/` ignore matched the folder inside each run's
Execution too, so the Deliverables as markdown (operating scope,
requirements, capability model, operating model, validation, guide) were
left out. They are now included for the published run only.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The evaluation (both cases three times: report, results, spread, each
run's Deliverables and lesson candidates) and the hand-off through the
Orchestration engine (report, the document of links, both agents' kept
files and records). Benchmark cases only, all fictional; no machine paths,
and the links carry no signatures. Other runs stay ignored.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>