This public sample shows what a Change Evidence Sprint handoff looks like. It is synthetic and redacted, not proof of a real customer change.

Sample receipt

{
  "record_id": "ER-SAMPLE-20260618-001",
  "record_type": "change_evidence_sprint",
  "environment": "customer-edge-dns-redacted",
  "change_summary": "DNS provider failover validation and rollback proof",
  "approval": {"source": "customer change ticket", "reference": "CHG-REDACTED-1842"},
  "record_hash": "3b7a4c0f90d20d934f1a732ba01d7a6139f9cfed16768f5a7bc1018df2d442e1",
  "status": "verified_sample"
}

What the package includes

  • Human-readable evidence summary.
  • Machine-readable receipt JSON.
  • Evidence inventory with placeholder hashes.
  • Verification checklist for future review.
  • Remaining-risk notes for follow-up.

Review checklist

  1. Confirm the record id, environment label, and change summary match the expected handoff.
  2. Confirm approval and scope are present.
  3. Recompute each evidence artifact hash in a real package.
  4. Review the timeline for unexplained gaps.
  5. Confirm the human summary does not claim more than the evidence supports.

Request a real Change Evidence Sprint.