Specifications
ECZ-ID Specification
An ECZ-ID is a stable parent identifier that can be cited across contracts, systems, platforms, agents, APIs, marketplaces and review processes. The identifier itself carries no changing status: current meaning comes from backend state and from Resolver where a public projection is available.
INFORMATIVE DRAFT Informative specification
Canonical URL: https://www.ecocitizenz.org/pages/ecz-id-specification
Identifier rule Link to section: Identifier rule
Identity stays stable; state changes through controlled processes. An ECZ-ID does not encode tier, authority, capability, approval, commercial status, live state or quality. Those meanings belong to backend state and to Resolver’s projection of it.
Canonical form Link to section: Canonical form
The canonical parent format is ECZ-CC-XXXXXX.
| Part | Meaning |
|---|---|
ECZ | Identifier family prefix. Separates ECZ-ID references from local names, domains, badges and marketplace labels. |
CC | Two-letter country code. It is not an authority or state field and does not change with state. |
XXXXXX | Stable six-character Base36 identifier body. It is not a tier, product, score, approval or lifecycle signal. |
Because the identifier is deliberately non-semantic, it can be cited safely in contracts, systems, manifests, logs, Resolver URLs, procurement records, agent metadata, API documentation and evidence references without changing when tier, authority or state changes. Resolver output, not the identifier string, determines current public reliance posture.
Parent and child separation Link to section: Parent and child separation
The parent identifier stays stable while child Passports describe scoped operating surfaces beneath it. A Passport can change, degrade, expire, be suspended or be revoked without changing the parent ECZ-ID.
| Form | Example |
|---|---|
| Parent ECZ-ID | ECZ-GB-A93K7Q |
| Child Passport instance | ECZ-GB-A93K7Q::API-2Q7X9B |
| Resolver public path | /p/ECZ-GB-A93K7Q/API/2Q7X9B |
The full child model is set out in the Passport Specification.
What an ECZ-ID is and is not Link to section: What an ECZ-ID is and is not
An ECZ-ID is
- A parent identity spine for one organisation, operator or eligible subject.
- A resolver-first identifier that people and machines can check.
- A stable reference for Passports, state records, receipts and lifecycle events.
- A non-semantic identifier designed to avoid version pollution and identity drift.
An ECZ-ID is not
- A rating, score, endorsement, approval or certification.
- Proof that a business, agent, API, product or Passport is currently active.
- A replacement for regulators, auditors, insurers, courts or institutional decision-makers.
- A checkout, entitlement, dashboard or customer account.
Interpretation rules Link to section: Interpretation rules
Authority is never inferred from presentation. A copied page, badge image, marketplace listing, agent profile, API label, screenshot or private message is not the authority plane.
- Backend controls state
- Issuance, authority changes, lifecycle state, suspension, revocation and eligibility are controlled by the ECZ-ID backend.
- Resolver projects proof
- Resolver is the public read-only surface for current state, public identifiers, receipt references and machine-readable output where available.
- TrustOps operates
- TrustOps handles acquisition, setup, payment, customer access, lifecycle and repair workflows.
- Developer Gateway guides
- Developer Gateway provides schemas, route indexes, examples and implementation guidance. It does not issue proof.
Evidence references Link to section: Evidence references
Public evidence associated with an ECZ-ID can include state records, public-safe receipt references, manifest hashes, effective dates, Resolver verification instructions and machine-readable proof metadata. A receipt records an ECZ-ID system event or reference; its evidential meaning depends on its source and context.
Citing an ECZ-ID Link to section: Citing an ECZ-ID
| Context | Recommended practice |
|---|---|
| Contracts and procurement | Cite the parent ECZ-ID as a stable identity reference, and require a Resolver check of current state before reliance. |
| Agents and automation | Include ECZ-ID references in agent metadata or manifests, and require Resolver output before automated reliance. |
| APIs and software | Use ECZ-ID references in API documentation, OpenAPI extensions, package metadata or software supply-chain records. |
| Badges and public pages | Route badges and public pages to Resolver. They are not proof copies or independent authority. |
| Insurers and auditors | Use the identifier to locate the relevant public proof, receipt references, effective dates and current state. |
| Platforms and marketplaces | Use the ECZ-ID as a reference key for review and routing, not as an endorsement or automatic approval signal. |
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.
Acquire, activate, manage or pay — TrustOps
- Why leave this site
- You want to acquire, activate, manage or pay for an ECZ-ID or Passport.
- Where you go
- TrustOps (trustops.ecocitizenz.com)
- Authority there
- Acquisition, payment, entitlement, activation and lifecycle operations.
- What happens next
- Start or manage the operational acquisition and lifecycle flow. Payment or activation is not itself proof.
Read together Link to section: Read together
Revision history Link to section: Revision history
| Date | Version | Status | Change summary |
|---|---|---|---|
| No controlled revision of this document has been published. Earlier versions of this page on the Shopify-hosted site were not issued under a documentary authority record, so no history is backfilled. | |||
Recommended citation Link to section: Recommended citation
EcoCitizenz Ltd, ECZ-ID Specification, DRAFT, https://www.ecocitizenz.org/pages/ecz-id-specification.
Fields that do not yet exist for this document, such as a document ID or version, are omitted rather than invented.