External State · AI.WIKI

01 · 白板上的便签和数据库里的工单，断电后一样吗01 · Is a sticky note as durable as a ticket record?

会话里写着“已完成两步”，但没有任何外部记录。刷新后，这个任务究竟该从哪里继续？The chat says “two steps complete,” but no external record exists. After a refresh, where should the task actually resume?

02写入外部进度和纯上下文便签，再刷新会话比较谁能恢复Write Durable Progress and a Context-only Note, Then Refresh and Compare Recovery

持久记录 vs 临时便签durable record vs transient note

状态 AMetric A

—

状态 BMetric B

—

状态 CMetric C

—

所有概率、成本、成功率与输出均为固定种子的教学模拟，不代表真实模型输出。把主变量拖回即可复核结论。All probabilities, costs, success rates, and outputs are fixed-seed teaching simulations, not real model output. Move the main variable back to verify the conclusion.

03把刚才的变化拆成 4 个零件Break the Change into Four Parts

External State

FACT

事实记录Fact record

任务 ID、状态与版本写入外部系统。Task ID, status, and version live in an external system.

CONTEXT

上下文便签Context note

便于当前推理，却会随会话边界消失。Useful during current reasoning but lost at the session boundary.

REFRESH

新会话New session

刷新不应靠模型猜旧状态。A refresh must not ask the model to guess old state.

RECOVER

按 ID 恢复Recover by ID

用稳定键读回已提交进度与中间结果。A stable key reloads committed progress and intermediate results.

04最小机制：主交互能逐项验证Minimal Mechanism: Verify Each Link in the Interaction

MECHANISM

recoverable = external_write_committed ∧ stable_task_id

刷新清空上下文便签；只有带稳定 task_id 的已提交外部记录能恢复，主交互将两侧同时展示。Refresh clears the context note. Only a committed external record with a stable task_id can recover, shown side by side in the interaction.

执行一步Do work生成进度与便签produce progress + note

分开写入Store外部记录 / 上下文external record / context

刷新恢复Refresh只读回外部事实reload external facts only

05只写上下文便签，不写外部状态就刷新Refresh after Writing Only a Context Note

主动制造失败Create a failure

边界实验Boundary experiment

自然语言便签可以帮助当前回合，但不能成为恢复协议。没有稳定 ID 与已提交记录，系统必须承认进度未知。A prose note can help this turn but cannot serve as a recovery protocol. Without a stable ID and committed record, progress is unknown.

尚未执行。先在主交互中观察正常机制。Not run yet. Observe the normal mechanism in the main interaction first.

✗ 模型提过的内容就是系统状态。Anything mentioned by the model is system state.→ ✓ 系统状态必须有外部记录、ID 与版本。System state needs an external record, ID, and version.

✗ 上下文越长，状态越可靠。More context makes state more reliable.→ ✓ 上下文是推理材料，不是事务性存储。Context is reasoning material, not transactional storage.

✗ 刷新后让模型猜即可。Let the model guess after refresh.→ ✓ 恢复必须读回已提交事实，猜测不能推进副作用。Recovery must load committed facts; guesses cannot advance side effects.

06 · 一句话带走06 · One line to keep

外部状态用稳定 ID 持久保存已提交事实；刷新后它能恢复，而只存在于上下文里的便签会消失。External state durably stores committed facts under a stable ID. It survives refresh; a context-only note disappears.