# ECZ-ID .org > Public governance and specifications for ECZ-ID — Reciprocal Trust Infrastructure for the Machine Economy. This site publishes documentation only. Current state and proof for any ECZ-ID or Passport are verified through Resolver. Websites publish documentation. Backend state is canonical. Resolver verifies public proof. Canonical accountability chain: IDENTITY → AUTHORITY → DELEGATION → INTENT → CURRENT STATE → DECISION → ACTION → RECEIPT → EVIDENCE → RE-VERIFY Documentary status: the governance and specification documents on this site are informative drafts. None has yet been published as a CURRENT controlled document, and no designated documentary authority record exists for them. This file is supplemental orientation for machine and AI clients. It is not a source of current state, and the canonical pages and sitemap take precedence over it. ## Governance - [Governance Overview](https://www.ecocitizenz.org/pages/governance-overview): How ECZ-ID governance is published: documentary authority boundaries, the governance documents, and why current proof stays in Resolver. - [Authority Model](https://www.ecocitizenz.org/pages/authority-model): How ECZ-ID treats identity, authority and delegation: authority is formal, scoped, time-bound and checkable, and never inferred from identity or relationship alone. - [Issuance Policy](https://www.ecocitizenz.org/pages/issuance-policy): The ECZ-ID issuance posture: issuance is a backend-controlled authority event, projected in Resolver, never a website claim, badge or listing. - [Revocation Policy](https://www.ecocitizenz.org/pages/revocation-policy): How ECZ-ID treats revoked, suspended, degraded, expired, mismatched and unresolved states so that stale proof is not mistaken for current authority. - [Trust Principles](https://www.ecocitizenz.org/pages/trust-principles): The public trust principles of ECZ-ID and the semantic equivalences it rejects, such as identity equals authority or documentation equals current state. - [System Rationale](https://www.ecocitizenz.org/pages/system-rationale): Why ECZ-ID exists: reliance fails when identity, authority, state and evidence are split across weak surfaces. ECZ-ID keeps them separately resolvable. ## Specifications - [Specifications Overview](https://www.ecocitizenz.org/pages/specifications-overview): Index of ECZ-ID public specifications — the ECZ-ID identifier, Passports and cloud and platform binding — with their documentary status. - [ECZ-ID Specification](https://www.ecocitizenz.org/pages/ecz-id-specification): The ECZ-ID parent identifier: a stable, non-semantic identity reference (ECZ-CC-XXXXXX) whose current meaning comes from backend state and Resolver. - [Passport Specification](https://www.ecocitizenz.org/pages/passport-specification): ECZ-ID Passports: scoped accountability objects attached to a stable parent ECZ-ID, with their own lifecycle state and Resolver-verifiable public proof. - [Cloud & Platform Binding Specification](https://www.ecocitizenz.org/pages/cloud-platform-binding-specification): How ECZ-ID represents relationships between an ECZ-ID and external cloud, platform, domain, repository, API, agent, model, dataset or MCP identifiers. - [Interoperability](https://www.ecocitizenz.org/pages/interoperability): Where ECZ-ID references can be used by other systems, how machines discover ECZ-ID surfaces, and where implementation detail lives. - [Version History](https://www.ecocitizenz.org/pages/version-history): Controlled revisions and supersession of ECZ-ID governance and specification documents. No controlled revision has yet been published. ## Architecture and institutional - [Public Architecture](https://www.ecocitizenz.org/pages/public-architecture): The public architecture of ECZ-ID at a safe level of abstraction: surface boundaries, authority and state, the Resolver model and the evidence model. - [Institutional](https://www.ecocitizenz.org/pages/institutional): An evaluation route for enterprises, regulators, procurement teams, insurers and auditors: what this site establishes, who operates each surface, and where to verify. - [Formal Enquiries](https://www.ecocitizenz.org/pages/formal-enquiries): Route a governance, specification or institutional question to the ECZ-ID surface that can answer it, and how to contact EcoCitizenz Ltd with minimal data. ## Other ECZ-ID surfaces - [Resolver](https://resolver.ecocitizenz.org/): current public proof for an ECZ-ID or Passport. Re-verify before relying on any ECZ-ID reference. - [Developer Gateway](https://developers.ecocitizenz.com/): implementation guidance, schemas and SDKs. Not live proof. - [TrustOps](https://trustops.ecocitizenz.com/start): acquisition, activation, lifecycle and payment. Payment is not proof. - [ecocitizenz.com](https://www.ecocitizenz.com/): commercial and category discovery. ## Machine resources - [Sitemap](https://www.ecocitizenz.org/sitemap.xml): canonical pages on this site. - [Site manifest](https://machine.ecocitizenz.org/manifests/ecocitizenz-org.json): surface role and routing for machines, discovered at https://www.ecocitizenz.org/.well-known/ecz-site.json. ## Optional - [Privacy Notice](https://www.ecocitizenz.org/policies/privacy-policy): How ecocitizenz.org handles personal information: a static documentation site with no cookies, analytics, tracking or forms. Enquiries are handled by email. - [Accessibility](https://www.ecocitizenz.org/pages/accessibility): Accessibility commitment for ecocitizenz.org: WCAG 2.2 AA as the release floor, how the site is built and tested, known limitations and how to report a problem.