Identify the operating surface
Start with the canonical ECZ-ID Passport that matches what is actually operating: Agent, MCP, Plugin, API, IoT, SDK or Service & Workload.
CLOUD & PLATFORM ACCOUNTABILITY
KEEP PROVIDER-NATIVE IDENTITY. ADD RECIPROCAL ACCOUNTABILITY ACROSS THE BOUNDARY.
AWS, Microsoft, Google and other platforms already provide powerful identity and policy. ECZ-ID does not replace them. It gives organisations and relying parties a provider-neutral route to identify the accountable actor, carry authority and Intent context, re-check relevant state and preserve evidence around consequential machine activity.
WHERE ECZ-ID FITS
Bind. Integrate. Resolve. Interpret. Prove.
Use the provider's identity, workload and access controls underneath. Use ECZ-ID where accountability must remain meaningful across providers, organisations, APIs, agents, services and evidence systems.
Bind provider context
Connect supported provider, domain, repository, API and workload context without pretending a binding is authority.
Carry authority and Intent
Keep identity, authority, delegation and Intent distinct so the proposed action can be evaluated in context rather than inferred from credentials.
Re-check current state
Use Resolver and configured current-state capabilities at the time of reliance instead of treating a past observation as present truth.
Decide at consequence
Where a configured decision path exists, IntentControl can evaluate whether a proposed action should proceed before consequence. ECZ-ID does not execute the customer's action.
Preserve evidence
Use Receipts, LedgerCore and related evidence capabilities to preserve what was recorded and support later review without claiming integrity proves every underlying assertion.
CURRENT LAUNCH PATH
Start with the free identity layer, then add the capability the consequence requires.
The current launch architecture centres the seven free machine-surface Passports and the common operating layer—not separate provider-specific identity products.
Identity
Business Passport plus the seven free machine-surface Passports.
Explore Passports →Control & state
Intent, IntentControl, Watch, PulseGuard and relevant current-state checks.
Explore control →Evidence
Receipts, LedgerCore, Resolver and re-verification.
Explore evidence →Scale & relationships
AEC and Graph support a growing machine estate and relationship context.
Open TrustOps ↗PROVIDER-NEUTRAL BY POSITION
One accountability model across many provider estates.
Specific provider integration claims belong only where implementation evidence exists. ECZ-ID is designed to complement provider-native IAM, workload identity, marketplaces, APIs and policy—not to replace them.