Governance
Issuance Policy
Issuance is how a stable identifier, or a scoped Passport state, becomes available for public reference. In ECZ-ID it is a backend-controlled authority event that Resolver can show as current public proof. It is not a website claim, badge graphic, directory listing or marketing statement.
INFORMATIVE DRAFT Informative policy document
Canonical URL: https://www.ecocitizenz.org/pages/issuance-policy
The issuance rule Link to section: The issuance rule
Display is not issuance. A page can explain ECZ-ID; TrustOps can guide acquisition and lifecycle action; backend authority controls issuance; and Resolver shows the current public answer.
- Backend-controlled
- Issuance is controlled through backend authority pathways. Websites, public copy, badges and directory listings do not create authoritative state.
- Resolver-projected
- Resolver is the public read-only surface for checking current public state before reliance.
- Parent-bound
- Passports and scoped proof surfaces remain attached to the parent ECZ-ID. They do not create competing identity roots.
- Machine-readable
- Issuance state is legible to people, agents, platforms and automated systems, so checks can be repeated without narrative interpretation.
Purpose Link to section: Purpose
Issuance exists so that relying parties do not need to infer identity or authority from copied text, outdated pages, private messages, screenshots, marketplace listings, directories or unofficial badges. It creates a reference point that can be resolved and re-checked.
Sequence Link to section: Sequence
Authority comes first, issuance second and public projection third.
| Step | What happens |
|---|---|
| 1. Identify the subject | The subject is distinguishable enough for a stable ECZ-ID or scoped Passport state to be attached, without relying on marketing copy. |
| 2. Check authority | Authority is scoped, attributable and controlled through backend pathways before any public state is projected. |
| 3. Record issuance | Issuance creates a reference point and lifecycle position that can later be inspected, changed, suspended, downgraded, expired or revoked. |
| 4. Project public proof | Resolver presents the current public answer. Relying parties check Resolver rather than infer state from websites or copies. |
What issuance creates and does not create Link to section: What issuance creates and does not create
Issuance creates
- An ECZ-ID or scoped Passport state that can be resolved.
- A public proof surface that people and systems can check.
- A time-bound reference point for authority, state and lifecycle history.
- A machine-readable path for integration, audit, procurement and review.
Issuance does not
- Certify business quality.
- Guarantee compliance, safety, performance or outcomes.
- Replace regulators, auditors, insurers, courts or institutional decision-makers.
- Make a website, badge, marketplace listing or directory entry authoritative.
For relying parties and automated systems Link to section: For relying parties and automated systems
Agents, MCP servers, platforms, procurement tools, insurers, auditors and integration systems treat Resolver as the public proof surface and re-check issuance state rather than trust stale presentation. Developer Gateway supports schemas, route indexes and implementation guidance; it is not itself public proof.
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.
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.
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.
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, Issuance Policy, DRAFT, https://www.ecocitizenz.org/pages/issuance-policy.
Fields that do not yet exist for this document, such as a document ID or version, are omitted rather than invented.