Governance or specification question
Use ecocitizenz.org.
Use this site to understand public governance, specifications, definitions, authority boundaries, issuance posture, revocation posture, and system rationale.
Formal enquiries
Use the correct route before asking for the wrong proof.
This page routes formal questions about ECZ-ID governance, specifications, public reference material, implementation guidance, and operating-surface boundaries. It is not the authority plane, not the public verification surface, and not the acquisition or lifecycle control surface.
Route the enquiry
Every question belongs to the surface that can answer it safely.
ECZ-ID is designed so humans, agents, reviewers, platforms, procurement teams, auditors, insurers, regulators, and automated systems can find the right public surface without turning websites into proof, support messages into authority, or guidance into backend truth.
Current public state or proof
Use Resolver.
Resolver is the public read-only verification surface. Use it to inspect current public state, identifiers, effective dates, and machine-readable proof outputs.
Acquisition, setup, lifecycle, or payment
Use TrustOps.
TrustOps handles acquisition, activation, setup, lifecycle control, customer access, repair paths, and payment over backend-owned truth.
Schemas, manifests, or integration
Use Developer Gateway.
Developer Gateway is for schemas, route indexes, implementation guidance, integration patterns, agent-facing docs, and machine-readable developer material.
Good formal enquiries
What this page is for.
- Clarifying published ECZ-ID governance, specification language, authority boundaries, issuance posture, revocation posture, or system rationale.
- Institutional review by auditors, procurement teams, insurers, regulators, platforms, partners, legal teams, or enterprise reviewers.
- Questions about where a user, agent, platform, or automated system should go next: Resolver, TrustOps, Developer Gateway, or this public specification layer.
- Requests to understand public machine-readable routing, resolver-first proof posture, or implementation guidance at a non-secret level.
Do not use this page for
What this page must not become.
- Do not use formal enquiries as proof of current ECZ-ID, passport, or binding state.
- Do not send private keys, secrets, tokens, raw logs, private contracts, or confidential evidence.
- Do not treat email, screenshots, page copy, badge display, or marketplace presence as authority.
- Do not ask this site to issue, activate, revoke, downgrade, repair, or mutate ECZ-ID state.
Human, agent, and machine routing
Public enquiries should make the next correct action obvious.
A human can read this page. An agent or automated system can also infer the surface boundary from the page structure, route labels, and public links. The rule is the same for both: use Resolver for public proof, TrustOps for action, Developer Gateway for implementation, and this site for public governance and specifications.
For humans
Understand before acting.
Read the public governance layer first, then check live public state in Resolver before relying on any ECZ-ID, passport, badge, or referenced proof surface.
For agents
Route before relying.
Agentic systems should not infer authority from page text. They should use public Resolver output and Developer Gateway guidance where machine-readable integration is required.
For institutions
Separate policy from proof.
Procurement, audit, insurance, platform, and regulatory reviewers can use this page to understand the rules, then use Resolver and TrustOps for state and action.
Public reference path
Ask formal questions here. Verify public state in Resolver.
Use this page for governance and specification enquiries. Use Resolver for public verification. Use TrustOps for acquisition, setup, lifecycle, repair, and operational action. Use Developer Gateway for schemas, route indexes, machine-readable guidance, and integration patterns.