Close case
The notarial system freezes inventory and authorized depositor.
MOBILE-ID · TRUSTED LTANS
Notarial and legal records
Package instruments, attachments and supporting documents by case ID with authorized retrieval and holds.
Problem and records to preserve
Transactions need links to source documents, participants and the exact versions used.
SYNTHETIC CASE
Synthetic notarial transaction
NOTARY-SYN-001| Element | Illustrative scope |
|---|---|
| Decision makers / users | Notarial practices, legal teams and legal-software providers |
| Source system | Notarial case management |
| Revision | Supplements retain identity, relationships and reason; export stays within authorized scope. |
| Record relationship | A supplemental annex links to the original without replacing signed bytes. |
Sector-specific record journey
Bind components
Retain instruments, attachments and detached signatures with source relationships.
Apply hold
Bind the case and record scope to the authorized decision.
Export on authority
Export only authorized scope; the recipient reconciles the package.
Delivered artifacts
| Recipient | Artifact |
|---|---|
| Source system | Intake receipts, source/revision-to-archiveId/jobId mappings and per-item errors. |
| Package recipient | Case-scoped package with signed/annex inventory, manifest and reconciliation results. |
| Record owner / operations | Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion. |
Rights, retention and deployment
Legal approves export scope; operators cannot release holds themselves.
LTANS supports technical evidence; it does not replace notarial practice or determine legal effect.
Retention authority and exit
The owner must approve the retention authority and trigger for this record class: Case identifier and authorized finalized document/annex set.
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 | Create two holds; releasing one must still block disposition. |
Scope a PoC for this dossier
Reconcile detached signatures, attachments and inventory; test held records and unauthorized exports.
Prepare a sector-specific requestFinalization point and specific acceptance
| Control point | Requirement |
|---|---|
| Source event | Case identifier and authorized finalized document/annex set. |
| Revision / decision | Supplements retain identity, relationships and reason; export stays within authorized scope. |
| Test and expected result | Two concurrent holds; releasing one still blocks disposition. |
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 | NOTARY-SYN-001 |
| Source system | Notarial case management |
| Revision relationship | A supplemental annex links to the original without replacing signed bytes. |
| Recipient and output | Case-scoped package with signed/annex inventory, manifest and reconciliation results. |
| Rights and authority | Legal approves export scope; operators cannot release holds themselves. |
| Required rejection test | Create two holds; releasing one must still block disposition. |
Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.