REFERENCE SCENARIO · IMPLEMENTATION-GRADERS-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.
Actors / systemsOwner/custodian; recycler/circularity operator; Field Operations; Economic Operator; lifecycle/evidence services.PreconditionsThing is resolvable and circularity/recycler actor has the required role/credential/mandate for the intended lifecycle action.TriggerA product is returned, dismantled, recovered, recycled or otherwise reaches a governed end-of-life action.
End-to-end flowResolve → verify actor and lifecycle eligibility → capture disposition/material outcome → attach evidence → transition lifecycle → update DPP/circularity view → retain records according to retention policy.State modelActive/In Service → End-of-life Pending → Recycled/Recovered/Closed as defined by product profile. Relationship claims may close separately.Authority boundaryRecycler/circularity actor can attest authorised lifecycle facts; regulatory/official product data keeps its original authority.
Policy / disclosureActor entitlement, product profile, hazardous-material rules, evidence requirements, lifecycle transition grammar and retention.EvidenceDisposition evidence, material/recovery record, actor credential reference, lifecycle transition receipt, timestamp and audit.API / event / connectorLifecycle API; evidence API; circularity/field operations connector; lifecycle events.
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
Product UI statusUI/UX BASELINE — *_final.png is embedded only when the approved source binary and provenance are available; no screenshot is fabricated to fill a missing source.