Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions

wai: a carousel schedule extends, what a receiver needs rides in band, a node schedules its own instance, and Raptor #658

Closed
dcharlot wants to merge 4 commits from wai/carousel-monotone-inband into main
pull from: wai/carousel-monotone-inband
merge into: Transaction-Science:main
Conversation 0 Commits 4 Files changed 30 +14779 -3030
dcharlot commented 2026-11-05 12:44:39 -05:00
Owner
Copy link

Merge order. Stacked on #655 (the timeliness ladder, wai/timeliness-ladder-scheduler), merge after it. Until #655 merges, this pull request's diff includes its commits. Both change the timeliness corpus, so this one holds both changes in one regenerated corpus.

A carousel schedule can grow, what a receiver needs rides on the bearer, a node can schedule its own instance, and Raptor joins the codes.

Monotone extension (carousel §4.5, §6.2 step 4)

Along the signer's chain, a later schedule extends the one before it when it keeps every earlier entry, with count at least as great and every other member equal. New objects may be added. The last schedule stands, and earlier ones get the label extended. Dropping an object or withdrawing, moving or changing a pass is still schedule_contradicted, and sets aside every schedule of the instance. Timeliness plans read the same schedule and label.

In-band repetition (carousel §8.1, §8.2)

A publisher MUST send on the instance the group receipt, its claims from the chain head to the instance's last schedule, and the head of its origin's key log, at least once per interval. A verifier checks whether what a receiver acquired suffices. New refusals: inband_chain_incomplete, inband_not_scheduled, inband_key_log_missing.

A node's own schedule (cache-authority §5.6, §4.1, §4.3, §7.2, §7.3, §9; carousel §4.3, §4.4; jwp-receipts)

A node may schedule its own instance in a schedule claim signed by its own key, under the schedule authority from its operator. The cache verdict now reads schedules, and a node's stands only beside its own instance that stands. It credits nothing: carousel's verdict and timeliness read publisher schedules only.

Raptor (carousel §4.1, §5.3 to §5.5, §6.3, §7, §8), in its own commit

New fec value raptor, FEC Encoding ID 1, from RFC 5053 and TS 26.346. RFC 5053 states no bound on decoding failure, and an independent decoder failed on 14 to 31 blocks in 100 at K + 2. So h of 0, 1 and 2 means K + 8, K + 16 and K + 28. Across block sizes from 4 to 8,192 symbols, with samples shrinking as blocks grow, the worst measured failure rates were 81 in 10,000, 2 in 18,000 and 4 in 6,000,000. That's one implementation with uniformly random symbols. §5.3 quotes these figures and says they are not a bound, and failure_one_in stays null. The ignored test raptor_margin_measurement reproduces them. §11 keeps the factual IPR notes, and no-code stays the default.

What stacking on #655 found

  • A limit, stated, not closed: timeliness §7.5.1 shares one set of claims across every plan of a run, while carousel §7 has a receiver plan with a later schedule from when it acquires it. A run given both schedules makes an earlier plan read passes the sink didn't yet know about. §7.5.1 now says a run doesn't date its claims, and that the run reproducing a sink's earlier decisions is the one given the claims it held then.
  • Fixed: cache-authority §9 still said one fallback, and the Rust corpus writer disagreed with Python on a ladder.
  • New vectors: a ladder rung on an extended schedule, with controls for a withdrawn schedule and for before the extension, and a cache-authority §9 line with a ladder, which closes the gap #655 left.

Verified

On a Linux build host, Rust 1.99.1, at this head:

  • Each of carousel_verify.py, timeliness_verify.py and cache_authority_verify.py: 0 failures, every mutated copy fails, every weakened verifier is caught.
  • wai_{carousel,timeliness,cache_authority}_vectors verify regenerates byte for byte, and claim_verify.py on each corpus has 0 failures.
  • The Rust tests of the touched features pass; clippy has no finding in the touched files; wai breaking has no unacknowledged break; check-advisories.py and check-lockfiles.sh pass (new dev-dependency raptor-code 1.0.12, MIT).
  • Falsification: all planted faults are caught.

