Sample package export and verification
Check synthetic-package hashes before delivery; distinguish byte integrity from authenticity, signatures and legal status.
Download and verify locally
python3 verify_export.py synthetic-export/manifest.jsonNo network requests. Alter a byte in content.txt to exercise MISMATCH; results do not assess signatures or legal status.
Package contents
The sample includes content.txt, metadata.json, manifest.json, lineage and a local Python verifier. The manifest records byte lengths and SHA-256 hashes; no signatures or LTANS receipts are included. The verifier checks missing files, traversal, lengths and hashes. MATCH establishes byte agreement with the sample manifest, not manifest-author authenticity.
Before a real handover
Agree recipients, formats, originals/derivatives, metadata, evidence bindings, independent verification and retained-copy inventories. Check retention/holds before deletion and treat backups under approved procedures. Downloading the sample ZIP is not a customer-record handover.
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