route-record: a third party's hop has a signed record of what was sent, what came back, and what the provider bills #572

Merged

dcharlot merged 3 commits from wai/third-party-hop into main 2026-11-02 11:04:26 -05:00

Conversation 0 Commits 3 Files changed 12 +4387 -16

2026-11-02

Transaction Science

CHANGELOG: Reason::ALL's length is acknowledged as breaking ...

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

2e3f09bcf0

• View at this point in history

2026-11-02 08:03:16 -05:00

Transaction Science

route-record §6.2: every form and bound of the third-party hop record has its control ...

The Rust mutations showed a usage's quantity of the wrong type went uncaught, and the same held of
other forms and bounds the text states. Each now has a control, at its first value past the limit,
so the two implementations are held to the same limits. A clause `unhex` already made redundant
is gone. The document kind is in the registry.

The Python verifier stops a mutated copy at its first failure: it only asks whether one fails.

routes corpus: 236 vectors. route_record_verify.py: 103 checks, 1,119 mutated copies.

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

2e6cfaef42

• View at this point in history

2026-11-02 08:03:16 -05:00

Transaction Science

route-record §6.2: a third party's hop has a signed record of what was sent, what came back, and what the provider bills ...

A hop sent to a third party's endpoint is work the router did not do. Its OER/2 receipt says the
hop served or failed; nothing WAI defines says what was sent, to whom, what came back, or what
the provider bills, so an implementation carries that in a record of its own that WAI's verifier
cannot read.

`wai-route-third-party-hop`, signed by the router and named by its digest: the provider and its
API origin, whose account the hop ran on (never the key), the provider's id for the work, each
exchange (method, URL without its query, times, status, the bodies by SHA-256 and length, the
response where it was JSON, with links' queries removed), the outputs by name and content hash,
the usage the provider bills, in the endpoint's unit, and what it reported charging, in its own
terms.

A verification document may carry the records beside its receipts (§7.2 step 9). Each is held to
the route record's signer and job, to its attempt and that attempt's candidate, and when it served,
its outputs to what the hop's receipt names and the attempt's count. No route record changes, since
the record names the receipt the route record already names.

routes corpus: 126 -> 202 vectors, from fixed seeds, every control refused at its own place.
route_record_verify.py verifies each from the text, shares no code with wai-rs, and catches each of
its 85 checks dropped and all 1,051 mutated copies.

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

25f011dac1

• View at this point in history

2026-11-02 08:03:16 -05:00