ECZ-ID PACKAGES & OUTCOME PACKS

Choose the package route that matches the reliance problem.

ECZ-ID packages combine the parent Business Passport, relevant child passports, add-ons, setup routes and Resolver proof around a specific business problem: agent reliance, vendor onboarding, software supply chain accountability, counterparty proof, regulated operations, commercial release, dispute reduction or machine-readable review.

The package route is designed to make the right operating surface easier to review, easier to route and easier to re-check before reliance. TrustOps handles acquisition and setup. The ECZ-ID backend controls state. Resolver projects the public answer.

View package catalogue View outcome packs Start with Business Passport
Business Passport Package Child passports Add-ons Current state Resolver proof

INSTANT VALUE

The package route in one glance.

Start with the Business Passport, choose the reliance problem, select the package route, attach the required child passports and add-ons, let backend-controlled state activate, then re-check Resolver before reliance.

01

Start with the parent

The Business Passport anchors the organisation, parent ECZ-ID, tier context and operating continuity.

02

Choose the problem

Select the reliance problem: agents, MCP, vendors, DORA, SBOM, counterparty proof, release, procurement, infrastructure or commercial outcomes.

03

Select the package

Packages group the right operating route so the buyer does not have to assemble every passport and add-on manually.

04

Attach the scope

Child passports, add-ons, binding routes and setup artefacts attach to the correct organisation context.

05

Backend state activates

The ECZ-ID backend controls entitlement, binding, lifecycle state, downgrade, suspension, revocation and public Resolver output.

06

Resolver can be checked

Humans, agents, platforms, insurers, procurement teams and policy systems can re-check current public proof before reliance.

Package route: choose the business problem, start the right TrustOps route, let ECZ-ID backend state control proof, and re-check Resolver before relying on the organisation or operating surface.

WHY PACKAGES MATTER

Most buyers do not want a passport list. They want the right route for the problem.

A business might need agent accountability, vendor review, software evidence, cyber posture, counterparty proof, package release, procurement evidence, DORA readiness, SBOM liability support, construction evidence or infrastructure operator review. Each problem needs a different combination of identity, authority, state, custody, evidence and Resolver proof.

Packages make ECZ-ID easier to buy and easier to understand. They group the relevant parent tier, child passports, add-ons, setup route and public proof boundary into a single commercial path.

CHOOSE THE PACKAGE ROUTE

Start from the reliance problem, then go to the right TrustOps section.

Agent / MCP first route

Agent, KYA & MCP packages

For agent operators, MCP providers, developers, platform teams and buyers who need agent or tool posture to be easier to review before reliance.

  • Agent Credential Entry.
  • KYA Starter and KYA Ready routes.
  • MCP Assurance and policy routes.
  • Useful for agent and tool review.
View Agent / MCP packages

Counterparty proof

Digital Counterparty Infrastructure

For websites, platforms, suppliers, merchants, APIs and counterparties that need a stronger machine-readable public proof route.

  • Counterparty proof route.
  • Website and portal posture.
  • Machine-readable guidance.
  • Resolver re-check path.
View DCI route

Supplier and buyer review

Vendor onboarding & procurement

For buyers, suppliers, procurement teams and platforms that need cleaner evidence, eligibility and review routes before supplier reliance.

  • Supplier onboarding route.
  • Procurement evidence direction.
  • Counterparty clarity.
  • Review-before-reliance fit.
View procurement route

Operational resilience

DORA vendor credentialing

For financial services, ICT providers, operational-resilience teams and vendor-risk owners that need clearer current-state vendor posture.

  • DORA-oriented route.
  • Vendor-risk posture.
  • Operational evidence path.
  • Resolver-verifiable direction.
View DORA route

Software evidence

SBOM & software supply chain

For software suppliers, APIs, platforms, procurement teams, insurers and cyber reviewers that need clearer software and supply-chain accountability.

  • Software supply-chain route.
  • SBOM liability posture.
  • Cyber and API context.
  • Evidence and Resolver direction.
View SBOM route

Outcome-led buying

Commercial Outcome Packs

For teams that want to start from the commercial outcome: release money, reduce disputes, improve eligibility, unlock review or reduce blocked reliance.

  • Outcome-led package route.
  • Trade, release and hold paths.
  • Dispute and evidence routes.
  • Business-first buying language.
View outcome packs

HOW TO PICK THE RIGHT ROUTE

Use the page that matches the buyer’s first problem.

Start with parent identity

Use the Business Passport page when the buyer needs to understand the ECZ-ID parent identity spine before choosing packages.

Open Business Passport page

Start with agents

Use the Agent Credential & KYA page when the buyer is operating, selling, reviewing or relying on agents.

Open Agent / KYA page

Start with MCP targets

Use the MCP Resolver Posture page when the buyer needs a server, tool, API, package or provider surface to be easier to review.

Open MCP page

Start with a corridor

Use the Corridors page when the buyer is unsure and needs a guided map across infrastructure, software, supply chain, mobility, procurement and commercial routes.

Open Corridors

Start with the full catalogue

Use TrustOps when the buyer is ready to browse parent passports, child passports, packages and add-ons from one acquisition surface.

Open full catalogue

Start with machine-readable guidance

Use Developer Gateway when the buyer or technical team needs schemas, route indexes, examples and integration guidance.

Open Developer Gateway

PUBLIC PROOF BOUNDARY

Packages guide acquisition. Backend state controls proof. Resolver is where public proof is checked.

This website explains and routes. TrustOps handles acquisition, setup, payment and lifecycle. The ECZ-ID backend controls entitlement, binding and current state. Resolver is the public proof surface for read-only re-checks.

A package is not a blanket safety claim, platform approval, compliance guarantee or proof that every related object is acceptable. It is a guided route that connects the right operating surfaces to the right ECZ-ID context.

Website explains TrustOps operates Backend controls state Resolver proves Machines re-check

HOW IT WORKS

From package selection to resolver-verifiable operating route.

01

Identify the reliance problem

Decide whether the issue is agent review, MCP posture, vendor onboarding, DORA, SBOM, counterparty proof, release, procurement, dispute or infrastructure accountability.

02

Start from the parent passport

The Business Passport anchors the accountable organisation and provides the parent context for downstream ECZ-ID routes.

03

Choose the package route

The package groups the relevant passports, add-ons, setup path and Resolver-facing proof boundary for the buyer’s problem.

04

Complete setup in TrustOps

TrustOps handles acquisition, setup, customer access and lifecycle control. It does not locally decide public proof state.

05

Backend-owned state controls proof

Resolver output depends on backend-owned activation and lifecycle state. Checkout, website copy and local files do not become proof by themselves.

06

Re-check before reliance

Humans, agents, insurers, platforms, procurement teams and policy systems can re-check Resolver before access, review, adoption or reliance.

MACHINE-READABLE ROUTE

Packages must be understandable by humans, agents and operating systems.

The best package route should be clear to buyers, developers, agents, procurement systems, insurers, platforms and AI governance workflows. Each surface should be able to understand what the package is for, where setup happens and where proof is checked.

Use TrustOps for acquisition and lifecycle. Use Resolver for public proof checks. Use Developer Gateway for schemas, examples, route indexes, `.well-known` patterns and integration guidance.

NEXT STEP

Choose the package route that matches your reliance problem.

Open TrustOps to review the package catalogue, or start from Commercial Outcome Packs when the buyer’s priority is release, eligibility, evidence, dispute reduction or blocked reliance.

View packages View outcome packs View corridors