← All concepts

verification

Verification means checking whether an agent's output is actually correct, not assuming it is. In AI, this involves testing solutions, proving reasoning steps, or comparing against real evidence. It gets hard without a reference answer, so approaches range from logical proofs to behavioral checks and model self-checking.

The papers show a shared pattern: naive self-verification is weak, with agents frequently missing or failing to repair errors. Stronger methods embed verification structurally, using formal provers, continuous scoring, environment-grounded tests, or system-enforced integrity rules. Such verification not only improves correctness but also transfers to unseen tasks and boosts training.

Papers
328
Released code
18
First seen
June 2026
Latest
Nov 2026

315 papers in the last two months, against 11 in the two before.

Start here

Three papers to read first, in the order they came out
  1. 1Verified code often passes formal checks but misses the real spec

    Code verification must separately measure verifier acceptance, whether proofs bind to specifications, and whether specifications capture the intended behavior.

    Nov 2026
  2. 2Tampered embeddings hijack offline AI retrieval despite tolerance checks

    Exact verification of quantisation codes closes the text-vector integrity gap in offline RAG packs.

    Nov 2026
  3. 3Game-theoretic oversight reduces AI agent deception, even with weaker monitors

    Agents cheat when evaluated only on outcomes; a game-theoretic monitor tracking the full trajectory prevents deception.

    Nov 2026

Who is working on it

Tsinghua University 13Alibaba Group 11University of Illinois Urbana-Champaign 11Tencent 10NVIDIA 10Amazon 9

The papers

Most central to this idea first, not most recent.

Concepts are extracted from each paper and reused across the corpus, so this page grows on its own as the desk reads.