Example
An archive snapshot captures every Print Prep Lab local-storage signal at one point in time and stores the JSON payload inside the archive record. Later edits create a new state rather than modifying the historical snapshot.
v93–v94 · ENTERPRISE PLATFORM
Snapshot completed job state with a content hash.
Create immutable-style local archive records that preserve the exact JSON state and SHA-256 when Web Crypto is available.
Interactive module
Production Archive
The snapshot contains local technical state, never source image bytes.
Practical workflow
Freeze the state that supported a decision
Interpretation
When Web Crypto is available, the module computes SHA-256 over the serialized snapshot. Matching hashes indicate identical serialized content; different hashes prove the payload changed, but neither result identifies the person who made or approved the change.
Boundary
Keep original production files in the project’s file archive as well. Print Prep Lab snapshots intentionally exclude image and PDF bytes, so the technical state and the actual deliverables should be retained together by the production workflow.
Why this module exists
Production context around the calculation.
An archive is a snapshot
Saving an archive record freezes the JSON state at that moment; later local edits do not alter the saved snapshot.
Hashing detects content change
SHA-256 can show that two archived JSON payloads differ, but it does not prove who approved them.
Keep external files too
The archive stores technical state, not the original image or production PDF bytes.