Developers

Guides

Start from what you need to do. Every guide states the production status of what it relies on, so you know before you start whether it runs today, runs in TrustOps, is documented ahead of release, or happens in your own system.

I need to verify something
- Verify before relianceLive · public
  Read a counterparty’s public ECZ-ID record live, apply your own policy to it, and hold the line in CI. Everything on this page runs today with no account.
- Resolver integrationLive · public
  Integrate the Resolver correctly: the right host, the right status handling, child identifiers, the publish kit, and the errors that are not verdicts.
I need to carry Intent
- Carry IntentLive · signed in
  Model what each machine is authorised to do as an ECZ-ID Intent, keep it narrow, and make every consequential request able to name the Intent it acts under.
I need a decision
- Request a decisionRelease-gated
  How an enforcement point asks IntentControl whether a proposed action may proceed, obeys the answer and reports what it did. Documented ahead of release.
I need to handle a Receipt
- Verify a ReceiptNo public retrieval
  What verifying an ECZ-ID Receipt means, what a valid result does and does not tell you, and what to read today while public receipt retrieval is not enabled.
I need to handle evidence
- Evidence handlingYour system
  Keep evidence by reference and digest, respect what a record consents to publish, and never turn a past observation into a present claim.
I need to mediate actions
- Enforcement integrationRelease-gated
  Choose where to mediate, start in monitor mode, move to enforce mode deliberately, and never describe a posture you cannot evidence.
I need to control disclosure
- Privacy and disclosureLive · public
  What ECZ-ID publishes, what it deliberately does not, and how disclosure profiles keep evidence useful without exposing it.

Guides by task