Some checks failed
joule-moq-remote host agent / joule-moq-remote · does this change touch it (push) Successful in 23s
joule-moq-room room service / joule-moq-room · does this change touch it (push) Successful in 28s
joule-moq-web browser client / joule-moq-web · does this change touch it (push) Successful in 28s
wai-app and Create / wai-app · does this change touch it (push) Successful in 28s
wai-fleet service / does this change touch it (push) Successful in 28s
joule-code conformance gate / joule-moq-relay, its own energy on a counter (macos) (push) Successful in 40s
joule-moq-remote host agent / joule-moq-remote, every target (macos) (push) Successful in 48s
wai-fleet service / service · macos (push) Successful in 38s
wai-app and Create / wai-app · Create, browser end-to-end (macos) (push) Successful in 5m2s
wai-app and Create / wai-app · tests, clippy, the line language's verifier (linux) (push) Successful in 38s
joule-code conformance gate / Build + round-trip C1-C4 vectors (push) Successful in 2m55s
joule-moq-web browser client / joule-moq-web · browser end-to-end (macos) (push) Successful in 17m6s
wai-fleet service / service · linux (push) Successful in 3m32s
joule-moq-remote host agent / joule-moq-remote, every target (linux-arm64) (push) Has been cancelled
joule-moq-room room service / joule-moq-room, every target (push) Has been cancelled
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Has been cancelled
joule-code conformance gate / joule-moq-relay, every target (push) Has been cancelled
joule-code conformance gate / joule-moq-ingest, every target (push) Has been cancelled
communicationOS consolidated into WAI, and its site is retired. Where these texts meant the transport they now say WAI or MoQT, and joule-moq's description, the Joule Code docs and the Three Faces tables follow. The transport example names joule-moq, which it uses, and its test drops the old name. Changelog: none Co-Authored-By: Claude Opus 5.5 <[email protected]>
3.2 KiB
3.2 KiB
Joule Code — Lexicon
The controlled vocabulary for the Joule Code standard. Terms are normative where ../SPEC.md uses them; this lexicon fixes their meaning so the spec, the reference library, and the conformance vectors agree. CC-BY-4.0.
Core
- Coding operation (
CodingOp) — the unit of cargo: a signed transition moving a source tree from a prior state to a successor state via an ordered edit set. Defined by base + edits, not by a restated result. - Operation id (
op_id) — the content address (BLAKE3-256 over deterministic CBOR) of aCodingOpexcluding its signature. - Tree state / tree id — a content-addressed snapshot of the relevant source;
tree_idis BLAKE3-256 over{ path: blob_id }. - Signed operation (
SignedOp) — aCodingOpplus an Ed25519 signature overop_id ‖ prior, scoping authorization to one base. - Anchor — where an edit applies: a byte range against the prior blob, or a content-addressed hunk (rename-stable).
Cascade
- Cascade — the ordered tier list a request resolves through; resolution stops at the first tier that closes the request.
- Tier —
L0 Cache(picojoules) ·L1 Lawful(nanojoules) ·L2 Embed(sub-millijoules) ·L3 Model(joules) ·L4 Wire(tens of joules). Inherited from JouleClaw. - Stage — the implementation of one tier; exposes
try_resolve(req) -> Option<Resolution>. - Close — a stage closing a request: returning
Some(Resolution). The closing tier is recorded in the receipt. - Wire / L4 / frontier agent — a remote coding agent (Claude Code, Gemini, Codex, ...) reached over ACP, with its credential held by the vendor's own client. The escape hatch, not the entry point.
Receipt and energy
- Receipt — the signed, two-part energy record carried in a JWP frame accounting for one operation.
- Energy —
{ measured_uj?, estimated_uj, provenance }, all integer microjoules. - Provenance — the honesty tag on an energy reading:
HwShunt(hardware-measured; requiresmeasured_uj),ModelBased(calibrated model),Estimator(coarse constant). - JWP — Joule Wire Protocol: the energy-aware framing that carries the receipt; cumulative energy is a first-class, signable frame field.
- Joules per accepted change — the standard's unit of merit; the substrate's falsifiable cost basis.
Doctrine
- Capability per joule — the doctrine: minimize energy per accepted change, not parameters per model.
- No capture — no protocol token; core operation never requires a single steward's servers; frontier credentials never enter the protocol.
- Ownerless — identity lives in content addressing and conformance vectors, not a brand; the spec and reference code are permissively licensed; anyone may fork.
- The offer — the commercial layer (managed nodes, drivers, certification) that a steward operates around the substrate, never inside it.
Collaboration (Research)
- Cluster — a known, signed-membership set of collaborators replicating operations by lockstep BFT.
- Federated collaboration — ownerless multi-endpoint editing: coding operations as Smart Byte envelopes, transported over WAI, shared via RemoteOS. Interface-level in v0.1.