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 Notary > Integrator and operator documentation for Registry Notary, pulled from the product repository. Registry Notary answers configured claims about a person or entity by reading the minimum data from a source registry, without becoming a copy of that registry. Depending on the claim, it returns a claim result, renders a supported format, or issues a short-lived SD-JWT VC credential. Pick your path below. New to Registry Notary? Start with the hosted walkthrough or a runnable local tutorial. If you are configuring or operating Notary, start with the [architecture overview](./architecture-overview/). - [See it live](https://docs.registrystack.org/start/see-it-live/): watch Notary issue a privacy-preserving credential against a hosted lab, with zero install. - [Verify a claim with Registry Notary](https://docs.registrystack.org/tutorials/verify-claim-registry-api/): add Notary to a local registry API project with `registryctl`. Its final section, [Run Notary standalone for an API you operate](https://docs.registrystack.org/tutorials/verify-claim-registry-api/#run-notary-standalone-for-an-api-you-operate), covers creating a standalone Notary project for a source API you operate. - [Architecture overview](./architecture-overview/): what Registry Notary is, the request lifecycle, and how the layers relate. - [Capability matrix](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/notary-capability-matrix.md): which flows Notary supports today, by persona and system. - [Identity and record matching](./identity-and-record-matching/): how Notary resolves the target entity to a source record, the outcome model, and matching policy. ## Integrate For application and wallet developers calling the API or the SDKs. - [Client SDK guide](./client-sdk-guide/): evaluate claims and issue credentials from Rust, Python, and Node.js. - [API reference](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/api-reference.md): the route-to-client-method matrix and the stable problem-code registry. - [Wallet interop with OID4VCI](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/oid4vci-wallet-interop.md): the OpenID4VCI wallet facade contract and compatibility checklist. - [SD-JWT VC conformance](./sd-jwt-vc-conformance-profile/): the supported credential wire contract and the explicit non-support list. - [OpenCRVS DCI tutorial](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/opencrvs-dci-standalone-tutorial.md): issue local demo SD-JWT VCs from OpenCRVS birth-record evidence. - [Scenario patterns](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/notary-scenario-patterns.md): reusable evaluation, federation, and issuance flows with sequence diagrams. ## Operate For operators deploying, configuring, and running a Registry Notary. - [Configuration reference](./operator-config-reference/): the config blocks for auth, evidence, sources, replay, status, self-attestation, OID4VCI, and federation. - [Model sources and claims](./source-claim-modeling-guide/): design source connectors, OpenFn sidecars, claim boundaries, disclosure, and batch reads. - [Signing key providers](./signing-key-provider/): SD-JWT VC signing-key configuration, rotation, and PKCS#11 setup. - [Self-attestation](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/self-attestation-operator-guide.md): citizen OIDC subject binding, token policy, allow-lists, and rollout. - [Federated evaluation](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/federated-evaluation-operator-guide.md): static-peer setup, environment variables, and the replay limitation. - [Credential lifecycle and status](./credential-lifecycle-status/): short-lived credentials, optional live status, retention, and verifier caveats. - [Sidecar trust and secret handling](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/sidecar-trust-and-secrets.md): how the OpenFn sidecar verifies its configuration, how Notary pins the sidecar it trusts, how secrets are handled, and what that path does and does not protect against. - [Deployment hardening runbook](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/deployment-hardening-runbook.md): production-readiness checklist for network boundaries, secrets, Redis, audit, and rollback. ## Build and maintain For maintainers changing the code or reviewing design history. - [Workspace layout](https://github.com/jeremi/registry-notary/blob/313a226b92a6e2075003b04353dcbdab335c2c10/README.md#layout): the crates and bindings and what each owns. - [Command-line interface](https://github.com/jeremi/registry-notary/blob/313a226b92a6e2075003b04353dcbdab335c2c10/crates/registry-notary-bin/README.md): the server binary and its subcommands. - [Design records](https://github.com/jeremi/registry-notary/blob/313a226b92a6e2075003b04353dcbdab335c2c10/specs/README.md): specifications and implementation traces, kept as design history. - [Security assurance](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/security-assurance.md): CI security gates, image publication and signing policy. ## Related - [Release notes](https://github.com/jeremi/registry-notary/blob/f182385a5065873aac030c41d9fe020704afc4e2/docs/release-notes.md) - [Security policy](https://github.com/jeremi/registry-notary/blob/313a226b92a6e2075003b04353dcbdab335c2c10/SECURITY.md)