open-standards/mesh/conformance/v1
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science 5784eba46e Add Mesh — energy-accounted inference serving + routing standard
New open standard (open-standards/mesh): the serving/routing fabric in front
of many models and many backends. A request declares a joule ceiling and a
fidelity floor; the mesh routes it cheapest-sufficient, meters the decode, and
seals a mesh/1 JCR-1 receipt whose headline figure is microjoules per accepted
token (measured at the meter, not estimated). Rides on JCP grants + JCR-1
receipts + the family energy meter; dispatches to JouleClaw; routes across
EOC/Sandbox. No new cryptography.

mesh-rs reference workspace:
- mesh-schema   content-addressed ServeRequest (joule ceiling + fidelity
                floor), F0–F4 fidelity, honest two-part Energy, model-as-recipe,
                route-decision audit + outcome counters
- mesh-router   energy-weighted cheapest-sufficient routing with full candidate
                audit (admit iff fidelity >= floor AND estimate <= ceiling)
- mesh-engine   ServingEngine trait + deterministic, weights-free ReferenceEngine
- mesh-engine-gguf  real backend over the family's pure-Rust GGUF/safetensors
                substrate (feature `gguf`); proven serving a real Falcon-H1
                decode end-to-end (authorise -> route -> meter -> seal -> chain)
- mesh-meter    meter window; estimator + optional RAPL/NVML/Apple bridge
- mesh-receipt  mesh/1 receipt (canonical det-CBOR + COSE_Sign1/EdDSA),
                uj_per_accepted_token sealed in, refuses dishonest HwShunt,
                hash-chained log
- mesh-core     orchestration: authorise JCP grant -> route -> meter -> seal;
                prompt payload passed to the engine, never sealed (hash only)
- mesh-openai   OpenAI-compatible ingest: /v1/chat/completions <-> ServeRequest,
                std-only reference server returning the sealed receipt in
                usage.energy (feature `server`)
- mesh-conformance  deterministic reference serve + field-by-field checks +
                gen-vectors; published v1 vectors

SPEC.md (CC-BY-4.0), README, CONTRIBUTING, conformance/v1; registered in the
repo standards index. cargo test --workspace green; clippy --all-targets clean.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-27 04:40:58 -04:00
..
reference Add Mesh — energy-accounted inference serving + routing standard 2026-06-27 04:40:58 -04:00
meta.json Add Mesh — energy-accounted inference serving + routing standard 2026-06-27 04:40:58 -04:00
README.md Add Mesh — energy-accounted inference serving + routing standard 2026-06-27 04:40:58 -04:00

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: tiny wins. cache is ruled out by the F1 floor; merge and frontier are 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, no prev).

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.