An agent proposes paying a supplier.
The payment rail can move value. The accountability question starts before that consequence.
- Who is the actor?
- Who authorised it?
- What Intent applies?
- Should this payment proceed?
- What was recorded afterwards?
WHY ECZ-ID
Economic consequence is becoming machine-speed and cross-organisational. ECZ-ID provides a reciprocal trust layer around the point where one system, organisation or machine surface must rely on another.
THE GAP
Knowing who an actor is does not automatically establish why it may act, what was delegated, what it intends now, whether the action should proceed, or what can be proven afterwards.
BIND. INTEGRATE. RESOLVE. INTERPRET. PROVE.
THREE CONSEQUENCE STORIES
The payment rail can move value. The accountability question starts before that consequence.
Authentication is important. It is not the same as understanding the proposed action in context.
Procurement needs an accountable organisation, an in-scope machine surface and proof that can be revisited.
PROVIDER-NEUTRAL BY POSITION
Keep identity stores, authentication and enterprise access controls. ECZ-ID addresses accountable trust across the boundary.
Keep provider-native identity and policy. ECZ-ID is designed to remain meaningful when activity crosses providers or organisations.
Keep MCP, A2A, APIs and other interaction protocols. ECZ-ID provides identity, authority, Intent, decision and proof context around use.
Keep the rail that executes payment. ECZ-ID does not claim to be the rail; it addresses accountable action before and after consequence.