open-standards/wai/live-conformance/machine-coding/README.md

live-conformance/machine-coding — coding for machines

The corpus of extensions/task-fidelity.md §5 (the split-computation claim), extensions/machine-descriptors.md and extensions/format-probes.md §19, in one file, vectors.json.

Provenance. Generated here by wai_machine_coding_vectors gen (wai-rs, feature machine_coding), from Ed25519 keys on seeds of one byte repeated 32 times, constant instants, and digests that are the SHA-256 of a phrase and name nothing: no parameter set, no tensor, no model and no media exists behind any of them. No input from outside this repository, and no bitstream of ISO/IEC 23888: neither part's text is openly readable, so none is written.

• candidates states, for wai.video.vcm and wai.tensor.fcm, that each is registered, a candidate, not dispatchable, and that its probe is no_probe.
• networks (task-fidelity §5.1) are each a cut, a head_set and a tail_set with the network digest over them.
• claims are each one split-computation claim's wire text; outcome is verified, or refuse with the step of jwp-receipts §3.1 and the reason.
• pairs (task-fidelity §5.3, §5.4) are each two claims, a and b, and held, the digests of the parameter sets the verifier holds (null where it holds none); outcome is composed with the account (each side, the rows by acquisition class, the unmetered sides and the coverage; it has no total), or refuse with its step and reason.
• descriptors (machine-descriptors §4) are each an event record in lowercase hexadecimal, read for the room room, with the models the reader admits (null where it is given none); outcome is read, with what was described and the msf record that carries the event (live-events §8.1, at t0_unix_us), or refuse and its reason.

Each case states the outcome it was written to have, declared in the generator and never copied from a verifier: a refusal's step and reason, an account's rows, a descriptor's items.

wai_machine_coding_vectors verify and tests/machine_coding.rs check that the file regenerates byte for byte, that wai-rs reaches every stated outcome, that a refusal restated as an acceptance is noticed, and that the extensions list the reference's reasons. ../machine_coding_verify.py is the second implementation, written from the extensions' text: it takes each claim through jwp-receipts §3.1 steps 1 to 4 with ../../claim-conformance/claim_verify.py, writes the pair's checks, the account, the event and descriptor readers and the MSF record itself, reads the candidates from the published registry export and format-probes' text, mutates copies of the corpus and drops each of its own checks in turn and requires each to be caught. claim_verify.py split vectors.json replays the claims alone.