SOTA: epistemic ancestry tracking so more agents do not count as more evidence
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
首先在不集成 RuVector 的情况下,使用其冻结输出、测试、独立基准测试、固定依赖、固定种子和无网络路径,复现公开的 ESB 基准测试。然后比较列出的四种聚合方法,并定义 RuVector 适配器和 RuV 特定用例。完成的标准是:留出校准得到实质性改善,错误佐证至少减少 50%,任务效用下降不超过 2 个点,遍历保持有界,并且不发生跨作用域或权限回归。
由索引模型根据 Issue 内容生成。
描述
Finding
Epistemic Sybil Resistance (arXiv:2609.01873, submitted 2026-09-01) formalizes a failure mode that directly affects distributed RuV intelligence: another agent report is not another independent observation.
The originating team reports more than 20,000 controlled LLM report and extraction calls. Holding one evidence root fixed while report multiplicity grows from 1 to 32 collapses naive posterior coverage from 0.940 to 0.263. Increasing true evidence-root multiplicity closes the gap. They also measure correlated extraction error among repeated agent calls and show that report-space deduplication tracks surface similarity much more strongly than actual evidential ancestry.
The public reproducibility repository is MIT licensed for code and includes frozen outputs, tests, a standalone benchmark, pinned dependencies, fixed seeds, and a no-network reproduction path.
RuV implication
RuVector, Ruflo, Autogenous, LatentMesh, Core Memory, and MetaHarness should reason over evidence roots and dependence, not agent count, report count, vote count, or embedding similarity.
This complements earlier correlation-aware memory work but gives a sharper invariant:
N reports from one evidence root never become N independent observations.
At the same time, common ancestry does not imply complete redundancy because independent extraction passes can still add bounded information. The model must track both ancestry and extraction dependence.
Proposed primitive
Add an experimental EvidenceAncestry graph above normal RuVector retrieval.
Each evidence-bearing artifact should be able to carry:
- immutable evidence root identifiers
- parent artifact identifiers
- observation or source class
- extractor or model family identity
- extraction attempt identity
- known shared context roots
- tenant and resource scope
- confidence and calibration metadata
- explicit
authority: none
Aggregation should estimate effective independent evidence from roots plus dependence, while retaining raw report multiplicity as descriptive telemetry only.
Benchmark
First reproduce the public ESB benchmark without integrating RuVector. Then implement a RuVector adapter and compare:
- naive report voting
- embedding or lexical deduplication
- evidence-root clustering only
- evidence-root clustering plus extraction-dependence correction
Add RuV-specific cases using multiple agents reading the same document, different documents with similar wording, the same source through multiple retrieval paths, and independent sensors producing superficially similar observations.
Metrics
Calibration coverage, Brier score, log loss, effective evidence count, false corroboration rate, missed corroboration rate, aggregation latency, index bytes, provenance traversal cost, and task utility.
Falsification
Reject the extra graph machinery if simple source-root counting performs within variance, if ancestry metadata is unavailable often enough that estimates become mostly unknown, or if dependence estimation is too unstable to improve held-out calibration.
Security and governance
Evidence ancestry is not identity authority and not execution authority. A signed agent cannot turn a duplicated source into independent evidence merely by signing it. A trusted source can still be wrong. RVM remains the privileged action boundary.
Test forged ancestry, omitted parents, cross-tenant roots, cyclic ancestry, source aliasing, identical reports from independent roots, distinct reports from one root, and correlation shifts across model upgrades.
Acceptance
Advance only if held-out calibration error improves materially over both naive voting and similarity deduplication, false corroboration falls by at least 50%, task utility does not regress by more than 2 absolute points, provenance traversal remains bounded, and zero cross-scope or authority regressions occur.
Coordinate independent reproduction through MetaHarness and record promotion state in Core Memory federation. No autonomous merge.
- 主要语言
- Rust
- 星标
- 4.5k
- 派生
- 603
- 平均合并
- 1 天 11 小时
- 30 天内合并 PR
- 56
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ruvnet/RuVector 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
相似的 Issue
-
type/bug
难度 2/5 1-3 小时 新手友好度 68/100
stackabletech/kafka-operator#1033 · 1 条评论 ·
维护者通常 1 天内回复
-
bug good first issue needs testing
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 90/100
farion1231/cc-switch#7744 · 1 条评论 ·
维护者通常 1 天内回复
-
datafusion
难度 2/5 1-3 小时 新手友好度 76/100
apache/iceberg-rust#3297 ·
维护者通常 1 天内回复