Offline verification checks the integrity of published files against their declared inventory. It does not expand the evidence set or validate the underlying decision.
Outcome, not repository
Problem and intended result
- 01
Customer problem
Reviewers need a durable record and a way to detect whether published files differ from their manifest.
- 02
Intended outcome
The decision loop ends at an inspectable dossier and an independent checksum-verification boundary.
- 03
The system boundaries involved
Evidence boundary
Expected evidence and explicit limits
Evidence produced
- Dossier inventory and linked evidence
- Manifest and checksum comparison
Limitations
- Checksum matching does not prove a decision correct, complete, or legally compliant.
- Pending mode publishes no factual bundle or successful verification result.
Integration posture
Prerequisites
- Complete publication-approved bundle
- Matching manifest, checksums, and approval record