statecraft.
Catalog/spec-spine

103-a-verifier-fixture-is-a-published-artifact

A verifier fixture is a published artifact

Lifecycle approvedImplementation completeVerification unknownQualification unknown

The tamper and cross-version cases an independent verifier must reproduce exist only as commands inside spec 068's acceptance block and as a measured table in docs/authority-evidence.md. A verifier outside this repository cannot run either. This emits them as a named, versioned fixture set: the bytes, the corpus each payload is about, and the outcome each case must reach, all measured against the shipped verifier rather than asserted.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
  "kind": "directory",
  "path": "crates/spec-spine-core/fixtures/verifier/"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/spec-spine-cli/tests/verifier_fixtures.rs"
}

Source headings

  1. 103: A verifier fixture is a published artifact
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 The boundary, stated first
  6. 3.2 Three kinds of bytes, never conflated
  7. 3.3 What a fixture case is
  8. 3.4 `case.json`, and the index
  9. 3.5 The reason classes, measured against the shipped verifier
  10. 3.6 Recompute cases carry their corpus
  11. 3.7 The version rule, so the set does not rot
  12. 3.8 The set describes the shipped verifier, and is proven to
  13. 3.9 Where the bytes come from, and what is not promised
  14. 4. Out of scope
  15. 5. Resolved decisions
  16. Verification

Frozen anchors

No frozen anchors declared.