Trust Gallery
Calm, proof-oriented examples of ECZ-ID trust infrastructure in action. See how resolver-verifiable identity material appears in badges, resolver responses, manifests, and real deployment patterns—from single-agent verification to multi-domain orchestration.
What ECZ-ID Proof Looks Like
ECZ-ID produces machine-readable and human-verifiable artefacts. The samples below are illustrative placeholders only — not live truth. Resolver returns live state for an exact ECZ-ID at request time.
EXAMPLE ONLY — not live truth. Resolver returns live state at request time. Trust badges are gateways. They link or scan through to a Resolver page on resolver.ecocitizenz.org, which holds the current proof. Badges are not proof on their own.
How to use ECZ-ID badges safely →{
"ecz_id": "ECZ-GB-7K2M4P::ROBOTAXI-7H2K9P",
"status": "verified",
"entity_type": "autonomous_vehicle",
"resolver_state": "active",
"evidence_records": [
"safety_evidence_record",
"operational_domain",
"insurance_evidence_reference"
],
"last_evidence_update": "2026-04-06T10:23Z",
"operator": "ECZ-GB-7K2M4P"
}EXAMPLE ONLY — not live truth. Resolver returns live state at request time. Resolver returns structured, machine-readable identity records. Any party can query. No account required. Public verification by design.
{
"manifest_schema": "ecz-manifest/v1",
"entity": "ECZ-GB-5R8T3W::D2-DRONE-4F8A2C",
"class": "D2",
"operator": "ECZ-GB-5R8T3W",
"mission": "infrastructure_inspect",
"corridor": "authorised",
"geofence": "compliant",
"sensors": ["lidar", "rgb_4k"],
"calibration": "evidence_recorded"
}EXAMPLE ONLY — not live truth. Resolver returns live state at request time. Identity manifests carry the full context of an entity's identity, capabilities, and evidence-state status. Attached to every action and interaction.
Trust Infrastructure in Action
Every pattern below is an illustrative example: it shows how the role split — operator setup in TrustOps, activation by ECZ-ID core systems, public proof at the Resolver — applies to a scenario. None of these is presented as a live-proven customer deployment.
Agent-to-Agent Verification
Illustrative example: two agents verify each other's identity before exchanging data, with decisive events recorded where receipts are emitted.
Agent A Presents Credentials
Agent A includes its ECZ-ID credentials in the request. Credentials contain identity, capabilities, delegation chain, and current resolver state.
Agent B Queries Resolver
Agent B sends Agent A's ECZ-ID to Resolver. Returns current status, resolver state, active evidence records, and capability confirmation.
Resolver-Checked Interaction
Interaction proceeds with resolver-verifiable identities on both sides. Where decisive receipts are emitted, a tamper-evident record links both agents and the outcome.
Custody Chain Transfer
A product passes through multiple custodians. Each transfer is evidence-linked through ECZ-ID.
Manufacture
Product receives ECZ-ID at creation. Composition, origin, and initial custody recorded with manufacturer identity.
Warehouse
Custody transfer to warehouse operator. Condition evidence recorded. Chain extended with evidence-linked handoff and timestamp.
Transport
Custody transfer to logistics provider. Route, vehicle identity, condition monitoring, and handler verification.
Delivery
Final custody transfer to end recipient. Complete chain verifiable through Resolver by any authorised party.
IoT Fleet Evidence Records
Thousands of devices reporting telemetry, each with resolver-verifiable identity and firmware evidence record.
Device Identity
Each device carries an ECZ-ID with firmware evidence record, calibration records, and operational boundaries, designed so identity survives reboots and firmware updates.
Data Provenance
Telemetry can be attributed to a resolver-verifiable device where the operator wires that attribution in. Data consumers can check device identity, calibration status, and last evidence update time.
Fleet Monitoring
Operators can monitor resolver state across a fleet and route anomalies to review under their own policy. Firmware updates can carry evidence chains; decommissioned devices are identity-revoked.
Autonomous Vehicle Credential Verification
Illustrative example: a robotaxi presents resolver-verifiable identity and safety evidence state to a ride-hail platform for review before accepting passengers. ECZ-ID supplies the evidence; it is not an autonomous-vehicle safety approval.
Vehicle Identity
The robotaxi carries the appropriate Road & Freight Mobility passport — for example a Robotaxi Passport — with resolver-verifiable safety evidence state, operational authority, and insurer-legible evidence.
Platform Verification
The ride-hail platform queries Resolver to verify identity, current safety evidence record, operational domain validity, and insurer evidence references before dispatching.
Passenger Trust
Passengers see resolver-verifiable identity and safety evidence state in-app. Every trip logged with resolver-verifiable vehicle identity, route verification, and safety event records.
Drone Mission Evidence Records
Illustrative example: a D2 commercial drone presents its declared mission context, geofence boundaries, and operator identity for review before entering controlled airspace.
Mission Identity
The drone carries the appropriate D1–D4 Drone Passport with mission plan, corridor authorisation, geofence boundaries, and operator identity link.
UTM Integration
A UTM system can check drone identity and declared mission context via Resolver at request time. ECZ-ID does not grant flight or airspace authorisation — that remains with the aviation authority.
Data Provenance
Survey data, imagery, and sensor readings carry verified drone identity. Clients receive data with full provenance chain from capture to delivery.
Humanoid Robot Deployment Verification
Illustrative example: a service humanoid presents its identity, safety evidence records, and interaction boundaries to a hospital facility for review using a Public-Space Robot Passport with humanoid profile. Operating approval remains the facility's decision.
Robot Identity
The humanoid carries a Public-Space Robot Passport with humanoid-specific profile (Assured tier). resolver-verifiable capability evidence, interaction boundaries, strength limits, and emergency protocols are recorded as evidence.
Facility Verification
Hospital facility management queries Resolver to verify safety evidence records, operational boundaries, and interaction protocols before granting access to patient areas.
Insurance & Audit
An insurer can query current resolver state and the safety evidence record at request time. Where the operator logs incidents with robot identity, accountability review is faster. Insurer acceptance remains the insurer’s decision.
Multi-Agent Compliance Workflow
A compliance agent coordinates with research and evidence agents. Each carries resolver-verifiable identity and delegation chains.
Primary Agent
The compliance agent holds the primary ECZ-ID and delegates specific tasks to specialised subagents with scoped permissions and time-bounded delegation.
Delegated Agents
Research and evidence agents carry delegated ECZ-ID credentials. Every action traces back through the delegation chain to the primary agent and its operator.
Audit Trail
Complete compliance workflow is auditable: every agent, every action, every data source, every decision—all linked to resolver-verifiable identities with timestamps.
From Gallery to Production
The patterns above are documented integration patterns: the role split and the Resolver checks they rely on are described on this site, and setup runs through TrustOps. Your own implementation work — wiring, logging, and policy — remains yours.
Agent Starter Kits
Pre-built templates with ECZ-ID identity hooks. Start building resolver-verifiable agents in minutes once credentialed.
Browse Starter Kits →Developer Onboarding
Step-by-step guide from first contact to production deployment.
Start Onboarding →See It For Real
These patterns illustrate deployment models. Verify real ECZ-IDs through Resolver, or provision your own through TrustOps.