Gallery

Trust Gallery

Calm, proof-oriented examples of ECZ-ID trust infrastructure in action. See how verified identity manifests in badges, resolver responses, manifests, and real deployment patterns—from single-agent verification to multi-domain orchestration.

Proof Artefacts

What ECZ-ID Proof Looks Like

ECZ-ID produces machine-readable and human-verifiable artefacts. These examples illustrate the outputs your systems and users will interact with.

Trust Badge
ECZ-ID Verified
Agent · Trust Score 94
Identityecz:agent:a1b2c3
StatusActive
Last Attested2 min ago

Trust badges provide at-a-glance verification status. Embeddable in dashboards, platforms, and partner portals. Machine-readable and human-verifiable.

Resolver Response
{
  "ecz_id": "ecz:vehicle:x7k9m2",
  "status": "verified",
  "entity_type": "autonomous_vehicle",
  "trust_score": 97,
  "attestations": [
    "safety_certification",
    "operational_domain",
    "insurance_valid"
  ],
  "last_attested": "2026-04-06T10:23Z",
  "operator": "ecz:org:fleet-co"
}

Resolver returns structured, machine-readable identity records. Any party can query. No account required. Public verification by design.

Identity Manifest
{
  "manifest": "ecz:manifest:v1",
  "entity": "ecz:drone:d2-4f8a",
  "class": "D2",
  "operator": "ecz:org:survey-ltd",
  "mission": "infrastructure_inspect",
  "corridor": "approved",
  "geofence": "compliant",
  "sensors": ["lidar", "rgb_4k"],
  "calibration": "attested"
}

Identity manifests carry the full context of an entity's identity, capabilities, and compliance status. Attached to every action and interaction.

Deployment Patterns

Trust Infrastructure in Action

These patterns illustrate how ECZ-ID works in real deployment scenarios across domains.

Agent-to-Agent Verification

Two agents verify each other's identity before exchanging data. Every interaction is attested and auditable.

Step 1 — Initiate

Agent A Presents Credentials

Agent A includes its ECZ-ID credentials in the request. Credentials contain identity, capabilities, delegation chain, and current trust score.

Step 2 — Verify

Agent B Queries Resolver

Agent B sends Agent A's ECZ-ID to Resolver. Returns current status, trust score, active attestations, and capability confirmation.

Step 3 — Attested Exchange

Verified Interaction

Interaction proceeds with verified identities on both sides. Immutable record links both agents, the data exchanged, and the outcome.

Custody Chain Transfer

A product passes through multiple custodians. Each transfer is verified and attested 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 attested. Chain extended with verified 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 Attestation

Thousands of devices reporting telemetry, each with verified identity and firmware attestation.

Device Identity

Each device has a hardware-anchored ECZ-ID with firmware attestation, calibration records, and operational boundaries. Identity survives reboots and firmware updates.

Data Provenance

Every telemetry reading is traceable to a verified device. Data consumers can check device identity, calibration status, and last attestation time.

Fleet Monitoring

Fleet-wide trust score monitoring. Anomaly detection triggers review. Firmware updates carry attestation chains. Decommissioned devices are identity-revoked.

Autonomous Vehicle Credential Verification

A robotaxi proves its driving credentials, safety record, and operational domain to a ride-hail platform before accepting passengers.

Vehicle Identity

The robotaxi carries the appropriate Road & Freight Mobility passport — for example a Robotaxi Passport — with verified safety status, operational authority, and insurer-legible evidence.

Platform Verification

The ride-hail platform queries Resolver to verify identity, current safety attestation, operational domain validity, and insurance coverage before dispatching.

Passenger Trust

Passengers see verified identity and safety status in-app. Every trip logged with attested vehicle identity, route verification, and safety event records.

Drone Mission Attestation

A D2 commercial drone proves its mission authorisation, geofence compliance, and operator identity 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

Unmanned Traffic Management system verifies drone identity, mission authorisation, and corridor compliance in real time via Resolver.

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

A service humanoid operating in a hospital proves its identity, safety certifications, and interaction boundaries before deployment using a Public-Space Robot Passport with humanoid profile.

Robot Identity

The humanoid carries a Public-Space Robot Passport with humanoid-specific profile (Assured tier). Verified capabilities, interaction boundaries, strength limits, and emergency protocols are attested.

Facility Verification

Hospital facility management queries Resolver to verify safety certifications, operational boundaries, and interaction protocols before granting access to patient areas.

Insurance & Audit

Insurer queries real-time trust score and safety attestation. Every interaction, movement, and incident is logged with robot identity. Operator accountability is immediate.

Multi-Agent Compliance Workflow

A compliance agent coordinates with research and evidence agents. Each carries verified 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 verified identities with timestamps.

Getting Started

From Gallery to Production

Every pattern shown here is implementable with ECZ-ID starter kits and the TrustOps provisioning platform.

Agent Starter Kits

Pre-built templates with ECZ-ID identity hooks. Start building verified agents in minutes.

Browse Starter Kits →

Developer Onboarding

Step-by-step guide from first contact to production deployment.

Start Onboarding →

Verification Model

Deep dive into the three layers of ECZ-ID verification.

Learn the Model →

See It For Real

These patterns are live in production. Verify real ECZ-IDs through Resolver, or provision your own through TrustOps.