Verifying a Record

Verification answers a narrow but important question: does the record you are holding match the record that was sealed, and does its evidence chain still line up?

Verification walkthrough

1. Check the record id. Confirm the id, type, environment label, and change summary match the handoff you expected.
2. Recompute the hash. Canonicalize the receipt payload and recompute the SHA-256 hash over the record fields that are supposed to be sealed.
3. Compare the chain. Confirm previous_record_hash and record_hash match the receipt sequence you were given.
4. Review attached evidence. For each evidence item, recompute or inspect the referenced hash, screenshot, log excerpt, or exported file.
5. Read the human summary. Confirm the summary does not overstate what the attached evidence proves.

Example command flow

# Private-pilot CLI shape. Public install commands will be published later.
edgerecord receipt inspect ER-SAMPLE-20260614-001.json
edgerecord receipt hash ER-SAMPLE-20260614-001.json
edgerecord receipt verify ER-SAMPLE-20260614-001.json --evidence ./evidence/

What a passing verification means

• The receipt content has not changed since it was sealed.
• The evidence hashes listed in the receipt match the evidence files you are checking.
• The receipt can be archived or shared without requiring access to the original production system.

What still needs human judgment

• Whether the evidence collected was complete enough for the risk.
• Whether the operator had proper authority.
• Whether business, legal, or customer obligations require additional artifacts.

Start with Receipts Explained for the receipt anatomy, or contact EdgeRecord for a real record package.