Inventory
Inventory source IDs, revisions, counts, formats and readability with provenance.
MOBILE-ID · TRUSTED LTANS
Legacy Archive Migration
Import legacy archives from checkpoints while distinguishing declared source dates, intake time and actual prior evidence.
Problem and records to preserve
A declared creation date is not cryptographic evidence of that historical time.
SYNTHETIC CASE
Synthetic historical-data migration batch
MIG-SYN-001| Element | Illustrative scope |
|---|---|
| Decision makers / users | Migration architects, repository owners and records administrators |
| Source system | Historical store / legacy DMS |
| Revision | Separate source-declared date from receipt; record actual historical material and gaps. |
| Record relationship | Retain source IDs, old revisions and target mappings; no retroactive trusted dates. |
Sector-specific record journey
Classify evidence
Distinguish existing cryptographic evidence, signatures, timestamps and self-declared metadata.
Hash/reconcile
Hash actual bytes and reconcile counts/attachments; claimed digests are not byte checks.
Batch deposit
Deposit with idempotency/per-item receipts; partial failure does not justify blind full replay.
Verify
Validate old evidence with explicit tools/context; missing material limits historical conclusions.
Accept scope
Accept source/target mappings and scope; a new timestamp does not prove an asserted historical date.
Delivered artifacts
| Recipient | Artifact |
|---|---|
| Source system | Intake receipts, source/revision-to-archiveId/jobId mappings and per-item errors. |
| Package recipient | Per-item receipts, reconciliation totals and outstanding-item list. |
| Record owner / operations | Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion. |
Rights, retention and deployment
Custodians grant reread access; acceptance owners approve migration scope.
Pilot representative records and fully reconcile before retiring source; estimate duration from measurements.
Retention authority and exit
The owner must approve the retention authority and trigger for this record class: A historical archive inventoried and batched by checkpoint.
Sample dossier and tests
Synthetic text files exercise inventory and hashing; they are not signed contracts, real records or ERS/XMLERS.
Download synthetic dossier| Test | Expected outcome |
|---|---|
| Intact | File inventory, size and SHA-256 match the manifest. |
| Missing / changed bytes | The verifier rejects the package without claiming inventory success. |
| Sector business case | Detect missing files or byte changes before retiring the source. |
Scope a PoC for this dossier
Test incomplete, duplicate and interrupted batches; resume from checkpoints and retain distinct ingestion time.
Prepare a sector-specific requestFinalization point and specific acceptance
| Control point | Requirement |
|---|---|
| Source event | A historical archive inventoried and batched by checkpoint. |
| Revision / decision | Separate source-declared date from receipt; record actual historical material and gaps. |
| Test and expected result | Checkpoint resume does not duplicate submissions; new genTime is not relabeled historical creation. |
Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.
Four distinct time concepts
| Time | Interpretation |
|---|---|
| Business date | Source-declared issue/transaction date; retain provenance and authority. |
| Receipt time | Service records receipt; evidence generation may still be pending. |
| genTime | Time in a verified TSA token; check digest binding and source. |
| evaluatedAt | Report evaluation time; read with policy, evidenceVersion and trust context. |
An old source date does not create historical evidence. Retain the source date/provenance; receipt or a new token cannot establish historical attestation.
Source-system handoff record
| Information | Value / decision |
|---|---|
| Record | MIG-SYN-001 |
| Source system | Historical store / legacy DMS |
| Revision relationship | Retain source IDs, old revisions and target mappings; no retroactive trusted dates. |
| Recipient and output | Per-item receipts, reconciliation totals and outstanding-item list. |
| Rights and authority | Custodians grant reread access; acceptance owners approve migration scope. |
| Required rejection test | Detect missing files or byte changes before retiring the source. |
Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.