| Filename | Latest commit message | Latest commit date |
|---|---|---|
1352aeea07
All checks were successful
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 1m39s
standards workspaces build + test / aac-rs (pull_request) Successful in 35s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 35s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 32s
standards workspaces build + test / map-rs (pull_request) Successful in 29s
standards workspaces build + test / mesh-rs (pull_request) Successful in 25s
standards workspaces build + test / openpay (pull_request) Successful in 1m23s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m50s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m18s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m15s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m8s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m33s
standards workspaces build + test / arl-rs (pull_request) Successful in 2m19s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 2m49s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 2m51s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 2m48s
standards workspaces build + test / sense-rs (pull_request) Successful in 2m50s
standards workspaces build + test / macOS energy backend (jcp-energy) (pull_request) Successful in 2m49s
A trace `Span` carried a micro-joule figure and nothing about where it came from. A provider's own figure, a tool step's duration estimate, a zero for an observation, and a delta a live counter read all looked the same, so nothing reading a trace could tell a measurement from an estimate. Every other eoc surface that reports energy says which it is (`JouleCost`, eoc-eval's `joule_source`); an agent trace did not. `Span` gains `joule_source: JouleSource`, eoc-core's tag, under eoc-core's rule: `Measured` only for what a live counter read over the step — both reads succeeded and the counter advanced — and `Estimated` for anything else. - The field is additive on the wire. It is `#[serde(default)]`, as eoc-eval's report field is: a trace written before it reads back with every span `Estimated`, since nothing in it says it was measured. Nothing in the monorepo outside eoc-agent uses eoc-agent, so no struct literal of `Span` breaks. - `Span::new` is `Estimated` (0 µJ that no counter read). `with_joule_cost` attaches a figure and its tag together, and `joule_cost()` reads them back. `with_microjoules` attaches a bare figure, which is an estimate: it no longer leaves an earlier `Measured` tag on a figure the counter did not read. - `AgentLoop::measured_with` and `measured_tool` return a `JouleCost` instead of a bare `u64`. The figure is unchanged — the reading, or the estimate when larger, or the estimate alone — and it is `Measured` exactly when it is the reading: a reading smaller than the estimate is not what is charged, so the estimate charged in its place is `Estimated`. `measured` still returns the bare figure, as on main. Both changed functions are new on this branch. - Model steps: `charge_llm_step` tags the provider's own figure `Estimated`; `LlmProvider`'s contract calls it an estimate and no counter here read it. This covers every loop's model steps (ReAct, CodeAct, Reflexion, ToT, LATS). - Tool steps: ReAct and CodeAct put `measured_tool`'s tag on the act span, and Plan-and-Execute on its plan and execute spans. - Other steps: ReAct's observation of an unknown tool is `Span::new`'s estimated 0, as nothing ran. Tests: - a new span and a bare figure are estimates; a measured cost survives `with_joule_cost`, and a bare figure attached after it is an estimate; - a trace round-trips through JSON with a `Measured` and an `Estimated` span, and a trace in the old format, without the field, reads back all `Estimated`; - `measured_tool`: the stub, a failed first or last read, a counter that held or went down, and one that advanced 10 µJ over a 20 ms step are all `Estimated` and charged at least the 300,000 µJ estimate; a 50 J reading is `Measured`. `measured_with` at a fixed estimate: a 450 µJ reading is `Measured` at estimates of 100 and 450, and an estimate of 1,000 is charged as `Estimated`; - `charge_llm_step` records the reply's figure as `Estimated`; - ReAct, with a counter that advances 50 J over the tool step: think spans `Estimated` at 1,000 µJ, the unknown tool's observation `Estimated` at 0, the act span `Measured` at 50 J, and the budget 3,000 µJ plus 50 J; with the stub, every span `Estimated`; - CodeAct, the same over code that succeeds and code that fails; - Plan-and-Execute: with the stub every span `Estimated`; with the scripted meter the plan step (40 J) and worker `b` (50 J) `Measured`, and worker `a`, over which the counter held, `Estimated`. Falsified, each mutant applied to this commit, run, and restored with `git checkout`: - every span pushed to a trace tagged `Measured`: 8 tests fail; - `Span::new` and `with_joule_cost` always `Measured`: 9 fail; - every span pushed to a trace tagged `Estimated`: 4 fail; - a span without the field reading back `Measured`: 1 fails; - `measured_with` tagging any reading `Measured`, including when the estimate is what is charged: 1 fails; - `charge_llm_step` tagging the provider's figure `Measured`: 5 fail; - `with_microjoules` keeping an earlier tag: 1 fails; - ReAct, CodeAct, and Plan-and-Execute each dropping the tag (`with_microjoules(cost.microjoules)`): 1 fails in each. `cargo test -p eoc-agent`: 38 unit and 9 integration tests pass. The eoc workspace (`cargo test --workspace`): 695 passed, 0 failed, 3 ignored, on an M5 Max (macOS 27.0.1). clippy for x86_64-unknown-linux-gnu on eoc-agent: the same two pre-existing warnings and no others. On macOS too clippy adds no warning (the two collapsible-if warnings predate this), and rustdoc reports nothing in the lines changed here. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| cookbook | ||
| docs | ||
| eoc-bench | ||
| eoc-rs | ||
| os | ||
| spec | ||
| standards | ||
| vocab | ||
| LICENSE | ||
| README.md | ||
| THREE_FACES.md | ||
EOC — Energy-Optimized Compute
A free, always-available, energy-honest AI substrate. AI that costs joules, not tokens.
AI is not free yet. The internet is. EOC closes the gap: a substrate that resolves work at the lowest sufficient cost and refuses to spend unbounded energy chasing benchmark deltas. Every query flows through a four-stage pipeline — state-construct → retrieve → refine → check — and a large language model is one of six refine operators, ordered last. The Fourth Truth: refinement before generation. The substrate runs in a browser, runs on commodity CPUs, denominates everything in joules per task against an open evaluation corpus, and cannot be turned off because no one entity runs it.
The substrate is intentionally ownerless: no protocol-level token, permissive licensing, conformance test vectors and open eval corpora so any implementation can verify itself without a trust relationship with the authors. Transaction Science is one steward — it publishes the spec, ships a reference implementation, and operates commercial services around the substrate (managed nodes, certification, registry hosting) — not its proprietor.
Contents
spec/eoc1_spec.docx,spec/eoc1_v0_1_1_patch.docx,spec/eoc1_v0_2.docx,spec/eoc1_v0_2_addendum_A.docx— EOC-1: the substrate architecture (v0.1 tiers → v0.2 four-stage pipeline; Addendum A: non-goals — token economics)spec/eoc2_wire.docx— EOC-2: the wire protocol (capability exchange, gossip, signed envelopes)spec/eoc3.docx— EOC-3: artifact distribution (content-addressed fetch for models, state machines, corpora)spec/eoc4_dcy.docx— EOC-4: DCY (Deterministic Cypher — the query language for the knowledge-graph retrieve operator)spec/eoc5_registry.docx— EOC-5: the Operator Family Registry (stable identifiers + conformance tests)spec/eoc1_eval001*.docx,spec/eval001_worked_instances.docx,spec/eval002.docx— Eval-001 (schema-conformant generation proficiency standard) and Eval-002 (retrieval/provenance)spec/eoc_architecture.docx— the architecture working draftspec/tokens_concealment.docx— Tokens Are the Concealment (the rhetorical companion to Addendum A)os/THEOREM.md,os/Q1_W_DEFINITION.md— the energy-first OS theorem the substrate is designed to run on, and the resolution of its open question on defining "useful work" in joules-per-work
Status
EOC-1 at v0.2; EOC-2..5 and Eval-001/002 at working-draft 0.1; OS theorem at v0.2. The reference implementation referenced across the specs as "v0.3" is to be brought into this repository.
Related
- Smart Byte (
../smart-byte/) — the value substrate; uses EOC's energy attribution. - TX Science AI (
ais.transaction.science) — the AI PaaS; its memoizing cascade is an instance of the EOC four-stage pipeline.