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:
@@ -92,6 +92,10 @@ def test_a_graph_that_holds_together_is_accepted():
|
||||
"Capability C-1 is needed 24x7, and no Role responsible for it works those hours",
|
||||
),
|
||||
(lambda g: g["checks"].pop(1), "Condition K-1 is carried by no Check"),
|
||||
(
|
||||
lambda g: g["checks"].pop(0),
|
||||
"Operational requirement OR-1 is verified by no Check",
|
||||
),
|
||||
(
|
||||
lambda g: g["checks"][0].update(on="C-9"),
|
||||
"Check OC-1 is on C-9, which is not",
|
||||
@@ -119,6 +123,14 @@ def test_a_graph_that_does_not_hold_together_is_refused(change, problem):
|
||||
assert any(problem in fault for fault in found), found
|
||||
|
||||
|
||||
def test_a_requirement_is_verified_through_the_conditions_it_comes_from():
|
||||
# OR-3 comes from K-1 and K-2: the Checks carrying them verify it.
|
||||
changed = graph()
|
||||
assert not any(c["source"] == "OR-3" for c in changed["checks"])
|
||||
|
||||
assert not any("OR-3" in fault for fault in faults(changed))
|
||||
|
||||
|
||||
def test_a_file_that_is_not_a_graph_is_named():
|
||||
assert "not valid JSON" in check({GRAPH_FILE: "{"}, upstream())[0]
|
||||
assert "must be an object with" in check({GRAPH_FILE: "[]"}, upstream())[0]
|
||||
|
||||
Reference in New Issue
Block a user