Registry stack documentation: machine-readable Markdown.
Index of all pages: https://docs.registrystack.org/llms.txt
Full corpus: https://docs.registrystack.org/llms-full.txt

# Registry Stack docs

> Documentation for Registry Stack: protected registry APIs, governed evidence exchange, Registry Relay, and Registry Notary.

Registry Stack adds registry-facing services, protected reads,
[governed evidence](reference/glossary/), and audit
records, over data an institution already holds.
The data never leaves the source system.

Start with [your first registry API](tutorials/publish-spreadsheet-secured-registry-api/), then
[evaluate a claim](tutorials/verify-claim-registry-api/) against that local API.

The hosted Relay quickstart passed its latest check, but the hosted credential continuation is not
the promoted first-run route while [GH#330](https://github.com/registrystack/registry-stack/issues/330)
remains open and the complete [GH#198](https://github.com/registrystack/registry-stack/issues/198)
fresh-reader run is unfinished.

## Two products

Registry Relay protects what an institution already holds. Registry Notary certifies answers drawn
from that data.
Use the local tutorials below for the current first-run path.

### Registry Relay

Registry Relay exposes protected, scoped, read-only APIs over existing sources: files, extracts,
databases, and legacy registry systems.

[Your first registry API](tutorials/publish-spreadsheet-secured-registry-api/): run a protected
API locally over a sample spreadsheet.

### Registry Notary

Registry Notary certifies evidence: claim evaluation, credential issuance, disclosure policy, and
audit provenance.

[Your first claim check](tutorials/verify-claim-registry-api/): evaluate a claim and compare the
result with a protected row read.

## Security

Registry Stack authorization is scope-based and deny-by-default.
Every request writes to a hash-chained audit envelope. Health and readiness probes are excluded
by default.
These docs are evidence-anchored: every claim points to code, a fixture, a test, or a
specification requirement ID.

Read the [security overview](security/) for the threat model and the public evidence a reviewer can
check.