REFERENCE SCENARIOREFERENCE

RS-06 — customs-verification

Hải quan xác minh product và DPP

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

ACTUAL PRODUCT UI

Reference UI for this scenario

Regulator / Customs Portal · Regulatory Dashboard Overview

07_REGULATOR_CUSTOMS_PORTAL.zip · TTID--M01-L01-001-Regulatory_Dashboard_Overview_final.png

REFERENCE SCENARIO · IMPLEMENTATION-GRADE

RS-06 — Customs verifies product, declaration and DPP status

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 / systemsCustoms Officer; Regulator/Customs Portal; declarant/Economic Operator; external Customs and DPP Registry systems.

PreconditionsCustoms authority session/mandate is valid; declaration/product identifier is available; external sources are reachable or freshness is known.

TriggerA customs officer opens a shipment/product verification task.

End-to-end flowMatch declaration to product identifier → resolve aliases → authenticate/authorise customs purpose → compose restricted authority view → verify registration/DPP status → compare declaration and governed product facts → inspect provenance/evidence → record decision support and authoritative hold/release reference.

State modelVerification Case Open → Checked → Decision Recorded/Closed. Customs hold/release remains an authoritative external action, not a local TTID state pretending to be customs.

Authority boundaryCustoms and relevant registries remain authoritative. Trusted ThingID resolves, composes, correlates and records evidence.

Policy / disclosureCustoms officer identity, legal mandate, purpose, case context, assurance and restricted-field disclosure.

EvidenceResolution/correlation trace, source freshness, viewed facts, discrepancy record, external response/receipt, policy decision and audit.

API / event / connectorResolver; DPP/status read; search; evidence; Customs/Registry connectors; reconciliation events.

Failure / retry / reconciliation

Registry timeout → show unavailable/freshness state; declaration mismatch → surface discrepancy; unknown external result → reconcile; never infer hold/release locally.

Architecture

P02 · P03 · P04 · P06

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

Standards / profiles

DPP identifier/registry profiles; Customs integration contracts; evidence/audit and API profiles.

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.