Only the jobs these files touch ran there; CI runs the rest.

🤖 Generated with Claude Code

Closed: Landed as direct commits on main with the timeliness work stacked on it, under the working model of 2026-11-06. 110 of 111 checks read passed or skipped. The other, cargo-class corpora on linux-arm64, stopped mid-word with only passing lines while the forge was refusing runners' results, and the same job passed on linux and on macos arm64 for this head; it runs again on main's nightly schedule. Before landing, on the rebased tree: the timeliness, carousel, cache-authority, bearer-receipts and compact-return conformance steps, each with its independent Python verifier, passed on a build host.

**Merge order.** Stacked on #655 (the timeliness ladder, `wai/timeliness-ladder-scheduler`), merge after it. Until #655 merges, this pull request's diff includes its commits. Both change the timeliness corpus, so this one holds both changes in one regenerated corpus. A carousel schedule can grow, what a receiver needs rides on the bearer, a node can schedule its own instance, and Raptor joins the codes. ## Monotone extension (carousel §4.5, §6.2 step 4) Along the signer's chain, a later schedule extends the one before it when it keeps every earlier entry, with `count` at least as great and every other member equal. New objects may be added. The last schedule stands, and earlier ones get the label `extended`. Dropping an object or withdrawing, moving or changing a pass is still `schedule_contradicted`, and sets aside every schedule of the instance. Timeliness plans read the same schedule and label. ## In-band repetition (carousel §8.1, §8.2) A publisher MUST send on the instance the group receipt, its claims from the chain head to the instance's last schedule, and the head of its origin's key log, at least once per interval. A verifier checks whether what a receiver acquired suffices. New refusals: `inband_chain_incomplete`, `inband_not_scheduled`, `inband_key_log_missing`. ## A node's own schedule (cache-authority §5.6, §4.1, §4.3, §7.2, §7.3, §9; carousel §4.3, §4.4; jwp-receipts) A node may schedule its own instance in a `schedule` claim signed by its own key, under the `schedule` authority from its operator. The cache verdict now reads schedules, and a node's stands only beside its own instance that stands. It credits nothing: carousel's verdict and timeliness read publisher schedules only. ## Raptor (carousel §4.1, §5.3 to §5.5, §6.3, §7, §8), in its own commit New `fec` value `raptor`, FEC Encoding ID 1, from RFC 5053 and TS 26.346. RFC 5053 states no bound on decoding failure, and an independent decoder failed on 14 to 31 blocks in 100 at K + 2. So `h` of 0, 1 and 2 means K + 8, K + 16 and K + 28. Across block sizes from 4 to 8,192 symbols, with samples shrinking as blocks grow, the worst measured failure rates were 81 in 10,000, 2 in 18,000 and 4 in 6,000,000. That's one implementation with uniformly random symbols. §5.3 quotes these figures and says they are not a bound, and `failure_one_in` stays `null`. The ignored test `raptor_margin_measurement` reproduces them. §11 keeps the factual IPR notes, and `no-code` stays the default. ## What stacking on #655 found - **A limit, stated, not closed:** timeliness §7.5.1 shares one set of claims across every plan of a run, while carousel §7 has a receiver plan with a later schedule from when it acquires it. A run given both schedules makes an earlier plan read passes the sink didn't yet know about. §7.5.1 now says a run doesn't date its claims, and that the run reproducing a sink's earlier decisions is the one given the claims it held then. - **Fixed:** cache-authority §9 still said one fallback, and the Rust corpus writer disagreed with Python on a ladder. - **New vectors:** a ladder rung on an extended schedule, with controls for a withdrawn schedule and for before the extension, and a cache-authority §9 line with a ladder, which closes the gap #655 left. ## Verified On a Linux build host, Rust 1.99.1, at this head: - Each of `carousel_verify.py`, `timeliness_verify.py` and `cache_authority_verify.py`: 0 failures, every mutated copy fails, every weakened verifier is caught. - `wai_{carousel,timeliness,cache_authority}_vectors verify` regenerates byte for byte, and `claim_verify.py` on each corpus has 0 failures. - The Rust tests of the touched features pass; clippy has no finding in the touched files; `wai breaking` has no unacknowledged break; `check-advisories.py` and `check-lockfiles.sh` pass (new dev-dependency `raptor-code` 1.0.12, MIT). - Falsification: all planted faults are caught. Only the jobs these files touch ran there; CI runs the rest. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- **Closed:** Landed as direct commits on main with the timeliness work stacked on it, under the working model of 2026-11-06. 110 of 111 checks read passed or skipped. The other, cargo-class corpora on linux-arm64, stopped mid-word with only passing lines while the forge was refusing runners' results, and the same job passed on linux and on macos arm64 for this head; it runs again on main's nightly schedule. Before landing, on the rebased tree: the timeliness, carousel, cache-authority, bearer-receipts and compact-return conformance steps, each with its independent Python verifier, passed on a build host. 
An entry's fallback is an ordered ladder: null, one rung as an object, or two to eight rungs as an
array in strictly falling value, no object named twice (§4.2 rule 3.4, timeliness_ladder_invalid).
One rung has one form, the object, so an entry with one fallback object is a ladder of one rung and
reads, judges and plans as it did; the cache-authority corpus regenerates unchanged.

