Skip to main content
Aggregate arXiv cs.AI 人工智能 4 Sep 2026 - 12:00

Fresh Memory, Stale Plans: Dependency-Scoped Validation for Distributed LLM-Agent Memory

RSS 官方收录 · 可信分层展示

关键摘要

arXiv:2609.03340v1 Announce Type: new Abstract: 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_3$, another agent m…
  • We call this \emph{stale-plan execution}: state freshness does not est…
  • We introduce PlanFence, a dependency-scoped action-validation protocol.

摘要引擎:抽取

正文提要

arXiv:2609.03340v1 Announce Type: new Abstract: 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_3$, another agent may commit $r_4$, and an executor may receive $r_4$ without replacing the plan derived from $r_3$. We call this \emph{stale-plan execution}: state freshness does not establish that the plan authorizing an action remains valid. We introduce PlanFence, a dependency-scoped action-validation protocol. Plans cite the exact public records they used, and an executor validates only the records that can affect the pending external action, replanning once or blocking when validation is incomplete. In 30 controlled live workflows with a post-plan revision, a freshness-only executor acts on the obsolete plan in every task, whereas PlanFence completes all tasks without an invalid action. Controlled replay reveals two conditional boundaries: proactive synchronization yields lower coordination stall at low churn, while PlanFence avoids repeated update-path coordination as churn grows and avoids validating unrelated state as the shared keyspace grows. These are controlled safety and systems-cost results, not general task-accuracy gains.

来源:https://arxiv.org/abs/2609.03340

打开官方原文 站点原文页 可信分区 本信源更多 今日简报 分享图 RSS 稍后再看列表