manifest.json the expected result for every fixture (the contract)
valid/ records that MUST validate with no error-severity issue
invalid/ records seeded with exactly one defect each
lineage-peers/
lineage-cycle-peer.json a peer record for the --lineage-peer cycle search (VER1604)
registries/
conflicting-spaces.json published space descriptors for the --spaces check (VER402)
test-registry-snapshot.json corpus-local VER Registry snapshot for --registry (VER1205/6)
keys/
corpus-signing-key.pub.pem public key for the corpus's detached-JWS fixtures
valid/ and invalid/ hold fixtures; every other directory holds inputs to a run. The manifest-and-disk agreement check covers the two fixture directories only, which is why a lineage peer — itself a well-formed record — lives in lineage-peers/ rather than in valid/: it has no expected result of its own, and registering one would claim it does.
