The Passport System
One identity spine. Thirty-three child passports. Accountability where it actually lives.
ECZ-ID does not collapse modern operations into one vague company credential. It begins with the required ECZ-ID Business Passport™, then expands into the specific passports needed for the software, products, machines, infrastructure, transfers, and operational systems another party may need to trust, inspect, or rely on.
The parent passport comes first
Every ECZ-ID deployment begins with the ECZ-ID Business Passport™. It is the required parent for the wider passport system, and its tiers are Declared, Verified, and Assured. The parent layer creates continuity of identity and provides the root surface that the rest of the system attaches to over time.
This matters because businesses do not just need to be named. They need to be resolvable, stable, and capable of carrying accountable state across operations, counterparties, software, evidence, lifecycle changes, and public verification.
Declared
The starting point of identity continuity and public resolvability. It establishes the root layer, but not the fullest operational trust posture on its own.
Verified
A stronger operating posture for businesses that need clearer eligibility, wider seriousness, and stronger trust across real counterparties and use cases.
Assured
The strongest parent posture and the insurer-recognised tier within the locked parent model. It is the highest-trust parent position in the core structure.
Why the system expands through child passports
A company name is not enough to explain what is actually running, shipping, deciding, exposing, moving, or failing. Modern risk lives in APIs, AI models, datasets, devices, software supply chains, products, custody chains, robots, drones, freight systems, industrial sites, financial authority flows, and other operational objects.
That is why ECZ-ID expands through child passports instead of pretending one generic credential can capture every accountability surface. The passport system maps trust to the real objects and operating domains that create dependency, liability, or public reliance.
Child passports are scopes of accountability
A passport is not decorative. Each passport is a scope of accountability. It defines what can go wrong, who is responsible, what evidence matters, and what insurers or regulators would expect that surface to prove.
That is what turns the passport system from a catalogue into infrastructure. It lets ECZ-ID map public trust and operational responsibility across very different object types without collapsing them into one incoherent credential.
The structure of the passport system
Core Digital & Operational
Covers agents, cyber resilience, APIs, AI models, datasets, IoT devices, and software supply chains.
Product, Risk & Transfer
Covers product identity, custody transfer, and risk-policy-linked operating surfaces where accountability must persist beyond a basic business listing.
Robotics
Covers industrial, public-space, and domestic robot accountability where machine action, authority, and current trust state must remain legible.
Road & Freight Mobility
Covers robotaxis, autonomous cars, autonomous haulage, cross-border haulage, and high-value cargo trucks where the operating object itself becomes part of the accountability surface.
Aerial Mobility — Drones
Covers the D1 to D4 drone classes, where machine identity, operating state, and responsibility must remain independently resolvable.
Infrastructure-Grade Additions
Covers intermodal transfer, industrial sites, critical infrastructure, funds-flow authority, marine vessels, cargo containers, aircraft, and aviation components. These are infrastructure-grade trust surfaces, not marketing accessories.
Control & Trust Overlays
Covers platform safe-harbour, identity continuity, and licensed infrastructure operation where the system needs additional control or reliance overlays on top of the core identity spine.
Resolver-verifiable and machine-readable by design
The passport system is built so another party does not need to rely on static claims alone. Parent identity and attached passport state resolve outward into public verification, while the wider system remains machine-readable by design so software, platforms, and agent-native environments can consume trust surfaces in a structured way.
This is the difference between saying something is trusted and making that trust inspectable.
PulseGuard™, LedgerCore™, and derived readiness
The passport system does not stop at naming assets. PulseGuard™ evaluates present-tense trust state, while LedgerCore™ records legally decisive state transitions. They are complementary and non-overlapping parts of the structure.
PulseGuard asks whether an identity or passport is safe to transact with right now. LedgerCore records what was true, when, and who was accountable. Insurability Readiness™ is then derived from active ECZ-ID passports and LedgerCore™ evidence. It is not a standalone product that can be bought or manually edited.
How a business should think about choosing passports
The right question is not “Which badge looks best?” It is “Which accountability surfaces do we actually need to make legible?”
Build the identity layer around what is real.
Start with the parent passport. Add the child passports that match the systems, products, machines, and operations you actually run. Obtain and manage capability in TrustOps. Verify state in Resolver.