§5.3 states which rung applies: at by_ms the primary held, else the first rung held; holding
neither, the sink has passed every rung, states `passed`, presents the primary late at its value at
arrival, and at the end, having presented nothing, abandons and states `ended`. §6.3 and §7.3 take
the ladder, and a plan's choice names its rung.

§7.5 and timeliness::scheduler run a sink's plans against the instants it first held each object:
fetch, abandon, present, passed and ended by exact steps, a function of those inputs alone. A later
plan replaces the one in force wholly. plans_invalid and arrivals_invalid refuse a run's inputs.

The corpus gains the group E, ladder claims, verdicts and plans, and runs, each outcome declared in
the generator. timeliness_verify.py writes the ladder and the run from the text, with mutations and
weakenings for both, and claim_verify.py holds rule 3.4.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
timeliness §6.3's lines now read each rung, and cache_authority.rs asks for each. The second
implementation read one fallback object, which raises on a fallback written as an array. For one
rung the statements it gives are the same, so the cache-authority corpus reads as it did.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
wai: a timeliness rung writes itself by value
All checks were successful
wai-ledger service / service · macos (pull_request) Successful in 1m24s
Details
joule-moq-web browser client / joule-moq-web · browser end-to-end (macos) (pull_request) Successful in 15m59s
Details
wai-pack / wai-pack · macos (pull_request) Successful in 4m32s
Details
WAI energy receipts / energy receipts · macos (pull_request) Successful in 11m25s
Details
wai-quantum studio and desktop / desktop app · macos (pull_request) Successful in 6m0s
Details
wai-sink-android native sink library / every ABI, the AAR, and the instrumented tests in a headless emulator · macos (pull_request) Successful in 10m18s
Details
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 20m45s
Details
WAI examples / WAI examples · the archive, the readiness check, the browser and Apple · macos (pull_request) Successful in 23m21s
Details
WAI Studio / Studio in Chromium and Firefox · macos (pull_request) Successful in 13m25s
Details
wai-sink-swift native sink package / libwai slices, desktop tests, simulator tests · macos (pull_request) Successful in 19m51s
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m10s
Details
joule-moq-remote host agent / joule-moq-remote, every target (linux-arm64) (pull_request) Successful in 2m16s
Details
joule-moq-room room service / joule-moq-room, every target (pull_request) Successful in 3m45s
Details
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 17s
Details
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 21m21s
Details
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 24s
Details
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 48s
Details
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 11m50s
Details
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 2m51s
Details
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 28m42s
Details
WAI HTTP delivery / HTTP corpus · verified both ways, and the differential (pull_request) Successful in 2m12s
Details
WAI HTTP delivery / cache rules · controls and labelled caches (pull_request) Successful in 1m55s
Details
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 1m51s
Details
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 25s
Details
wai-pack / wai-pack · dependency licences (pull_request) Successful in 14s
Details
WAI examples / WAI examples · android-app · linux-arm64 (pull_request) Successful in 8m3s
Details
wai-sink-android native sink library / the JNI layer and the platform-free half on the host JVM · linux-arm64 (pull_request) Successful in 2m9s
Details
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 10m43s
Details
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 9m41s
Details
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h17m5s
Details
73b68b245e 
Fallback is Copy, so its to_value takes self, as clippy's wrong_self_convention asks.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Carousel §4.5 and §6.2 step 4: along their chain, a later schedule of one
instance that keeps every earlier entry, with at least its passes at the same
instants sending the same symbols, extends the one before it and may add
objects. The last stands and the earlier are labelled `extended`. A schedule
that drops an object, or withdraws, moves or changes a pass, still sets aside
every schedule of its instance. Timeliness plans read the same schedule.

