cas-sos-damped-rotation-lyapunov-artifact-recheck
- Kind
- witness-replay
- Status
- checked
Supports: the committed Lyapunov certificate re-checks from disk: 8 named obligations discharged in exact rational arithmetic, with the certified decay rate itself pinned at 1/26 by --expect-rate
cargo run --release -q -p axeyum-cas --example sos_certify -- artifacts/sos-certificates/damped-rotation-lyapunov.json --expect-kind lyapunov --expect-id damped-rotation-lyapunov --expect-checks 8 --expect-rate 1/26 Evidence notes
WHY THIS COMMAND CANNOT PASS ON A BROKEN RUN. Two independent pins, both verified 2026-09-01 against the UNCHANGED honest artifact: `--expect-checks 7` exits 1 (`expected 7 obligations, discharged 8`) and `--expect-rate 1/25` exits 1 (`expected the certified decay rate 1/25, got 1/26`). The RATE pin is the stronger of the two and is the reason it is here: it fails on a certificate that still discharges all eight obligations but establishes a WEAKER bound, which is precisely the regression an obligation COUNT cannot see. Nine committed tampered fixtures target this certificate -- lyapunov-inflated-decay, lyapunov-loose-upper, lyapunov-zero-decay, lyapunov-negative-decay, lyapunov-negative-weight, lyapunov-tampered-field, lyapunov-tampered-square, lyapunov-naive-witness-moved, float-coefficient -- and scripts/check-sos-negative-controls.sh asserts each is REJECTED and the honest artifact still ACCEPTED. ON THE DISTINCTION QUESTION: the sandwich constants are separate stored fields (`lower`, `upper`, `decay`), so a weaker certificate is a different FILE rather than the same file read two ways, and the four boundary controls above pin exactly those fields. The one distinction this format cannot carry is STRICT versus NON-STRICT: every obligation is stated non-strictly (a sum-of-squares identity gives `>= 0`, never `> 0`), and where positivity is genuinely needed it is obtained from the separately-recorded constants being positive -- the `sandwich-constants-positive` obligation -- rather than from a strictness flag on an inequality. That is sound for this certificate shape, and it means the format cannot express a strict polynomial inequality at all. A future certificate kind needing one must add a margin field, as the sibling barrier certificate does, not reuse this shape.