diff --git a/docs/architecture/rfcs/app-conversation-and-async-inbox-v0.md b/docs/architecture/rfcs/app-conversation-and-async-inbox-v0.md
index a1d4e40878..6044fcb147 100644
--- a/docs/architecture/rfcs/app-conversation-and-async-inbox-v0.md
+++ b/docs/architecture/rfcs/app-conversation-and-async-inbox-v0.md
@@ -2078,8 +2078,18 @@ separate, idempotent phase. Reservation crashes adopt that exact queued review.
 If writable continuation was already admitted before the request journal was
 updated, the worker first recovers that same queued Turn. Dispatch still
 requires the original source, queue and native effect checks.
-The retained business obligation stays pending independently of the review's
-prose or failure; a review never starts a writable retry or another review.
+The retained business obligation stays pending after the review. Once a
+successful plain-text review is delivered, the original worker can independently
+qualify the still-unspent `work-1` continuation against the original typed
+partial. The current owner of the same native thread must prove settled effects
+again, including the intervening review and other later inputs. Core rechecks
+the original source and grant, queue, stop and steering, and exact original and
+review identities. The worker verifies the inventory again before execution and
+returns the result separately from both earlier replies. A review failure,
+review gate, loss of native ownership, superseding input or an uncertain effect
+leaves the original obligation pending. An admitted continuation stays visible
+while it is failed, gated, unfinished or awaiting verified result delivery.
+The review itself grants no execution authority and can run only once.
 
 A completed review does not consume the original one-shot `work-1` reservation.
 If the original writable owner later becomes available through ordinary work,
diff --git a/docs/architecture/rfcs/app-conversation-and-async-inbox-v0.zh-CN.md b/docs/architecture/rfcs/app-conversation-and-async-inbox-v0.zh-CN.md
index 2b72029f81..eb882e45bd 100644
--- a/docs/architecture/rfcs/app-conversation-and-async-inbox-v0.zh-CN.md
+++ b/docs/architecture/rfcs/app-conversation-and-async-inbox-v0.zh-CN.md
@@ -1363,8 +1363,15 @@ completed Turn 继续明确保留，本路径不提供通用动作或执行重
 发送、委派或替换原未完声明。旧问题中的指代仅使用原提问之前的 Core 上下文。
 原部分答复 Turn 和投递保持不变，由同一个飞书 worker 使用独立、幂等阶段补回新
 答复；预约崩溃只采用同一个已入队复核。如果可写续办已入队、原请求日志尚未更新，
-worker 先认回同一个 Turn。执行前仍重查原来源、队列和原生效果。原业务义务独立于复核正文或失败继续保留
-为待办。复核不能触发可写重试或又一次复核。
+worker 先认回同一个 Turn。执行前仍重查原来源、队列和原生效果。
+
+复核后原业务义务继续保留。无 gate 的复核成功送达后，原 worker 可以依据原有结构化
+部分答复重新核验尚未使用的 `work-1` 续办资格。原线程的当前 owner 必须重新证明效果
+已结清，包括期间的复核与后续输入。Core 核对原来源、授权、队列、停止与 steering，
+以及原 Turn 与复核 Turn 的精确关联。原 worker 在执行前再次核验效果清单，续办结果
+独立于此前两次答复送达。复核失败、复核 gate、原生 owner 丢失、新输入替代或效果未知
+时继续保留原待办。已准入的续办在失败、有 gate、未完成或尚未核验结果送达时继续可见。
+复核本身不授予执行权限，每条请求最多复核一次。
 
 已完成的复核不消耗原请求仅一次的 `work-1` 预约。如果原可写运行进程通过普通工作
 恢复可用，现有回复 worker 可以重新检查保留的原未完声明。它必须取得新鲜的原生