[Task][RFC]: Complete external-evidence research through real providers and user readback
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python, typescript
调研方向
Start with the canonical RFC and the existing owner in loopx/control_plane/capabilities/external_evidence.ts, then inspect the CLI commands and apps/presentation/dashboard entrypoints named in the issue. Identify one bounded milestone and exact files before proposing work, coordinating with the current App research delivery. Verify a real authorized provider path and CLI/UI readback; document commands, passed/failed/untested evidence, and remaining gates without claiming a merged PR completes the RFC.
由索引模型根据 Issue 内容生成。
描述
Outcome / 目标
完成外部证据研究的真实 provider 与用户回读。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: S6/S8, 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.
#4813 shipped discover/plan/receipt/admit/retire through a typed TS owner and CLI. The RFC explicitly distinguishes observing a caller-presented receipt from proving provider execution, and names frontend/Lark as companion work.
Work remaining
- Reuse the exact-plan lifecycle with one existing research method and one supported connector where needed; retain their own execution/permission owners.
- Expose the same plan, source provenance, parent admission, downstream use and retirement facts in the affected product entrypoints.
Ownership and ongoing work
Coordinate with capability Portfolio and current App research delivery. This issue completes this RFC’s evidence lifecycle; it does not create a browser, connector registry, new scheduler or another evidence authority.
Contribution route: available for a bounded proposal/PR within this RFC. Name the intended milestone and exact files in a claim comment so simultaneous contributors do not duplicate work.
Acceptance
- Inventory-only or stale providers cannot be selected as ready; plan/receipt/admission mutation is rejected.
- Partial, empty and failed evidence preserve the caller’s original-source fallback; admission and downstream coverage are independently shown.
- Demonstrate a real authorized provider path and actual CLI/UI readback without automatic evidence acceptance or raw-content leakage.
- 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
- loopx/control_plane/capabilities/external_evidence.ts
- loopx/cli_commands
- apps/presentation/dashboard
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
- 平均合并
- 7 小时 35 分钟
- 30 天内合并 PR
- 928
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
loopx-project/loopx 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
loopx-project/loopx#6842 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
loopx-project/loopx#6108 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
loopx-project/loopx#5688 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 60/100
loopx-project/loopx#5632 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
loopx-project/loopx#5443 · 1 条评论 ·
维护者通常 1 天内回复
查看 loopx-project/loopx 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
CLIMADA-project/climada_python#1337 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
8go/matrix-commander#233 ·
-
documentation
难度 2/5 1-3 小时 新手友好度 66/100
-
documentation enhancement priority:high size:M
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
Validate non-divisible effective batch sizes in the Unsloth LoRA backend可能已有人在做 @debesh-biswas 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100