01 /
Service-specific evidence
Define which claims a service needs, who may issue them and when they expire. Reuse requires an authorised purpose and a valid credential, not blanket acceptance.

Government DPI / public trust
A sovereign trust coordination model for agencies, ministries and public platforms—with identity evidence, service-specific credentials and human review at its foundation.
Public infrastructure, public responsibility
Public services need dependable evidence, but a check for one service must not become unrestricted access across every agency. Identity, eligibility and authorisation are different questions.
TrustProtocol models the relationships between people, institutions, credentials and services while preserving purpose, provenance and review. Sovereignty depends on governance and operational control—not a label on a dashboard.
Build around the public interest
01 /
Define which claims a service needs, who may issue them and when they expire. Reuse requires an authorised purpose and a valid credential, not blanket acceptance.
02 /
Make agency responsibilities, jurisdiction, access boundaries and audit requirements explicit. Cross-agency exchange needs policy and accountable owners.
03 /
Explain requested information and decisions in understandable terms. Preserve correction, assisted access, privacy controls and a meaningful appeal path.
A governed service journey
A reference model for public-service coordination. It does not assert an active national identity integration or determine eligibility for any public benefit.
Document the legal authority, eligibility criteria, minimum evidence and assistance options before collecting information.
Use authorised sources and issuers. Keep identity confidence separate from service eligibility, and record provenance, validity and expiry.
Limit exchange to the claims needed by an authorised recipient. Apply consent where appropriate without treating consent as a substitute for legal authority.
Record reasons and responsible actors. Provide correction and appeal routes, with oversight that respects privacy and retention boundaries.

People, not just records
A person should be able to ask why information is needed, get help when a digital process fails and challenge an incorrect record without being reduced to a risk label.
Inclusive service design keeps assisted routes and human judgement visible. A missing credential should trigger an appropriate review—not an unexplained, irreversible exclusion.
Sovereignty requires evidence
Data residency, procurement, accessibility, security and institutional mandates require jurisdiction-specific assessment and documented approval. This page establishes no government endorsement, certification or deployed sovereign service.
No identity registration, credential issuance or public-benefit decision happens here. Production adoption requires validated controls, authorised integrations, operational ownership and tested recourse.
Review deployment boundariesStart with a public-service need
Identify the participating agencies, evidence requirements, disclosure boundaries and review responsibilities before planning an integration.