Multi-domain thinking verifiers trained via Reinforcement Learning with Verifiable Rewards (RLVR) are a cornerstone of modern post-training. However, their adoption in code generation has lagged behind that of execution feedback due to the prohibitive costs of the full RLVR pipeline. In this work, we ablate three primary choices along the performance-cost trade-off in RLVR: intermediate thinking traces, learning from negative samples, and on-policy training. We introduce Aletheia, a controlled, execution-grounded testbed to facilitate a contamination-free analysis of code verifier training recipes across disparate model sizes and covariate shifts across two common verifier application scenarios. Our analysis reveals that the optimal training recipe is scale-dependent: on-policy learning is the primary performance driver for small verifiers, whereas the thinking budget becomes the most vital factor at larger scales. While leveraging negative samples has a consistent impact on top-1 selection accuracy across sizes, their contribution to ranking reconstruction increases monotonically with scale and plays a key role in stabilizing training at large sizes. Our Pareto optimality analysis demonstrates that eliminating on-policy training at larger model scales yields a verifier that performs comparably to the full RLVR recipe. Furthermore, we find that eschewing thinking traces serves as a compute-efficient strategy at lower budgets, offering a strong trade-off between training cost and verifier accuracy. Ultimately, our work provides the empirical foundation necessary to efficiently deploy robust code verifiers, thereby enabling their wider adoption in post-training pipelines for large code generation models.
This organization hosts the official release of the Aletheia benchmark: the datasets and fine-tuned code verifier models accompanying the paper "Aletheia: What Makes RLVR For Code Verifiers Tick?"
Fine-tuned code verifiers at 1.5B, 7B, and 14B scales using several algorithms:
| Algorithm | Thinking | Negatives | Online | Description |
|---|---|---|---|---|
| GRPO-Think | ✅ | ✅ | ✅ | Standard GRPO-style approach to training verifiers. |
| GRPO-Instruct | ❌ | ✅ | ✅ | RLVR training without intermediate thinking traces. |
| RAFT | ✅ | ❌ | ✅ | On-policy rejection sampling fine-tuning using only positive reasoning samples. |
| DPO-Think | ✅ | ✅ | ❌ | Offline preference optimization using pre-collected thinking traces. |
| BatchOnline-GRPO | ✅ | ✅ | ⚠️ | Semi-online training where the generator policy is synced every 4 steps. |
The -4k / -8k / -16k suffix on GRPO-Think checkpoints denotes the reasoning-token budget (maximum completion length) used during training.
The Aletheia dataset collection includes:
If you find this work useful, please cite our paper:
@misc{venkatkrishna2026aletheiamakesrlvrcode,
title={Aletheia: What Makes RLVR For Code Verifiers Tick?},
author={Vatsal Venkatkrishna and Indraneil Paul and Iryna Gurevych},
year={2026},
eprint={2601.12186},
archivePrefix={arXiv},
primaryClass={cs.SE},
url={https://arxiv.org/abs/2601.12186},
}
This work is licensed under CC BY-NC-SA 4.0.