Evidence and preservation
Manifests identify contents; hashes test bytes; provenance establishes origin; QC assesses criteria; approvals record decisions; signatures/timestamps apply under agreed services. Preservation packages retain required components and version histories.
Content, adapter and evidence boundaries
Boundaries to preserve
Manifests identify contents; hashes test bytes; provenance establishes origin; QC assesses criteria; approvals record decisions; signatures/timestamps apply under agreed services. Preservation packages retain required components and version histories.
Pre-deployment checks
Cross-check configuration, permissions, sample data, exceptions and approvers. Keep version-bound test records; architecture describes design rather than proving every control is implemented.
Content and evidence preservation
Choose a profile before admission. Separate content storage, readability, LTANS evidence and backup/DR. Mobile-ID connectivity is based on published capability; storage models, APIs, receipts and deployment authority require agreement. Hash/fixity checks do not replace signature or provenance validation.
Continue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment