# live-conformance/sink-reel — highlight reels assembled on the sink

The corpus of [`extensions/sink-predicate.md`](../../extensions/sink-predicate.md) §9, in one file,
`vectors.json`.

**Provenance.** Generated here by `wai_sink_reel_vectors gen` (`wai-rs`, feature `sink_reel`), from
Ed25519 keys on seeds of one byte repeated 32 times and constant instants; the programme's marks are
derived by `pack_marks` from a stage index the generator writes. No input from outside this
repository. Every region is an ISO 3166-1 user-assigned code (`XA`, `XB`, …) or a subdivision of
one, and names no place.

`keys` names every key by its role, as 64 lowercase hexadecimal digits: the `source` that signs the
reel predicates, `other_source`, and `small_order`, the identity point.

- `predicates` (§9.1) are each a reel predicate's `text`; `outcome` is `read`, with its `digest`,
  `source`, `marks` and `state`, or `refuse` and its `reason`.
- `evaluations` (§9.3) are each a reel predicate's `text`, the programme's `marks` (a document of
  packaging §8.11.3), a sink's `state` (its `location`, its `interests` and its `exposures`, each
  `null` when not kept, and its `sources`) and the instant `now`; `outcome` is `evaluated`, with
  each reel assembled (`reel`, its `clips` in the order presented, `taken_ms` and `rest_ms`), or
  `refuse` and its `reason`.
- `logs` (§9.4) are each the same inputs, a `reel` and the `log` of clips presented; `outcome` is
  `conforms`, or `refuse` and its `reason`.

Everything is synthetic: keys attest nothing, and the clips' tags name no team. Each case states the
outcome it was written to have, declared in the generator and never copied from a verifier.

`wai_sink_reel_vectors verify` and `tests/sink_reel.rs` check that the file regenerates byte for
byte and that `wai-rs` reaches every stated outcome. `../sink_reel_verify.py` is the second
implementation, written from the extension's text, which also mutates copies of the corpus and
drops each of its own checks in turn and requires each to be caught.