Glossary · Claim Keys & Adjudication

Claim Keys & Adjudication.

Knowledge graduates on evidence, not optimism.

Direct answer

A claim key (hash of claim-kind, subject, scope) gives every extracted lesson a stable identity so corroboration, contradiction, and supersession compose across sessions. New claims enter invisible as hypotheses; N-of-M distinct corroborations (or Beta posterior) confirm them; contradictions supersede without deleting history. One session's pain is a hypothesis, repeated independent confirmation is knowledge.

In Anvaya

How We Implement It.

01Claim Keys & AdjudicationAnvaya's adjudication pipeline implements exactly this: contrastive extraction with counterfactuals, ten reject filters, N-of-M confirmation, full version chains on supersede.

Questions

Asked About Claim Keys & Adjudication.

Q

Why not serve lessons immediately?

Single sessions mislead, a fix that worked once may be incidental. Serving uncorroborated rules is how agents learn superstitions.

Q

What happens to contradicted claims?

Superseded, never deleted: they leave the live index but keep full history for audit.

Q

What makes a claim corroborating vs duplicate?

Distinct sessions, files, or failure modes. Same-session repetition is corroboration-neutral.

Run Agents That Fit On Your Laptop.

25.6 MB median RSS. 25 agents ran in parallel on a Core 2 Duo with 4 GB RAM. Hundreds on your machine. Zero cloud required on the Ollama path.

Requires Rust/cargo to build from source. Linux and macOS today, Windows not yet supported. Pre-1.0, public beta. Pricing TBD.