Scope Validation Integrity
Agents write scope fields inconsistently and nothing catches it. Kind was added to the scope template and wired through the CLI — but 1 of 4 post-fix scopes omitted it entirely, 1 wrote an invalid compound value (`fix + chore`), and all 4 produced MISSING in the proof chain because the CLI binary was never rebuilt after the fix merged. The same pattern applies to Size (10 of 70 scopes used non-standard values like `small-medium` or `medium (with explanation)`) and Multi-phase (4 of 70 had trailing context that would break strict parsing). The validator at `ana artifact save scope` checks ACs, Structural Analog, and Intent — but doesn't check any Complexity Assessment fields. Agents populate what they want, the pipeline accepts it silently, and data is lost downstream.
Pipeline timeline
Intent to proven code in 1h 11m across Think, Plan, Build, and Verify.
Assertion ledger
24 claims, each independently verified. Showing 8 — show all →
| ID | Says | Matcher | |
|---|---|---|---|
| A001 | Scopes without a Kind field are rejected at save time | verified | ok |
| A002 | Scopes with an invalid Kind like 'fix + chore' are rejected with a message showing the bad value | verified | ok |
| A003 | Scopes with a valid Kind like 'fix' are accepted | verified | ok |
| A004 | Scopes without a Size field are rejected at save time | verified | ok |
| A005 | Compound sizes like 'small-medium' are accepted using lenient parsing | verified | ok |
| A006 | Sizes with trailing context like 'medium (8 items)' are accepted | verified | ok |
| A007 | Non-standard size values like 'tiny' are rejected | verified | ok |
| A008 | Scopes without a Multi-phase field are rejected at save time | verified | ok |