Parent exists
The stable parent ECZ-ID identifies the organisation, operator or eligible subject.
PASSPORT SPECIFICATION
Passports are scoped accountability objects.
An ECZ-ID Passport describes a bounded operating surface under a stable parent ECZ-ID. It does not create a second identity root.
It attaches structured scope, lifecycle state, authority boundaries, evidence expectations and Resolver-verifiable public proof to the parent identity where available.
Scope
Authority
Lifecycle
Resolver proof
Parent-child
Machine-readable
Evidence
State control
Core boundary: Websites explain. TrustOps operates. ECZ-ID Core controls state. Resolver verifies public proof where available. Developer Gateway documents implementation routes.
PASSPORT RULE
Scoped state remains subordinate to parent identity.
A passport may represent an API, agent, dataset, product, robot, cyber posture, custody transfer, risk policy, infrastructure surface or other operating object.
The passport remains attached to the parent ECZ-ID and inherits its public identity context.
REFERENCE ROUTE
How a passport becomes public reference.
The parent ECZ-ID identifies the subject. The passport identifies the scoped operating surface. Resolver verifies the current public state where proof is available.
Scope is selected
A controlled passport type defines the bounded operating surface.
Instance is created
A scoped instance separates one passport object from another under the same parent.
State is controlled
ECZ-ID Core controls issuance, activation, downgrade, suspension, expiry and revocation.
Resolver projects
Resolver shows public-safe proof fields where a projection is available.
Reviewer decides
Humans, agents, platforms and policy systems apply their own review rules.
WHAT A PASSPORT DEFINES
Each passport makes one operating surface publicly referenceable.
Scope
What the passport covers, what it does not cover and which operating surface it represents.
Authority boundary
Which backend-controlled authority conditions allow the passport state to exist, change, downgrade, suspend or revoke.
Lifecycle state
Whether the passport is issued, active, suspended, degraded, expired, mismatched, revoked or unresolved.
Public proof
What Resolver may safely project for humans, agents, platforms, auditors, insurers and automated relying systems.
PASSPORT BOUNDARY
A passport strengthens reference. It does not become a guarantee.
A passport provides
- A scoped, Resolver-verifiable accountability surface.
- A public way to distinguish parent identity from operating object state.
- Lifecycle posture that can change without losing the parent ECZ-ID.
- Machine-readable reference material for integration, procurement, audit and review.
- A safer route for humans, agents, platforms and counterparties to re-check state before reliance.
A passport does not
- Create a second ECZ-ID identity root.
- Prove business quality, reputation, performance, safety or commercial suitability.
- Replace regulators, auditors, insurers, courts or institutional decision-makers.
- Make a website, badge, marketplace listing, directory entry or copied document authoritative.
- Allow public pages, agents or third-party interfaces to write ECZ-ID truth.
PARENT AND CHILD STRUCTURE
The parent ECZ-ID is stable. The passport instance is scoped.
Parent ECZ-ID
The stable identity spine for the organisation or entity. It remains non-semantic beyond the country code and unique identifier.
Passport code
The controlled passport scope, such as API, Agent Credential, Product, Dataset, Software Supply Chain, Cyber Resilience or Robotics.
Instance suffix
The derived instance suffix separates one passport instance from another without turning the suffix into a second identity root.
Resolver path
The public route used to inspect current state and safe public proof for that passport instance.
MACHINE-READABLE PUBLIC INFRASTRUCTURE
Passports must be understandable to humans and re-checkable by machines.
ECZ-ID Passport pages should support human comprehension, agent review, marketplace checks, procurement evaluation, insurer review, regulatory inspection and automated re-checking.
Machines should not infer passport state from stale pages, screenshots, badges, directory entries or copied claims.
Resolver
Use Resolver for current public state and public proof where available.
TrustOps
Use TrustOps for acquisition, setup, activation, lifecycle, repair and customer action.
Developer Gateway
Use Developer Gateway for schemas, integration guidance, route indexes and implementation patterns.
ECZ-ID Core
Truth, entitlement, eligibility, state mutation, revocation and lifecycle decisions remain backend-controlled.
EVIDENCE AND SECURITY
Passport proof stays tied to current state.
Passport evidence and public projection should remain tied to ECZ-ID Core state and Resolver verification. Public pages, badges, screenshots and copied documents should not become independent proof.
Evidence-grade passport artifacts may use quantum-safe or hybrid signature approaches where required so long-lived proof material remains more resilient over time.
PUBLIC REFERENCE PATH
Read the specification here. Check current public state in Resolver.
Use this page to understand passport structure and scope. Use Resolver for public verification where available. Use TrustOps for acquisition, activation, lifecycle and operational action. Use Developer Gateway for docs, schemas, route indexes and implementation guidance.