wai: energy reports, labelled JWP leaves and what signatures cover #133

Merged

dcharlot merged 6 commits from wai/land-14-energy-reporting into main 2026-10-01 14:54:28 -04:00

Conversation 0 Commits 6 Files changed 71 +16050 -592

2026-10-01

Transaction Science

Merge main into wai/land-14-energy-reporting ...

Main now carries links 12 and 13. This merge makes main the base of the
pull request, so its diff is this link's own change.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2934038be9

• View at this point in history

2026-10-01 14:53:28 -04:00

Transaction Science

Merge main into wai/land-14-energy-reporting ...

joule-code/CHANGELOG.md: main's entry (a vendor counter is a hardware
reading only while it is demonstrably live) and this link's joule-moq 0.2.0
entry both land under the unreleased section, main's first. The joule-code
workspace builds with --locked and the joule-moq tests pass on the merge.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

93d5ce5845

• View at this point in history

2026-10-01 09:54:06 -04:00

Transaction Science

wai: state what CI builds, the meters' new feature, and the /verify change ...

The v0.4.0 energy-report entry said the conformance build builds the
reference meters on every platform. It builds two of them, wai_meter and
wai_world_meter. wai-energy-receipts.yml builds those two, wai_video_meter
and wai_quantum_meter on linux, linux-arm64 and macos. No workflow builds
wai_prov, which needs codecs. The entry now says so, and the conformance
workflow's comment no longer names a Windows leg its matrix does not have.

The entry now records two compatibility changes. Every reference meter bin
requires receipt_claims, and Cargo skips a bin whose required features are
off without an error. POST /verify in wai-quantum-serve renders an unmetered
receipt's joules_micro as null and adds a metered member, so the crate moves
to 0.4.0 and the Wire paragraph names the change.

jwp-receipts §2.4.9 rule 2 reads "A point that is present MUST NOT be
empty", in the form of the other rules. quantum-sim names the meter's other
unmetered paths: a rail that is not live in both brackets (energy-measurement
§3.1), and a §4 ratio or §2.3 uncertainty that cannot support a figure.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

bc0dffa965

• View at this point in history

2026-10-01 09:05:14 -04:00

Transaction Science

Merge wai/land-13-parameter-set-identity into wai/land-14-energy-reporting ...

Brings link 13's review fixes and the link 12 commits it had merged: the
strict gate reads only dispatchable capabilities, a pinned ONNX model
that keeps tensors in another file is refused with set_incomplete,
sha256.json sidecar writes are serialized, and the public text the
review found stale or overstated is corrected. The merge needed no
conflict resolution. On the merged tree the registry exports are up to
date, and the conformance workflow's library, integer-kernel, carriage
and C ABI envelope steps and the neural gates workflow's three steps
passed locally.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

17cca049df

• View at this point in history

2026-10-01 09:01:31 -04:00

Transaction Science

wai: name jwp-conformance in the decoded-output sidecar exclusions ...

every_decoded_output_states_a_sha256 enumerates every wai/*-conformance
directory and requires a sha256.json sidecar or a named exclusion. The
new JWP corpus holds delivery receipts, receipt content with no decoded
output, so it is excluded for the reason the claim and OER corpora are.
Without this, the fast-kernel steps of wai-conformance.yml fail on the
assembled tree.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2904219c9c

• View at this point in history

2026-10-01 06:48:31 -04:00

Transaction Science

wai: energy reports, labelled JWP leaves and what signatures cover ...

Two claim classes report on one energy figure without changing the
receipt that seals it. `measurement` carries a bracket's values as
integers with each bracket's liveness facts, the build and the power
reader, and is accepted only against the receipt that carries its
figure. `operating-point` records the requested, committed and
delivered operating points and a prediction. The ratio, verdict and
residual are derived by every reader, never stated.

energy-measurement §6.2 gives the figure and the least declaration a
report's integers support as exact integer formulas; wai-rs
`energy_report` implements them with no floating-point arithmetic.
§3.1 defines a live power reader: a rail must advance in two
consecutive intervals, in at least five and in at least four of every
five, over at least 300 ms. A frozen or held rail is refused rather than
sealed under a hardware class. An unmetered `0` is never a figure of
zero joules.

A JWP object's figure, class and origin are bound into its Merkle leaf
(`\x02`), and a labelled group payload signs the total's class, its
coverage and the parent link. An object must sit at the position its
inclusion proof walks, and group signatures follow the strict Ed25519
rule claims use. `jwp_delivery` and `energy_figure` implement this in
wai-rs; joule-moq 0.2.0 builds and verifies both labelled forms.

New corpus `jwp-conformance/` with `jwp_verify.py`, more claim vectors
with the earlier ones pinned, and a CI job that runs claim_verify.py,
differential.py and jwp_verify.py. Legacy receipts keep their bytes.
External JWP implementations must adopt the `\x02` leaf and the
labelled group payload before verifying objects or groups that use
them.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

cc371d815a

• View at this point in history

2026-10-01 06:37:25 -04:00