Bind basis
Retain policyId, applied revision, period type and start-event source; the website prescribes no sector-specific years.
MOBILE-ID · TRUSTED LTANS
Archival Period & Retention
Apply date- or event-based periods, retaining change history and checking holds before end-of-period actions.
Outcome and scope
Calculate review dates and eligibility under retention profiles while preserving reasons for period changes.
Documentation scope Workflow design and integration contract; operational configuration is confirmed per environment.
| Prepare | Receive |
|---|---|
| Records with a defined end date or a period triggered by a verified business event. | A review queue and disposition-eligibility decision; expiry alone does not mean deletion. |
Participants: Record owners, policy administrators and retention approvers.
Workflow and decision points
Calculate schedule
Event-based periods await a verified trigger. Time zone and end-date rules belong to the approved configuration.
Review changes
Extension or shortening needs authority, reasons and impact review; never silently apply a new policy retroactively.
Assess eligibility
Expiry only opens review. Active holds, storage locks and handover obligations continue to block effects.
States, guards and authority
| Current | Guard | Actor | Next | Artifact / recovery |
|---|---|---|---|---|
| Awaiting trigger [model] | Source attests the start trigger | Record owner + Policy | Scheduled [model] | Keep basis, time, zone and calculation; absent triggers remain pending. |
| Scheduled [model] | Review time reached; inspect all holds | Policy Service | Review eligible / blocked [model] | This is not a deletion command; retain reason and policy revision. |
| Scheduled [model] | Approved basis change with frozen scope | Retention approver | Rescheduled [model] | Retain before/after schedules; no silent global retroactivity. |
Exceptions and controls
| Situation | Action | Boundary |
|---|---|---|
| Unverified start event | Await source reconciliation. | Do not infer the start from ingestion time. |
| Policy revision changes | Review scope and approval. | Retain the applied policy snapshot. |
| Expired but held | Retain under the hold. | No automatic deletion command. |
Authorization, approval and recovery
Only retention:manage may alter the period; preserve reason and policy version. Always evaluate holds before deletion.
An unverified trigger keeps evaluation pending. Correct the event source, recalculate the period and audit the change.
Reconciliation artifacts and acceptance
Retain record-class basis, trigger event, recalculation date, approver and rule revision; reconcile untriggered records.
- Changing the trigger produces a recalculated schedule and change trail while retaining the earlier calculation.
- An expired held record remains ineligible for disposition.
Integration and data contract
| API | Application scope | Documentation |
|---|---|---|
| GET /v1/profiles | policies:read | Policy and Profile API |
GET /v1/profiles/{profileId} | policies:read | Policy and Profile API |
GET /v1/policies/{policyId} | policies:read | Policy and Profile API |
Technical input and references
| Element | Definition |
|---|---|
| Input | Time-based or event-based period, start date, object group and approved extension/shortening rules. |
| Output | Next evaluation date and disposition eligibility; expiration does not automatically delete data. |
Execute and reconcile a scenario
| Element | Action |
|---|---|
| Synthetic ID | policy-test-v1 |
| Task | Bind record class, trigger and policyVersion; recalculate only under approval. |
| Acceptance case | Missing trigger enters review; never silently replace it with upload date. |
These are business test criteria; synthetic packages alone do not establish backend execution or valid ERS.