feat: every Operational requirement verified by a Check; eval spread, report and published runs #1
Reference in New Issue
Block a user
Delete Branch "feat/eval-coverage-and-spread"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Every Operational requirement must now be verified by a Check, the evaluation measures it and the spread of repeated runs, and the runs of 2026-10-21 are published.
The architect's instructions and the
operating-chainSkill state the new rule; the test fixture gained the two Checks it lacked.Evidence
After:
test_a_graph_that_does_not_hold_together_is_refused[…OR-1 is verified by no Check]fails before the rule and passes after; 184 tests pass,ruffandmypyclean.Merge Danger
Door: two-way
Blast Radius: operating-models
Executions will be refused, and revised, where an Operational requirement has no Check: more Checks a model, possibly a Revision more a run, more for the validator to judge. The published results add 193 files (about 2.2 MB) of fictional benchmark data; the hand-off's links carry no signatures.
🤖 Generated with Claude Code