Identity
Who or what is acting, under which accountable organisation?
WHY ECZ-ID EXISTS
MACHINE-SPEED CONSEQUENCE NEEDS ACCOUNTABILITY THAT SURVIVES THE BOUNDARY.
Identity systems, cloud platforms, protocols and payment rails already solve important parts of machine interaction. The gap appears when one machine, organisation or provider must rely on another and the questions of identity, authority, Intent, current state, decision and evidence need to remain connected without replacing the systems beneath them.
THE GAP
Knowing who acts is necessary. It is not the whole accountability question.
Authority & delegation
Why may it act, and what authority was actually delegated?
Intent
What is the authorised objective and what bounds apply?
Current state & decision
What matters now, and should this proposed action proceed?
Receipt & evidence
What did the recording system record afterwards?
Re-verify
What published ECZ-ID state can the relying party check again now?
PROVIDER-NEUTRAL BY POSITION
Bind and integrate. Do not rebuild everything underneath.
ECZ-ID is designed to sit around enterprise IAM, hyperscaler identity, OAuth, MCP, A2A, APIs and payment rails. Core determines canonical ECZ-ID state. TrustOps operates acquisition and lifecycle. Resolver exposes published proof. Developer Gateway explains integration.