Verification envelope
When a closed-form solver produces a value, the result can carry a structured
proof-of-correctness block — the computed value re-checked against an
independent re-evaluation of its own cited closed form, through the gate's
real re-evaluator (verifyNumericClaim + FORMULA_REGEX).
It appears on the compute result as verificationDetail:
{
"computed": 1000000000.0000001,
"reference": 1000000000.0000001,
"source": "ω_r = 1/√(LC), Q = ω₀L/R",
"method": "closed-form-reeval",
"deviation_pct": 0,
"within_tolerance": true,
"tolerance_pct": 0.1
}
What it is — and isn't
- The reference is an independent re-evaluation of the solver's own cited
closed form (a different code path —
new Function("Math", …)gated by a strict regex — than the solver's hand-written arithmetic). A divergence is a real transcription / drift / refactor signal. method: "closed-form-reeval"is the honest label: this is not an external experimental or NIST ground-truth measurement.sourcecites the equation.- Optional + never fabricated. When the solver supplies no re-evaluatable reference (generic / pattern-matched results), the block is omitted entirely.
It powers the three-state verdict
The compute result's verification verdict is verified | unverifiable | disputed:
- corroborating re-eval (within tolerance) →
verified - out-of-tolerance independent re-eval →
disputed(an independent recompute disagreed — the long-reserved state, now live) - no finite value / no reference →
unverifiable
Verify it yourself
KEY=$(curl -s https://zeqstate.com/api/demo-key | jq -r .key)
curl -s -X POST https://zeqstate.com/api/zeq/compute \
-H "authorization: Bearer $KEY" -H 'content-type: application/json' \
-d '{"domain":"Quantum Resonance","inputs":{"L":1e-6,"C":1e-12,"R":50}}' | jq .verificationDetail
# → a true deviation_pct + within_tolerance; a generic domain omits the block.
Source: shared/api-core/src/lib/verificationEnvelope.ts,
lib/zeqSolvers.ts (referenceExpr), lib/zeqWizard.ts.