open-standards

Watch

History

Repository files (latest commit first)
Filename	Latest commit message	Latest commit date
Transaction Science f4847eafce All checks were successful standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 1m41s Details standards workspaces build + test / aac-rs (pull_request) Successful in 34s Details standards workspaces build + test / joule-code-rs (pull_request) Successful in 34s Details standards workspaces build + test / joulecontract-rs (pull_request) Successful in 36s Details standards workspaces build + test / map-rs (pull_request) Successful in 32s Details standards workspaces build + test / mesh-rs (pull_request) Successful in 25s Details standards workspaces build + test / openpay (pull_request) Successful in 1m23s Details standards workspaces build + test / eoc-rs (pull_request) Successful in 1m53s Details standards workspaces build + test / jcp-rs (pull_request) Successful in 1m16s Details standards workspaces build + test / proof-rs (pull_request) Successful in 1m10s Details standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m6s Details standards workspaces build + test / smart-byte-rs (pull_request) Successful in 2m32s Details standards workspaces build + test / arl-rs (pull_request) Successful in 3m52s Details standards workspaces build + test / joule-ui-rs (pull_request) Successful in 3m42s Details standards workspaces build + test / jouledesk-rs (pull_request) Successful in 3m12s Details standards workspaces build + test / joulehook-rs (pull_request) Successful in 3m16s Details standards workspaces build + test / sense-rs (pull_request) Successful in 3m17s Details standards workspaces build + test / macOS energy backend (jcp-energy) (pull_request) Successful in 2m48s Details eoc-meter: the one-thread burn test's floor matches what 200 ms of CPU can cost The process-energy burn test asked for user-interactive QoS so its burn would run on the fast cores, and it asserted at least 0.2 J. The QoS call returns 0 but changes nothing: the kernel caps a process with no app role, such as a test binary, at default QoS. rusage books all of the burn as default QoS (measured in jcp-energy's matching test, `22e5a6ad`). The burn already counts 200 ms of the thread's own CPU time, not wall time, but the energy those 200 ms cost still depends on which core class ran them, and at what clock. On an M5 Max at default QoS it read 0.18-1.24 J, so a 0.2 J floor sits at the bottom of the real range. This drops the ineffective QoS call and its declarations, records why in the test's doc, and lowers the floor to 0.1 J: half the lowest reading, and the sleeping test's ceiling. A counter that reads wall time at a fixed power still cannot pass both tests, and a counter reading 0 still fails. On this M5 Max, 4/4 pass: the burn read 0.504 J, and 500 ms asleep 21 µJ. Co-Authored-By: Claude Opus 5.5 <[email protected]>		2026-09-30 22:49:58 -04:00
..
eoc	eoc: the in-process burn test's backend is built only on macOS, where its one test runs	2026-09-30 22:41:13 -04:00
eoc-agent	eoc-agent: every span says whether its joule figure was measured or estimated	2026-09-30 22:38:48 -04:00
eoc-cache	eoc-cascade: a cache hit claims no measurement, and a total is measured only if every microjoule was read	2026-09-30 20:17:08 -04:00
eoc-carbon	eoc-carbon: an account and an SCI score are measured only where every part was, and a run with no correct answer has no score	2026-09-30 21:07:25 -04:00
eoc-cascade	eoc-cascade: a cache hit claims no measurement, and a total is measured only if every microjoule was read	2026-09-30 20:17:08 -04:00
eoc-core	eoc-cascade: a cache hit claims no measurement, and a total is measured only if every microjoule was read	2026-09-30 20:17:08 -04:00
eoc-distributed	ingest wave A4: 3 crates · smart-byte-atproto + op-openbanking + eoc-distributed	2026-05-24 12:22:09 -04:00
eoc-embeddings	Repo-wide toolchain refresh + jouleclaw policy/sandbox updates	2026-06-07 17:04:45 -04:00
eoc-eval	eoc-carbon: an SCI score is only as measured as the joules it was computed from	2026-09-30 20:17:24 -04:00
eoc-graph	Parallel ingest: 9 issues' worth of work across openpay / smart-byte / eoc	2026-05-23 13:24:05 -04:00
eoc-kv	Parallel ingest: 9 issues' worth of work across openpay / smart-byte / eoc	2026-05-23 13:24:05 -04:00
eoc-local	eoc: the CLI's cascade is metered by this process's own counter, because all of its stages run in-process	2026-09-30 22:39:01 -04:00
eoc-memory	ingest wave F: 3 crates · op-crypto-extra + smart-byte-acdc + eoc-memory	2026-05-24 17:28:24 -04:00
eoc-meter	eoc-meter: the one-thread burn test's floor matches what 200 ms of CPU can cost	2026-09-30 22:49:58 -04:00
eoc-multimodal	Repo-wide toolchain refresh + jouleclaw policy/sandbox updates	2026-06-07 17:04:45 -04:00
eoc-neural	Parallel ingest: 9 issues' worth of work across openpay / smart-byte / eoc	2026-05-23 13:24:05 -04:00
eoc-observability	ingest wave C: 3 crates · op-statements + smart-byte-activitypub + eoc-observability	2026-05-24 13:51:09 -04:00
eoc-quantize	ingest wave D: 3 crates · op-fraud-graph + smart-byte-ilp + eoc-quantize	2026-05-24 16:10:10 -04:00
eoc-rag	ingest wave A3: 3 crates · op-ewallets-asia + smart-byte-zk + eoc-rag	2026-05-24 12:08:49 -04:00
eoc-rerank	Repo-wide toolchain refresh + jouleclaw policy/sandbox updates	2026-06-07 17:04:45 -04:00
eoc-route-learned	eoc-route-learned: unbreak the build — rand_distr 0.4 pulled rand 0.8	2026-07-20 12:46:50 -04:00
eoc-safety	ingest wave E: 3 crates · op-bin + smart-byte-tendermint + eoc-safety	2026-05-24 16:52:07 -04:00
eoc-spec-decode	Repo-wide toolchain refresh + jouleclaw policy/sandbox updates	2026-06-07 17:04:45 -04:00
eoc-streaming	eoc-streaming: a stream nothing metered has no energy figure, never 0 µJ	2026-09-30 20:17:36 -04:00
eoc-tools	eoc: pin rand off 0.10.2, which does not compile	2026-08-27 13:32:56 -04:00
eoc-vendor-api	Repo-wide toolchain refresh + jouleclaw policy/sandbox updates	2026-06-07 17:04:45 -04:00
eoc-wasm	Parallel ingest: 9 issues' worth of work across openpay / smart-byte / eoc	2026-05-23 13:24:05 -04:00