ECZ-ID.orgGovernance & specifications

Formal Enquiries

Formal Enquiries

Most questions are answered fastest by the surface that holds the relevant authority. Use the routing table first; write to us only if the published material does not answer your question.

INFORMATIVE Site information

Canonical URL: https://www.ecocitizenz.org/pages/formal-enquiries

Route your question

Which surface answers which question
If your question is aboutGo toBecause
Governance, specifications, definitions or authority boundariesThis site — Governance and SpecificationsDocumentary publication lives here.
Whether a specific ECZ-ID, Passport or binding is currentResolverResolver is the public read-only verification surface.
Acquisition, setup, activation, lifecycle, repair or paymentTrustOpsTrustOps operates those workflows.
Schemas, manifests, SDKs or integrationDeveloper GatewayImplementation guidance lives there.
Offers, use cases or commercial questionsecocitizenz.comCommercial discovery lives there.
A specific Passport typeThe relevant Passport site: Agents, MCP servers, APIs, IoT and connected products, Plugins, SDKs, Services and workloadsPassport discovery and acquisition live there.
Managed services or partnershipECZ-ID for MSPsThe managed-service and partner channel.

What formal enquiries are for

Appropriate

  • Clarifying published governance, specification language, authority boundaries, issuance or revocation posture.
  • Institutional review by auditors, procurement teams, insurers, regulators, platforms, partners or legal teams.
  • Questions about where a person, agent or system should go next.
  • Questions about public machine-readable routing, at a non-secret level.

Not appropriate

  • Requests to treat a reply as proof of current ECZ-ID, Passport or binding state.
  • Requests to issue, activate, revoke, downgrade, repair or otherwise change ECZ-ID state.
  • Sending private keys, secrets, tokens, raw logs, private contracts or confidential evidence.
  • Treating email, screenshots, page copy, badges or marketplace presence as authority.

How to contact us

Write to info@ecocitizenz.com. This site has no contact form and stores nothing you send.

Please include only what is needed to answer you:

Your name
So that we can address the reply.
Organisation
Optional, unless the enquiry is made on its behalf.
Reply address
The address you want the answer sent to.
Category
Governance, specification, institutional review, routing or accessibility.
Your question
With links to the pages it concerns.

Do not send phone numbers, postal addresses, identity documents or other personal data unless we specifically ask for them. How we handle enquiry emails is described in the privacy notice.

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.