cas-sos-motzkin-psd-not-sos-artifact-recheck
- Kind
- witness-replay
- Status
- checked
Supports: the committed Motzkin certificate re-checks from disk: 5 named obligations discharged in exact rational arithmetic, the certificate identified by id and kind, and the obligation count pinned so a checker asserting less exits non-zero
cargo run --release -q -p axeyum-cas --example sos_certify -- artifacts/sos-certificates/motzkin-psd-not-sos.json --expect-kind psd-not-sos --expect-id motzkin-psd-not-sos --expect-checks 5 Evidence notes
WHY THIS COMMAND CANNOT PASS ON A BROKEN RUN. The exit status depends on what the run found, not on the build succeeding, and both directions were verified 2026-09-01 on this host: (i) `--expect-checks 4` against the UNCHANGED honest artifact exits 1 with `expected 4 obligations, discharged 5`, so a checker that stopped discharging an obligation fails here; (ii) artifacts/instances/sos/negative-controls/motzkin-tampered-square.json exits 1 with `the squares expand to a polynomial differing from the target in 6 monomial(s)`, so a false certificate is refused. A TRAP for anyone extending this: `sos_certify --show` prints SIX lines for this certificate, because `dual-support` (crates/axeyum-cas/examples/sos_certify.rs:189) is a display-only line printed OUTSIDE the obligation loop and is not an obligation. Counting --show lines is not a substitute for --expect-checks. ON THE DISTINCTION QUESTION -- whether the certificate records every distinction its producer makes: the claim `M is not a sum of squares` is DEGREE-RELATIVE, and the certificate does record the degree it is relative to. `half_degree: 3` is a stored field, the checker builds the degree-3 monomial basis FROM it rather than inferring it from the dual functional's support, and artifacts/instances/sos/negative-controls/motzkin-dual-off-degree.json is the committed control for exactly that distinction. Two further controls, motzkin-dual-not-psd.json and motzkin-dual-nonneg-on-form.json, cover the two halves of the moment argument separately, so neither can be dropped without a test dying. This certificate shape therefore does NOT have the failure documented for nra_monomial_bound_cert, where the producer distinguished a strict from a non-strict bound and the certificate stored only the constant.