| Filename | Latest commit message | Latest commit date |
|---|---|---|
62a81b3472
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 6s
repository checks / lockfiles, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 44s
standards workspaces build + test / joule-ui-rs (joule-ui/joule-ui-rs, joule-ui-rs, linux) (pull_request) Successful in 1m22s
standards workspaces build + test / jcp-rs (jcp-conformance, jcp/jcp-rs, -p jcp-energy --features nvml, jcp-rs, linux) (pull_request) Successful in 1m41s
standards workspaces build + test / mesh-rs (mesh/mesh-rs, -p mesh-engine-gguf -p mesh-openai --features mesh-engine-gguf/gguf,mesh-openai/server, mesh-rs, linux-arm64) (pull_request) Successful in 1m23s
standards workspaces build + test / joulehook-rs (joulehook/joulehook-rs, joulehook-rs, linux) (pull_request) Successful in 1m11s
standards workspaces build + test / jouleclaw-rs (-nodebug, jouleclaw/jouleclaw-rs, -p jouleclaw-energy --features rapl,nvml, jouleclaw-rs, linux-arm64, -C target-feature=+fp16) (pull_request) Successful in 3m7s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 3m54s
standards workspaces build + test / sandbox-rs (sandbox-conformance, sandbox/sandbox-rs, sandbox-rs, linux) (pull_request) Successful in 2m16s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 7m37s
standards workspaces build + test / jouledesk-rs (jouledesk/jouledesk-rs, jouledesk-rs, macos) (pull_request) Successful in 2m42s
A mesh receipt bound what was asked (request_id) and what it cost, and
nothing about what came back, so no one could later show which answer a
receipt was for. AR-1 had the same gap beside input_hash.
mesh/1 (SPEC §6.4):
- output_commitment: a salted BLAKE3 commitment over the request id, the
digest of the prompt payload the engine was handed, and the output tokens.
It is a commitment, not a hash, because a short output is reversible from
its hash. The opening is derived per request from a key drawn from the
steward's signing key, so a restarted steward can still disclose it.
The field is absent for a typed decision, whose answer the engine
interface does not carry, and omitted when absent, so older receipts keep
their bytes.
- The payload is bound because prompt_hash addresses the prompt's bytes
while an engine is handed token ids, so request_id alone cannot confirm
what a replay runs on.
- ServingEngine::deterministic (default false; the reference engine true).
- mesh_core::replay re-executes a sealed serve. Its verdicts:
- Verified: the re-run opens the commitment.
- Diverged { first_difference }: only when a disclosed output opens the
commitment on the same payload and opening, so the mismatch is the
serve's and not the replayer's input.
- NotReplayable(why): the engine samples; another backend, recipe or
weights; another request; no commitment; or a mismatch nothing
attributes.
- The conformance pack is regenerated (the reference receipt gains the
field; the envelope grows from 663 to 747 bytes).
AR-1: output_hash, an optional field after input_hash, sealed only when
bound (§2.3). It recommends a commitment over a plain hash and names
mesh's output_commitment as one. The published AR-1 vectors regenerate
byte-identical.
Also: ar-verify's `len() % 2 == 0` becomes `is_multiple_of(2)`, a clippy
error that predates this change, so the crate is clippy-clean.
Tests:
- mesh: the commitment binds request, opening, payload and tokens; a
generation commits and a decision does not; deterministic replay
verifies and locates a drift; replay refuses what it cannot settle,
including a wrong payload with the honest output disclosed; a restarted
steward reopens.
- AR-1: output_hash sealed when bound and absent otherwise.
- Mutation testing: 20 mutants, all killed (13, then 7 more after
binding the payload; one of the 13 targets code since replaced).
Verified on the build host:
- mesh-rs: 94 tests plus 19 behind features; clippy and rustdoc clean.
- jcp-rs: 565 tests and the conformance binary; jcp-action-receipt
clippy-clean.
- Repo checks pass.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
||
| .. | ||
| reference | ||
| meta.json | ||
| README.md | ||
Mesh conformance vectors — v1
The mesh/1 receipt profile, pinned to a deterministic reference serve. These
vectors are generated by the reference implementation and are byte-stable; a
conforming implementation (in any language) MUST reproduce them.
cargo run -p mesh-conformance --bin gen-vectors -- ../conformance/v1
Files
| File | What it pins |
|---|---|
meta.json |
profile (mesh.receipt/1), algorithm (EdDSA, COSE -8), steward did:key, steward public key, and the wedge metric name |
reference/receipt.json |
the mesh/1 wire projection of the reference receipt |
reference/signed_core.hex |
the canonical det-CBOR signed core (what the envelope signs over) |
reference/envelope.hex |
the sealed COSE_Sign1 envelope |
The reference serve
A steward (seed [7;32]) registers a four-tier fidelity cascade — cache (F0),
tiny (F1), merge (F2), frontier (F4) — and serves a 64-token request with a
floor of F1 and a ceiling of 8 J, metered by a HwShunt source reporting
a fixed 3,200,000 µJ span.
The pinned outcome:
- Route:
tinywins.cacheis ruled out by the F1 floor;mergeandfrontierare ruled out by the 8 J ceiling. Every candidate and its reason is recorded. - Energy:
HwShunt,measured_uj = 3_200_000. - Wedge metric:
uj_per_accepted_token = 3_200_000 / 64 = 50_000. - Chain: genesis receipt (
sequence = 0, noprev).
Cross-language check
Take reference/signed_core.hex, wrap it as a COSE_Sign1 Signature1 structure
per RFC 9052 (protected header {1: -8, 4: <steward bytes>}, empty external AAD),
sign with the steward key — and you MUST reproduce reference/envelope.hex byte
for byte. The signed core is canonical det-CBOR (RFC 8949 §4.2.1): length-first
key order, shortest integer form, no floats/booleans/nulls.