3 Commits

Author SHA1 Message Date
4c1f1662de docs: include each run's Deliverables in the published evaluation
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>
2026-10-22 09:39:02 +01:00
628b6ee170 docs: publish the runs of 2026-10-21
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>
2026-10-22 09:25:03 +01:00
efe543e6e2 feat: working TOM agent 2026-10-21 19:47:12 +01:00