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

@@ -133,7 +133,7 @@ def test_the_scenarios_verdicts_are_written_into_the_validators_file_by_code():
"OC-3",
"OC-4",
]
assert len(merged["checks"]) == 14
assert len(merged["checks"]) == 16
# Merging again replaces the scenarios' verdicts; it never adds them twice.
again = json.loads(scenarios.merge(json.dumps(merged), found))
assert again == merged
@@ -165,7 +165,7 @@ def test_a_verdict_on_every_check_is_accepted():
def test_a_check_without_a_verdict_is_refused():
missing = {"checks": VERDICTS["checks"][:-1]}
assert verdict_faults(missing) == ["verdicts.json: Check OC-4 has no verdict"]
assert verdict_faults(missing) == ["verdicts.json: Check OC-6 has no verdict"]
def test_a_check_that_waits_on_a_finding_cannot_pass():