| Filename | Latest commit message | Latest commit date |
|---|---|---|
5c0b1110d4
All checks were successful
joule-code conformance gate / Build + round-trip C1-C4 vectors (pull_request) Successful in 1m26s
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (pull_request) Successful in 57s
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 2s
standards workspaces build + test / aac-rs (pull_request) Successful in 2m36s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m46s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 2m47s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m12s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m9s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 2m48s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m0s
standards workspaces build + test / map-rs (pull_request) Successful in 2m0s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m33s
standards workspaces build + test / mesh-rs (pull_request) Successful in 3m21s
standards workspaces build + test / openpay (pull_request) Successful in 3m23s
standards workspaces build + test / arl-rs (pull_request) Successful in 8m26s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 8m18s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 8m40s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 17m26s
standards workspaces build + test / sense-rs (pull_request) Successful in 45m3s
`probe_metal_mpp` calls `jouleclaw_backend_apple::mps_device_name()`, but
`jouleclaw-backend-apple` is declared under
`[target.'cfg(target_os = "macos")'.dependencies]` — so on any other target the
crate is absent and the reference does not resolve:
error[E0433]: cannot find module or crate `jouleclaw_backend_apple`
--> crates/jouleclaw-fabric/src/detect.rs:135
Its two siblings, `probe_amx` and `probe_metal_gpu`, both carry
`#[cfg(target_os = "macos")]`; this one was missed. The *call site* is inside a
macOS-gated block, which is why it looked fine — but the *definition* is still
compiled on every target, and its body names a crate that isn't there.
This is why `joule-code conformance gate` has failed all 11 runs since it was
added on 2026-07-23 and has never once passed: it is `runs-on: linux`, and its
third step builds `joule-code/examples/l3-jouleclaw`, which pulls
jouleclaw-fabric in via `jouleclaw-loader-gguf`'s `fabric` feature. The failure
had nothing to do with the commits that triggered it.
It survived because nothing else compiles this crate for Linux: `jouleclaw-rs`
is not in the standards-build matrix, so its only non-macOS build in CI is this
one transitive path through an example in another standard's workflow.
Verified `cargo check --target x86_64-unknown-linux-gnu --all-targets` on
l3-jouleclaw — clean, where it previously failed on this error — and macOS is
unaffected (jouleclaw-fabric 13 tests, l3-jouleclaw green).
Co-Authored-By: Claude Opus 5 <[email protected]>
|
||
| .. | ||
| conformance/v1 | ||
| jouleclaw-rs | ||
| vocab | ||
| LICENSE | ||
| README.md | ||
| ROADMAP.md | ||
| SPEC.md | ||
JouleClaw — Energy-Optimized AI Runtime
The substrate for AI that costs Joules, not tokens.
Capability per Joule, not capability per parameter.
What JouleClaw is
JouleClaw is a pure-Rust, omni-modal AI runtime + harness + agentic layer governed by Transaction Science as an open standard (5th in the open-standards quartet, alongside OpenPay, Smart Byte, EOC, and WAI).
Every operation JouleClaw performs walks an explicit energy-tiered cascade, top to bottom, stopping at the first stage that closes the query:
| Tier | Name | Cost class | What runs here |
|---|---|---|---|
| L0 | Cache | picojoules | Content-addressed cache hits |
| L1 | Lawful | nanojoules | Deterministic, pre-compiled primitive (text/code only) |
| L2 | Embed | sub-millijoules | Matryoshka embeddings + nearest-neighbor + hybrid search |
| L3 | Model | joules | Local SSM / ternary / multimodal / diffusion / etc. |
| L4 | Wire | tens of joules | Remote frontier RPC (escape hatch only) |
L1 (Lawful) is only meaningful for text and code modalities. For image, audio, video and 3D generation, the cascade collapses to L0 / L2 / L3 / L4 — the energy savings come from caching plus dispatch to the cheapest model that meets the quality bar.
Why JouleClaw exists
The mainstream "agentic AI" ecosystem treats inference as the entry point. Every state shift, every tool call, every routing decision runs through a 70-billion-parameter stochastic engine, burning kilojoules to do work that deterministic compute or a hot cache could resolve for microjoules.
JouleClaw inverts the default. Inference is the last resort, not the first. Frozen model weights are less trustworthy than current world state; fresh, provenance-stamped retrieval beats synthesis from training cuts. Every operation is metered in microjoules where the hardware permits it, and in millijoules where it doesn't — the spec is honest about the floor on every platform.
The thermodynamic circuit breaker is the safety mechanism. Set an energy budget; when measured consumption exceeds the budget, the breaker trips and the operation halts. Hallucination loops cannot survive an honest joule ledger.
What's here
| Path | Contents |
|---|---|
SPEC.md |
JouleClaw v1 spec — cascade tiers, energy contract, receipt |
CHARTER.md |
Stewardship pattern (shared across open-standards) |
jouleclaw-rs/ |
Apache-2.0 Rust reference implementation |
spec/ |
Tier specifications, energy provenance, receipt format |
conformance/v1/ |
Signed wire vectors for cross-implementation verification |
Reference implementation
jouleclaw-rs/ is the Apache-2.0 reference implementation in Rust. It
runs on Apple Silicon (M3/M4/M5 with UMA + Metal 4 Tensor APIs), AMD Strix
Halo / Ryzen AI Max, Intel Lunar Lake, NVIDIA Jetson, and discrete
NVIDIA / AMD GPUs.
It is omni-modal: text, code, vision, audio, video, image diffusion, 3D Gaussian splatting, and cross-modal fusion all dispatch through the same energy-tiered cascade.
The MCP tool surface is a JCP consumer: jouleclaw-jcp wraps any
jouleclaw-mcp metered tool so every dispatch is decided by the JCP runtime
against a signed, metered Grant before a byte reaches the tool — the tool's
identity is the content-addressed resource, the call's energy estimate is
debited from the grant's joule budget, and every decision (allow and deny
alike) seals as a JCR-1 receipt. An injected instruction can name an ungranted
tool; it cannot make the gate dispatch it.
Status
v0.1.0 reference implementation in active development. The spec is draft status. Cross-implementation conformance vectors will land with v1.0.0.
License
- Code: Apache-2.0 (see
LICENSE) - Spec text: CC-BY-4.0 (see
spec/LICENSE)