PlanFence: Dependency-Scoped Validation Prevents Stale-Plan Execution in Distributed LLM-Agent Memory

Forum topic · 小凯 · 2026-09-06

Summary

Distributed LLM-agent teams can read the latest shared facts and still act on obsolete plans. This paper, by Evan Chen, Shiqiang Wang, and Christopher G. Brinton (arXiv:2509.00004, September 2026), identifies "stale-plan execution": a planner derives an action from requirement r3, another agent commits r4, and the executor receives r4 without replacing the plan derived from r3 — so state freshness does not guarantee the plan authorizing an action remains valid. The authors introduce PlanFence, a dependency-scoped action-validation protocol in which plans cite the exact public records they used, and executors validate only the records that can affect the pending external action, replanning once or blocking when validation is incomplete. In 30 controlled live workflows with post-plan revisions, a freshness-only executor acted on obsolete plans in every task, while PlanFence completed all tasks with no invalid actions. Controlled replays further show active synchronization yields lower coordination stall at low churn rates, while PlanFence avoids repeated update-path coordination as churn grows and avoids validating irrelevant state as the shared key space grows. The authors note these are controlled safety and system-cost results, not general task-accuracy improvements.

Paper Overview

Field: AI/ML Authors: Evan Chen, Shiqiang Wang, Christopher G. Brinton Published: 2026-09-06 arXiv: 2509.00004

The Problem: Stale-Plan Execution

Distributed LLM-agent teams can read the latest shared facts and still act on an obsolete plan. A planner may derive an action from requirement r₃, another agent may commit r₄, and an executor may receive r₄ without replacing the plan derived from r₃. The authors call this stale-plan execution: state freshness does not establish that the plan authorizing an action remains valid.

PlanFence

PlanFence is a dependency-scoped action-validation protocol:

Plans cite the exact public records they used.
Executors validate only the records that can affect the pending external action.
When validation is incomplete, the executor replans once or blocks.

Experimental Findings

In 30 controlled live workflows with a post-plan revision, a freshness-only executor acted on the obsolete plan in every task, whereas PlanFence completed all tasks with no invalid actions.
Controlled replays revealed two conditional boundaries:
Active synchronization produces lower coordination stall at low churn rates.
PlanFence avoids repeated update-path coordination as churn grows, and avoids validating irrelevant state as the shared key space grows.

Scope Caveat

These are controlled safety and system-cost results, not general task-accuracy improvements.

---

*Auto-collected on 2026-09-06.*