Skip to main content
Open navigation
An open contemporary civic courtyard and accessible ramp leading to a warmly lit public hall

Government DPI / public trust

Connected public services. Accountable institutions.

A sovereign trust coordination model for agencies, ministries and public platforms—with identity evidence, service-specific credentials and human review at its foundation.

01 / Purpose-bound exchange02 / Institutional governance03 / Citizen agency

Public infrastructure, public responsibility

A connected service should not mean an exposed person.

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

Connect what is needed. Govern what is shared.

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.

02 /

Institutional oversight

Make agency responsibilities, jurisdiction, access boundaries and audit requirements explicit. Cross-agency exchange needs policy and accountable owners.

03 /

Citizen agency

Explain requested information and decisions in understandable terms. Preserve correction, assisted access, privacy controls and a meaningful appeal path.

A governed service journey

From evidence to a decision people can understand.

A reference model for public-service coordination. It does not assert an active national identity integration or determine eligibility for any public benefit.

  1. 01

    Define the service purpose

    Document the legal authority, eligibility criteria, minimum evidence and assistance options before collecting information.

  2. 02

    Verify and issue in scope

    Use authorised sources and issuers. Keep identity confidence separate from service eligibility, and record provenance, validity and expiry.

  3. 03

    Control disclosure

    Limit exchange to the claims needed by an authorised recipient. Apply consent where appropriate without treating consent as a substitute for legal authority.

  4. 04

    Explain, review and oversee

    Record reasons and responsible actors. Provide correction and appeal routes, with oversight that respects privacy and retention boundaries.

Illustrative public-service conversation between an older man and an attentive adviser
Illustrative generated scene. Not actual staff or a customer endorsement.

People, not just records

Public trust starts with being heard.

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

Authority must be explicit. Oversight must be real.

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 boundaries

Start with a public-service need

Define the service. Protect the person.

Identify the participating agencies, evidence requirements, disclosure boundaries and review responsibilities before planning an integration.