MOBILE-ID · TRUSTED LTANS

Policy Governance

Versioned policy configuration, effective conditions and record-level history.

Outcome and scope

Keep preservation decisions consistent by revision and scope without silently changing record history.

Documentation scope Workflow design and integration contract; operational configuration is confirmed per environment.

Prepare	Receive
Versioned period rules, algorithms, TSA selection, end-of-period handling, principal rights and storage configuration.	Applicable policy snapshot per object and change history without overwriting prior versions.

Participants: Policy owners, approvers and tenant administrators.

Separate format, algorithms, TSA sources, retention and permissions, with accountable ownership.

Review effects on new and existing records. Resolve conflicts using an approved precedence policy.

Separate authoring/approval and record scope/effective time. A REVIEW website document is not an active configuration.

Records retain applied revisions; rollback creates a new decision instead of erasing history.

Current	Guard	Actor	Next	Artifact / recovery
DRAFT	Accountable ownership and impact scope documented	Policy owner	REVIEW	Retain diff and impacted-object scope.
REVIEW	Independent approver accepts	Approver	APPROVED	Not automatically effective; time/environment conditions remain.
APPROVED	Approved activation conditions met	Configuration administrator	EFFECTIVE / SUPERSEDED	Objects retain applied revision; rollback is a new decision.

Situation	Action	Boundary
Conflicting policies	Block unresolved decisions or apply approved precedence.	Do not automatically choose the least restrictive option.
Retroactive change	Require explicit scope and approval.	Retain before/after history.
No policy-write API	Describe the target administrative workflow.	Publish only interfaces present in the current contract.

Authorization, approval and recovery

Apply only EFFECTIVE policies with a release record. Separate internal approval from public publication; never auto-promote status.

Return an explicit error for unsupported policyId. Restore an approved configuration; existing objects retain historical policy references.

Retain intake-time policy snapshots, revision history and decisions activating the profile.

Existing records still identify their applied revision after a new profile activates.
Authors cannot self-approve when the profile requires separation of duties.

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
POST /v1/archives/{`archiveId`}/holds	holds:write	Policy and Profile API

Technical input and references

Element	Definition
Input	Versioned period rules, algorithms, TSA selection, end-of-period handling, principal rights and storage configuration.
Output	Applicable policy snapshot per object and change history without overwriting prior versions.

LTANS profile details · Target interface illustration.