Skip to content
C.W.K.
Stream
Lesson 04 of 04 · published

Freeze Proves What You Saw

~12 min · hashes, evidence, review, integrity

Level 0Cold Vessel
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

Freeze Proves What You Saw

A frozen package is valuable because later readers can compare evidence against the same premises. The brief identifies the instructions; the manifest identifies attachments; content digests identify the exact bytes. Together they answer the review question that memory cannot: what did the executor actually receive?

A hash is narrow evidence. It proves equality of bytes when recomputed under the same algorithm. It does not prove the attachment was correct, safe, or authorized. Those are separate checks. Overclaiming a digest turns a useful instrument into security theater.

The freeze also protects the author. If a source packet is corrected after take, the original session should not be blamed for failing to use information it never had. A superseding delegation can carry the corrected bytes while the first record remains an honest account.

Review tools should display both human names and digests. Names make the package understandable; digests make substitution detectable. The landing record can cite the frozen package identity without copying private content into a public or long-lived log.

Recompute at Review

When a reviewer opens an attachment, recompute its digest and compare it to the frozen manifest before judging content. A mismatch is a package-integrity blocker, not a content finding.

Then preserve the distinction in reporting: “bytes match the frozen package” and “the document satisfies the task” are two claims with two instruments. Passing the first is necessary for fair review and insufficient for acceptance.

A freeze records the evidence boundary, not merely a timestamp. The stored brief, attachment identities, and pipeline version define what the executor could actually observe at claim time. Later provenance is credible because it can distinguish that snapshot from subsequent edits.

Code

Verify package identity before content review·python
from hashlib import sha256

def digest(data: bytes) -> str:
    return sha256(data).hexdigest()

frozen = b"scope,proof\nrepair,served-check\n"
stamped = digest(frozen)
received = b"scope,proof\nrepair,served-check\n"
assert digest(received) == stamped
print("package identity verified; content review may begin")

External links

Exercise

Write a review checklist that separates package identity, malware/safety checks, factual correctness, and task acceptance into four distinct claims.
Hint
Only the first claim is answered by a content digest.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.