Published specifications
Read the formal specification set.
ECZ-ID specifications define how identity, authority, passport scope, lifecycle state, public proof, machine-readable outputs, and operating-surface boundaries are structured.
The specification rule
Public proof must be structured before it can be relied on.
A page may explain ECZ-ID. Resolver provides public verification. TrustOps handles acquisition, activation, lifecycle, and payment. Backend truth remains canonical.
Specification index
Each reference has one job.
Core specification
ECZ-ID Specification
Defines the parent identifier model, stable ECZ-ID format, public reference purpose, canonical identity boundaries, and resolver-first interpretation rules.Passport specification
Passport Specification
Defines scoped passport structure, parent-child relationship, passport state, authority boundaries, capability boundaries, and public proof projection.Authority reference
Authority Model
Defines why authority must be formal, scoped, time-bound, revocable, and reconstructable before state can become canonical.Issuance reference
Issuance Policy
Defines why issuance must be resolver-first and why display, marketing, marketplace, or badge presence must not be mistaken for issuance.Revocation reference
Revocation Policy
Defines why revoked, suspended, degraded, expired, mismatched, or unresolved state must not continue to look operational.System rationale
System Rationale
Explains why identity, authority, state, custody, time, and evidence must remain publicly resolvable rather than inferred from presentation.Human and machine reference
Specifications are for people, agents, platforms, reviewers, and systems.
The ECZ-ID public specification layer is designed to be understandable to humans and legible to machines. It supports procurement review, platform review, agentic workflows, integration planning, audit preparation, and deterministic public reference.
What specifications do not do
- They do not issue ECZ-IDs.
- They do not activate capability.
- They do not process payment.
- They do not replace Resolver verification.
- They do not replace backend authority.
Operating-surface routing
Use the correct surface for the correct job.
Ecocitizenz.org
Public governance, specifications, definitions, and formal reference material. This site explains the rules but does not write truth.
Resolver
Public verification surface for authoritative current state, identifiers, effective dates, and machine-readable proof outputs.
TrustOps
Acquisition, activation, lifecycle, customer access, operational setup, payment, and guided control over backend-owned truth.
Developer Gateway
Schemas, route indexes, implementation guidance, integration patterns, agent-facing docs, and machine-readable developer material.
Public reference path
Read specifications here. Check current public proof in Resolver.
Use this page to find the correct specification. Use Resolver for public verification. Use TrustOps for acquisition and lifecycle action. Use Developer Gateway for schemas, implementation guidance, route indexes, and machine-readable integration patterns.