open-standards/mesh/mesh-rs
Repository files (latest commit first)
Filename Latest commit message Latest commit date
David Charlot ab5f508023
All checks were successful
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 2m34s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 1m21s
standards workspaces build + test / aac-rs (pull_request) Successful in 2m37s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 55s
standards workspaces build + test / map-rs (pull_request) Successful in 56s
standards workspaces build + test / mesh-rs (pull_request) Successful in 54s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 47s
standards workspaces build + test / openpay (pull_request) Successful in 3m8s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 4m43s
lockfiles / every Cargo.lock is current (pull_request) Successful in 34s
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 5s
no-vanity-metrics / WAI public text names no comparison (pull_request) Successful in 4s
no-vanity-metrics / WAI public text names no company or product (pull_request) Successful in 3s
no-vanity-metrics / No new orphan source files (pull_request) Successful in 7s
spec citations resolve / Code cites no section its SPEC lacks (pull_request) Successful in 7s
standards workspaces build + test / arl-rs (pull_request) Successful in 1m15s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m58s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m34s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 1m11s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 1m12s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m26s
standards workspaces build + test / sense-rs (pull_request) Successful in 1m14s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m24s
tests in CI / every test file is run by a job or listed with its reason (pull_request) Successful in 3s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 3m56s
mesh: the identity rides the whole path, and the keys it adds are exactly two
The receipt-level test pins that the identity changes the sealed bytes. This
one pins the path: two meshes differing only in whether the engine reports
what ran, same recipe name on both, and the envelopes must differ. If the
identity were carried but not sealed they would match, and a verifier
comparing signatures could not tell a receipt bound to these weights from one
bound to any others.

It also asserts the added keys are *exactly* `precision` and `weights_digest`,
which catches an extra key as well as a missing one — the same assertion shape
the delivered-fidelity test uses, and the reason that test is worth copying.

Falsified three ways, each caught at a different assertion:
  - projection removed      → the wire assertion fires
  - digest projected as a constant → the hex assertion fires
  - wire keeps it, `signed_core_bytes` drops it → the signed-core assertion
    fires, which is the "carried but not sealed" case the test is named for
and the third is the one a weaker test would have missed.

No conformance vector is added, deliberately: #183 took the same decision for
`delivered_fidelity`. The published pack's value is that its bytes do not
move, and `reporting_model_identity` exists so the fields are exercisable
without touching it.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-10-14 01:33:23 -04:00
..
crates mesh: the identity rides the whole path, and the keys it adds are exactly two 2026-10-14 01:33:23 -04:00
Cargo.lock mesh-openai: the serve example seals what its meter read, not a fixture 2026-10-10 17:47:11 -04:00
Cargo.toml mesh: an in-process engine is metered by this process's own CPU and GPU energy 2026-10-08 20:21:15 -04:00