Design record
The documents that were written before and during the build. They are kept as a record of what was decided and why, not as a description of the current system — where a spec and the code disagree, the code is right and the rest of this site describes it.
They are worth reading for the reasoning. The chapters elsewhere say what the registry does; these say what else was considered.
| Design | The whole system: the model, the endpoints, the authorisation rules, the open questions. |
| Vocabulary audit | Which standard vocabularies the RDF terms were checked against, and where a registry-specific term was unavoidable. |
| Workload identity | How a deployment authenticates without a stored secret. |
| Artifact subscriptions | Filters, delivery, retries, and the security argument for refusing private webhook targets. |
| Federated search propagation | Live fan-out across a graph of registries without looping. |
The frontend handoff is the corresponding document for the UI, including the questions it left open and the answers they got.