statecraft.
Catalog/statecraft-cli

005-acceptance-and-evidence

Independent acceptance, the receipt, the separately reported evidence dimensions, and the envelope two products exchange

Lifecycle approvedImplementation in-progressVerification unknownQualification unknown

How a claim of completion becomes, or fails to become, an acceptance. Fixes the identification of candidate bytes and the trusted base, the authority-set rule that stops a candidate from being judged by rules it wrote, the receipt that binds repository, base, candidate, suite, exit codes and policy digest, the four evidence dimensions reported separately from admission with closed value sets, independently supplied trust roots, the preservation of original bytes and named hash constructions, and the three names for absence, none of which reads as success. It also owns the envelope crate the statecraft platform wrote against these serializations and transferred here, which makes one owner for the reference, the dimensions, admission and the absence words rather than two implementations of one wire format.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
  "kind": "directory",
  "path": "crates/statecraft-acceptance/"
}
  • establishes
    {
  "kind": "directory",
  "path": "crates/statecraft-envelope/"
}

Source headings

  1. 005: Independent acceptance, the receipt, the evidence dimensions, and the envelope
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 What is judged
  6. 3.1.1 Which outcomes are even eligible
  7. 3.2 Independence
  8. 3.3 The authority-set rule
  9. 3.3.1 How the report is obtained
  10. 3.3.2 Which class witnesses which member
  11. 3.3.3 When there is no answer
  12. 3.3.4 What reading the report permits, and what it does not
  13. 3.4 The receipt
  14. 3.5 The four evidence dimensions, and admission
  15. 3.6 Trust roots
  16. 3.7 Bytes, digests and constructions
  17. 3.8 The three names for absence
  18. 3.9 The reviewable outcome
  19. 3.10 Observable negative cases
  20. 3.11 One owner, and who re-exports
  21. 3.12 `Recorded<T>`: the three words are reserved
  22. 3.13 The reference
  23. 3.14 What a compatibility fixture must prove
  24. 3.15 Provenance and the licence
  25. 3.16 The native golden vectors stay provisional
  26. 3.17 The platform's dependency
  27. 3.18 Whether the contract an attempt was bound to still holds
  28. 3.19 The suite runs inside the protected evidence boundary
  29. 4. Out of scope
  30. 5. Resolved decisions
  31. Verification

Frozen anchors

No frozen anchors declared.