Energy oracle & work classes

JouleOS bills in joules — and it refuses to lie about them. Energy is measured wherever the hardware allows, and every reading carries an honest provenance tag.

The oracle, by coordinate

Oracle	Source	Where
AppleSiliconOracle	ri_energy_nj via proc_pid_rusage (AMU)	M-class Macs
RaplOracle	RAPL MSRs	Linux
EstimatorOracle	calibrated time × power model	everywhere else

The HUD shows you which one produced a number — ⚡AmuAgx for a measured reading versus ~Estimator for a modeled one. The system never claims an accuracy it cannot deliver.

Eight work classes — never summed

A joule spent rendering a frame is not the same as a joule spent emitting a token. JouleOS pins work to eight non-fungible classes, and J/W is always reported per class:

• W_render — frames meeting their deadline
• W_infer — valid output tokens
• W_storage — durable bytes
• W_network — acknowledged bytes
• W_sensing — valid samples
• W_control — realized commands
• W_string — processed input bytes (internal)
• W_recall — recall queries returning a record

Mixing them would produce a meaningless average. The non-fungibility (principle P1) is enforced: classes are tracked separately end-to-end, from the cost ledger to the receipt.

Receipts

Every metered operation can seal a JCR-1 receipt — the family’s canonical det-CBOR + COSE_Sign1 format — carrying a two-part measured + estimated cost with its provenance tag. See Receipts.