RESOURCES · VERIFICATION
Receipts, hashes, signatures, manifests, releases and independent verification answer different questions. This resource family keeps them separate.
OVERVIEW
Hashed, signed, encrypted, timestamped, receipted and independently verified are not synonyms. Each control establishes a bounded property, and none by itself proves the factual or legal interpretation of the underlying material.
A receipt records a declared event, action or transition with enough identity and ordering context to support later reconstruction. It establishes what the system recorded about an operation; it does not automatically prove the real-world truth of every assertion inside that operation.
A cryptographic hash provides content identity and change detection under a named algorithm. Matching hashes can show that two byte sequences are identical; a hash does not identify who created the content or whether its interpretation is correct.
A digital signature binds data to a signing key under a declared cryptographic scheme. Verification can establish the signature/data/key relationship, while identity, authorization and legal effect still depend on the surrounding key-management and governance context.
A manifest declares which artifacts, versions, identifiers and checks belong to a release or evidence universe. It prevents an output set from silently changing after release and gives independent verifiers a concrete inventory to inspect.
Independent verification means supported properties can be checked without private execution authority or blind dependence on the originating runtime. The verifier should state exactly what passed, what was not tested and which claims remain interpretive rather than cryptographic.