Choose where to start
Use this page when you are new to Registry Stack and need the shortest route to a useful answer. The docs are organized around questions, not around repository names.
The short model
Section titled “The short model”Registry Stack has three current product surfaces. Registry Relay makes existing registry-like data available through protected, read-only APIs. Registry metadata describes the registry surface before an integration is written. Registry Notary answers configured evidence questions without exposing a full source record.
Stay in these docs for the problem model, product boundaries, cross-project architecture, standards evidence, and API contracts. Go to an owning repository when you need source code, runtime configuration, contribution workflow, or implementation issues.
Choose by question
Section titled “Choose by question”| If your question is | Start with | Then read |
|---|---|---|
| What exists today, and where are the boundaries? | capabilities | project map |
| Why do safer registry surfaces matter now? | Why safer registry surfaces matter now | Safeguards need technical enforcement |
| How do existing files, extracts, databases, or legacy systems become usable? | Existing data is not service-ready | Legacy registry API use case |
| How does a caller discover what a registry provides? | Registry capabilities are hard to discover | Describe registries |
| How can a service verify a status or claim without receiving the full record? | APIs over-share records | Certify evidence |
| How do I review safeguards? | Safeguards need technical enforcement | Audit and operate |
| Which repository owns which part? | Project map | The relevant project overview |