Registry Stack documentation
Registry Stack helps an institution answer questions about data it already holds without giving callers direct access to the source. Two doors: Evidence Gateway signs the answer to one bounded question, and Registry Relay publishes selected records through a protected read-only API.
Answer a bounded question with Evidence Gateway
Section titled “Answer a bounded question with Evidence Gateway”Use Evidence Gateway when the caller needs to learn only a fact, not to read a record. It answers one bounded question about one subject and signs the answer, releasing the answer rather than the row behind it. Adult status, residence region, professional licence status, and legal-parent relationship are coequal acceptance definitions; you author whichever one your institution needs, the same way.
Evidence Gateway overview explains the source, assertion, verification, and audit boundaries. Continue with your first Evidence Gateway assertion to see the boundary in one verified request. When local authoring is complete, build and deploy an Evidence Gateway project creates a reviewed candidate without promoting local development state. Registry Mint remains an optional token issuer for deployments without a suitable identity provider.
Publish selected records with Registry Relay
Section titled “Publish selected records with Registry Relay”Use Relay when the caller needs to read specific records or fields. The
institution exposes a reviewed read-only SQLite view, a data publisher writes
one contract naming the resources, operations, access profiles, and disclosure
rules, and relayctl compiles, tests, and seals that contract into a package
the relay service verifies before it opens a listener. Database tables and
columns never become routes by convention.
Publish a governed SQLite registry runs the supplied synthetic business Registry end to end in about 20 minutes. Continue with author a Registry Relay project to bind an institution-owned view, then operate Registry Relay for sources, token issuers, audit retention, and revision replacement.
Keep the product boundaries clear
Section titled “Keep the product boundaries clear”Registry Relay owns source access and protected record surfaces. Evidence Gateway owns bounded question answering, signing, and minimum disclosure, and runs independently of Relay against its own configured authoritative sources. The caller receives only the output authorized for that service.
The two products share no tooling and no deployment shape. A Relay deployment is
one sealed package per process, authored with relayctl and served by relay.
Evidence Gateway has its own toolset and deployment project shape, covered by the
Evidence Gateway overview. Relay responses are not
signed: portable signed minimum disclosure is what Evidence Gateway is for.