Carousel §8.1 and §8.2: on an instance whose schedule stands, the publisher
sends the group receipt, its claims from the head of their chain to the
instance's last schedule, and the head of its origin's key log, at least once
per the schedule's interval. A verifier given what a receiver acquired checks
that it suffices: inband_chain_incomplete, inband_not_scheduled or
inband_key_log_missing otherwise.

Cache-authority §5.6, §7.2 step 4, §7.3 and carousel §4.3 step 2: a node states
its plan for its own cache instance in a schedule claim signed by its own key.
The cache verdict reads schedules, publisher's and nodes', sets aside another
key's schedule of a node's instance (cache_schedule_signer_mismatch), and holds
a statement of carousel §6.4 to the schedule that stands. A node's schedule
credits nothing.

Vectors for each rule in the carousel, timeliness and cache-authority corpora,
verified by wai-rs and by the Python verifiers, each with mutated copies and
weakened checks for the new rules. On the timeliness ladder: a plan and a run take
a rung over a schedule a later one extends, a plan loses it over the same two
withdrawing a pass, and timeliness §7.5.1 says a run does not date its claims.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Cache-authority §9 derives timeliness §6.3's lines for an entry from all three
kinds of held-at statement. Its text and its corpus still spoke of one fallback.
The text now reads every rung, and states a ladder's line as timeliness §6.3 does,
the list of each rung's least instant. The corpus writes a line through
timeliness' own form, which it did not: an array's instants were lost.

