Specifications
Specifications Overview
The public reference set for ECZ-ID identity, Passport structure, binding, lifecycle state and Resolver proof. Specifications explain structure; they do not replace a live state check in Resolver.
INFORMATIVE Informative index
Canonical URL: https://www.ecocitizenz.org/pages/specifications-overview
Specification index Link to section: Specification index
| Specification | Defines | Classification | Lifecycle |
|---|---|---|---|
| ECZ-ID Specification | The stable parent identifier: format, identity boundary and resolver-first interpretation. | Informative | Draft |
| Passport Specification | Parent-bound child Passports: scope, lifecycle state, capability boundary, public proof and the current public Passport families. | Informative | Draft |
| Cloud & Platform Binding Specification | Relationships between an ECZ-ID and external cloud, platform, domain, repository, API, agent, model, dataset or MCP identifiers. | Informative | Draft |
Related reference pages: Interoperability describes where ECZ-ID references are used and where implementation detail lives; Version History lists controlled revisions.
Status of these specifications Link to section: Status of these specifications
None of the specifications has yet been published as a NORMATIVE or CURRENT controlled document: no designated documentary authority or approval record exists for them. They are informative drafts. No version numbers or revision history have been invented for them; see the documentary authority rules.
How a specification is used Link to section: How a specification is used
| Step | Surface | What happens |
|---|---|---|
| Define | ecocitizenz.org | Specifications define identity, authority, scope, state, evidence and public reference. |
| Operate | TrustOps | Acquisition, setup, lifecycle, customer access and repair workflows. |
| Control | ECZ-ID backend | Deterministic state, entitlement and lifecycle decisions. |
| Verify | Resolver | Public read-only verification where a public projection is available. |
| Decide | The relying party | People, agents, platforms and policy systems apply their own review rules. |
Where to go next Link to section: Where to go next
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.
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.