RS-09 — end-of-life
End-of-life, retention và continuity
Actor → Channel → AuthN → AuthZ → Disclosure → Core/DPP → Evidence → Connector → External Authority.
Not every scenario traverses every optional capability; the path shows the governance checkpoints that must remain explainable.
State changes require more than an event name.
Define what makes this journey auditable.
| Evidence area | Expected record |
|---|---|
| Identity / mandate | Actor/context and mandate evidence where applicable |
| Policy | Decision + policy/profile version |
| Business object | Subject identifier + authority context |
| Transition | Previous/resulting state + preconditions |
| Evidence | Source/provenance + trusted time |
| Integration | Correlation + delivery/reconciliation outcome |
RS-09 — End-of-life / circularity lifecycle closure
This scenario connects a user action to state, authority, policy, evidence and integration boundaries. It is a reference model; legal or regulatory decisions remain with the authoritative party for each data domain.
Failure / retry / reconciliation
Actor not authorised → deny transition; missing mandatory evidence → hold pending; conflicting lifecycle state → resolve through transition policy, never overwrite silently.
Architecture
P03 · P04 · P05
Actor → Experience → Action → Business Object → Authority → Policy → State → Evidence → API/Connector → Architecture → Standard.
Standards / profiles
Applicable circularity/lifecycle DPP profile and evidence/retention requirements.
REFERENCE ARCHITECTURE