liveBook · Manning

Verifier

A verifier is an entity or process that checks whether a claim, answer, result, or artifact satisfies specified correctness or validity criteria.

How 9 Manning books explain it

Applied Reinforcement Learning

A verifier is a procedure that checks a model's answer against a specified correctness criterion or reference answer.

How it is used
Replaces a learned reward model with a checkable correctness signal for tasks that have ground-truth answers.
How deep it goes
Parses a final answer and compares it with a reference, but provides no token-by-token feedback during generation.
Examples
Uses FinQA gold answers and code test-suite results as concrete verification targets.
What you can do after
Build it from scratch as a function that parses a final answer and checks it against a gold answer.

Read how Applied Reinforcement Learning explains verifier →

Authorization in Action

A verifier is an entity that checks the validity, provenance, and trustworthiness of presented claims or credentials.

How it is used
Evaluates presented credentials as trusted context for authorization decisions across organizational boundaries.
How deep it goes
Explains cryptographic checks, issuer governance, claim normalization, protocol integration, freshness, and exceptions, but defers protocol internals.
Examples
Uses an auditor credential, ACME access requests, the trust triangle, and the trust diamond to demonstrate verification and trust.
What you can do after
Evaluate credential presentations, distinguish authenticity from issuer trust, and provide normalized claims for policy decisions.

Read how Authorization in Action explains verifier →

Vibe Engineering

A component or process that checks an artifact or action against specified rules and conditions.

How it is used
Places a deterministic gate around probabilistic code generation to enforce executable specifications.
How deep it goes
Defines the verifier’s role and rationale but stops short of implementation details for specific CI/CD systems.
Examples
Uses an executable specification, a CI/CD pipeline, generated code, and a Friday-afternoon diff as verification examples.
What you can do after
Operate/configure an impartial verification gate around model-generated code and team-owned tests.

Read how Vibe Engineering explains verifier →

LLM Evaluation and Alignment, The Foundational Ideas

A verifier is a deterministic or objective computational system that checks whether an output satisfies a correctness criterion.

How it is used
Deploys objective checks to evaluate outputs or provide reinforcement-learning rewards for verifiable tasks.
How deep it goes
Explains task-selection criteria and concrete checks, but stops short of implementing a complete verifier.
Examples
Uses math answers, unit-tested code, regex-checked formats, and financial-assistant citation and schema checks.
What you can do after
Build from scratch objective checks that score mathematical, code, structural, or source-grounded outputs.

Read how LLM Evaluation and Alignment, The Foundational Ideas explains verifier →

Build a Reasoning Model (From Scratch)

A component that checks whether a candidate answer is correct or acceptable, often by comparing it against a reference.

How it is used
Evaluates free-form math answers by checking extracted candidates against reference solutions.
How deep it goes
Explains the full verification pipeline through parsing, normalization, and symbolic comparison, but leaves broader evaluation methods aside.
Examples
Uses boxed answers, fraction equivalence, and the MATH-500 evaluation workflow.
What you can do after
Apply it to judge whether a generated mathematical answer is correct and to support model evaluation or later reward signals.

Read how Build a Reasoning Model (From Scratch) explains verifier →

Build a DeepSeek Model (From Scratch)

A deterministic checker is a procedure that evaluates an output against fixed criteria and produces the same result for the same input.

How it is used
Uses deterministic checking to provide training rewards for objectively verifiable mathematics, code, and symbolic tasks.
How deep it goes
Builds a toy extractor-and-comparator, then extends design to formatting, equivalence, tolerance, parsing, and reward-hacking risks.
Examples
Uses final-number extraction, unit tests, compilers, symbolic rules, structured answers, and reasoning/final-answer formatting.
What you can do after
Build it from scratch for simple answer-only tasks and evaluate when stronger parsing or preference signals are required.

Read how Build a DeepSeek Model (From Scratch) explains verifier →

Real-World Cryptography

A verifier is the participant in a proof protocol who checks whether the prover has demonstrated the claimed statement or knowledge.

How it is used
Checks a prover’s claim or knowledge while preserving hidden witness values in proof protocols.
How deep it goes
Explains the role through discrete-log proofs and polynomial evaluations, stopping short of a complete verification algorithm.
Examples
Uses Victor checking Peggy’s knowledge and a verifier completing polynomial components in a zk-SNARK-style protocol.
What you can do after
Evaluate whether a prover’s evidence supports the claimed knowledge or program output without requiring the hidden witness.

Read how Real-World Cryptography explains verifier →

Elliptic Curve Cryptography for Developers

A verifier is the party in a proof protocol that checks whether the prover's claim and evidence satisfy the required conditions.

How it is used
Checks a prover’s claim against public inputs and proof data while preserving the private witness.
How deep it goes
Describes verification inputs and QAP equation checks, but stops short of implementation code or a complete verifier algorithm.
Examples
Uses blockchain data, anonymous transactions, certificates, and a medical record proving medicine and dose without identifying the patient.
What you can do after
Evaluate whether a proof is consistent with public data and return acceptance or rejection without exposing the witness.

Read how Elliptic Curve Cryptography for Developers explains verifier →

Designing AI Agents

A verifier is a component that checks whether an answer or result satisfies relevant criteria.

How it is used
Checks agent results and supplies recovery signals within bounded repair and publication workflows.
How deep it goes
Explains protected verification boundaries and recovery steps, but limits assurance to conditions the checks can observe and judge.
Examples
Uses a removed tool argument and a code-repair publication gate to illustrate checks after agent changes.
What you can do after
Evaluate where verification supports recovery or publication, where it falls short, and whether an extra verifier call justifies its cost.

Read how Designing AI Agents explains verifier →

Also covered in

What to know first

Related concepts

Questions about verifier

What is verifier?

A verifier is an entity or process that checks whether a claim, answer, result, or artifact satisfies specified correctness or validity criteria.

Which Manning books explain verifier?

Applied Reinforcement Learning, Authorization in Action, Vibe Engineering, LLM Evaluation and Alignment, The Foundational Ideas, Build a Reasoning Model (From Scratch), Build a DeepSeek Model (From Scratch), Real-World Cryptography, Elliptic Curve Cryptography for Developers and 1 more.

What should I know before learning verifier?

Manning books that teach verifier usually introduce language model, reinforcement learning, reward model and baseline first.

What is verifier a kind of?

Verifier is a kind of language model. A language model is a computational model that represents patterns in linguistic sequences to assign probabilities, predict, generate, or evaluate language.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.