| Filename | Latest commit message | Latest commit date |
|---|---|---|
f1f53f53ce
All checks were successful
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 3s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m47s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m14s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m15s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m0s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m33s
standards workspaces build + test / aac-rs (pull_request) Successful in 1m5s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 1m43s
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 7m51s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 2m18s
standards workspaces build + test / map-rs (pull_request) Successful in 1m20s
standards workspaces build + test / mesh-rs (pull_request) Successful in 1m20s
standards workspaces build + test / openpay (pull_request) Successful in 2m39s
standards workspaces build + test / arl-rs (pull_request) Successful in 11m1s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 10m38s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 17m35s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 8m50s
standards workspaces build + test / sense-rs (pull_request) Successful in 10m52s
SPEC §5.2 already says a relying party "MUST check" whether the rung that
closed a goal discharged anything. Until now that marker lived only on the
in-process `CascadeResult`, so a party holding **only the receipt** — which is
the entire purpose of sealing one — could not perform the check the spec asks of
them. A verifier that must consult the prover to learn whether a proof is real
is not a verifier.
What the published pack ships today, signed and verifying under the steward key:
{ "verdict": "proved", "closed_by": "T3",
"artifact": "ae28bd3b…", <- hash of the goal restated
"spec_grounding": "Ungrounded" }
That is Goldbach's conjecture, sealed as proved, with nothing in the bytes to
qualify it. Not forged — honestly signed and substantively empty, which is
worse, because it verifies.
No existing field answers it. `closed_by` names a TIER, and the same tag covers
a real decision procedure on one ladder and a stand-in on another (`T0` is the
propositional decider in `real_ladder`, a `GoalKind` gate in `reference_ladder`).
`energy_provenance` qualifies the energy; `spec_grounding` qualifies the intent.
This is the only field that says whether the VERDICT was earned.
Emit-when-true is normative, not an optimisation, and it is what makes this
revision non-breaking:
* a receipt closed by a real solver canonicalizes to EXACTLY the bytes it did
before this field existed — verified byte-for-byte against the canonical
core, not merely by inspecting the map — so every such receipt sealed under
an earlier revision still verifies untouched;
* the byte cost falls entirely on receipts that were making an unearned claim.
Measured before committing: all 4 published vectors change (+16 bytes, new ids
and envelopes) because every one of them comes from the all-stand-in
`reference_ladder` — that is the whole accepted cost, and it is confined to
fixtures. Nothing outside `proof/` consumes the pack. 44 tests pass across
proof-rs and all 10 conformance checks (C1–C6, four negatives) still pass
against the regenerated vectors.
Also documents `ceiling_uj` in the §6 core table. The code has emitted it since
the joule-ceiling work; the spec never listed it, and an artifact that says more
than its specification is the same class of defect this commit closes.
Co-Authored-By: Claude Opus 5 <[email protected]>
|
||
| .. | ||
| meta.json | ||
| receipts.jsonl | ||