PRODUCT PROFILEGOVERNED REFERENCE

Registry & External Connector

Operate versioned connector contracts with retry, reconciliation, status mapping, evidence and explicit authority boundaries.

RELEASE2026.09

STATUSEXTERNAL DEPENDENCY

AUDIENCEIntegration Engineer · Operations Administrator · DPP Operations

SOURCE OF TRUTHProduct profile + architecture/evidence registers

PRODUCT FACTS

Operate versioned connector contracts with retry, reconciliation, status mapping, evidence and explicit authority boundaries.

External registries and authorities have their own availability, contract, status and authority semantics that must not be hidden behind a simple API success response.

Family: Integration & Operations
Maturity: EXTERNAL DEPENDENCY
Primary personas: Integration Engineer · Operations Administrator · DPP Operations
Business objects: Connector Contract · External Interaction · Reconciliation Case
Architecture: P06
Standards: OpenAPI/AsyncAPI · external protocol/profile
Last reviewed: 2026-09-02

OPERATING WORKFLOW

From input to evidence-backed state.

Prepare → Send → Correlate → Interpret → Reconcile → Evidence → Observe

01Prepare

02Send

03Correlate

04Interpret

05Reconcile

06Evidence

07Observe

Inputs: Outbound command/query · correlation ID · authoritative context · connector contract
Outputs: Transport result · business status · reconciliation state · connector evidence
API: Connector API · Events / AsyncAPI
Events: connector.degraded · reconciliation.required · reconciliation.completed
Connectors: EU/external DPP Registry · ERP/PLM · Customs/authority · marketplace

Authority: External system remains authoritative for the domain it owns.
Policy: Version compatibility · retry/idempotency · reconciliation · failure policy
Mandate: External submission may require organisation/authority credentials.
Evidence: Request/response digest · transport status · business status · reconciliation trail
External dependencies: Official external interface, credentials and contract version

ACTUAL PRODUCT UI

Approved reference screen from the UI/UX package.

No website-made screenshot replacement.

Operations Dashboard OverviewTTID--M01-L01-001 · 06_OPERATIONS_ADMIN_PORTAL(2).zip

BOUNDARY & EVIDENCE

Decision boundaries stay explicit before deployment.

Failure & recovery

Failure modes: Timeout · 5xx · schema mismatch · business rejection · contradictory external status
Retry / recovery: Retry only when safe; reconcile business state; never promote ambiguous local status as authoritative.
Limitations: Connector availability does not transfer external authority into Trusted ThingID.

Implementation links

Related portals: Operations Admin · Developer · Economic Operator
Related scenarios: RS-01 · RS-06 · RS-08
Architecture: P06
Standards: OpenAPI/AsyncAPI · external protocol/profile

READINESS PASSPORT

Readiness is scoped—not a certification claim.

PROFILE IDTTID-REGISTRY_CONNECTOR-2026.09

MATURITYEXTERNAL DEPENDENCY

ARCHITECTUREP06

ACTUAL UIEMBEDDED

API CONTRACTREFERENCE

CONFORMANCEREFERENCE / PROJECT GATE

SECURITYDEPLOYMENT-SPECIFIC

EXTERNAL DEPENDENCYOfficial external interface, credentials and contract version

LAST REVIEWED2026-09-02

EVALUATE / PILOT

Exercise success, timeout, rejection and reconciliation paths with evidence.

Review Product Readiness Explore API Center Reference Architecture