b838b86a8b
Joule Code is the coding cargo class of the substrate: a coding operation — an edit, refactor, or generated function — is a content-addressed, signed transition over a source tree, resolved through the energy-tiered cascade (L0 Cache → L1 Lawful → L2 Embed → L3 Model → L4 Wire, stop-at-first-close) with a signed JWP receipt (measured + estimated µJ, honest Provenance) per operation. The agent schema is JouleClaw; L4 frontier agents are reached over ACP with the credential held by the vendor's own client — no protocol token, no required contact with any single company. Stands up the standard to the family schema: - README, SPEC.md (RFC-2119 normative), dual licence (Apache-2.0 code / CC-BY-4.0 spec), ROADMAP, CONTRIBUTING, CHANGELOG. - spec/: cargo (the coding-operation type), cascade (the tier binding), receipt (the JWP energy record), collab (federated, interface-level/Research). - vocab/LEXICON.md. - conformance/v1/: C1 content-addressing, C2 signing, C3 receipt, C4 cascade vectors + VERSIONS + regeneration; real Ed25519 RFC-8032 KATs, derived fields regenerated against the reference library. - joule-code-rs/: lean reference library (schema, cargo, receipt, cascade, conformance). cargo test --workspace passes; the conformance harness runs 11 pass / 0 fail / 7 skip (derived fields pending regeneration). Single-endpoint operation is the v0.1 surface; federated collaboration is specified at interface level and classified Research. Registers the standard in the family README. Co-Authored-By: Claude Opus 4.8 <[email protected]>
27 lines
2 KiB
Markdown
27 lines
2 KiB
Markdown
# Joule Code roadmap
|
||
|
||
Where the standard goes after v0.1.0. The reference library in [`joule-code-rs/`](joule-code-rs/) is a multi-crate Rust workspace; the flagship consumer is the agent-zed editor.
|
||
|
||
## v0.1.0 (current)
|
||
|
||
- Coding-operation cargo, content addressing, deterministic CBOR, signing (§2–§4).
|
||
- The receipt: `estimated` energy with `Estimator` provenance, JWP-signed (§6).
|
||
- The cascade interface and the conformance suite C1–C4 (§5, §8).
|
||
- Single-endpoint operation only; collaboration is interface-level (Research).
|
||
|
||
## Near-term (v0.2)
|
||
|
||
- **Measured energy.** Bind the receipt's `measured_uj` / `HwShunt` path to real hardware interfaces (RAPL on Linux, SMC/IOReport on Apple Silicon) via JouleClaw's energy + calibration crates. Promote §6 measured path from Engineering toward Solid where the platform delivers it.
|
||
- **Cascade lower tiers.** Land real L0 (content-addressed op cache) and L2 (embedding + hybrid retrieval) stages so frontier calls (L4) are genuinely the last resort, not the first.
|
||
- **Per-task routing.** Choose the closing tier and the L4 leg per request from intent + budget, recorded in the receipt.
|
||
|
||
## Mid-term
|
||
|
||
- **Federated collaboration (Research → Engineering).** Promote [`spec/collab.md`](spec/collab.md) from interface-level to a conformance-bearing binding: coding operations as Smart Byte envelopes, lockstep replication, CommunicationOS transport for session and presence, RemoteOS for shared sessions. Add a `conformance/v1/lockstep_vectors.json`-style pack when the binding stabilizes.
|
||
- **Post-quantum signatures.** Exercise the one-byte algorithm identifier (§2) with a PQ successor alongside Ed25519.
|
||
|
||
## Non-goals
|
||
|
||
- A protocol-level token. There will not be one.
|
||
- Reimplementing vendor agent authentication. Frontier agents (L4) are reached through the vendor's own logged-in client; the credential never enters the protocol.
|
||
- Reimplementing codecs, editors, or model runtimes. Joule Code composes existing standards (JouleClaw, Smart Byte, EOC, CommunicationOS, RemoteOS); it does not absorb them.
|