Governance

System Rationale

ECZ-ID exists because trust needs to remain resolvable. Systems depend on identity, authority, state, time, custody and evidence being answerable at the moment of reference, not reconstructed later from screenshots, stale pages, copied manifests or informal claims.

INFORMATIVE Informative explanation

The structural problem Link to section: The structural problem

Websites, profiles, marketplaces, badges, documents and directories often describe a subject. They rarely answer reliably whether that subject is current, authorised, bound, active, suspended, revoked, expired, mismatched or unresolved at the moment someone relies on it.

Why a resolver-first model Link to section: Why a resolver-first model

ECZ-ID separates parent identity, Passport scope, bindings, evidence history, current state and public proof. Each layer has one job and a strict authority boundary.

That separation is what makes ECZ-ID more useful than a badge, profile, public claim, listing or self-published document. Presentation can direct attention; Resolver carries the public answer.

ECZ-ID canonical accountability chain, ten stages.
  1. IDENTITY
  2. AUTHORITY
  3. DELEGATION
  4. INTENT
  5. CURRENT STATE
  6. DECISION
  7. ACTION
  8. RECEIPT
  9. EVIDENCE
  10. RE-VERIFY

System layers Link to section: System layers

Layers of the ECZ-ID model
LayerJob
Identity spineA stable ECZ-ID gives an organisation or entity a persistent reference that does not encode tier, product, status, rating or commercial meaning.
Scoped PassportsPassports attach bounded operating surfaces — agents, APIs, products, datasets, software, robotics, infrastructure and others — to the parent identity.
BindingsDomains, manifests, APIs, repositories, tools and platforms can be linked to the accountable operator without making public pages authoritative.
Evidence historyLifecycle and evidence events remain reconstructable, so state can be understood across time.
Current statePresent-tense posture — active, suspended, degraded, revoked, expired, mismatched or unresolved — is checked before reliance.
Public proofResolver projects safe, read-only, machine-readable output for people, agents, platforms and reviewers.

Who it is for Link to section: Who it is for

ECZ-ID is designed for people and machines alike: agents, platforms, developers, procurement teams, insurers, auditors, regulators, counterparties, support teams and Resolver users. It is also designed with adversarial actors in mind, which is why presentation never confers authority.

Where to go next Link to section: Where to go next

Explore commercially — ecocitizenz.com

Why leave this site
You want the commercial picture: what is offered, for whom, and why it matters.
Where you go
ecocitizenz.com (www.ecocitizenz.com)
Authority there
Commercial and category discovery: offers, corridors and use cases.
What happens next
Explore categories, corridors and use cases on the commercial site.

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.