Registry Notary

Registry Notary evaluates claims and issues evidence. For registry-backed evidence, it consumes only authenticated, typed Registry Relay consultation results. For Notary-only projects it can evaluate source-free self-attested evidence, but it cannot issue credentials from those claims. Credential issuance requires a newly executed, compiler-pinned Relay consultation for every selected claim. It never connects directly to a registry source.

Understand

• Architecture overview
• Capability matrix
• Consultation identity and outcomes
• Scenario patterns
• Source and claim modeling

Integrate

• Client SDK guide
• API reference
• Wallet interop with OID4VCI
• SD-JWT VC conformance

Operate

• Operator configuration reference
• Self-attestation
• Federated evaluation
• Credential lifecycle and status
• Credential issuance trust-boundary migration
• Signing key providers
• Configuration trust
• Deployment hardening
• Security assurance

Maintain

• Product layout
• Design records
• Release notes
• Security policy

Registry source adaptation belongs to Relay and Registry Stack project authoring. Rhai is Relay’s reviewed script capability and CEL is Notary’s evidence-claim policy language. Product and version metadata never selects either runtime. The evidence consumer determines how returned evidence is used, and the decision owner remains accountable for requirements, decisions, workflow, and actions. CEL is not a general-purpose consumer decision engine.