Capabilities
Registry Stack provides a registry-facing layer for systems that already hold authoritative data. The capabilities are organized around one sequence: describe what the registry can provide, expose protected read-only access, and return evidence that fits the purpose of the request.
The sequence
Section titled “The sequence”Start with metadata. A caller cannot safely use a registry if the fields, schemas, services, policies, evidence offerings, and confidence boundaries are not inspectable. After the registry surface is described, Registry Relay can expose scoped routes over the existing source. Registry Notary can then evaluate configured claims and return a minimized evidence response when the caller does not need the whole record.
| Capability | Use it when | Primary project |
|---|---|---|
| Describe registries | Other teams need to inspect fields, schemas, policies, services, and evidence offerings before integration. | Registry Manifest |
| Expose protected APIs | A file, extract, database, or legacy registry needs a governed read-only API without replacing the source. | Registry Relay |
| Certify evidence | A caller needs a status, predicate, selected value, or supported credential instead of the source record. | Registry Notary |
Supporting capabilities
Section titled “Supporting capabilities”Inspect published artifacts helps reviewers check what a registry actually publishes before an integration is built. Registry Atlas reads generated metadata artifacts and runs strict capability queries against known machine terms.
Audit and operate explains the shared audit and operational behavior that makes Registry Relay and Registry Notary reviewable. Registry Platform supplies shared primitives for authentication, HTTP security, audit envelopes, cryptography, and credential support.
How to choose
Section titled “How to choose”- Start with describe registries if the registry surface is not yet documented in machine-readable form.
- Start with expose protected APIs if a source already exists and the immediate need is governed read-only access.
- Start with certify evidence if the integration already has a clear claim and the caller should receive an answer rather than a full record.
- Start with inspect published artifacts if the task is review, discovery, or integration planning.
- Start with audit and operate if the question is how runtime requests are logged, secured, and reviewed.
Boundaries
Section titled “Boundaries”Registry Stack does not replace a domain registry platform (such as OpenCRVS, OpenSPP, DHIS2, OpenIMIS, …), a workflow engine, an exchange layer, a wallet, or a public-service portal. It provides the registry-facing controls those systems can call: metadata, protected routes, evidence responses, and audit records. See the ecosystem map for how Registry Stack fits alongside those systems.
Registry Stack also does not solve foundational identity, deduplication, legal authority, semantic governance, or institutional approval by itself. The capabilities make those boundaries explicit so they can be reviewed before data starts moving.