Define
Specifications define identity, authority, scope, state, evidence and public reference.
PUBLISHED SPECIFICATIONS
The ECZ-ID specification index.
The public reference set for ECZ-ID identity, passport structure, authority boundaries, lifecycle state, Resolver proof, cloud and platform binding, machine-readable output and operating-surface interpretation.
Specifications explain structure. TrustOps operates customer workflows. ECZ-ID Core controls state. Resolver verifies public proof where available.
Identity
Authority
Passports
Lifecycle state
Resolver proof
Cloud binding
Machine-readable
Evidence
Core rule: Websites explain. TrustOps operates. ECZ-ID Core controls state. Resolver verifies public proof where available. Developer Gateway documents implementation routes.
SPECIFICATION INDEX
Formal references for the ECZ-ID system.
Core specification
ECZ-ID Specification
Parent identifier model, stable ECZ-ID format, identity boundary, public reference purpose and resolver-first interpretation.
Passport specificationPassport Specification
Passport scope, parent-child relationship, lifecycle state, capability boundaries and public proof projection.
Cloud and platform referenceCloud & Platform Binding Specification
Supported relationships between ECZ-ID and cloud, platform, repository, domain, API, agent, model, dataset, MCP or service identifiers.
Authority referenceAuthority Model
How authority remains scoped, time-bound, attributable and reconstructable for public reference.
Issuance referenceIssuance Policy
Why issuance must be controlled by ECZ-ID authority and not inferred from marketing, display or marketplace presence.
Revocation referenceRevocation Policy
How revoked, suspended, degraded, expired or unresolved state should stop looking operational in public interpretation.
System rationaleSystem Rationale
Why identity, authority, state, custody, time and evidence must remain publicly resolvable.
Formal routeFormal Enquiries
Governance, specification, institutional and formal public reference enquiries.
Verification surfaceResolver
Public read-only verification route for current ECZ-ID proof where available.
REFERENCE ROUTE
How public reference becomes usable.
A specification defines how a public proof route should be interpreted. It does not replace the live state check. Current public proof should be checked in Resolver where available.
Operate
TrustOps guides acquisition, setup, lifecycle, customer access and repair workflows.
Control
ECZ-ID Core controls deterministic state, entitlement and lifecycle decisions.
Verify
Resolver provides public read-only verification where proof is available.
Interpret
Humans, agents, platforms and policy systems apply their own review rules.
OPERATING SURFACES
Use the correct surface for the correct job.
Ecocitizenz.org
Governance, specifications, definitions and formal public reference. It explains structure but does not write truth.
TrustOps
Acquisition, setup, payment, lifecycle, customer access and repair workflows over backend-controlled state.
ECZ-ID Core
Deterministic state, entitlement, lifecycle, binding and public projection control.
Resolver
Public read-only verification for current state, identifiers, effective dates and machine-readable proof where available.
EVIDENCE AND SECURITY
Specification language stays tied to deterministic proof.
ECZ-ID specifications can describe evidence-grade artifacts, machine-readable outputs, Resolver projection and long-lived proof protection. They do not turn public pages into proof authority.
Where required, evidence-grade artifacts may use quantum-safe or hybrid signature approaches so long-lived proof material remains more resilient over time. ECZ-ID Core, not quantum computation, decides state.
PUBLIC REFERENCE PATH
Read here. Operate in TrustOps. Verify in Resolver.
Use this page to find the correct specification. Use TrustOps for acquisition and lifecycle action, Resolver for current public verification, and Developer Gateway for schemas and machine-readable implementation routes.