EcoCitizenz

EcoCitizenz

ECZ-ID Public Resolver

Public proof surface

ECZ-ID Public Resolver

Public proof surface for ECZ-ID records. Resolve identity, authority, state, bindings, evidence, and machine-readable reliance for an ECZ-ID. Designed for humans, automated systems, insurers, platforms, auditors, procurement teams, security tools, and AI agents.

Example format: ECZ-GB-ABC123Parent ECZ-ID format: ECZ-XX-XXXXXXChild passport format: ECZ-XX-XXXXXX::AGENT_CREDENTIAL-XXXXXXIntentional resolution only. No directory, no search of companies.

Intentional resolution only. Resolver is read-only. It does not issue ECZ-IDs, modify records, activate passports, or process payments.

Resolve

What Resolver answers

Is this ECZ-ID publicly resolvable?

Resolver returns whether a published, public-projection record exists for the requested ECZ-ID.

What is the current public state?

Active, suspended, revoked, degraded, mismatched, proof-unavailable, or unavailable, as published.

What parent tier is published?

The parent tier and authority semantics published on the record. Tier reflects published verification only.

What binding, evidence, ledger, and public proof is published?

Bindings, PulseGuard state when published, evidence receipts, and LedgerCore™ public receipts.

What should machines do before reliance?

Fetch the canonical machine JSON, re-verify before reliance, and fail closed where policy requires.

What must not be inferred?

No regulatory approval, no insurance, no safety certification, no agent authority from a parent record.

For humans, machines, and institutions

One Resolver record. Three reliance audiences.

For humans

Read the current Resolver state and reliance boundaries. Use the human-readable view to understand what the record says and does not say.

For machines and agents

Use the machine JSON. Do not scrape human prose for policy. Re-verify before reliance and fail closed where policy requires.

For institutions

Insurers, platforms, procurement teams, auditors, and security tools should use the live Resolver and machine JSON for policy gates and audit trails.

Proof surfaces

Proof surfaces and their roles

Resolver

Resolver = live public proof surface.

Machine JSON

Machine JSON = canonical machine projection.

QR

QR = route to Resolver. The QR encodes a Resolver URL only.

Trust Card

Trust Card = human share asset, not proof.

Print / PDF

Print/PDF = Snapshot only — may become stale, not live proof.

Reliance boundaries

What Resolver does not mean

  • Regulatory decisions. Resolver provides public evidence state and machine-readable verification context. Final approval remains with the relevant authority.
  • Insurance decisions. Resolver provides evidence inputs for risk and underwriting review. Cover, quotes, and policy decisions remain with insurers.
  • Resolution is not safety certification.
  • Resolution is not compliance certification.
  • Resolution is not a statement of business quality.
  • Resolution is not KYB or KYC completion.
  • Resolution does not confer agent authority unless an Agent Credential child passport proof exists.
  • Resolution is not live monitoring unless PulseGuard state is published.

Machine policy

Recommended machine policy

  • Recommended use: fetch the canonical machine JSON for the ECZ-ID.
  • High-risk action: fail closed if the record is revoked, suspended, degraded, mismatched, proof-unavailable, unavailable.
  • Re-verify before reliance.
  • Do not scrape human prose for policy. Use the machine JSON fields.

Canonical Resolver pattern

https://resolver.ecocitizenz.org/p/{ecz_id}

Canonical machine JSON pattern

https://api.ecocitizenz.com/api/p/{ecz_id}.json

Intentional resolution only

Intentional resolution only

This page resolves a specific ECZ-ID. It is not a directory. It is not a search engine for companies. It does not reveal private records. Public fields are limited to the public projection.

Resolver handoff

Resolver handoff

Resolver handoff lets one system pass a live Resolver URL and machine JSON endpoint to another system for verification. The handoff is a pointer to live Resolver proof, not proof itself. The receiving system should fetch the machine JSON, evaluate the policy fields, and fail closed where required.