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:
@@ -29,3 +29,4 @@
|
||||
| T12 | The rate card Skill's format and checks | built (`steps/step-1.md`) |
|
||||
| T13 | Staffing and cost in code | built (`steps/step-1.md`) |
|
||||
| T14 | Evaluation with real models | built; two cases passed (`steps/step-2.md`) |
|
||||
| T15 | Every Operational requirement verified by a Check; the spread of repeated runs; a report to publish | A requirement no Check verifies is refused; three runs of each case report their spread | built (`steps/step-4.md`); runs in progress |
|
||||
|
||||
Reference in New Issue
Block a user