Governance overview

Governance rules are published here.

ECZ-ID governance defines the public rules, authority boundaries, lifecycle principles, and specification references that keep identity, authority, state, time, and evidence independently resolvable.

Open Resolver ECZ-ID Specification Authority Model

ECZ-ID provides

  • A stable, non-semantic ECZ-ID that can be cited across contracts, platforms, systems, and official processes.
  • A parent-and-passport framework for structured, resolver-verifiable state across businesses, machines, products, and operating surfaces.
  • A time-bound record of authority and state transitions, including issuance, activation, suspension, revocation, and lifecycle change.
  • Machine-readable and machine-verifiable public trust surfaces for deterministic resolution and integration.
  • Ledger-linked receipts and canonical references for tamper-evident historical reconstruction.

ECZ-ID does not

  • Rank, score, endorse, or certify business quality.
  • Provide opinions, recommendations, or reputational ratings.
  • Replace regulators, auditors, insurers, courts, or institutional decision-makers.
  • Guarantee outcomes, performance, safety, compliance, or commercial suitability.
  • Publish pricing, promotions, or commercial offers on this public infrastructure surface.

The structural requirement

Modern systems need identity, authority, state, time, and evidence to remain resolvable.

Economic, regulatory, and machine-operated systems repeatedly depend on four questions being answerable at the moment of reference.

01

Who is the entity?

The subject being relied on must remain identifiable across systems, contracts, platforms, and time.

02

Who held authority?

Authority must be scoped, time-bound, attributable, and reconstructable later.

03

What state existed?

State must be distinguishable at the relevant moment, not inferred from stale pages or documents.

04

Was reliance justified?

Relying parties need public Resolver output rather than narrative reconstruction after the fact.

How ECZ-ID works

Each surface has one job. Each job has a strict authority boundary.

Public specification surface

Ecocitizenz.org

Publishes governance, specifications, public definitions, and formal reference material. It does not issue ECZ-IDs, activate capability, or provide authoritative verification.

Operational control surface

TrustOps

Handles acquisition, activation, setup, lifecycle control, customer access, and payment. It controls operations over backend truth, but is not an independent truth source.

Authority plane

Backend

Maintains canonical system truth. Issuance, state mutation, authority change, eligibility, downgrade, suspension, and revocation are controlled by deterministic backend rules.

Public verification surface

Resolver

Projects authoritative public proof, including current state, public identifiers, effective dates, machine-readable outputs, and referenced evidence receipts where available.

Machine-readable public infrastructure

Use Developer Gateway for implementation guidance, not public proof.

Developers, agents, platforms, and reviewers can use Developer Gateway for schemas, route indexes, implementation guidance, and safe integration patterns. Public proof still belongs in Resolver, lifecycle action still belongs in TrustOps, and canonical truth still belongs in Backend.

Open Developer Gateway Start in TrustOps

Public reference path

Read governance here. Check current public proof in Resolver.

Use this site for governance and specifications. Use Resolver for public verification. Use TrustOps for acquisition, activation, lifecycle, and operational control. Use Developer Gateway for docs, schemas, route indexes, and implementation guidance.

Open Resolver Issuance Policy Revocation Policy Formal Enquiries