Watch

History

Repository files (latest commit first)
Filename	Latest commit message	Latest commit date
Transaction Science 18bdfd276c Some checks failed wai-quantum energy-landscape jobs / does this change touch it (push) Successful in 14s Details joule-moq-remote host agent / joule-moq-remote · does this change touch it (push) Successful in 36s Details WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (push) Successful in 16s Details joule-moq-room room service / joule-moq-room · does this change touch it (push) Successful in 41s Details joule-moq-web browser client / joule-moq-web · does this change touch it (push) Successful in 37s Details wai-audit collector and player integration / does this change touch it (push) Successful in 36s Details wai-fleet service / does this change touch it (push) Successful in 50s Details wai-sink-android native sink library / does this change touch it (push) Successful in 35s Details wai-ledger service / does this change touch it (push) Successful in 58s Details wai-quantum studio and desktop / does this change touch it (push) Successful in 59s Details WAI operation catalogue / does this change touch it (push) Successful in 1m5s Details wai-sink-swift native sink package / does this change touch it (push) Successful in 26s Details wai-key-proxy / does this change touch it (push) Successful in 1m1s Details wai-quantum for JavaScript / does this change touch it (push) Successful in 59s Details wai-app and Create / wai-app · does this change touch it (push) Successful in 1m13s Details WAI Studio / does this change touch it (push) Successful in 42s Details joule-moq-remote host agent / joule-moq-remote, every target (macos) (push) Successful in 1m18s Details wai-fleet service / service · macos (push) Successful in 1m2s Details wai-app and Create / wai-app · tests, clippy, the line language's verifier (linux) (push) Successful in 37s Details wai-audit collector and player integration / collector, player integration and the browser end to end · macos (push) Successful in 1m44s Details wai-audit collector and player integration / collector · linux (push) Successful in 2m9s Details wai-ledger service / service · macos (push) Successful in 2m24s Details wai-key-proxy / proxy · linux (push) Successful in 2m8s Details WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (push) Successful in 3m21s Details joule-moq-remote host agent / joule-moq-remote, every target (linux-arm64) (push) Successful in 3m30s Details WAI Studio / Studio in WebKit · linux (push) Failing after 51s Details WAI Studio / the catalogue's actions, the unit tests and the core · linux (push) Successful in 1m38s Details wai-ledger service / service · linux (push) Successful in 4m17s Details wai-quantum studio and desktop / desktop app · macos (push) Successful in 3m27s Details repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Successful in 6m15s Details wai-fleet service / service · linux (push) Successful in 4m51s Details wai-quantum energy-landscape jobs / the same bits · macos (push) Successful in 6m33s Details wai-sink-android native sink library / the JNI layer and the platform-free half on the host JVM · linux-arm64 (push) Successful in 4m53s Details joule-moq-room room service / joule-moq-room, every target (push) Successful in 7m8s Details wai-quantum for JavaScript / javascript · linux (push) Successful in 6m16s Details wai-quantum energy-landscape jobs / native against WebAssembly, over many seeds (push) Successful in 9m31s Details WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (push) Successful in 9m28s Details wai-sink-android native sink library / every ABI, the AAR, and the instrumented tests in a headless emulator · macos (push) Successful in 9m3s Details wai-app and Create / wai-app · Create, browser end-to-end (macos) (push) Successful in 9m59s Details wai-quantum studio and desktop / studio · browser (push) Successful in 10m26s Details wai-quantum energy-landscape jobs / the module under wasm32-wasip2 (wasmtime) (push) Successful in 12m55s Details wai-quantum energy-landscape jobs / the same bits · linux-arm64 (push) Successful in 13m18s Details WAI operation catalogue / the catalogue and every door · linux (push) Successful in 13m10s Details WAI Studio / Studio in Chromium and Firefox · macos (push) Successful in 13m21s Details joule-moq-web browser client / joule-moq-web · browser end-to-end (macos) (push) Successful in 18m47s Details wai-sink-swift native sink package / libwai slices, desktop tests, simulator tests · macos (push) Successful in 18m25s Details wai-quantum studio and desktop / desktop app · linux (push) Successful in 17m24s Details wai-quantum energy-landscape jobs / reader, kernels, answers and the stated result · linux, release (push) Successful in 22m34s Details wai-quantum studio and desktop / desktop app · windows (push) Successful in 12m33s Details wai: sink-evaluated predicates and per-session ad tracks — targeting and frequency caps decided on the sink from its own state, and a session's own ad bound into a room's ad frame extensions/sink-predicate.md registers the record `wai.delivery.sink_predicate` (`wai-sink-predicate`): a source's signed predicate travelling beside a programme, the registered form of unidirectional-delivery §2's sink-evaluated predicate. It carries the programme's blackouts (audience-decision §4.2) and its ad slots, each a list of candidate ads in the order the source prefers them, with the regions each is shown in and its frequency caps (a counter, a limit, a window), and declares exactly the state classes it reads (`location`, `exposures`); it is a route-record document signed in its canonical form under `wai:sink-predicate`. A sink evaluates it from its own state alone: the programme's verdict is audience-decision §4.6's at its aggregated location (unresolved, every blackout applied, when it holds none), and when that is `show` it fills each slot itself, taking in order the candidates shown at its location (a country of which a candidate lists only a subdivision is shown neither `only` nor `except`), whose caps its own exposures have not reached in their windows, with those the earlier slots and candidates added, and that fit the avail. A sink that keeps no exposures is shown no capped candidate. The evaluation causes no request and nothing about the device leaves it. A predicate holding, at any depth, a member by which its evaluation would send something away (`report`, `beacon`, `callback`, `uri`) or count across devices (`household`, `account`) is refused `predicate_needs_report`; a sink's log of a slot that presents a candidate whose cap was reached is refused `predicate_cap_breached`, one not shown at the location `predicate_not_targeted`, and any other departure from the fill `predicate_fill_mismatch`. unidirectional-delivery §2 and audience-decision §1 and §6 name it. live-compose §5.10 adds per-session ad tracks: in a squeeze or a double box, a session's sink may show the session's own ad, decided by a stitched-presentation pod-input record of that session, on the session's ad track (owner `ad_` and the session), bound to the composition by an ad-track binding, `WAT1`, signed by the record's signer under `wai:live-compose-ad-track`. A binding that does not match its session's composition is refused `ad_track_mismatch`, naming what differs: a descriptor that is not an ad frame, a record other than the one it names, a shared record or another session's, a record whose frame is not the descriptor's (layout, canvas, corner, window, gap, aspect), or a slot the record does not have; one signed by another key `ad_track_not_permitted`; one out of its bounds `ad_track_invalid`. While a binding is in effect (from `start` for its ad's duration), the session's layout is §5.9's with the track in the ad tile, the program where the room's frame puts it, and the room's ad participant with no tile and no voice. live-compose's §10 table, its descriptor and its receipt are unchanged; its codes for the binding are §5.10.5's. stitched-presentation §4.6 and §6: a composited break whose ad region shows each session its own ad is decided by a record of each session under the room's ad frame, never by a shared record, and the session's claim is that record's one presentation; no record, claim or verification rule changes. The references are the `sink_predicate` module of wai-rs (feature `sink_predicate`) and the `compose_ad_track` module (feature `compose_ad_track`). The corpora are live-conformance/sink-predicate/ (68 predicates, 23 evaluations, 18 logs) and live-conformance/compose-ad-track/ (36 bindings, 17 layouts); sink_predicate_verify.py and compose_ad_track_verify.py are their second implementations, which agree on every case, fail every mutated copy (17 of 17, 13 of 13) and catch every weakened verifier (35 of 35, 21 of 21). Nineteen faults planted in the reference each fail its tests, each matched by a check the second verifier drops: a cap breach (the fill ignoring caps, the log check ignoring them, an exposure a whole window old still counted, a sink that keeps none admitting a capped candidate); a predicate needing a report (the check removed, read only at the top level, the across-device members dropped); a per-session ad track not matching its session's composition (another frame, another session's record, a shared record, a descriptor that is no ad frame, a missing slot, another signer, the track kept at its binding's end); and a signature over the wrong bytes (a predicate's without its domain, under the audience decision's, over the text as written; a binding's without its domain and under the pod-input record's). Co-Authored-By: Claude Opus 5.5 <[email protected]>		2026-11-09 21:15:45 -05:00
..
corpora	wai: integer neural fields, wai.field.int_grid: a scene the sink computes	2026-11-09 17:18:42 -05:00
verifiers	wai: sink-evaluated predicates and per-session ad tracks — targeting and frequency caps decided on the sink from its own state, and a session's own ad bound into a room's ad frame	2026-11-09 21:15:45 -05:00
baseline.json	wai-conformance starts on a change to joule-ui-catalogue, the crate wai-app now links	2026-11-07 03:10:33 -05:00
README.md	wai conform relay --suite moqt holds a relay to the MOQT interop cases, pq joins the verifier suites, and wai conformance gen writes a corpus by its generator	2026-11-08 14:44:52 -05:00

