@@ -118,6 +118,24 @@ different questions; their proximity is not proof they should be one state.
   benefit experiments. Replace real consumers in the delivery slice; preserve
   historical decoding and original effect readback across code rollback.
 
+**Source proposal (2026-10-28).** The existing Effect runtime now composes
+journal receipt qualification and ordered continuation in the typed Turn owner.
+`managed_step.py` sends one complete journal/decision request instead of rebuilding
+an execution payload; the driver uses the same route classifier. The registered
+ordered contract, historical journal decoder and independent recovery decision
+remain. Public Python receipt/budget value objects keep their API, including exact
+integer transport. Native File/SQLite retry, saved-result replay and lost-spend
+response tests retain the original Turn and one debit. Rule mutations exercise
+the actual TS evaluator. This is a single-session source proposal, not C1 cutover,
+C4.2/C4.3 adoption, installed qualification or long-horizon benefit. Reconcile
+original receipts before rollback; no journal or settlement schema changes.
+The same inventory measures 43 maintained Python/TS pairs on the base and 45 on
+this proposal: the new controller and host-failure pairs retain the Python API
+and native failure producer while sharing TS decisions. The pair budget records
+that maintenance cost (43 → 45); generated exclusions and the over-budget
+negative check remain. Deleted Python decisions, rather than the pair count,
+establish convergence. Added bridge traffic is disclosed without a speedup claim.
+
 ## C4.2 — Thin outer-worker semantic adoption
 
 **Candidate for bounded policy convergence.**
 
@@ -94,6 +94,18 @@ execution 形状的回执，同时调用 `turn_journal.ts` 检查一致性。`re
   等待完整 C1 收益实验。在交付切片中替换真实消费者；代码回退时保留历史解码与原
   effect readback。
 
+**源码提案（2026-10-28）。** 既有 Effect runtime 在 typed Turn owner 内组合 journal
+回执资格与有序继续判定。`managed_step.py` 一次传入完整 journal/decision，不再重建
+execution 载荷；driver 复用同一路由分类器。原注册有序契约、历史 journal decoder 和
+独立恢复判定保持。公开 Python 回执/预算值对象保留 API，整数通过精确编码传递。
+真实 File/SQLite 重试、已存结果重放和扣额丢响应测试保留原 Turn 与单次扣额；规则
+mutation 直接验证实际 TS evaluator。本项仅为单会话源码提案，不代表 C1 切换、
+C4.2/C4.3 采用、已安装资格或长程收益。回滚前核对原回执；journal 和结算 schema 不变。
+同一 inventory 在 base 测得 43 对独立维护的 Python/TS 模块，本提案为 45 对：新增
+controller 与 host-failure 配对保留 Python API 和原生失败 producer，同时共享 TS
+决策。配对预算据此记录维护成本（43 → 45）；生成排除规则和超预算负例保持。
+收敛依据是删除了 Python 决策，不是配对计数；额外 bridge 传输如实披露，不宣称提速。
+
 ## C4.2 — 外层 worker 的薄语义采用
 
 **有界策略收敛候选。** `scripts/external_scheduler_worker.py` 的 `_host_attempt`、