The case timeliness_line_ladder holds a rung in the group and a rung in another:
each held alone, on time over both, and the first late with the second in time.
wai-rs and cache_authority_verify.py reach it, the verifier with two more mutated
copies and a weakened check that reads only the first rung.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
wai: a schedule names Raptor (RFC 5053), the code MBMS download uses
Some checks failed
wai-quantum for JavaScript / javascript · linux (pull_request) Has been cancelled
Details
wai-quantum studio and desktop / does this change touch it (pull_request) Has been cancelled
Details
wai-quantum studio and desktop / studio · browser (pull_request) Has been cancelled
Details
wai-quantum studio and desktop / desktop app · macos (pull_request) Has been cancelled
Details
wai-quantum studio and desktop / desktop app · linux (pull_request) Has been cancelled
Details
wai-quantum studio and desktop / desktop app · windows (pull_request) Has been cancelled
Details
wai-quantum WebGPU member / does this change touch it (pull_request) Has been cancelled
Details
wai-quantum WebGPU member / shader checks · browser build · wasip2 inertness (pull_request) Has been cancelled
Details
wai-quantum WebGPU member / member · software Vulkan (linux) (pull_request) Has been cancelled
Details
wai-quantum WebGPU member / member · Metal (macos) (pull_request) Has been cancelled
Details
wai-quantum WebGPU member / member · GPU, Vulkan (jetson-hub) (pull_request) Has been cancelled
Details
wai-quantum WebGPU member / member · GPU, Vulkan (thor) (pull_request) Has been cancelled
Details
wai-quantum WebGPU member / member · integrated GPU, Vulkan (framework-128gb) (pull_request) Has been cancelled
Details
wai-quantum WebGPU member / member · browser WebGPU (macos) (pull_request) Has been cancelled
Details
wai-quantum WebGPU member / member · DX12 and Vulkan (cbio-windows) (pull_request) Has been cancelled
Details
wai-sink-android native sink library / does this change touch it (pull_request) Has been cancelled
Details
wai-sink-android native sink library / the JNI layer and the platform-free half on the host JVM · linux-arm64 (pull_request) Has been cancelled
Details
wai-sink-android native sink library / every ABI, the AAR, and the instrumented tests in a headless emulator · macos (pull_request) Has been cancelled
Details
wai-sink-swift native sink package / does this change touch it (pull_request) Has been cancelled
Details
WAI mbt2018_mean integer decode (regenerated vectors) / does this change touch it (pull_request) Has been cancelled
Details
WAI mbt2018_mean integer decode (regenerated vectors) / regenerate mbt2018_mean integer vectors → Rust decode, required (pull_request) Has been cancelled
Details
WAI Studio / does this change touch it (pull_request) Has been cancelled
Details
WAI Studio / the catalogue's actions, the unit tests and the core · linux (pull_request) Has been cancelled
Details
WAI Studio / Studio in Chromium and Firefox · macos (pull_request) Has been cancelled
Details
WAI Studio / Studio in WebKit · linux (pull_request) Has been cancelled
Details
wai-web reach builds / wai-web reach · does this change touch it (pull_request) Has been cancelled
Details
wai-web reach builds / wai-web reach builds · the package of record, every output as recorded (pull_request) Has been cancelled
Details
wai-web reach builds / wai-web reach builds · this tree's wai-web, every rung on its engine line (pull_request) Has been cancelled
Details
wai-web wasm32 / does this change touch it (pull_request) Has been cancelled
Details
wai-web wasm32 / wai-web wasm32 build · corpus, menu and writers (pull_request) Has been cancelled
Details
d9af1781c9 
Carousel §4.1, §5.5: an entry's fec may be raptor (FEC Encoding ID 1), with RFC
5053's F, T, Z, N and Al, held to its fields and to its block sizes, 4 to 8,192
source symbols, with ESIs in 16 bits. 3GPP TS 26.346 §7.2.2 requires a receiver
of MBMS download to support the code.

Carousel §5.3: RFC 5053 states no bound on a decoder's failure. An independent
implementation failed on 14 to 31 blocks in 100 at K + 2, so a Raptor block is
held at K and a margin set by measurement, 8, 16 or 28 at overhead 0, 1 or 2,
and failure_one_in is null. tests/carousel.rs decodes each Raptor object a case
holds available with that implementation, a new development dependency, holds a
fixed sample of it to the measurement, and keeps the measurement as an ignored
test.

