open-standards/wai/live-conformance/holdings/README.md

live-conformance/holdings — who holds which objects

The corpus of extensions/holdings.md §8, in one file, vectors.json.

Provenance. Generated here by wai_holdings_vectors gen (wai-rs, feature holdings), from Ed25519 keys on fixed 32-byte seeds, constant instants, and envelopes whose payloads are opaque test bytes written by the generator; no media and no input from outside this repository.

keys names every key by its role, as 64 lowercase hexadecimal digits: the publisher's (did:web:publisher.example#d1) and three holders' (holder_a, holder_b, holder_c).

• records (§4) are each a record's bytes in hexadecimal, and its outcome: read, with its digest, holder and count of entries; or refuse and its reason.
• verdicts (§5.1 to §5.3) are each records, the group receipts a verifier holds and the instant at_ms; outcome.records gives each record's verdict: stands, superseded, set-aside reason=… or reject reason=….
• queries (§5.4) are each a record, a group's link hash and an index; outcome is held or the reason it is not.
• plans (§5.4) are a verdict's inputs, the records in the asker's order, and the wanted objects; outcome gives the records' verdicts, each wanted object's holders in that order, and from_origin, the wanted objects no holder holds.

Everything is synthetic: keys attest nothing, and the publisher's origin is a reserved example domain. Each case states the outcome it was written to have, declared in the generator, never copied from a verifier. §4.4's bound of 1,048,576 bytes is carried by no vector (a megabyte of hexadecimal); both implementations check it themselves.

wai_holdings_vectors verify and tests/holdings.rs check that the file regenerates byte for byte and that wai-rs reaches every stated outcome. ../holdings_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.