Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions
open-standards/mesh/CONTRIBUTING.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

1.6 KiB
Raw Permalink Blame History

Contributing to Mesh

Mesh is one of the Transaction Science open standards. The wire format and the right to fork are public; Transaction Science is the steward, not the proprietor.

Ground rules

  • Reference code (mesh-rs/) is Apache-2.0. Specification text (SPEC.md) is CC-BY-4.0.
  • The Rust toolchain is pinned by the repo rust-toolchain.toml. cargo test --workspace MUST pass and cargo clippy --workspace --all-targets MUST be warning-free.
  • Any change to a wire structure (the ServeRequest id, the mesh/1 receipt core, the canonical encoding) requires regenerating and committing conformance/v1/: 
    cargo run -p mesh-conformance --bin gen-vectors -- ../conformance/v1

Two invariants are correctness, not style

A PR that weakens either will be declined:

  1. Authorisation happens outside the model. The JCP grant check runs in the steward, before any inference. A prompt can never grant itself budget or capability.
  2. Honesty is enforced at seal time. A receipt may not claim a measurement it does not have: HwShunt requires a measured figure, Estimator forbids one. A deployment without a hardware meter produces honest Estimator receipts.

Scope

Mesh is the serving + routing fabric. It rides on JCP for authorisation and JCR-1 for receipts, dispatches to runtimes such as JouleClaw, and routes across compute described by EOC. Proposals that re-implement a grant model, a receipt envelope, or an energy meter that the family already publishes will be redirected to compose the existing primitive instead.