no-code stays the default, and carousel §11 keeps the IETF's disclosures on RFC
5053 for implementers.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
wai dev's test: the stand-in room service listens without a reverse lookup
Some checks failed
wai-quantum WebGPU member / member · browser WebGPU (macos) (pull_request) Successful in 1m57s
Details
wai-sink-android native sink library / every ABI, the AAR, and the instrumented tests in a headless emulator · macos (pull_request) Successful in 5m35s
Details
WAI examples / WAI examples · the archive, the readiness check, the browser and Apple · macos (pull_request) Successful in 18m11s
Details
wai-pack / wai-pack · macos (pull_request) Successful in 2m53s
Details
wai-quantum WebGPU member / member · Metal (macos) (pull_request) Successful in 5m47s
Details
WAI Studio / Studio in Chromium and Firefox · macos (pull_request) Successful in 7m45s
Details
joule-moq-web browser client / joule-moq-web · browser end-to-end (macos) (pull_request) Successful in 16m7s
Details
WAI examples / WAI examples · portable · linux (pull_request) Successful in 41m5s
Details
wai-sink-swift native sink package / libwai slices, desktop tests, simulator tests · macos (pull_request) Successful in 16m50s
Details
wai-quantum studio and desktop / desktop app · windows (pull_request) Successful in 9m33s
Details
wai-quantum WebGPU member / member · GPU, Vulkan (jetson-hub) (pull_request) Successful in 18m38s
Details
joule-moq-remote host agent / joule-moq-remote, every target (linux-arm64) (pull_request) Successful in 2m42s
Details
joule-moq-room room service / joule-moq-room, every target (pull_request) Successful in 5m29s
Details
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 2m0s
Details
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 7m12s
Details
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 1m53s
Details
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 3m35s
Details
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 3m9s
Details
WAI HTTP delivery / HTTP corpus · verified both ways, and the differential (pull_request) Successful in 3m49s
Details
WAI examples / WAI examples · android-app · linux-arm64 (pull_request) Successful in 10m3s
Details
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 19m6s
Details
WAI HTTP delivery / cache rules · controls and labelled caches (pull_request) Successful in 9m5s
Details
wai-sink-android native sink library / the JNI layer and the platform-free half on the host JVM · linux-arm64 (pull_request) Successful in 4m53s
Details
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 3m15s
Details
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 20m21s
Details
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 55s
Details
wai-pack / wai-pack · dependency licences (pull_request) Successful in 2m6s
Details
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Failing after 39m56s
Details
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 10m37s
Details
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h42m31s
Details
effff8f260 
tests/cli_studio.rs failed on every run on one macOS runner and passed on
every other runner, 3 of 3 against 19 of 19 on 5 November, with "the room
service's clock on the relay: not within 30 s".

The stand-in room service starts an HTTPServer, whose server_bind calls
socket.getfqdn before the server listens. On that host, under the runner's
Python 3.15.2, getfqdn("127.0.0.1") takes 35 s, past the 30 s wai dev waits, and
a stack dump of the stalled stand-in shows it there. The stand-in relay opens a
plain socket and answers in 0.1 s. Nothing here reads the name, so the fixture
no longer asks for it.

On that host and Python the room stand-in took 35.5 s and now takes 0.12 s. A
socket.getfqdn planted to stall for 40 s fails the test without this change,
with the same message, and passes with it.

Changelog: none

