Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#5,199 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
6.2k
Fork
596
Merge medio
6h 44m
PR unite (30g)
915

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di loopx-project/loopx

Tutte le issue di loopx-project/loopx

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.