Specifications
Interoperability
This page states ECZ-ID’s public interoperability positions: how other systems can carry ECZ-ID references, how machines discover the right surface, and where implementation detail lives.
INFORMATIVE Informative reference
Canonical URL: https://www.ecocitizenz.org/pages/interoperability
Public positions Link to section: Public positions
- References, not copies
- Other systems carry the ECZ-ID or Passport reference and re-check Resolver. They do not copy proof and treat the copy as current.
- Provider identity stays with providers
- Bindings link an ECZ-ID to provider identifiers without replacing provider login, permissions or access control. See the Cloud & Platform Binding Specification.
- Human and machine forms
- Resolver serves people and machines. Each surface publishes machine-readable routing so automated clients reach the right authority.
- Relying parties keep their own policy
- ECZ-ID output is an input to a relying party’s decision, not a substitute for it.
Machine discovery of this site Link to section: Machine discovery of this site
Machines can discover ecocitizenz.org and its role through standard web resources first. The llms.txt file is supplemental orientation for AI clients.
Machine-readable /sitemap.xml canonical pages on this site
Machine-readable /robots.txt crawl guidance and sitemap reference
Machine-readable /llms.txt supplemental orientation for machine and AI clients
Machine-readable Site manifest reached from /.well-known/ecz-site.json; routes machines to surface roles and Resolver
None of these resources is a source of current state. They point to the canonical pages and to Resolver.
Where implementation detail lives Link to section: Where implementation detail lives
Standards and alignment Link to section: Standards and alignment
This site makes no claim of conformance with, or endorsement by, any external standard or standards body. An evidence-backed standards alignment matrix will be published only when the supporting evidence exists.
Where to go next Link to section: Where to go next
Implement — Developer Gateway
- Why leave this site
- You need schemas, SDKs, route indexes or integration patterns rather than governance text.
- Where you go
- Developer Gateway (developers.ecocitizenz.com)
- Authority there
- Implementation, interoperability, SDK and schema guidance. It is not live proof.
- What happens next
- Use the implementation guides and reference material. Live proof still comes from Resolver.
Verify — Resolver
- Why leave this site
- This page explains rules. It cannot show whether a particular ECZ-ID, Passport or binding is current.
- Where you go
- Resolver (resolver.ecocitizenz.org)
- Authority there
- Current public proof: a read-only projection of backend-controlled state.
- What happens next
- Open the ECZ-ID or Passport record and re-check its current public status before you rely on it.