Define object set
Retain document, detached-signature and attachment relations. For groups, identify all members before building the hash tree.
MOBILE-ID · TRUSTED LTANS
Evidence Service
Bind data to hash trees, timestamps and preservation history using the selected ERS or XMLERS model.
Outcome and scope
Bind a frozen object or file group to timestamps and re-verifiable evidence history.
Documentation scope Workflow design and integration contract; operational configuration is confirmed per environment.
| Prepare | Receive |
|---|---|
| Individual files or structured data groups; documents and detached signatures need explicit relationships. | A versioned evidence record retrievable with its supporting validation material. |
Participants: Preservation applications, policy owners and TSA adapters.
Workflow and decision points
Apply syntax
Select an ERS or XMLERS processing profile. Canonicalization and encoding parameters belong to that profile; these formats are not interchangeable wrappers.
Validate timestamp
Check MessageImprint, algorithm, nonce when used, policy OID, TSA certificate and genTime against the selected trust inputs.
Publish revision
Publish only after digest binding and token validation; retain prior revisions, chains and validation material.
States, guards and authority
| Current | Guard | Actor | Next | Artifact / recovery |
|---|---|---|---|---|
| Awaiting generation [model] | Pin member set, syntax and policy revision | Evidence Service | Generating [model] | Retain input inventory; missing members require source reconciliation. |
| Generating [model] | Token binds the imprint and approved TSA | Evidence + Trust Adapter | Awaiting publication [model] | Retain token, tree path and context; timeout cannot publish success. |
| Awaiting publication [model] | Complete validation and revision persistence | Evidence Service | Published [model] | Prior revisions remain immutable; failed storage must not emit EvidenceGenerated. |
Exceptions and controls
| Situation | Action | Boundary |
|---|---|---|
| Attachment missing | Block a complete-set conclusion. | Retain inventory findings for source repair. |
| Signed token has wrong imprint | Reject the token for this object. | Token signature alone does not establish data binding. |
| Use fallback TSA | Use only approved TSA/policy combinations. | Retain the actual token origin and checks. |
Authorization, approval and recovery
Check MessageImprint, nonce when used, TSA policy, certificate path and genTime. Preserve algorithm parameters; client time is not trusted time.
Quarantine a digest mismatch or untrusted token. Retry with a policy-approved TSA; publish a new version only after successful verification.
Reconciliation artifacts and acceptance
Record syntax, algorithms, TSA token reference, evidence version and predecessor links; check immutability on release.
- Changing group membership or token must produce the corresponding validation failure, not retain an old success.
- Revision retrieval must identify syntax, context and required validation components; illustrative JSON must not be called valid ERS.
Integration and data contract
| API | Application scope | Documentation |
|---|---|---|
GET /v1/archives/{archiveId}/evidence | evidence:read | Evidence API |
GET /v1/archives/{archiveId}/evidence/{evidenceVersion} | evidence:read | Evidence API |
Technical input and references
| Element | Definition |
|---|---|
| Input | Data or object-group digests, ERS/XMLERS selection, policy references and a validated TSA response. |
| Output | Immutable evidence version, reduced hash tree, timestamp chains and validation material for the selected syntax. |
Execute and reconcile a scenario
| Element | Action |
|---|---|
| Synthetic ID | arc-test-001 / evidenceVersion 1 |
| Task | Freeze members/syntax before generation; verify imprint before publication. |
| Acceptance case | Changed members or mismatched tokens block publication; retain prior revision. |
These are business test criteria; synthetic packages alone do not establish backend execution or valid ERS.