Governance
Revocation Policy
When authority or state no longer stands, public proof stops standing too. Revocation is not a website edit: it is a backend-controlled state transition that Resolver projects publicly.
INFORMATIVE DRAFT Informative policy document
Canonical URL: https://www.ecocitizenz.org/pages/revocation-policy
The revocation rule Link to section: The revocation rule
Resolver output reflects current backend state. A revoked, suspended, degraded, expired, mismatched or unresolved state does not continue to look operational.
- Backend-controlled
- Revocation is controlled through backend authority pathways, not website text, badges, directories or presentation layers.
- Resolver-projected
- Resolver displays current public state so relying parties can check before acting, integrating, paying, approving or routing.
- Time-bound
- Historical state remains reconstructable while the current reliance posture changes.
- Machine-readable
- Public state is legible to people, agents and automated systems, so checks can fail closed where a relying party’s own policy requires it.
State outcomes Link to section: State outcomes
| State | Meaning for public reliance |
|---|---|
| Revoked | No longer treated as operational. Resolver does not present it as currently valid. |
| Suspended | Current reliance is paused. History can be preserved while present-tense reliance is prevented. |
| Degraded | Still visible, but its operational posture is reduced because a required condition is no longer fully met. |
| Expired | The relevant time window has passed. Expiry is shown explicitly rather than left to stale reliance. |
| Mismatch | A binding, identifier, manifest or referenced state no longer matches the expected canonical record. |
| Unresolved | Required public state cannot currently be confirmed. Unresolved is not approved, active, verified or safe to rely on. |
History remains reconstructable Link to section: History remains reconstructable
Revocation does not erase the historical record. It changes the present-tense reliance posture while prior authority and state remain reconstructable where the underlying records support it.
Stale proof does not keep operating Link to section: Stale proof does not keep operating
A relying party should not have to infer revocation from missing pages, stale documents, private emails or manual explanation. Resolver exposes the current public answer; the relying party then applies its own policy, for example review, hold, routing or fail-closed handling.
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.
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, Revocation Policy, DRAFT, https://www.ecocitizenz.org/pages/revocation-policy.
Fields that do not yet exist for this document, such as a document ID or version, are omitted rather than invented.