TAO status logoTAO statusBeta

Convergent Agent

A Bittensor on-chain quantum analysis agent that argues the consensus-supported reading of the evidence.

1. What Convergent Agent Does

Convergent Agent is seeded into a quantum analysis to argue the position the plurality of retrieved evidence actually supports, giving the quantum analysis a reliably evidence-anchored voice alongside Critical's high-bar caution and Divergent's deliberate contrarianism.

It never invents a position from the model's own memory: it pulls the same fused evidence that Chain Agent, Github Agent, Discord Agent, Wallet Agent, and Twitter Agent collect, and argues for the reading that the majority of that evidence points to.

SourceWhat it contributes
Chain snapshots and eventsOn-chain state and activity.
GitHub recordsDevelopment activity.
Discord and Twitter countersCommunity and social signal.
Wallet ledgerHolder and staking behavior.

2. Where It Sits in the Tao Status Economy

BT-Arena quantum analysis orchestrator→Convergent Agent→Protocol Backend→Tao Status Validator→Bittensor chain

Convergent Agent is a consumer of miner-contributed LLM keys through the same quantum analysis turn endpoint as the data agents, preferring a pooled miner key on each attempt and falling back to its own static key, invisible to scoring, only when contribution is disabled, the pool declines, or the vendor is unsupported.

3. The Turn Pipeline

  • No evidence at all across every pooled source: the agent declines rather than guessing.
  • Up to five attempts are made, each with a freshly acquired key.

False balance

An insufficient verdict issued when the pooled evidence sources are lopsided, at least 70% of weighted evidence pointing one direction. Convergent's job is to state the majority reading, not manufacture artificial uncertainty.

Fabricated evidence

A confident supported or refuted verdict whose cited evidence shares zero numeric fingerprints with the pooled context.

4. Quality Grading

GradeMeaningWhen
1.0Genuinely grounded, majority-consistentSUPPORTED/REFUTED that passed the fabrication check
0.6Reasoned uncertaintyINSUFFICIENT issued when evidence genuinely is mixed (below 70% weight either way)
0.2False balanceRejected attempt: hedged despite lopsided evidence
0.1FabricatedRejected attempt: confident verdict, invented evidence
—Not assessableProse turn, unparseable reply, unknown verdict shape — neutral

5. Reporting

One report is filed per turn, feeding directly into the reporting miner's scoring window:

{
  "hotkey": "5F...",
  "success": true,
  "latency_ms": 1602.1,
  "error_category": null,
  "quality_score": 1.0,
  "lease_token": "the token from this attempt's acquire grant"
}
  • success is false only on a raised exception during the LLM call.
  • A report without a valid, unconsumed lease_token is rejected and never recorded.

6. Simulated Example

A quantum analysis turn on the claim: "Subnet 12 is healthy."

  1. 1

    Pooled retrieval

    The chain snapshot shows stable emission, GitHub shows 340 commits over 60 days, Discord shows rising activity, and wallet data shows mild stake concentration, four of five weighted signals leaning positive, roughly 78% weighted toward healthy.

  2. 2

    Attempt 1

    The first miner's key returns an insufficient verdict citing no evidence at all, despite the lopsided 78% weighting. This is false balance, reported at quality 0.2.

  3. 3

    Attempt 2

    A second miner's key returns a SUPPORTED verdict citing the 340 commits and Discord messages rising from 1,050 to 2,140. The figures overlap the pooled context, so it is not fabricated, and it is graded 1.0.

7. Operating Limits

LLM attempts per turn5
Majority threshold70% weighted evidence counts as lopsided
Quantum Analysis turn budget180 seconds
Key lock per acquired key5 minutes
Cooldown after a reported failure60 minutes