Use cases
Each scenario starts from a registry that already exists and ends with a bounded answer instead of a copied file. The pattern is the same across domains: a question asked, the evidence returned, and the record that is never over-shared. Every one is small enough for a single pilot.
One source, many bounded answers
Each request reads only what it needs and returns a minimal answer; the rest stays with the data owner, and every request is logged.
Scenario gallery
From foundational registries to business and sector data. The shape is registry-generic.
Civil registration
Evidence returned
Issue a signed proof-of-life the person can hold and present.
Record not over-shared
Do not disclose the full civil-registration record.
Smallest pilot
A pension authority confirms vital status for continuations without a database credential.
Social protection
Evidence returned
Confirm the household has an active entry in the social registry.
Record not over-shared
Do not expose the household case file, income tier, or transfer history.
Smallest pilot
A school-feeding program confirms a child’s household is already listed in a separate ministry’s registry.
Business registry
Evidence returned
Return active registration status tied to the national business number.
Record not over-shared
Do not disclose filing history, registered address, or beneficial ownership.
Smallest pilot
A procurement platform checks supplier status before processing a tender submission.
Farmer registry
Evidence returned
Confirm registration and return farm size (for example, 2.5 ha).
Record not over-shared
Do not expose plot location, household roster, crop history, or financial records.
Smallest pilot
A subsidy program confirms registration and size band for an input grant.
Legacy registry
Evidence returned
Expose only the policy-allowed fields through an authorized, audited route.
Record not over-shared
Do not hand out database credentials or the full record and correction history.
Smallest pilot
A registrar wraps a legacy source with a governed read boundary instead of replacing it.
Registry metadata
Evidence returned
Publish catalog, schema, policy, and evidence-offering metadata partners can read.
Record not over-shared
Do not open record-level access to answer discovery questions.
Smallest pilot
A ministry gives three integration teams one canonical description before any agreement is signed.