REFERENCE SCENARIOREFERENCE

RS-05 — recall-surveillance

Giám sát thị trường / recall

END-TO-END PATH

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.

Thing / Product

Official Identifier

Trusted ThingIDResolver · Alias · Assurance

DPP

Claims · Policy · Evidence

External ecosystem

MATERIAL TRANSITION

State changes require more than an event name.

Event

Authorized actor

Precondition

Evidence

Trusted time

Policy / profile version

Resulting state

ACCEPTANCE EVIDENCE

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

REFERENCE SCENARIO · IMPLEMENTATION-GRADE

RS-05 — Recall and market-surveillance verification

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 / systemsMarket Surveillance Authority / Regulator; Economic Operator; Regulator Portal; external recall/regulatory sources.

PreconditionsAuthority identity/mandate is valid; product is resolvable; relevant recall/restriction sources can be queried.

TriggerAn authority inspects a product, receives an alert or opens a case.

End-to-end flowResolve product → authenticate authority → compose authority view → verify DPP/registration/recall status → inspect evidence/provenance → record inspection → flag/restrict through authoritative process if permitted → reconcile result.

State modelInspection Open → Decision Pending → Closed; recall/restriction status changes only through the authoritative domain/process.

Authority boundaryThe regulator/market-surveillance system remains authoritative for regulatory actions. Trusted ThingID supports verification, evidence and orchestration.

Policy / disclosureAuthority role, legal mandate, case purpose, field-level disclosure and action entitlement.

EvidenceInspection evidence, viewed-source references, policy decision, authority action receipt, status reconciliation and audit chain.

API / event / connectorResolver/DPP/status reads; evidence API; regulator connector; status/reconciliation events.

Failure / retry / reconciliation

External authority unavailable → do not fabricate status; stale status → mark freshness; denied authority action → preserve error/receipt and keep local case state distinct.

Architecture

P02 · P03 · P04 · P06

Actor → Experience → Action → Business Object → Authority → Policy → State → Evidence → API/Connector → Architecture → Standard.

Standards / profiles

Applicable DPP/regulatory status profiles; authority-specific integrations and evidence contracts.

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.