| 1 | > 后续变更：执行与验收机制已进一步精简。当前行为见 [执行模型迁移说明](EXECUTION_MODEL_SIMPLIFICATION.md)；本文保留交付模式退役的接口兼容背景。 |
| 2 | |
| 3 | > Follow-up: execution and acceptance were simplified further. See [the execution model migration](EXECUTION_MODEL_SIMPLIFICATION.md) for current behavior. |
| 4 | |
| 5 | # Delivery mode retirement |
| 6 | |
| 7 | [简体中文](#简体中文) |
| 8 | |
| 9 | Reasonix no longer offers Delivery as a session mode. New and restored local |
| 10 | sessions use standard execution. Plan, Goal, project checks, task-risk rules, |
| 11 | explicit user verification requirements, and recorded test evidence continue to |
| 12 | work independently. |
| 13 | |
| 14 | Legacy `/preset`, `/work-mode`, `/profile`, HTTP, desktop, and ACP inputs remain |
| 15 | readable for compatibility. Recognized old values are validated, report that the |
| 16 | setting is retired, and do not change runtime policy; unknown values still fail. |
| 17 | New status and persistence writes use `qualityFloor=standard`, |
| 18 | `agentPreset=standard`, and `tokenMode=full`. |
| 19 | |
| 20 | Historical checkpoints and receipts are preserved. A historical |
| 21 | `policy_floor=delivery` stamp no longer creates requirements when the current |
| 22 | task contract is rebuilt, and an ordinary old pause is informational rather than |
| 23 | a current blocker. Plan and Goal checkpoints still follow their existing |
| 24 | recovery rules. Reasonix never clears missing checks or rewrites failed evidence |
| 25 | as passed. |
| 26 | |
| 27 | The desktop client does not send policy changes to remote hosts. If an older |
| 28 | remote service reports Delivery state or a Delivery-created pause, the client |
| 29 | keeps that state and its recovery action visible and shows one upgrade notice |
| 30 | per remote session. Upgrade the remote service to remove its old policy. A |
| 31 | new-format session remains data-readable after a downgrade, but an old binary |
| 32 | may apply Delivery behavior again to historical fields; compatibility does not |
| 33 | make old runtimes adopt the new semantics. |
| 34 | |
| 35 | ## 简体中文 |
| 36 | |
| 37 | Reasonix 不再提供“交付”会话模式。新建和恢复的本地会话统一采用标准执行。 |
| 38 | Plan、Goal、项目检查、任务风险规则、用户显式验证要求和真实测试记录继续独立生效。 |
| 39 | |
| 40 | 旧 `/preset`、`/work-mode`、`/profile`、HTTP、桌面和 ACP 输入作为兼容入口保留。 |
| 41 | 已知旧值仍会校验并返回退役说明，但不会改变运行策略；未知值仍报错。新状态与正常 |
| 42 | 持久化写入固定使用 `qualityFloor=standard`、`agentPreset=standard` 和 `tokenMode=full`。 |
| 43 | |
| 44 | 历史检查点和回执原样保留。重建当前任务合同时，历史 `policy_floor=delivery` 印记不再 |
| 45 | 产生要求；普通任务过去的暂停只作为历史信息展示，不再成为当前阻断。Plan 和 Goal |
| 46 | 检查点继续使用原有恢复规则。Reasonix 不会清空缺项，也不会把失败证据改写成通过。 |
| 47 | |
| 48 | 桌面客户端不会向远端发送策略切换。旧远端若返回 Delivery 状态或由它产生的暂停， |
| 49 | 客户端会保留真实状态和恢复操作，并按远端会话显示一次升级提示；升级远端服务后才会 |
| 50 | 移除旧策略。新格式会话降级后仍可读取，但旧程序可能根据历史字段再次执行 Delivery |
| 51 | 行为；数据兼容不代表旧运行时遵守新语义。 |
| 52 |