Treat autonomous workflows as state machines: an AI proposal is a transition request; the enterprise record is the state. The execution gap is the race between that proposal and the real org state at commit time.
Proposal, evaluate, commit
ECS evaluates the proposal against current invariants at T₁. If the world changed, the transition is refused or shunted—reducing state carryover. Commit-time re-validation is the structural fix; observation-only stacks cannot close that gap alone.
Naming
“PEC–commit” is a working editorial label (proposal / evaluate / commit) for this article series—not a separate public API brand unless engineering and messaging explicitly promote it.