Co-Authored-By: Claude Opus 5.5 <[email protected]>
dcharlot closed this pull request 2026-11-06 18:25:18 -05:00
Some checks failed
joule-moq-room room service / joule-moq-room · does this change touch it (pull_request) Successful in 5s
Details
joule-moq-remote host agent / joule-moq-remote · does this change touch it (pull_request) Successful in 7s
Details
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 9s
Details
WAI operation catalogue / does this change touch it (pull_request) Successful in 7s
Details
WAI conformance / does this change touch it (pull_request) Successful in 6s
Details
WAI examples / WAI examples · does this change touch them (pull_request) Successful in 7s
Details
WAI energy receipts / does this change touch it (pull_request) Successful in 7s
Details
wai-fleet service / does this change touch it (pull_request) Successful in 9s
Details
WAI HTTP delivery / WAI HTTP · does this change touch it (pull_request) Successful in 12s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 0/3 (pull_request) Has been skipped
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 1/3 (pull_request) Has been skipped
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 2/3 (pull_request) Has been skipped
Details
WAI JPEG-AI whole decode (pinned inputs, required) / does this change touch it (pull_request) Successful in 10s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 0/3 (pull_request) Has been skipped
Details
WAI HTTP delivery / HTTP corpus · falsify patches 1/3 (pull_request) Has been skipped
Details
WAI HTTP delivery / HTTP corpus · falsify patches 2/3 (pull_request) Has been skipped
Details
wai-key-proxy / does this change touch it (pull_request) Successful in 9s
Details
wai-ledger service / does this change touch it (pull_request) Successful in 9s
Details
wai-ops-gpu integer operators on GPUs / does this change touch it (pull_request) Successful in 8s
Details
WAI neural sink gates / does this change touch it (pull_request) Successful in 9s
Details
wai-quantum for JavaScript / does this change touch it (pull_request) Successful in 7s
Details
wai-audit collector and player integration / does this change touch it (pull_request) Successful in 23s
Details
joule-moq-web browser client / joule-moq-web · does this change touch it (pull_request) Successful in 26s
Details
wai-app and Create / wai-app · does this change touch it (pull_request) Successful in 26s
Details
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (pull_request) Successful in 23s
Details
wai-sink-android native sink library / does this change touch it (pull_request) Successful in 7s
Details
wai-quantum studio and desktop / does this change touch it (pull_request) Successful in 9s
Details
wai-quantum WebGPU member / does this change touch it (pull_request) Successful in 9s
Details
wai-sink-swift native sink package / does this change touch it (pull_request) Successful in 8s
Details
wai-web reach builds / wai-web reach · does this change touch it (pull_request) Successful in 8s
Details
WAI Studio / does this change touch it (pull_request) Successful in 9s
Details
WAI mbt2018_mean integer decode (regenerated vectors) / does this change touch it (pull_request) Successful in 9s
Details
wai-web wasm32 / does this change touch it (pull_request) Successful in 12s
Details
wai-pack / wai-pack · does this change touch it (pull_request) Successful in 24s
Details
wai-quantum WebGPU member / member · DX12 and Vulkan (cbio-windows) (pull_request) Successful in 12m49s
Details
WAI conformance / fast integer kernels, every x86_64 kernel set (AVX-512 silicon) (pull_request) Successful in 3m2s
Details
wai-quantum WebGPU member / member · integrated GPU, Vulkan (framework-128gb) (pull_request) Successful in 7m51s
Details
wai-quantum WebGPU member / member · GPU, Vulkan (thor) (pull_request) Successful in 28m43s
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 3m42s
Details
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 38s
Details
WAI conformance / faces from keypoints under wasm32-wasip2 (wasmtime) (pull_request) Successful in 2m10s
Details
WAI HTTP delivery / HTTP corpus · every patch and mutation in exactly one shard (pull_request) Successful in 5s
Details
WAI conformance / quantum core and corpus under wasm32-wasip2 (wasmtime) (pull_request) Successful in 4m32s
Details
wai-key-proxy / proxy · linux (pull_request) Successful in 1m14s
Details
wai-fleet service / service · linux (pull_request) Successful in 2m23s
Details
wai-ledger service / service · linux (pull_request) Successful in 2m30s
Details
WAI neural sink gates / model-free refusals of the neural sink (pull_request) Successful in 2m2s
Details
wai-app and Create / wai-app · tests, clippy, the line language's verifier (linux) (pull_request) Successful in 29s
Details
WAI neural sink gates / the exact JPEG-AI decoder reports its path (pinned inputs, required) (pull_request) Successful in 2m18s
Details
wai-ops-gpu integer operators on GPUs / builds · no adapter is not a pass (linux) (pull_request) Successful in 3m27s
Details
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (pull_request) Successful in 1m37s
Details
wai-audit collector and player integration / collector · linux (pull_request) Successful in 5m52s
Details
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (pull_request) Successful in 3m8s
Details
wai-quantum WebGPU member / shader checks · browser build · wasip2 inertness (pull_request) Successful in 2m53s
Details
wai-quantum WebGPU member / member · software Vulkan (linux) (pull_request) Successful in 2m12s
Details
WAI Studio / the catalogue's actions, the unit tests and the core · linux (pull_request) Successful in 1m6s
Details
wai-quantum for JavaScript / javascript · linux (pull_request) Successful in 5m1s
Details
WAI JPEG-AI whole decode (pinned inputs, required) / fetch pinned JPEG-AI inputs → whole decode + pixel hash, required (pull_request) Successful in 9m26s
Details
wai-web reach builds / wai-web reach builds · the package of record, every output as recorded (pull_request) Successful in 2m36s
Details
joule-moq-remote host agent / joule-moq-remote, every target (macos) (pull_request) Successful in 52s
Details
wai-pack / wai-pack · linux (pull_request) Successful in 2m14s
Details
wai-quantum studio and desktop / studio · browser (pull_request) Successful in 6m11s
Details
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 25s
Details
wai-quantum studio and desktop / desktop app · linux (pull_request) Successful in 8m20s
Details
wai-web wasm32 / wai-web wasm32 build · corpus, menu and writers (pull_request) Successful in 5m21s
Details
WAI conformance / codec wrappers · fuzz smoke, text decode limits, C entry points, provenance, the semantic path (pull_request) Successful in 1m4s
Details
WAI energy receipts / energy receipts · linux (pull_request) Successful in 15m16s
Details
WAI operation catalogue / the catalogue and every door · linux (pull_request) Successful in 19m5s
Details
WAI mbt2018_mean integer decode (regenerated vectors) / regenerate mbt2018_mean integer vectors → Rust decode, required (pull_request) Successful in 9m9s
Details
wai-fleet service / service · macos (pull_request) Successful in 1m27s
Details
wai-ledger service / service · macos (pull_request) Successful in 1m15s
Details
WAI Studio / Studio in WebKit · linux (pull_request) Successful in 11m54s
Details
wai-audit collector and player integration / collector, player integration and the browser end to end · macos (pull_request) Successful in 2m15s
Details
WAI energy receipts / energy receipts · macos (pull_request) Successful in 6m42s
Details
standards workspaces build + test / macOS energy backends (pull_request) Successful in 11m28s
Details
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 25m8s
Details
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 13m2s
Details
wai-quantum studio and desktop / desktop app · macos (pull_request) Successful in 4m28s
Details
wai-web reach builds / wai-web reach builds · this tree's wai-web, every rung on its engine line (pull_request) Successful in 19m6s
Details
wai-app and Create / wai-app · Create, browser end-to-end (macos) (pull_request) Successful in 6m34s
Details
wai-ops-gpu integer operators on GPUs / Metal GPU and browser WebGPU (macos) (pull_request) Successful in 8m2s
Details
wai-quantum WebGPU member / member · browser WebGPU (macos) (pull_request) Successful in 1m57s
Details
wai-sink-android native sink library / every ABI, the AAR, and the instrumented tests in a headless emulator · macos (pull_request) Successful in 5m35s
Details
WAI examples / WAI examples · the archive, the readiness check, the browser and Apple · macos (pull_request) Successful in 18m11s
Details
wai-pack / wai-pack · macos (pull_request) Successful in 2m53s
Details
wai-quantum WebGPU member / member · Metal (macos) (pull_request) Successful in 5m47s
Details
WAI Studio / Studio in Chromium and Firefox · macos (pull_request) Successful in 7m45s
Details
joule-moq-web browser client / joule-moq-web · browser end-to-end (macos) (pull_request) Successful in 16m7s
Details
WAI examples / WAI examples · portable · linux (pull_request) Successful in 41m5s
Details
wai-sink-swift native sink package / libwai slices, desktop tests, simulator tests · macos (pull_request) Successful in 16m50s
Details
wai-quantum studio and desktop / desktop app · windows (pull_request) Successful in 9m33s
Details
wai-quantum WebGPU member / member · GPU, Vulkan (jetson-hub) (pull_request) Successful in 18m38s
Details
joule-moq-remote host agent / joule-moq-remote, every target (linux-arm64) (pull_request) Successful in 2m42s
Details
joule-moq-room room service / joule-moq-room, every target (pull_request) Successful in 5m29s
Details
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 2m0s
Details
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 7m12s
Details
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 1m53s
Details
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 3m35s
Details
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 3m9s
Details
WAI HTTP delivery / HTTP corpus · verified both ways, and the differential (pull_request) Successful in 3m49s
Details
WAI examples / WAI examples · android-app · linux-arm64 (pull_request) Successful in 10m3s
Details
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 19m6s
Details
WAI HTTP delivery / cache rules · controls and labelled caches (pull_request) Successful in 9m5s
Details
wai-sink-android native sink library / the JNI layer and the platform-free half on the host JVM · linux-arm64 (pull_request) Successful in 4m53s
Details
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 3m15s
Details
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 20m21s
Details
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 55s
Details
wai-pack / wai-pack · dependency licences (pull_request) Successful in 2m6s
Details
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Failing after 39m56s
Details
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 10m37s
Details
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h42m31s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!658
No description provided.