Close file
The file owner closes the case inventory and identifies originals/copies under the applicable process.
MOBILE-ID · TRUSTED LTANS
Government & Public Records
Inventory public-sector case files and acknowledge repository handover with checkable packages and controlled access classification.
Problem and records to preserve
System changes must retain classification, file structure and intake history.
SYNTHETIC CASE
Synthetic administrative case file
GOV-SYN-001| Element | Illustrative scope |
|---|---|
| Decision makers / users | Registry, archives, system owners and information-security teams |
| Source system | Case-record system |
| Revision | Retain access classification, approver and relationships; recipient reconciles inventory. |
| Record relationship | Corrections retain case linkage and new intake authority. |
Sector-specific record journey
Check components
Check components, access classification and attachments; identify omissions without false completeness.
Acknowledge
Retain per-record receipts, source IDs and jobs; reconcile mixed-result batches item by item.
Preserve
Apply owner-defined retention authority; retain corrections and holds.
Handover
Prepare manifested transfer packages and recipient acknowledgements; export does not delete the source.
Delivered artifacts
| Recipient | Artifact |
|---|---|
| Source system | Intake receipts, source/revision-to-archiveId/jobId mappings and per-item errors. |
| Package recipient | Transfer package with inventory, per-item results and recipient acknowledgement. |
| Record owner / operations | Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion. |
Rights, retention and deployment
The owner defines classification, retention and authorized users.
Retention and data location follow procurement scope and applicable authority; this site does not prescribe legal periods.
Retention authority and exit
The owner must approve the retention authority and trigger for this record class: A finalized case file entered into a transfer inventory.
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 | Mixed-result batches retain per-item outcomes and unresolved transfers. |
Scope a PoC for this dossier
Reconcile inventory, counts and structure; test incomplete transfers and recovery.
Prepare a sector-specific requestFinalization point and specific acceptance
| Control point | Requirement |
|---|---|
| Source event | A finalized case file entered into a transfer inventory. |
| Revision / decision | Retain access classification, approver and relationships; recipient reconciles inventory. |
| Test and expected result | Metadata lookup does not grant restricted content access; missing records prevent complete acknowledgement. |
Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.
Source-system handoff record
| Information | Value / decision |
|---|---|
| Record | GOV-SYN-001 |
| Source system | Case-record system |
| Revision relationship | Corrections retain case linkage and new intake authority. |
| Recipient and output | Transfer package with inventory, per-item results and recipient acknowledgement. |
| Rights and authority | The owner defines classification, retention and authorized users. |
| Required rejection test | Mixed-result batches retain per-item outcomes and unresolved transfers. |
Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.