Choose preservation configurations by record class, designated community and required evidence. Illustrative profiles are not approved service offerings.
synthetic-preservation-001Source images by side/attempt, metadata and manifest; dissemination derivatives retain lineage. The designated community comprises records managers and authorized consumers.
QC/reconciliation, acceptance receipts, baseline fixity and retention/hold decisions.
synthetic-signed-evidence-001Retain signed-object bytes and profile-specific validation material; converted PDF/A is a separate object. LTANS handles evidence only under a verified provider model.
Initial validation, signature coverage, evidence bindings and verification results.
synthetic-born-digital-001Manifest/hashes, metadata schemas, access context and representation information; Flow R is bypassed.
Validation/quarantine, declaration authority, versions, format checks and verifiable exports.
| Scope | Decisions and conditions |
|---|---|
| Owner / designated community | Managers, authorized users and the knowledge needed to interpret objects |
| Format / validator | Format/profile allowlists and tool versions; errors need a plan |
| Retention / holds | Triggers, periods and authority; no default schedule imposed |
| Fixity / replicas / DR | Configuration-specific cadences, locations, recovery and rehearsals |
| LTANS / TSA / validation | Storage model, provider/profile, input validation, receipts and evidence binding |
| Exit / acceptance | Independent retrieval/export, manifests/lineage, retained data and recipient authority |
Each profile requires an owner, purpose, source/preservation/dissemination copies, format/validator versions, metadata, provenance, retention triggers/holds, fixity, replicas/recovery and format risks. Contracts or authorized decisions define cadences, periods, locations and SLAs; there is no universal default.
Migration creates a new object/version with derived-from links, tool versions and QC results. PDF/A addresses format rather than provenance. Original-byte signatures do not automatically cover converted objects; retain originals and validation results.
Require versioned manifests, hash checks, authority/custody evidence, representation information and retrieval/export tests. LTANS additionally needs agreed provider/profile/receipt/evidence bindings and verification. Draft profiles may be exercised with synthetic data without becoming retention commitments.
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsExercise ingest → job tracking → registration → verification with synthetic data.
Read detailsEach evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsAgree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment