PLATFORMREFERENCE ARCHITECTURE

A modular trust layer with explicit authority boundaries.

Explore the governed Trusted ThingID platform modules for identity resolution, DPP lifecycle, claims, policy, evidence, device trust and integration.

11Modules
6Canonical pages
By data domainAuthority rule
PRODUCT DECISION SURFACE

Business outcome

A governed control plane lets every Experience reuse the same identity, DPP, policy, evidence and authority semantics without absorbing source-system authority.

Outcome

Reduce ad-hoc integration while keeping business decisions traceable.

Authority

External systems of record remain authoritative by data domain.

Evidence

Material actions carry correlation, policy/version and evidence context.

Maturity

Capabilities are disclosed as Available / Pilot Ready / Reference / Roadmap.

MODULE CATALOGUE

Capabilities are separated by business responsibility.

Each module page states what it does, what it does not do, its authority boundary, objects, APIs/events, evidence, standards and maturity.

Thing Identity & Resolver

REFERENCE IMPLEMENTATION

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

Identifier Governance

REFERENCE ARCHITECTURE

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

DPP Regulatory Engine

PILOT READY

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

Claims & Credentials

REFERENCE IMPLEMENTATION

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

Ownership, Custody & Delegation

UI/UX BASELINE

Keep legal ownership, possession, custody, maintenance and delegation as separate evidence-backed relationships rather than DPP side effects.

Policy, Mandate & Disclosure

REFERENCE ARCHITECTURE

Separate authentication, authorization and field-level disclosure through PAP/PIP/PDP/PEP policy semantics.

Evidence & Provenance

PILOT READY

Bind business events and claims to source evidence, provenance, trusted time, immutable audit and retention policy.

Device Trust & Attestation

REFERENCE ARCHITECTURE

Select assurance from L0 passive carrier through L3 runtime attestation according to risk and device capability.

Repositories & Read Models

REFERENCE ARCHITECTURE

Keep systems of record, claim/evidence stores, derived indexes and external-source representations explicit and non-confused.

Connector & Integration Platform

PILOT READY

Use domain-specific adapters over shared API, event, workflow, semantic mapping, retry and reconciliation capabilities.

Governance & Conformance

REFERENCE ARCHITECTURE

Make decision ownership, risk acceptance, architecture traceability, conformance evidence and design handoff explicit.

POLICY SEMANTICS

AuthN ≠ AuthZ ≠ field disclosure.

Identity and policy are not decorative middleware: they determine who may do what and which fields may be disclosed.

01REQUESTIdentity · Resource · Purpose
02PIP CONTEXTRole · Mandate · Attributes
03PDP DECISIONPolicy · Lawful basis · Risk
04PEP ENFORCEMENTAllow · Deny · Mask · Constrain
05COMPOSED VIEWPermitted fields only
ARCHITECTURE INVARIANTS

Non-negotiable rules keep the model explainable.

These guardrails are repeated across product, portal, developer and trust-center content.

Official identifiers remain authoritative

TTID resolves/correlates; it does not replace them.

Ownership is evidence-backed

DPP creation does not establish legal ownership.

Device states stay independent

Certificate validity does not equal runtime trust.

Ledger is optional

Full business/DPP data stays off-chain.

Private keys stay protected

They do not enter DPP/business repositories.

External authority stays external

Connectors integrate; authority is not transferred.

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.