Vendor A
AUTHORIZED · permission is valid; the outcome is not yet proved.
CROSS-VENDOR OUTCOME FINALITY
Finality provides a neutral, portable cross-vendor mechanism for determining and communicating whether the whole consequential outcome is actually final.
The decisive boundary
Authorization, agent completion and workflow closure remain evidence inputs. The Outcome Contract determines which source is authoritative for each required predicate.
AUTHORIZED · permission is valid; the outcome is not yet proved.
AGENT COMPLETED · a task reached its vendor-local terminal state.
WORKFLOW CLOSED · the workflow system reports local closure.
AUTHORITATIVE STATE STILL WRONG · the required real state remains false.
NOT FINAL · CURE REQUIRED. No local success self-promotes into whole-outcome FINAL.
Cross-vendor control path
Evidence normalization is attached after the existing Gateway and before deterministic reconciliation; production certificates remain under existing key custody.
Freeze whole-outcome predicates, source roles, integration bindings and authoritative sources.
Normalize AuthZEN, MCP, A2A, CloudEvents and system-of-record evidence without flattening trust roles.
Apply unchanged FRP and FSK authority, contradiction, freshness, STOP and false-FINAL rules.
Issue the existing release-bound Certificate and FinalityID; write Registry and Transparency state.
Create successor lineage when later authoritative reality contradicts a prior FINAL.
Interoperability profiles
No endorsement, partnership or external adoption is implied.