PLATFORM MODULEREFERENCE ARCHITECTURE

Identifier Governance

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

Review module scope Related architecture

P03Architecture

REFERENCE ARCHITECTUREMaturity

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

Namespace policy, persistence, collision control, key reuse constraints and supersession records.
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

Platform Operator · Identifier governance owner · External identifier authority · Developer

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.

Identifier Governance object mapping
ID	Object	Authority	Repository role	API	Architecture
OBJ-001	Thing	Domain-qualified	Thing Master	Resolver API	P01/P03
OBJ-002	Product	Economic operator / applicable authority	Thing Master	DPP API	P03/P04
OBJ-003	Model	Official identifier domain	Thing Master	Resolver API	P03
OBJ-004	Batch	Official identifier domain	Thing Master	Resolver API	P03
OBJ-005	Item	Official identifier domain	Thing Master	Resolver API	P03/P04
OBJ-006	Official Identifier	External / scheme authority	External source + alias map	Resolver API	P01/P03

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/...
POST /v1/...
event.*

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
Reference	Status	OJEU	Impact	Implementation
EU 2024/1781	IN FORCE	N/A	DPP regulatory profile; lifecycle; authority boundaries	TRACKED
EU 2026/1736	IN FORCE	OJEU PUBLISHED	Standards status and public wording	TRACKED
EN 18216:2026	HARMONISED	OJEU CITED	Integration protocol mapping	MAPPED
EN 18219:2026	HARMONISED	OJEU CITED	Identifier governance / resolver	MAPPED
EN 18220:2026	HARMONISED	OJEU CITED	QR/NFC/data-carrier experience	MAPPED

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

DPP Regulatory Engine

PILOT READY

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

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.

Resolve authoritative identifiers, correlate governed aliases and maintain stable item/model/batch context without redefining the official identifier.

INPUTIdentifier / policy / evidence / source status

OUTPUTSource-aware, policy-qualified result with evidence context

AUTHORITYQualified by data domain; external authority remains external

API / EVENTResolver API

EVIDENCEResolution decision · alias provenance · authority context

MATURITYReference implementation

Open Product Ecosystem View 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 workshop Explore architecture