receipt-ledger: tariff version 3 prices media jobs per operation and bills the work done #550

Merged

dcharlot merged 2 commits from wai/ledger-work-priced into main 2026-10-31 08:50:18 -04:00

Conversation 0 Commits 2 Files changed 13 +1415 -136

2026-10-31

Transaction Science

Merge origin/main (#553: two arm64-heavy conformance jobs build without debuginfo) into wai/ledger-work-priced ...

Co-Authored-By: Claude Opus 5.5 <[email protected]>

4dc270aeb2

• View at this point in history

2026-10-31 06:10:47 -04:00

2026-10-30

Transaction Science

receipt-ledger: tariff version 3 prices media jobs per operation and bills the work ...

A job price of version 2 is (capability, unit, divisor, price), so one
capability's encode (a motion search, then a codestream written) and decode
(a reconstruction) shared a price although they spend different energy for
the same output units. And a chain billed every record once, the output's
int_motion decode receipt among them: the codecs are deterministic, so a
re-run of a request (a new hop, new energy, a new OER/2 receipt) delivered
the same output receipt and was refused record_rebilled.

Version 3 (WLT1 and WLI1 with version byte 3) adds op_len and operation to
each job price, which a version-2 reader cannot read, and prices a job by its
serving capability and its route record's operation, in strictly ascending
order of (capability, operation, unit); an unpriced (capability, operation)
bills nothing. Under it a chain bills a job's work once (its route record and
its hops' OER/2 receipts); the output receipt is cited and carried in the
citation digest but is not once-only, so a re-run is billed and a replayed hop
receipt or route record is still refused (record_rebilled, record_duplicate).
Two route records of one job are two runs, no longer record_overlap. Version 2
reads, verifies and bills exactly as before; packages keep their rule. A job
price whose capability or operation is not text is tariff_invalid, as §4.3
reads it (the reference said malformed).

wai-rs, receipt_ledger_verify.py and the ledger service follow. The corpus adds
nine vectors (encode and decode at their own prices, a re-run billed, one
output under two hops, an unpriced operation, a replayed hop, one hop under
two lines, prices out of order by operation, a version-2 invoice under a
version-3 tariff, the re-run refused under version 2); its version-3 jobs are
routed under the route corpus's seeds, whose file is unchanged. The control
invoice_version now gives version 4.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

8642b13940

• View at this point in history

2026-10-30 12:17:07 -04:00