README.md

What wai-conformance.yml runs, one file a step

wai-conformance.yml keeps no hand list of its verifier steps, corpora or kernel tests. Its lists are derived, when it runs, from the files here and from tags in the test files, by scripts/wai-conformance-lists.py, whose docstring states every key; its gate reads the steps' paths: through scripts/pr-touches-paths.py. A change that adds a verifier, a corpus or a kernel test adds a file, or a line to a file of its own, and edits no line of the workflow, unless a step's paths: names a file under none of the trigger's paths (check names it). Its features and [[test]] entries in wai/wai-rs/Cargo.toml stay shared (wai/CONTRIBUTING.md).

verifiers/<name>.sh: one step of the independent-verifiers job. Its body is the step's shell, run in wai/ (or working-directory:) with bash -eo pipefail, as a workflow step runs. Its header, the leading # key: value lines, gives step: (its name), order: (steps run in ascending order, a tie by file name), features: (each list compiles alone in features-alone, and every feature joins WAI_FEATURES), and where it needs them alone:, build: pq, release-features:, bins:, pq-bins:, paths: (the extension texts it reads, which the workflow's gate then runs on) and working-directory:. Its corpus's independent verifier is an independent: line, <name> <area> [needs=<packages>] [verdicts=<file>] [dir=<dir>] python3 [-I] <script> <args>, the command line its README gives, run in wai/ by the job's one step wai conform --independent and never by the body; wai-rs/build.rs reads the binary's table of independent verifiers from these lines. A file with such lines and no body is a declaration: its verifiers run in that step alone. Prose comments follow the header, after a # line.
corpora/<name>.txt: one cargo-class corpus, verified by its own tool on every leg of cargo-classes (corpus:, order:, bin:, dir:), and written by it through wai conformance gen --suite <corpus>: its gen mode, or the modes gen: names in order (none where the tool writes nothing and the corpus's README says what does). wai-rs/build.rs reads these files for that command's table, and a dir: that names no corpus fails the build.
A test file of wai/wai-rs/tests/ whose first line is // wai-conformance: int-kernels runs in the fast integer kernels' steps of both profiles (int-kernels-release: the release step only; int-kernels-amd: the AVX-512 host too). The steps' features are the tagged tests' required-features.
baseline.json: the lists the workflow kept by hand before they were derived. The repository checks require every derived list to hold every entry of it, and every step it names to run.

To see what the workflow runs: python3 scripts/wai-conformance-lists.py dry-run (of another commit: --ref <commit>; two of them diff line by line). To run one step as CI does: python3 scripts/wai-conformance-lists.py run --only <name>. To check the files: python3 scripts/wai-conformance-lists.py check.