Skip to content
Registry stack docs v0 · draft
Search

Certify evidence

Certify evidence is how a registry answers a configured question about its data, a status, a predicate, or a selected value, and returns the answer as a signed artifact instead of the full source record. The primary implementation is Registry Notary, which evaluates configured eligibility claims against registry data, applies disclosure policy, and returns structured results, CCCEV-shaped JSON-LD, or SD-JWT VC credentials.

A service can attest that a configured claim was evaluated and can package the result for a calling program or wallet flow. Registry Notary does not decide program entitlement; the caller decides what a verified claim means for a benefit, service, or workflow.

What it produces

Section titled “What it produces”

Registry Notary returns:

  • A predicate result (true/false) with the configured grounds, without returning the underlying record.
  • A redacted or value-bearing result when policy permits additional disclosure.
  • A CCCEV-shaped JSON-LD evidence artifact.
  • An SD-JWT VC credential for wallet or OID4VCI flows.
  • A delegated evaluation result when the claim is answered by a trusted peer service.

Audit records are written for every evaluation.

Primary project

Section titled “Primary project”

Registry Notary: claim model, rule types, credential issuance, and v0 caveats.

How to use it

Section titled “How to use it”

Define a claim, configure evaluation rules, and set disclosure policy. See Configure a claim for the configuration surface. See the Notary API reference for the HTTP contract.

Example: a social protection workflow asks whether a household is currently enrolled in a conditional cash transfer programme and receives a predicate response (true/false plus the configured grounds), not the enrollment record.

Section titled “Related docs”