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

SOTA: epistemic ancestry tracking so more agents do not count as more evidence

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

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
rust
領域
ai, databases

調査の方向性

RuVectorを統合せず、その固定された出力、テスト、スタンドアロンベンチマーク、固定された依存関係、固定シード、ネットワークなしのパスを使用して、まず公開ESBベンチマークを再現します。次に、列挙された4つの集約アプローチを比較し、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:

  1. naive report voting
  2. embedding or lexical deduplication
  3. evidence-root clustering only
  4. 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時間
マージ済み PR（30日）
56

環境構築

このプロジェクトの環境構築ファイルはまだ確認していません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

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

ruvnet/RuVector のほかの issue

ruvnet/RuVector の issue をすべて見る

似ている issue

Rust の issue をもっと見る

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

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