Website
Explains and routes.
Ecocitizenz.com frames the problem, explains ECZ-ID, introduces the operating model, and routes visitors to TrustOps, Resolver, governance material, corridor pages, or specialist guidance.
TRUST & RESOLVER
Trust does not come from websites. It is resolved through the right surface.
A website can explain a business, product, agent, API, platform, or operating surface. It can route visitors and show where to begin. But it should not be the authority for identity, authority, state, custody, evidence, or accountability.
ECZ-ID separates explanation from verification. Public pages explain. TrustOps handles acquisition and lifecycle. Backend-owned truth remains deterministic. Resolver is where relying parties check current public proof before decisions are made.
Websites explain
TrustOps operates
Backend truth decides
Resolver proves
Machines can re-check
THE TRUST BOUNDARY
ECZ-ID becomes stronger because no public page becomes the proof source.
Most trust surfaces blur the boundary. A profile says one thing. A badge suggests another. A document goes stale. A marketplace listing changes. A screenshot survives after the state behind it has moved.
ECZ-ID avoids that weakness by separating the public explanation layer from the public proof layer. The website can explain and route. TrustOps can operate the customer journey. Backend truth can decide state. Resolver can project the current public answer.
TrustOps
Acquires and operates.
TrustOps is where ECZ-ID capability is discovered, acquired, activated, configured, managed, renewed, downgraded, revoked, or controlled through the customer lifecycle.
Backend truth
Determines state.
Backend-owned records, deterministic eligibility, binding state, lifecycle rules, LedgerCore™ events, and PulseGuard™ current-state logic determine what can be projected.
Resolver
Projects public proof.
Resolver is the public verification surface. It allows humans, agents, platforms, insurers, regulators, procurement teams, and counterparties to check safe, machine-readable proof output.
WHAT RESOLVER IS FOR
Resolver gives relying parties a public place to check the current answer.
Resolver is not a marketing page. It is not a trust badge. It is not the checkout surface. It is the public proof surface where current ECZ-ID state can be checked before reliance.
When another party needs to review, onboard, insure, connect to, approve, buy from, or let a system act, Resolver gives them a cleaner place to check what is publicly resolvable now.
Identity
Who or what is being relied on?
Resolver points relying parties toward the relevant ECZ-ID identity spine, so the surface being checked is linked to an accountable operating reference.
Authority
Who is accountable for it?
Public proof can show the resolver-visible relationship between an operating surface and the accountable organisation or operator, without turning the website into authority.
State
What is current now?
State can change. Resolver gives relying parties a place to check whether public proof is active, degraded, suspended, revoked, expired, mismatched, or unresolved where available.
Evidence
Where can proof be referenced?
Resolver can point to public-safe evidence references and machine-readable outputs while keeping private operational data out of the public verification surface.
BADGES AND PUBLIC SIGNALS
Badges carry attention. Resolver carries the answer.
A badge, link, QR code, directory entry, product page, developer listing, agent profile, or marketplace surface can point to ECZ-ID proof. None of those surfaces should be treated as the authority by themselves. They should route the relying party back to Resolver.
Badge links outward
QR opens Resolver
Resolver shows current state
Machines can re-check
MACHINE-READABLE PUBLIC PROOF
Resolver is built for humans and machines to check before reliance.
Human readers need clarity. Machines need structured output. Platforms, agents, APIs, procurement workflows, insurers, marketplaces, and governance systems need a proof surface they can route to and re-check without scraping claims from websites.
That is why ECZ-ID preserves the machine-readable / machine-verifiable posture. Public proof should be understandable to a person and usable by systems that need to check identity, state, and accountability before acting.
WHEN TO USE RESOLVER
Use Resolver when another party needs a cleaner public answer.
Before onboarding
Check the public ECZ-ID proof surface before onboarding a supplier, agent, API, platform, product, system, operator, or counterparty.
Before access
Route reliance to Resolver before allowing a software surface, tool, API, agent, server, marketplace participant, or platform workflow to act.
Before money moves
Check identity, authority, state, and public proof before payment, capital release, procurement, trade finance, or high-value commercial decisions.
When state changes
Re-check Resolver when authority, lifecycle state, capability, binding posture, package status, or public proof has changed.
When evidence matters
Use Resolver as the public reference point when disputes, audits, underwriting, platform reviews, procurement checks, or regulatory questions need a cleaner starting point.
When machines rely
Let agents, platforms, APIs, and automated workflows resolve public proof instead of relying on unstructured text, screenshots, or static claims.
FORMAL PUBLIC MATERIALS
Governance and specifications sit on the infrastructure surface.
Ecocitizenz.com is the commercial and explanatory website. It helps visitors understand the system and route to TrustOps or Resolver.
Ecocitizenz.org is the formal public infrastructure and specification surface for ECZ-ID governance, issuance, revocation, authority, resolver behaviour, machine-readable proof, and system documentation.
NEXT STEP
Open Resolver before reliance. Start in TrustOps to obtain ECZ-ID.
Use Resolver to check current public proof. Use TrustOps to obtain ECZ-ID, activate passports, packages, bindings, and proof surfaces, and manage the operating lifecycle.