safety security
Fresh Memory Still Authorized an Obsolete Plan
PlanFence validates only the shared records that could change the pending external action, then replans once or blocks.
Summary
PlanFence validates only the shared records that could change the pending external action, then replans once or blocks.
A distributed team may see the newest facts while executing a plan derived from an older requirement. In thirty controlled workflows with a post-plan revision, a freshness-only executor performed the now-invalid action every time; PlanFence completed all tasks without doing so. The protocol makes plans cite their dependencies and checks only the records that can affect the next action. Proactive synchronization stalled less under low churn, while dependency-scoped validation scaled better as changes and unrelated shared state grew. These are controlled safety and coordination-cost results, not general agent-performance guarantees.
Why it matters
PlanFence validates only the shared records that could change the pending external action, then replans once or blocks.
Limits and context
- In thirty controlled workflows with a post-plan revision, a freshness-only executor performed the now-invalid action every time; PlanFence completed all tasks without doing so.
- The protocol makes plans cite their dependencies and checks only the records that can affect the next action.
- These are controlled safety and coordination-cost results, not general agent-performance guarantees.
Key claims
PlanFence validates only the shared records that could change the pending external action, then replans once or blocks.
Qualification: In thirty controlled workflows with a post-plan revision, a freshness-only executor performed the now-invalid action every time; PlanFence completed all tasks without doing so.
Evidence: source-2026-09-05-016
Sources
- arXiv preprint 2609.03340arXiv · primary research
Corrections
No corrections have been recorded for this story.