receipt-ledger: version 5 holds a decode to the frames it delivered, its codestream what it read #559

Merged

dcharlot merged 3 commits from wai/decode-output into main 2026-11-01 04:38:01 -05:00

Conversation 0 Commits 3 Files changed 10 +1823 -108

2026-11-01

Transaction Science

receipt-ledger: a decode delivers its frames as one animated PNG ...

Version 5 held each frame of a decode to its own PNG object, matched in order
against the served hop's outputs. A route record states those outputs once each
and at most 1024 (route-record §5.2), so a decode longer than 1024 frames could
not be recorded and a still scene, whose frames repeat, could not be stated.

A decode's `frames` is now one animated PNG (PNG's third edition: acTL, fcTL,
fdAT) of 8-bit RGB, read whole first by a still's chunk rules and the
animation's (each frame the whole picture, blended over nothing; the default
image the first frame; the sequence numbers in order; acTL counting the frames
it holds), of the receipt's size and count, and then frame by frame as a
still's image data, each frame's samples hashing to the receipt's frame. The
served hop states that one object and nothing else.

png_still gains encode_animation, every byte a function of the frames and the
delay, and animation, which reads the structure and inflates a frame only when
asked; the still reader and writer share their steps with it, their output
unchanged. The corpus replaces the per-frame controls with the animation's:
89 to 108 vectors, every other vector and source unchanged.
receipt_ledger_verify.py reads the animation with a reader of its own.

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

4eb5caa684

• View at this point in history

2026-11-01 01:10:01 -05:00

Transaction Science

receipt-ledger: a frame is read as packaging §5 reads a still ...

packaging numbers its subsections in bold, not as headings, so §5.7 is not a
section the cross-reference check can resolve; the other texts cite §5.

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

fff7c5b8a6

• View at this point in history

2026-11-01 01:07:31 -04:00

2026-10-31

Transaction Science

receipt-ledger: version 5 holds a decode to the frames it delivered, its codestream what it read ...

Version 4 gives every int_motion output as its receipt and its codestream and holds the
codestream to what the hop delivered (§5.1). That is true of an encode and false of a decode,
which delivers its reconstruction: a conforming router had to state the codestream the decode
read as what it delivered, and commit the hop's receipt to an object it never delivered.

Tariff and invoice version 5 (§4.8) are version 4's layout, rules and prices with one rule
more. A decode's output also gives `frames`, one PNG of 8-bit RGB per frame read as packaging
§5.7 reads a still, each one's samples hashing to the receipt's frame at its index; the receipt
is still re-derived from the codestream, the decode's input; and the served hop states exactly
those frames, in order, and nothing else. Versions 1 to 4 read, verify and bill as before.

The corpus adds thirteen vectors (one accepted, twelve controls) and keeps every other vector
but the `invoice_version` control byte for byte; receipt_ledger_verify.py reads version 5 with
the packaging verifier's PNG reader and drops one more check (`decode-frames`); the ledger
service bills version 5 as version 4.

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

b9ed0f2b5e

• View at this point in history

2026-10-31 23:11:21 -04:00