qf-nia-univariate-unsat-is-certified-1
- Kind
- unsat-certificate
- Status
- checked
Supports: One named refutation reaches `outcome=verified` end-to-end. Anchored on the row rather than on a test-count line: `test result: ok` is true of a suite that produced no certificate at all, and this pattern is false unless a certificate was produced AND re-derived.
out=$(cargo test -q -p axeyum-solver --features full --test certified_implies_revalidatable -- --nocapture 2>&1) && test "$(printf "%s\n" "$out" | grep -Ec 'nia_non_square_discriminant .*kind=unsat-int-univariate-poly .*certified=1 outcome=verified')" -ge 1 Evidence notes
Anchored on `certified=1 outcome=verified` in one row of `certified_implies_revalidatable`, which re-validates against a FRESH PARSE of the SMT-LIB text rather than the producing run's arena. That distinction is the whole point of the anchor: checking against the producer's own arena passes for any certificate, including one that merely copies the producer's conclusions. `UnsatQuantInstanceSet` shipped `certified=1` over a FAILED re-check on 2026-08-17 because its TermIds meant nothing in a second arena, and this suite exists because of it.