feat: every Operational requirement verified by a Check; eval spread and report

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>
This commit is contained in:
2026-10-21 21:32:05 +01:00
parent efe543e6e2
commit 6fdac22876
12 changed files with 356 additions and 23 deletions

View File

@@ -232,6 +232,18 @@ GRAPH: dict[str, list[dict[str, Any]]] = {
"source": "OR-2",
"condition": "No change to the network is applied without the platform owner's approval.",
},
{
"id": "OC-5",
"on": "C-1",
"source": "OR-4",
"condition": "A recovery of the hub network is rehearsed each quarter within 4 hours.",
},
{
"id": "OC-6",
"on": "C-3",
"source": "OR-5",
"condition": "Every Role is placed in a country the customer allows.",
},
],
}