Receipts Explained

A receipt in EdgeRecord is a compact record that captures what changed, who or what performed the action, what evidence was attached, and how the record can be checked later.

What a receipt is for

• Preserving the baseline before an operational change.
• Keeping approval, actor, timeline, and verification evidence together.
• Giving a third party enough context to understand the record without reading raw chat logs or production systems.
• Letting a customer archive the proof in plain text or JSON.

Redacted sample receipt

{
  "record_id": "ER-SAMPLE-20260614-001",
  "record_type": "change_evidence_sprint",
  "environment": "customer-edge-dns-redacted",
  "change_summary": "DNS provider failover validation and rollback proof",
  "actor": {
    "type": "operator",
    "display": "redacted-ops-lead"
  },
  "approval": {
    "source": "customer change ticket",
    "reference": "CHG-REDACTED-1842"
  },
  "timeline": [
    {"at": "2026-06-14T16:10:00Z", "event": "baseline captured"},
    {"at": "2026-06-14T16:24:00Z", "event": "change window opened"},
    {"at": "2026-06-14T16:42:00Z", "event": "verification checks passed"}
  ],
  "evidence": [
    {"kind": "dns_snapshot", "sha256": "9c6f...d2aa"},
    {"kind": "operator_note", "sha256": "72ab...19e1"},
    {"kind": "rollback_check", "sha256": "f913...2c77"}
  ],
  "previous_record_hash": "0000000000000000000000000000000000000000000000000000000000000000",
  "record_hash": "7f2c2f8e3a7a3a9e6b0c43f7a5c9c1d5e5d6a84c9f0e7d1b1a0a0e7c9a1b2c3d",
  "status": "verified_sample"
}

Before, during, after

1. Before: capture baseline state, declared scope, approval source, expected rollback path, and known risks.
2. During: record actor, command or system action, timestamp, and any unexpected variance.
3. After: attach verification checks, compare to baseline, note remaining risk, and package the handoff record.

What the receipt does not claim

A receipt proves what was recorded and how it was sealed. It does not magically prove that every underlying business statement was true. Good receipts pair cryptographic structure with careful evidence collection.

Next: verify a record or request a scoped Change Evidence Sprint.