| Filename | Latest commit message | Latest commit date |
|---|---|---|
26a1b6aa63
The liveness rule counts intervals and never looked at how long one lasted. A rail that steps twice a second steps in every interval once sampling slows to that cadence, and a contended host slows it just so. On an M3 Ultra the same rail, burned and sampled by the same code in one quiet process, was Frozen in 17 of 17 probes ticking at 25, 100 or 250 ms and Live in 12 of 12 at 500 or 800 ms. With four test binaries sampling at once, 6 of 20 runs cached Live for the process, on a rail every other crate on that host called Frozen, and in CI the status selected the counter. An IOReport interval now counts only within MAX_INTERVAL_TICKS (3) of the tick the probe asked for. A longer one shows which rails exist, and is otherwise no evidence either way: not its advances, not the interval, not its time. So the 300 ms window is 300 ms of intervals that count, or a burst beside one long interval would fill it. A probe that cannot sample near its cadence ends Frozen and falls back to its estimator: estimated, never over-claimed. Three, from interval streams recorded on real hosts and replayed under each cap. That rail under contention: Live in 57 of 80 streams with no cap, 13 at eight ticks, 9 at five, 2 at four, none at three. A RAPL counter that is live: Live in 10 of 10 on a quiet host, 9 of 10 with a spinning thread for every core, 2 of 10 with twice as many. Only IOReport's rails have the cap. RAPL, NVML and a process's counter publish at least as often as their probes tick, so sampling slowed by contention shows nothing a quiet probe would not. Capping them too made the tests that hold a process's counter to Live fail under load: 5 of 27 runs on an M5 Max with four busy threads a core, four of them on the counter's status. RailWatch::default is IOReport's watch, for a probe ticking at PROBE_TICK. every_channel, the vendor counters' watch, has no cap. The tests that called a rail sampled every 600 ms Live, as intended, now say it is not. 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.
Licence
Specification text: CC-BY-4.0 (see LICENSE).
Reference implementation in eoc-rs/: Apache-2.0 (see eoc-rs/LICENSE).
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.