REFERENCE SCENARIOREFERENCE

RS-01 — manufacturer-publishes-dpp

Nhà sản xuất tạo và công bố 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

Economic Operator Portal · Dashboard Overview

03_ECONOMIC_OPERATOR_PORTAL.zip · TTID--M01-L01-001-Dashboard_Overview_final.png

REFERENCE SCENARIO · IMPLEMENTATION-GRADE

RS-01 — Manufacturer creates and publishes a DPP

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 / systemsManufacturer / Economic Operator; Trusted ThingID DPP services; external DPP Registry where applicable

PreconditionsEconomic Operator onboarding is valid; product identity and applicable product-group profile are resolved; required evidence sources are available.

TriggerAn authorised Economic Operator starts or resumes DPP authoring for a product/model/batch/instance according to the applicable profile.

End-to-end flowResolve product identity → author governed fields → validate profile/schema and evidence → approve under mandate → submit/register through connector → reconcile external result → publish composed DPP view.

State modelDraft → Validated → Approved → Registration Pending → Registered/Reconciled → Published. External registration remains an external-authority state.

Authority boundaryOfficial identifiers and external registry status remain authoritative in their domains; Trusted ThingID orchestrates, composes and evidences the workflow.

Policy / disclosureEconomic Operator role + representative mandate + applicable product-group profile + field-level publication/disclosure policy.

EvidenceAuthoring/validation evidence, approval evidence, submission receipt, connector reconciliation record, publication evidence and immutable audit references.

API / event / connectorDPP API; Evidence API; lifecycle transition API; connector submission/reconciliation; DPP lifecycle events.

Failure / retry / reconciliation

Validation failure → correct draft; registry timeout → retry idempotently; accepted-but-unknown outcome → reconcile; authority rejection → preserve rejection evidence and return to governed correction state.

Architecture

P02 · P03 · P04 · P06

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

Standards / profiles

DPP identifiers/profiles; GS1 Digital Link where applicable; OpenAPI/AsyncAPI integration contracts; applicable EN DPP references.

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.