Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Task][RFC]: Finish evidence-driven Effect Interpreter adoption

オープン
  • 何か問題がありますか？
#5,199 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
リファクタリング
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
backend

調査の方向性

Read the linked RFC and inspect loopx/control_plane/effect_program.ts, loopx/control_plane/turn_driver, and loopx/control_plane/coordination; coordinate with the active owners in #3225 and #3245 before proposing any change. First identify an unowned acceptance gap, then document the actual duplicate authority removed, compatibility and rollback, and the integrated revision with commands and passed, failed, and untested evidence.

索引モデルが issue の本文から書いたものです。

説明

direction/architecture-evolution

Outcome / 目标

完成 Effect Interpreter 的有收益迁移与验收。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree.

Canonical design: RFC. Roadmap: S2, under #4574. Design acceptance is distinct from implementation, live qualification and promotion.

Current boundary

Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim.

The RFC records M0–M7.2 delivered, M7.3 closed without a shared executor, and task-lease adoption under M7.4. This is not a request to build Effect Program again.

Work remaining

  • Reconcile current M7.4 callers with the native TS transaction owners; select further adoption only where it removes demonstrated duplicate decisions or recovery truth.
  • For each retained adoption, migrate the complete effect/observation/recovery boundary and delete the replaced rule; record an explicit no-adoption conclusion where owners merely share algebra.

Ownership and ongoing work

Coordinate with #3225 and #3245 before touching transaction writers; current authority recovery and retirement are already in flight. M7.3 must not be reopened by this task.

Contribution route: implementation/integration overlaps active work. Start from the linked current owners/PRs and identify an unowned acceptance gap in a claim comment; do not begin a competing rewrite.

Acceptance

  • A real caller preserves identity, original-receipt replay, failure observations and effect ordering; mutation/counterexample cases exercise the contract.
  • Report the actual duplicate authority removed, retained compatibility and rollback. No speculative shared executor or leaf-RPC expansion.
  • Reconcile the RFC's current delivery checkpoint and this issue with the integrated revision, commands, passed/failed/untested evidence and remaining gates. Close the accepted scope only; no claim that a merged PR alone completes the RFC.

Starting points and delivery boundary

Base: latest main. Reuse the existing typed owner and provider boundaries. Include affected CLI/frontend/Lark companions; verify real entrypoints and backend where changed. Preserve existing first-screen review and maintainer merge gates. Public artifacts contain only synthetic/public-safe evidence, no private operational state. This task does not authorize provider promotion, benchmark launches, release/deployment or unrelated protected effects.

主要言語
Python
スター
6.2k
フォーク
596
平均マージ
6時間 44分
マージ済み PR（30日）
915

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

loopx-project/loopx のほかの issue

loopx-project/loopx の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。