Establish identity
Start with the Business Passport and the canonical free machine-surface Passport that matches what actually operates.
Seven free Passports →COMMERCIAL ROUTES
START WITH THE RELIANCE PROBLEM. USE THE CURRENT ECZ-ID LAYERS TO SOLVE IT.
ECZ-ID no longer asks a buyer to understand a catalogue of specialised Passport variants before they can start. Establish the accountable organisation and the real machine surface, then add the current control, monitoring, assurance, evidence or scale capability the consequence requires.
THE CURRENT ENTRY PATH
Identity → capability → proof.
Use the simplest route that matches the real decision. Older package designs remain preserved as product-development IP; they are not presented here as current launch offers unless the underlying product is active in the catalogue.
Add authority / assurance
Use current products such as KYA Authority or MCP Assurance when a higher-value reliance case needs stronger accountable context.
Agent ↔ MCP route →Add control / current state
Use Intent, IntentControl, Watch and PulseGuard where the action or reliance case needs bounded intent, decision or current-state context.
Control layer →Add evidence
Use Receipts, LedgerCore and Resolver when the case needs a retrievable record, integrity, retention or later re-verification.
Evidence layer →Add regulatory / software routes
DORA and SBOM product families remain current commercial pathways where those specific review problems apply.
DORA → SBOM →Scale the estate
AEC and Graph support growing machine estates, relationship context and operational scale.
Open TrustOps ↗START FROM THE OUTCOME
Route people to the specialist surface that already matches their problem.
Procurement / supplier review
Organisation accountability, machine scope, current state and public re-check before reliance.
Procurement guidance →Agent / MCP trust
Free identity first, then KYA Authority or MCP Assurance where reliance requires it.
Agent ↔ MCP guidance →Software / SBOM
Publisher, software and supply-chain accountability with a current SBOM commercial route.
SBOM guidance →Operational resilience / DORA
Vendor and ICT operational-resilience review with active DORA commercial products.
DORA guidance →Cloud / platforms
Provider-neutral accountability without replacing provider-native IAM or workload identity.
Cloud & platform guidance →MSP / MSSP
Turn machine trust into a repeatable managed-client service through the dedicated MSP estate.
MSP estate ↗Robotics / autonomy
Map physical and autonomous systems onto the canonical machine-surface Passports and consequence boundary.
Robotics guidance →Audit / insurance / evidence
Understand what was proposed, decided, done and recorded—and what can be re-checked later.
Evidence route →COMMERCIAL TRUTH
A route can guide acquisition. Only current catalogue and backend state determine what is actually available.
Website copy does not make a DRAFT product live. TrustOps handles acquisition and lifecycle, Core determines canonical state and Resolver exposes published proof. Historic outcome-pack concepts remain preserved for future development but are not presented here as purchasable launch offers.