wai identify, the carousel schedule and holdings: what a file is, when each object passes on a one-way bearer, and which neighbour holds it #605
2026-11-03
wai: holdings — which objects of which groups a node holds now, for its neighbours
All checks were successful
WAI energy receipts / energy receipts · linux (pull_request) Successful in 14m13s
wai-quantum studio and desktop / desktop app · linux (pull_request) Successful in 6m16s
WAI mbt2018_mean integer decode (regenerated vectors) / regenerate mbt2018_mean integer vectors → Rust decode, required (pull_request) Successful in 5m25s
wai-web wasm32 / wai-web wasm32 build · corpus, menu and writers (pull_request) Successful in 6m31s
wai-sink-swift native sink package / libwai slices, desktop tests, simulator tests · macos (pull_request) Successful in 17m37s
WAI Studio / Studio in WebKit · linux (pull_request) Successful in 11m12s
wai-quantum docs, course and locales / every command and snippet in the docs · linux (pull_request) Successful in 40m51s
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 21s
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 32s
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 55s
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 2m16s
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 19m1s
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 26m32s
WAI examples / WAI examples · android-app · linux-arm64 (pull_request) Successful in 8m8s
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 12m25s
WAI HTTP delivery / HTTP corpus · falsify patches 0/3 (pull_request) Successful in 7m48s
WAI HTTP delivery / HTTP corpus · falsify patches 1/3 (pull_request) Successful in 7m41s
WAI HTTP delivery / HTTP corpus · falsify mutations 0/3 (pull_request) Successful in 35m19s
WAI HTTP delivery / HTTP corpus · every patch and mutation in exactly one shard (pull_request) Successful in 7s
WAI HTTP delivery / HTTP corpus · verified both ways, and the differential (pull_request) Successful in 2m15s
WAI HTTP delivery / cache rules · controls and labelled caches (pull_request) Successful in 1m31s
WAI HTTP delivery / HTTP corpus · falsify patches 2/3 (pull_request) Successful in 7m13s
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 1m56s
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 26s
wai-pack / wai-pack · dependency licences (pull_request) Successful in 13s
WAI HTTP delivery / HTTP corpus · falsify mutations 2/3 (pull_request) Successful in 34m7s
wai-sink-android native sink library / the JNI layer and the platform-free half on the host JVM · linux-arm64 (pull_request) Successful in 2m33s
WAI HTTP delivery / HTTP corpus · falsify mutations 1/3 (pull_request) Successful in 39m55s
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 7m7s
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h31m0s
A receiver that stores what a broadcast carried, a neighbourhood cache or a peer can serve those objects over a short link; a neighbour that knows who holds what fetches from them before it spends the backhaul. Nothing said who holds what. extensions/holdings.md registers `wai.delivery.holdings`: a record (WHD1) of, per group a node holds objects of, the group's link hash, its leaf count and either `whole` or a bitmap (as a reconciliation's), in one canonical form, with the instant it states them at and the one it expires at, signed by the holder under SPEC §7 Signatures. Groups and bitmaps rather than a filter over hashes: WAI delivers everything under group receipts that name objects by position, a node holds objects as groups arrive, and a bitmap is exact (no neighbour sent after an object its holder lacks) at a bit an object, 41 bytes for a group held whole. A verifier holds a record to its instant and to the group receipts it has (a misstated leaf count refuses it whole; a group with no receipt held is kept), keeps a holder's latest record and sets aside two of one instant that differ, answers whether a record holds an object, and derives an asker's plan: each wanted object's holders in the asker's order, and the objects no neighbour holds, which come from the origin. An object a neighbour serves is verified under its receipts like any other; a record is never evidence of bytes. A node advertises only what reached it over a broadcast bearer, and may sign each record with a fresh key. The reference is the `holdings` module of wai-rs; the corpus is live-conformance/holdings/ (21 records with a control for each rule, 11 verdicts, 6 queries, a plan over three neighbours), with holdings_verify.py as its second implementation: 39 cases agree, 9 of 9 mutated copies and 10 of 10 weakened verifiers caught. Co-Authored-By: Claude Opus 5.5 <[email protected]>
carousel §11: the patents disclosed on RaptorQ and Raptor, and no-code as the default
The IETF holds disclosures on RaptorQ (RFC 6330; #2554 current, updating #1958) and on Raptor (RFC 5053; #1957 current, with #1176 the holder's general licence statement). Both current ones give two terms by product: a licence within the holder's standard terms for a device that implements a wireless wide-area standard, and a non-assertion, conditional on full implementation and suspended against a party that asserts, for one that implements none. No disclosure relates to RFC 5445 or RFC 5052. §11 cites them by number and states each licence class as disclosed. Since neither code is royalty-free for every implementer, no-code is the default a tool that writes schedules uses, as SPEC §5 keeps a capability that is not royalty-free from being a default. The reference implementation encodes and decodes no symbol; its RFC 6330 decoder is a development dependency. Security and privacy considerations move to §12; nothing cites them by number. Co-Authored-By: Claude Opus 5.5 <[email protected]>
wai: the carousel schedule — when each object passes on a bearer with no return path, and when a receiver holds it
On a bearer with no return path a receiver cannot ask for what it missed: it holds an object only if the passes it heard carried enough encoding symbols. bearer-receipts declares the transmission and reconciles it afterwards; nothing stated the plan in between. extensions/carousel.md registers `wai.bearer.carousel` and the jwp-receipts claim class `schedule` (§2.4.16): a publisher's signed plan, beside the group receipt and the instance's transmission claim, naming for each object its forward error correction (RaptorQ, RFC 6330 with its verified erratum 5548; Compact No-Code, RFC 5445) and that code's object transmission information, the repair symbols each pass adds, whether later passes repeat their ESIs or send new ones, and the passes' times and count. Step 4 holds each code's parameters to its bounds and division into source blocks; step 6 holds the entries to the group, its objects' content hashes and, where the bytes are held, their lengths. From it a verifier derives, for a loss bound in parts per million, the pass after which a receiver whose losses stay within it holds each object, for every pattern of loss within the bound: a RaptorQ block at K' + h distinct symbols, the count RFC 6330 §5.8 states its decoding failure bound at, and a symbol a repeating pass missed counted as missed again. It checks a statement that an object or a group is held by an instant, sets aside schedules that contradict each other or whose instance is undeclared or two-way, and a receiver derives the passes it must listen to and how long its radio must be on. The reference is the `carousel` module of wai-rs with the class's body in `claim_receipt::schedule`; the corpus is live-conformance/carousel/ (33 verdicts, 50 claims, 16 plans) with carousel_verify.py as its second implementation and claim_verify.py's new `carousel` mode for steps 1-4. tests/carousel.rs checks K' and Partition[] against an independent RFC 6330 implementation (a dev-dependency) for every block size, and decodes each RaptorQ object a case holds available from what a receiver within the bound holds. A receipt index served over HTTP now checks a schedule claim against its group and listed objects. Co-Authored-By: Claude Opus 5.5 <[email protected]>
wai mcp: media_inspect is in the core toolset's list
The core toolset serves media_inspect after envelope_inspect; tests/cli_mcp.rs and the README's toolset table now name it in that place. Co-Authored-By: Claude Opus 5.5 <[email protected]>
int_kernels_vectors: the identify corpus decodes nothing
every_decoded_output_states_a_sha256 requires each conformance directory to state its decoded outputs' SHA-256 or say why it has none. identify-conformance decodes nothing: each vector states what a file's bytes are read as, and the file's SHA-256 in vectors.json. Co-Authored-By: Claude Opus 5.5 <[email protected]>
wai identify: what any file is, from its bytes alone
`wai inspect` reads envelopes; most files a toolchain meets are not envelopes, and the first question about one is what it is. `wai identify <file>` (operation media.inspect, extensions/media-identify.md) answers it for any file: - the formats the bytes fit, each with the offsets of the bytes that say so, how far its structure was followed and where and why that stopped; - a container's tracks as it states them: codec, size, channels, rate, protection; - the registered capabilities they map to, and what a format probe reads of them; - signatures found inside the file; - where no format is recognised, measures that still hold: how the byte values are spread, uniform windows, and the lags at which the bytes repeat. The verdict is identified, ambiguous, signature_only or unknown, and there is no confidence figure: a candidate's strength says what was checked. Nothing is decoded, no protected track is opened, and unknown stays unknown. Walks cover ISO media, Matroska, transport streams, Ogg, FLAC, RIFF, MPEG audio, ADTS, PNG, JPEG, GIF, IVF, YUV4MPEG2, FLV, AV1 OBU and Annex B streams, and HLS and DASH text; 35 more formats are known by their signature. Every walk is bounded, reads a file where its lengths lead (a large file is never held whole), and has been given hostile bytes; it builds for wasm32. The agent door has it as media_inspect, its results marked untrusted_content: a file's author chooses the strings in it. identify-conformance/ holds files written by real muxers and encoders from test patterns and tones, what an independent media prober reads of them (prober.json), and generated cases sitting on each rule's edge. identify_verify.py is a second implementation written from the text; it reads the extension's tables, gives every file its whole result, and holds ext/ to the prober's reading. tests/identify.rs holds the reference's tables to the extension's. Co-Authored-By: Claude Opus 5.5 <[email protected]>