IoT Passport
Use for a connected physical device or device identity module that needs a resolvable machine identity.
Open IoT estate ↗ROBOTICS, DRONES & AUTONOMY
GIVE THE OPERATING SURFACE A REAL IDENTITY BEFORE PHYSICAL CONSEQUENCE.
Robots, drones, autonomous vehicles and machine-operated systems can change physical state, access, custody, infrastructure and liability. ECZ-ID applies the same accountability chain: identify the real operating surfaces, establish authority and Intent, evaluate relevant state, then preserve what was recorded.
MODEL THE REAL SURFACES
Do not invent a new identity class for every machine shape.
At launch, use the canonical Passport family that matches the enduring surface being operated. A robot or autonomous system may legitimately involve more than one ECZ-ID because different accountable surfaces perform different jobs.
Service & Workload Passport
Use for the enduring service or workload behind a machine-operated runtime—not a pod, replica, process or region.
Open Workloads estate ↗Agent Passport
Use where an AI or agentic actor makes or proposes decisions for the organisation.
Open Agent estate ↗API Passport
Use for an API surface that agents, applications or machine systems call.
Open API estate ↗MCP Passport
Use when the accountable surface is an MCP server. Individual tools inside it are not separate Passports.
Open MCP estate ↗Business Passport
The organisation remains the accountable parent context for the machine surfaces it operates.
Explore Business Passport →THE CONSEQUENCE BOUNDARY
Before. At. After.
Physical autonomy makes the distinction especially important: permission to reach a controller is not Intent, a decision is not the action, and a Receipt is not automatic proof that every real-world assertion was true.
Before
Identity, authority, delegation, Intent, relevant state, policy and constraints establish the basis for action.
At
Where configured, IntentControl can evaluate whether the proposed action should proceed. The actual machine action still runs—or does not—in the customer's system.
After
Receipts, evidence, LedgerCore and Resolver support what was recorded, integrity, retrieval and later re-check.
TRUTH BOUNDARY
Accountability infrastructure is not safety certification.
ECZ-ID does not certify a robot, drone or vehicle as safe, licensed or legally permitted to operate. Regulators, operators, insurers and relying parties retain their own obligations and judgement. ECZ-ID provides identity, authority, Intent, current-state and evidence context around the machine interaction.