| Filename | Latest commit message | Latest commit date |
|---|---|---|
e5a1b96e7a
Some checks failed
standards workspaces build + test / aac-rs (push) Successful in 1m47s
standards workspaces build + test / eoc-rs (push) Successful in 2m0s
standards workspaces build + test / jcp-rs (push) Successful in 1m25s
standards workspaces build + test / joule-code-rs (push) Successful in 2m11s
standards workspaces build + test / proof-rs (push) Successful in 1m13s
standards workspaces build + test / sandbox-rs (push) Successful in 2m21s
standards workspaces build + test / smart-byte-rs (push) Successful in 2m32s
standards workspaces build + test / jouleclaw-rs (push) Failing after 8m2s
standards workspaces build + test / joulecontract-rs (push) Successful in 1m14s
standards workspaces build + test / map-rs (push) Successful in 1m4s
standards workspaces build + test / mesh-rs (push) Successful in 45s
standards workspaces build + test / openpay (push) Successful in 3m45s
standards workspaces build + test / arl-rs (push) Successful in 2m29s
standards workspaces build + test / joule-ui-rs (push) Successful in 2m27s
standards workspaces build + test / jouledesk-rs (push) Successful in 2m23s
standards workspaces build + test / joulehook-rs (push) Successful in 2m7s
standards workspaces build + test / sense-rs (push) Successful in 2m3s
conformance/v1 says a conforming implementation "MUST reproduce" its bytes, and
gen_vectors writes it, but nothing read it back. The existing tests re-run
reference_scenario() and compare it against the crate's own constants, so they
check the implementation against itself.
That gap is measured, not assumed. Changing the reference serve (SPAN_UJ
3_200_000 -> 3_200_001) leaves all four existing end_to_end tests green: both
sides of every comparison move together. A receipt-shape change would have
left this pack silently stale -- which is what happened to joulehook's.
tests/pack.rs answers two separate questions:
- Drift: the reference implementation still emits exactly the published
envelope.hex, signed_core.hex, receipt.json and meta.json, compared in the
form gen_vectors writes them. Under the change above, this and the
pinned-outcome test go red.
- The README's cross-language check, done the way a third party would: from the
pack files and RFC 9052 alone, with a hand-built CBOR encoder and no mesh COSE
code, build Sig_structure ["Signature1", {1:-8, 4:steward}, h'', signed_core],
verify the published signature under meta.json's key, and re-sign with the
documented seed to rebuild the 663-byte envelope byte for byte. It does. So
the claim holds from the RFC, not merely from the implementation agreeing
with itself. These pack-only tests correctly stay green under the change
above, since the pack remains self-consistent.
Plus negatives -- a single flipped payload byte and a stranger's key must both
fail verification -- and the pinned outcome read from the published receipt,
with the wedge metric recomputed from measured_uj / tokens_accepted rather than
trusted as a number.
The pack is current: a fresh regeneration into a scratch directory matched all
four files byte for byte, so nothing needed refreshing.
Co-Authored-By: Claude Opus 5 <[email protected]>
|
||
| .. | ||
| mesh-conformance | ||
| mesh-core | ||
| mesh-engine | ||
| mesh-engine-gguf | ||
| mesh-meter | ||
| mesh-openai | ||
| mesh-receipt | ||
| mesh-router | ||
| mesh-schema | ||