Verification Receipt Storage

Verification Receipt Storage

A verification receipt should make it possible to reconstruct what was checked and which result was produced.

Suggested record boundary

Store at least:

• receipt identifier;
• artifact or state identifier;
• contract or schema version;
• immutable verification result payload;
• evidence references;
• verification timestamp;
• verifier or component version where available.

Example relational shape

verification_receipt
  id
  artifact_id
  contract_version
  verifier_version
  status
  result_json
  evidence_json
  verified_at

This is a storage pattern, not a DigiEmu database schema.

Preserve history

If a later review changes the interpretation of a result, create a new review or correction event.

Do not overwrite the original verification receipt.

Querying

Useful queries include:

• all receipts for one artifact;
• all failed or incomplete results;
• all receipts produced by one contract version;
• all artifacts missing expected evidence;
• all results superseded by a later review event.