open-standards/mesh/conformance/v1/README.md
Transaction Science a24982ce5a wai.generate.spectral: extend the lexicon to 370 words (data-only, pin unchanged)
Adds ~110 more words across new domains: creatures (tiger→warm horizontal stripes,
zebra→vertical, peacock/jellyfish→radial, dragon/phoenix, swan/raven/wolf/whale…),
food & drink (wine/honey/coffee/cherry/mango/saffron/matcha/blueberry…), gems
(opal/pearl/onyx/quartz/topaz/garnet/obsidian/moonstone…), architecture
(city/cathedral/temple/tower/dome/labyrinth/maze/spire…), abstract concepts
(love/passion/harmony/energy/freedom/infinity/eternity/zen/echo…), cosmic/sci-fi
(plasma/quasar/pulsar/supernova/blackhole/matrix/circuit/hologram/wormhole…),
botanical (lotus/orchid/daisy/sunflower/poppy/tulip/lily…), seasons
(autumn/spring/summer/winter/harvest/solstice…) and synesthetic music
(rhythm/melody/pulse/bass/jazz/blues/resonance…). Shape-bearing words carry the
right primitive — supernova/pulsar/lotus→radial, cathedral/maze/matrix→mirror,
blackhole/blues→gradient.

Data-only: generate.rs + architecture unchanged (wasm unchanged), and the
conformance prompt still matches only calm+horizon, so the pin is UNCHANGED
(4bd80c0ef51bb843) — no test churn. Verified: tiger→horizontal stripes,
supernova→radial rings, cathedral→symmetry, all byte-exact.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-27 05:33:47 -04:00

42 lines
1.8 KiB
Markdown

# 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.
```text
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.