PLATFORM MODULEPILOT READY

DPP Regulatory Engine

Apply versioned product-group profiles, authoring controls and registry orchestration while keeping external legal authorities authoritative.

Review module scopeRelated architecture
P04Architecture
PILOT READYMaturity
Domain-qualifiedAuthority
SCOPE

What the module does—and what it deliberately does not do.

A clear negative boundary is part of the product definition.

DOES
  • Applicability, profile versioning, authoring, validation, publication, registration, update, recall and continuity.
  • Publishes explicit domain objects and version-aware interfaces/events.
  • Links business outcomes to evidence and architecture references.
DOES NOT
  • Does not replace external legal/identifier authorities.
  • Does not imply universal certification or conformity.
  • Does not make optional assurance mechanisms mandatory for all products.
OPERATING MODEL

Actors, inputs, outputs and authority remain explicit.

The module is not treated as a black box; its authority and evidence responsibilities are visible.

Actors

Economic Operator · Regulator · Customs · EU DPP Registry / authority

Inputs

Identity/context, versioned business data, policy inputs and external-source references as applicable.

Outputs

Versioned decision/data/evidence artifacts with correlation and provenance.

Authority boundary

Qualified by data domain; external authority is not absorbed through integration.

BUSINESS OBJECTS

Semantic objects connect UI, API, repository and evidence.

The semantic registry prevents architecture vocabulary from drifting between portals and integration contracts.

DPP Regulatory Engine object mapping
IDObjectAuthorityRepository roleAPIArchitecture
OBJ-002ProductEconomic operator / applicable authorityThing MasterDPP APIP03/P04
OBJ-009DPPEconomic operator + external legal contextDPP RepositoryDPP APIP04
OBJ-010Regulatory ProfileApplicable law/profile governanceProfile repositoryProfile APIP04
OBJ-014OwnershipClaim/source/legal contextClaim StoreClaims APIP03
POLICY & EVIDENCE

Material actions are policy-versioned and evidence-linked.

Where the module changes a material state, the transition grammar applies.

Event
+
Authorized actor
+
Precondition
+
Evidence
+
Trusted time
+
Policy / profile version
=
Resulting state
INTERFACES & EVENTS

Reference contracts are versioned and publication-gated.

The public API package is a reference contract; actual deployment availability must be confirmed by release/environment.

GET /v1/dpp/{identifier}
POST /v1/dpp
POST /v1/dpp/{id}/transitions
RELEASE GATE
SELECTINTEGRATETESTAPPROVEOPERATE

Publish support only for the exact version/profile/environment that has supporting evidence.

STANDARDS & LIMITATIONS

Mapping is not certification.

Standards are shown with status and implementation wording so reference mapping is not mistaken for assessed conformity.

Relevant standards
ReferenceStatusOJEUImpactImplementation
EU 2024/1781IN FORCEN/ADPP regulatory profile; lifecycle; authority boundariesTRACKED
EN 18222:2026HARMONISEDOJEU CITEDDPP APIs / search / lifecycleMAPPED
RELATED MODULES

Compose capabilities without collapsing responsibilities.

Related modules are linked explicitly rather than hidden behind one monolithic platform claim.

Thing Identity & Resolver

REFERENCE IMPLEMENTATION

Resolve official identifiers, correlate aliases and extend assurance without redefining the authoritative product identifier.

Explore

Identifier Governance

REFERENCE ARCHITECTURE

Govern namespace uniqueness, persistence, collision detection, supersession and the rule that identifiers are never silently reused.

Explore

Claims & Credentials

REFERENCE IMPLEMENTATION

Represent roles, responsibilities and verifiable assertions as source-aware, evidence-backed records with lifecycle and dispute handling.

Explore
PRODUCT COMPLETENESS

From module to business outcome.

Apply versioned product-group profiles to authoring, validation, publication, registration orchestration and lifecycle maintenance.

INPUTIdentifier / policy / evidence / source status
OUTPUTSource-aware, policy-qualified result with evidence context
AUTHORITYQualified by data domain; external authority remains external
API / EVENTDPP API · lifecycle API
EVIDENCEValidation · publication · registry status · lifecycle evidence
MATURITYPilot ready
Open Product EcosystemView Readiness
ARCHITECTURE WORKSHOP

Turn the architecture into a scoped pilot.

Align product-group applicability, authority boundaries, portal journeys, integration contracts and evidence before committing to production claims.

Request a workshopExplore architecture