ECZ-ID LedgerCore Evidence Anchoring Add-on™
Adds a TrustOps-routed path for anchoring additional evidence references and receipt events to the customer's ECZ-ID context where supported. Developer Gateway explains the route; TrustOps and ECZ-ID Core handle evidence actions and lifecycle.
Who it is for: Businesses, platforms, regulated operators, insurers, procurement teams, and dispute-sensitive customers that need stronger evidence continuity around important events, documents, checks, or state changes.
In plain terms
LedgerCore™ Evidence Anchoring is the add-on that records decisive lifecycle and evidence events where supported.
The real-world problem
What this removes
Counterparties relying on a passport stack often need a way to anchor decisive lifecycle and evidence events for later review by insurers, adjudicators, or regulators.
Ambiguity removed
Removes ambiguity about whether a decisive event was recorded and is referenceable.
What it binds / includes
Scope of accountability
Binds decisive events (issuance, activation, authority changes, child passport creation, revocation, bundle activation, badge state changes, receipt references) to a resolver-referenceable record.
Parent requirement: Verified or Assured ECZ-ID Business Passport™. Assured recommended for regulator, insurer, or dispute-sensitive use.
Detailed inclusions are confirmed in TrustOps. Developer Gateway documents the model only.
Stack contributions
What PulseGuard™, LedgerCore™, and Resolver contribute
PulseGuard™
PulseGuard™ contributes present-state monitoring such as liveness, freshness, revocation or suspension state, and posture changes where supported by the activated passport/package.
LedgerCore™
This add-on is what gives LedgerCore™ its evidence-anchoring contribution to the stack, where supported.
Resolver
Resolver shows references to anchored events where supported. The ledger record is referenceable, not a public dump of every event.
Badge / mandate plate
Where this product has an ECZ-ID badge or mandate plate, the badge is an embeddable visual pointer to the Resolver state. The badge is not proof by itself; the Resolver check is the proof surface.
Insurability Readiness™ impact
Insurability Readiness™ is derived, free, non-sellable, and not manually editable. It is earned from the active passport stack, PulseGuard state, and LedgerCore evidence where supported. You do not buy readiness; you earn it.
Boundary of claim
What this product does not claim
- · Does not anchor every customer document.
- · Does not make all events public.
- · Does not by itself constitute legally conclusive evidence.
Guided flow
Six steps from need to resolved state
- 01
Understand the need
Decide what commercial friction you are trying to remove. Developer Gateway documents the model. It does not determine eligibility, issue credentials, or create entitlements.
- 02
Confirm parent requirement
Every child passport, package, and add-on attaches to an active ECZ-ID Business Passport™. Verified or Assured may be required (per TrustOps).
- 03
Review what this product does
Check what is bound, what is included, and what it does not claim. No safety, certification, approval, or partnership claim is made on this page.
- 04
Continue to TrustOps
Acquisition, activation, payment, and lifecycle happen in TrustOps. Developer Gateway only routes the handoff.
- 05
Return to Developer Gateway
After TrustOps, return here for next-step docs and related guidance. Developer Gateway still does not prove current state.
- 06
Check current proof in Resolver
Current proof must be checked in the public Resolver. Copied metadata, screenshots, or website claims do not replace Resolver.
TrustOps midpoint
Acquisition, setup, payment, and lifecycle happen in TrustOps
Developer Gateway only routes. It does not host checkout, change canonical state, issue credentials, or replace Resolver proof. TrustOps owns the operational state for this product.
Continue evidence setup in TrustOps ↗TrustOps URL: https://trustops.ecocitizenz.com/start
Return path
Come back here for next-step docs
After TrustOps completes acquisition or activation, return to Developer Gateway for related docs and guided next steps. Developer Gateway still does not prove current state. Current proof remains in Resolver.
Resolver proof
Current proof must be checked in Resolver
Copied metadata, screenshots, badges on third-party websites, or any claim made on Developer Gateway do not replace Resolver. The Resolver is the sole public proof surface for ECZ-ID.
Open Resolver ↗Resolver URL: https://resolver.ecocitizenz.org
Recommendation
Find your recommended starting point
Enter your website URL. TrustOps will use it to recommend a starting point. Developer Gateway sends the URL only; TrustOps handles the recommendation, setup, payment, and lifecycle controls.
Developer Gateway does not host checkout, change canonical state, issue credentials, or replace Resolver proof. Current proof must be checked in Resolver.