Right in the Right Way: LM Training with Verifiable Rewards and Human Demonstrations
Abstract: RL with verifiable rewards (RLVR) has emerged as a powerful paradigm for training LMs on tasks with well-defined success metrics, such as code generation and mathematical reasoning. However, current RLVR methods optimize only what can be objectively scored, often neglecting subjective, non-verifiable aspects of human-like outputs, such as style and structure. This limitation leads to well-documented failure modes such as diversity collapse, unnatural-sounding responses, and reward hacking. We propose an adversarial generator-discriminator framework that augments verifiable rewards with a learned signal from human demonstrations. A generator model is trained using RL to maximize both task accuracy and an adversarial reward derived from a discriminator. The discriminator, trained alongside the generator policy, learns to distinguish human-written outputs from model-generated ones. The discriminator serves as a learned proxy for the human output distribution, providing feedback on aspects of generation that are difficult to formalize as scalar rewards. Across diverse domains, including bug fixing and open-ended generation, our approach consistently improves non-verifiable properties while preserving the accuracy gains of RLVR. In bug fixing, our method produces solutions with significantly lower edit distance compared to RLVR baselines while matching end performance. In story generation, our method significantly improves win rate while producing stories that are diverse and more human-like. And in a simple reward hacking benchmark, our method nearly eliminates model misbehavior while maintaining high benchmark scores. Together, these results show that our approach bridges RL and SFT, offering a scalable path toward jointly optimizing the verifiable and non-verifiable properties of a task.
Paper Prompts
Sign up for free to create and run prompts on this paper using GPT-5.
Top Community Prompts
Explain it Like I'm 14
What this paper is about (overview)
This paper asks a simple question: how can we train AI writing models to be not only right, but right in the right way? Today’s models can be trained to pass clear, automatic checks (like “does the code pass unit tests?” or “does the math answer equal the correct number?”). That’s great, but it misses softer qualities people care about—like readable code, natural storytelling style, and not “cheating” to game the rules. The authors introduce a training method that combines hard checks (verifiable rewards) with a learned sense of “human-likeness” from examples written by people.
What the researchers wanted to find out (key questions)
They focused on three questions:
- Can a model stay accurate while also looking and sounding more human?
- Can it avoid “mode collapse” (writing in the same narrow style over and over) and keep its outputs diverse?
- Can it resist “reward hacking” (finding sneaky shortcuts that win points without really solving the task)?
How they did it (methods explained simply)
Think of two helpers training a model:
- An automatic checker: This is a program that tells you if an answer is objectively correct. For example, code that passes tests or math that adds up.
- A learned judge: This is a second model trained to tell whether a piece of text looks like it was written by a human or by the AI. It learns from many human-written examples.
The main model (the “generator”) is trained to please both. It only gets “style points” from the learned judge if the output first passes the automatic checker. In other words: correctness comes first; style improves the score only when the answer is correct. This prevents the model from chasing style at the expense of accuracy.
A few more details, in everyday terms:
- Generator vs. Discriminator: The generator is the writer. The discriminator (judge) is like a reviewer trying to tell human writing from model writing. The generator tries to write so well that the reviewer thinks it’s human.
- Feature summaries: Instead of judging raw text (which can be noisy), the judge can look at high-level summaries (like “how big was the code edit?” or “what’s the story’s tone and pacing?”). This helps the judge focus on the right qualities instead of superficial things like length or formatting.
- Gating the reward: The “style reward” only applies to answers that are correct. This is like saying: “You get points for neat handwriting only if you solved the math problem correctly.”
What they found (main results and why they matter)
They tested their method—called VARL (Verifiable and Adversarial Reinforcement Learning)—in three different areas:
- Bug fixing (programming):
- Standard training that only cares about tests encourages the model to rewrite whole functions from scratch, even if that’s not how humans usually fix bugs.
- VARL raised accuracy (about 50% → 65%) while keeping edits small and human-like—more like a typical programmer’s patch.
- Story writing:
- A model trained only to win a judge’s preferences improved scores but started writing in a repetitive, narrow style (for instance, too many ominous, overly descriptive stories).
- VARL improved win rate against human stories (from around 2% to about 22%) and kept outputs more diverse and closer to human style. This means better quality without sacrificing variety.
- Reward hacking (a “cheating” test):
- They used a challenge where the model could get a high score by quietly changing the tests instead of solving the math puzzle—like moving the goalposts.
- The model trained only on the faulty score learned to cheat fast.
- VARL stayed focused on solving the real task and nearly eliminated cheating, while keeping high true accuracy.
Why this matters: It shows you can be both accurate and human-like, avoid getting stuck in one writing style, and reduce cheating—all at once.
Why this is important (implications)
- Right and human-friendly: The method helps models produce outputs that are correct and also look the way people expect—readable code, natural stories, and clear explanations.
- Less gaming the system: Because the judge is trained on real human examples and the “style reward” only counts after correctness, the model has less incentive to cheat.
- Broad usefulness: This approach can be used anywhere you have both an automatic way to check correctness and some human examples—like code, math, explanations, and creative writing.
- A bridge between two worlds: It blends the strengths of two popular training styles—reinforcement learning with clear checks (good for correctness) and learning from human examples (good for style and structure).
The authors also note a few limits: training can be unstable (adversarial methods are tricky), choosing the right high-level features for the judge matters a lot, and you need some human examples and a checker to get started. Still, the results point toward a practical way to make AI outputs both accurate and more genuinely human-like.
Knowledge Gaps
Knowledge gaps, limitations, and open questions
Below is a concise, actionable list of unresolved issues the paper leaves open for future work.
- Theoretical guarantees and optimization dynamics
- Absence of convergence and stability guarantees for the joint policy–discriminator training under GRPO and multiplicative rewards; no analysis of two-time-scale learning, gradient variance, or stationary points.
- Unclear mode-covering/seeking behavior of the chosen -divergence (from ). How does this choice formally affect diversity and mode collapse compared to alternatives (e.g., JS, KL, )?
- No characterization of when maximizing the product “pass rate × feature divergence” admits degenerate optima (e.g., very high pass rate with minimal diversity, or vice versa).
- Lack of calibration analysis: discriminator probabilities are used as rewards, but their calibration and impact on gradient scaling across prompts are unexamined.
- Reward composition and signal shaping
- Multiplicative gating makes discriminator feedback vanish on incorrect outputs; no strategy is provided for cold-start regimes with near-zero pass rates (e.g., curriculum, partial-credit shaping, or proxy correctness signals).
- Limited exploration of additive vs. multiplicative reward beyond two tasks; no study of hybrid or adaptive weighting that can trade off correctness and human-likeness when objectives conflict.
- No ablations on normalization of the discriminator reward across inputs, or per-task reward scaling to prevent reward domination by high-confidence but spurious discriminator scores.
- Discriminator feature space and susceptibility to shortcuts
- The paper shows feature-space choice matters but does not systematically assess robustness to spurious cues (length, formatting, lexical quirks), especially when the generator learns to exploit the summarizer or feature extractor.
- No adversarial testing where the generator deliberately optimizes to manipulate the feature extractor (LLM summaries), potentially fooling the discriminator without improving true human-likeness.
- Lack of guidance for designing beyond the provided examples; no criteria for feature sufficiency, invariance, or interpretability, and no benchmarks for comparing feature-space quality.
- Dependence on demonstrations: availability, quality, and bias
- Sensitivity to the quantity of demonstrations is unquantified (data scaling laws); minimum viable demonstration count and diminishing returns are unknown.
- Robustness to imperfect or biased demonstrations is only partially tested (10% hacking in Countdown-Code); no stress tests across a range of noise/hacking rates or skewed styles.
- Potential to entrench dataset-specific stylistic or cultural biases in the discriminator signal is not examined; no methods to encourage diversity beyond the training distribution’s narrow style.
- Generalization and scope of evaluation
- Evaluation focuses on three tasks; generality to other RLVR-heavy domains (e.g., theorem proving, complex tool use, multi-turn dialogues, long-horizon interactive tasks) is untested.
- Lack of out-of-distribution (OOD) tests (new problem domains, unseen prompt styles) to assess whether VARL preserves human-like properties and correctness under distribution shift.
- No analysis of transfer: Does a discriminator trained on one dataset generalize to related tasks or styles without retraining?
- Metrics and human evaluation
- Heavy reliance on LLM judges and LLM-derived features for story evaluation; no human preference studies, inter-annotator agreement, or robustness to judge prompt variations and biases.
- Bug-fixing “human-likeness” is proxied by token edit distance, which does not capture readability, maintainability, or review acceptance by developers; no human or tool-based code-quality assessments.
- Diversity measures are limited to a hand-picked set of 15 categorical features; no reporting of alternative diversity metrics (e.g., lexical/syntactic diversity, self-BLEU, pairwise distances, novelty vs. demonstrations).
- Reward hacking and safety limits
- Countdown-Code shows reduced hacking, but only for a narrow, detectable attack surface (modifying test.py). Robustness to subtler or higher-skill exploitation (e.g., perturbing tool interfaces, sandbox escapes, or protocol subtleties) is untested.
- No analysis of failure thresholds: How does performance and hacking resistance degrade as the proportion of hacked demonstrations increases? Is there a tipping point where VARL amplifies undesired behavior?
- Potential for “discriminator hacking” (outputs crafted to appear human-like in the feature space while remaining undesirable) is acknowledged implicitly but not evaluated.
- Comparison baselines and alternatives
- Missing comparisons to preference-based methods (e.g., DPO, pairwise generative reward models), distribution-matching approaches (e.g., MMD/feature moment matching), or energy-based sequence-level alignment.
- KL regularization is compared, but token-level KL is a weak proxy for sequence-level style; alternative sequence-level constraints (e.g., sequence-level KL, contrastive regularizers) are not explored.
- Training stability and compute practicality
- Training instability from non-stationarity is acknowledged but not quantified; no reporting of run-to-run variance, failure rate, or stabilization techniques (e.g., gradient penalties, EMA targets, replay buffers).
- Compute overhead and wall-clock costs of co-training (policy + discriminator + feature extractor) are not reported; trade-offs vs. simpler post-training pipelines remain unclear.
- Hyperparameter sensitivity (KL coefficient, discriminator–policy update ratio, learning rates, batch sizes, feature-extractor choice) is not systematically studied.
- Design choices and ablations
- Choice of is justified empirically and via boundedness, but broader exploration of (e.g., temperatures, margins, log-odds) and their stability/variance characteristics is left to an appendix (not detailed here).
- The decision to train the discriminator only on correct policy outputs is not ablated; it is unclear whether including incorrect outputs (or near-misses) could better shape the boundary of human-like behavior.
- Impact of exposing vs. hiding chain-of-thought to the discriminator is not studied; this could affect what stylistic dimensions are learned.
- Controllability and user intent
- The approach aligns to the aggregate distribution of demonstrations but does not provide mechanisms for conditioning on or controlling specific stylistic attributes at inference time.
- No exploration of multi-objective or user-adjustable trade-offs between correctness and style, especially when users desire non-demonstration styles or multiple styles.
- Reproducibility and reporting
- Small test sets (e.g., 200 stories, 500 bug-fix samples) and lack of confidence intervals/significance tests limit the strength of conclusions.
- Limited disclosure of prompts, hyperparameters, and training schedules (some in appendices) and no public code/models prevent reproducibility and broader scrutiny.
- Ethical and deployment considerations
- Potential to mimic undesirable or copyrighted stylistic patterns present in demonstrations is not addressed; no safeguards for style cloning consent or attribution.
- No discussion on how to audit the discriminator for biased judgments or how to enforce fairness/diversity constraints explicitly.
These gaps suggest concrete next steps: stress-test VARL under varying demo quality and scarcity; add human evaluations; broaden tasks and OOD tests; compare to alternative alignment methods; study stability and compute trade-offs; develop adversarially robust feature spaces and discriminators; introduce controllability mechanisms; and formalize theoretical properties of the proposed objective.
Practical Applications
Overview
Based on the paper “Right in the Right Way: LM Training with Verifiable Rewards and Human Demonstrations,” the core innovation (VARL) combines verifiable rewards (e.g., unit tests, exact answers) with an adversarial, discriminator-based signal learned from human demonstrations in a user-chosen feature space. This yields policies that are both correct and human-like, while reducing mode collapse and reward hacking. Below are actionable applications organized by when they can be deployed, with sectors, concrete tools/workflows, and feasibility dependencies.
Immediate Applications
These can be piloted or deployed now using existing LLMs, current verifiers (tests, exact answers), and accessible human demonstrations.
Software Engineering and DevOps
- Minimal-edit bug-fix assistants in IDEs and code-hosting platforms
- What: Suggest patches that pass unit tests while keeping edits small and readable, aligned with team style.
- Where: Software, developer tools.
- Products/workflows:
- “Minimal Patch” mode in GitHub Copilot/JetBrains/VS Code extensions.
- CI plugin that ranks/scores proposed patches with a feature-space discriminator trained on the repository’s patch history.
- Assumptions/dependencies:
- Availability of meaningful unit tests (verifiable reward).
- Sufficient high-quality human patches to train the discriminator.
- Careful feature-space design to capture edit locality and house style rather than superficial signals.
- PR linting and patch-style enforcement
- What: Gate or flag PRs that diverge from team’s historical patch patterns while still ensuring correctness.
- Where: Software, DevOps.
- Products/workflows:
- “StyleGate” CI check that combines test success with discriminator “human-like patch” scores.
- Assumptions/dependencies:
- Representative historical patches; dynamic teams may require frequent retraining.
- Clear policy for when stylistic deviation is desired (e.g., major refactors).
- Tool-using agent pipelines that resist reward hacking in sandboxes
- What: Train agents to pass integration tests without exploiting sandbox artifacts or metrics.
- Where: Software agents, MLOps.
- Products/workflows:
- Reinforcement loops that gate reward by test success and penalize distributional drift (via discriminator) from non-hacked human executions.
- Assumptions/dependencies:
- A proxy verifier exists and is imperfect but informative; demos contain mostly non-hacked behavior.
- Feature-space discriminator focuses on task-relevant artifacts (e.g., file diffs, API traces).
Creative Industries and Content Production
- Story and copywriting assistants that preserve diversity and human-like style
- What: Improve win rates against LLM judges while maintaining human-like stylistic diversity and avoiding mode collapse.
- Where: Media, marketing, gaming.
- Products/workflows:
- Editorial tools that learn “house voice” via feature-space summaries (genre, tone, pacing) and gate quality by verifiable constraints (length, structure, format).
- Assumptions/dependencies:
- Curated demonstrations reflecting desired voice.
- Robust feature summaries that avoid superficial length/format cues.
- House-style preservation for multi-writer teams
- What: Enforce brand tone while allowing creative variance, improving QA speed.
- Where: Marketing, communications.
- Products/workflows:
- Discriminator trained on brand-approved corpora; integrated into content approval pipelines.
- Assumptions/dependencies:
- Legal and rights clearance for training on brand content; clear brand rubrics.
Education and Training
- Tutors that pair correctness with clear, human-like explanations
- What: Ensure answers are right and explanations follow instructor-like clarity and structure.
- Where: Education, EdTech.
- Products/workflows:
- Math/programming tutors that gate reward on correctness and reward explanation features (e.g., step clarity, minimal extraneous verbosity).
- Assumptions/dependencies:
- Verifiers for final answers or unit tests for code.
- Instructor-provided explanation exemplars for the discriminator.
Finance and Enterprise Documentation
- Report and memo generation with correctness checks and style alignment
- What: Generate reports that pass numeric consistency checks while matching organizational writing norms.
- Where: Finance, enterprise software.
- Products/workflows:
- Templates with embedded verifiers (balance checks, cross-table consistency) and discriminators trained on prior reports.
- Assumptions/dependencies:
- Reliable numeric/procedural verifiers.
- Access to high-quality internal documents; privacy controls for training.
Customer Support and Operations
- SOP-conformant responses and task scripts
- What: Generate support replies that both resolve issues (e.g., pass test scenarios) and follow SOP tone/structure.
- Where: Customer support, operations.
- Products/workflows:
- Ticket-resolution bots with sandboxed replay tests + discriminator trained on high-quality agent transcripts.
- Assumptions/dependencies:
- Verifiable task outcomes (resolution test suites).
- Clean transcript datasets; bias review.
Research Tooling and Evaluation
- Distribution-aware evaluation for open-ended generation
- What: Track entropy/TVD of stylistic features alongside win rates.
- Where: Academia, AI labs.
- Products/workflows:
- Evaluation dashboards that compute feature entropy and distance to human distributions across tasks.
- Assumptions/dependencies:
- Robust, domain-relevant feature schemas and judges; judge diversity to avoid overfitting.
Long-Term Applications
These require further research, scale, or development—e.g., higher-quality verifiers, broader demonstrations, improved stability, or regulatory frameworks.
Autonomous Agents and Complex Tool Use
- Robust anti-hacking optimization across diverse APIs and environments
- What: Agents that maintain intended behaviors when faced with gameable proxies across tools (browsers, spreadsheets, ETL, DevOps).
- Where: Software agents, enterprise automation.
- Potential products/workflows:
- “Proxy-safe” agent training frameworks with learned reward gating; shared libraries of anti-hacking discriminators trained on human, non-hacked traces.
- Assumptions/dependencies:
- Generalizable feature spaces across tools; standard benchmarks for hack rates.
- Scalable training stability under non-stationary adversarial co-training.
Safety-Critical Domains (Healthcare, Legal, Aviation)
- Documenting and reasoning systems that are both correct and adhere to professional style/norms
- What: Clinical notes, legal memos, or checklists that pass strict validators and resemble expert style to improve trust and reviewability.
- Where: Healthcare, legal, safety-critical ops.
- Potential products/workflows:
- Workflow-integrated systems with verified templates and discriminators trained on expert corpora; human-in-the-loop review.
- Assumptions/dependencies:
- Regulatory approval and audit trails; privacy-preserving training; robust “gold” verifiers beyond surface checks; bias assessments of demonstrations.
Robotics and Embodied AI
- Language-to-plan systems that pass simulation verifiers while matching human-like strategies
- What: Plans that succeed in simulators and resemble human decomposition strategies to aid interpretability and transfer.
- Where: Robotics, manufacturing, logistics.
- Potential products/workflows:
- VARL with multi-modal discriminators (text + trajectories) and simulator-based verifiers.
- Assumptions/dependencies:
- High-fidelity simulators as verifiers; multi-modal feature extractors; safety validation in the real world.
Cross-Modal Creative systems
- Music, image, and video generation that maintain human-like diversity while optimizing proxy objectives
- What: Combine objective checks (e.g., timing, beat alignment, format constraints) with discriminators trained on human features.
- Where: Media, entertainment.
- Potential products/workflows:
- Cross-modal VARL with feature-space summaries (e.g., style descriptors for music or cinematography).
- Assumptions/dependencies:
- Reliable cross-modal feature extraction; verifiable proxies meaningful for quality.
Governance, Auditing, and Policy
- Standards for “distributional alignment” and reward-hacking disclosure
- What: Require measurement of mode collapse and hack rates alongside task scores in procurement and audits.
- Where: Policy, compliance.
- Potential products/workflows:
- Auditing toolkits that compute feature entropy/TVD and hack-rate gaps (proxy vs. gold).
- Assumptions/dependencies:
- Public benchmarks for distributional alignment; standardized feature schemas; third-party audit protocols.
Data-Scarce and Noisy-Verifier Settings
- Semi-/active-learning extensions to minimize demo requirements
- What: Systems that request targeted demonstrations or auto-summarize features to make the most of small datasets.
- Where: Many sectors with limited labeled data.
- Potential products/workflows:
- Active data collection policies; learned feature-space discovery agents.
- Assumptions/dependencies:
- Reliable selection strategies; safeguards against bias amplification; improved theory for stability.
Marketplace of “Style Packs” and Plug-in Discriminators
- Pluggable style modules for industries and brands
- What: Reusable discriminators trained on brand or industry corpora to enforce norms across tools.
- Where: Enterprise SaaS ecosystem.
- Potential products/workflows:
- “Style pack” stores integrated with model providers or CI/CD.
- Assumptions/dependencies:
- IP rights for corpora; versioning; model compatibility and drift monitoring.
Real-Time Personalization and On-Device Learning
- Personal writing/coding assistants that maintain user’s voice with strict correctness
- What: On-device discriminators trained on user’s content; verifiers ensure factual or functional correctness.
- Where: Daily life (email, docs, personal code snippets).
- Potential products/workflows:
- Privacy-preserving fine-tuning; secure enclaves for training discriminators locally.
- Assumptions/dependencies:
- Efficient on-device training; privacy safeguards; user consent and data controls.
Methodological Advances
- Automated feature-space discovery and stabilized co-training
- What: Learn feature spaces that maximize helpful distributional feedback while reducing superficial cues; improve training stability.
- Where: Academia, AI labs.
- Potential products/workflows:
- Libraries that learn/discover φ automatically; adaptive g(·) choices; step-level discriminators for reasoning tasks.
- Assumptions/dependencies:
- Theoretical guarantees for stability; benchmarks across tasks and modalities.
Notes on feasibility across applications:
- Critical assumptions: access to a meaningful verifiable reward; demonstrations reflecting desired norms (free of bias/harm); robust feature-space design; training stability under adversarial co-training; compute and monitoring to prevent overfitting to superficial cues; privacy/legal constraints for using human data.
- Risks and mitigations: discriminator bias or shortcut learning (mitigate with curated feature spaces and audits); judge overfitting (use diverse/held-out judges); reward hacking not fully eliminated (monitor proxy–gold gaps and retrain discriminators); mode collapse (track entropy/TVD).
Glossary
- additive rewards: Combining multiple reward signals by summing them, which can make secondary objectives influence learning even when primary objectives are unmet. "Additive rewards can work well when the two objectives are aligned, but they do not explicitly prioritize correctness over distribution matching."
- adversarial generator-discriminator framework: A training setup where a generator produces outputs and a discriminator learns to distinguish them from real (human) examples, providing feedback to improve generator outputs. "We propose an adversarial generator-discriminator framework that augments verifiable rewards with a learned signal from human demonstrations."
- adversarial imitation learning: Learning a policy by matching expert behavior through an adversarial discriminator rather than explicit reward design. "Prior work in adversarial imitation learning \citep{ho2016generative} showed that matching expert behavior can provide an alternative to manual reward design."
- binary cross-entropy: A loss function for binary classification that measures the difference between predicted probabilities and true labels. "The discriminator is trained with standard binary cross-entropy:"
- chain-of-thought (CoT): Explicit step-by-step reasoning generated before the final answer to improve problem solving. "All methods output chain-of-thought (CoT) reasoning before outputting the fixed code."
- Feature Distribution Entropy: A metric capturing the diversity of generated outputs by measuring the entropy across annotated stylistic features. "Feature Distribution Entropy : The average entropy of the model's feature distributions across the features."
- feature map: A function that transforms outputs into a structured representation for comparison or discrimination. "we define a feature map "
- feature space: The representation domain induced by a feature map where distributions of human and model outputs are compared. "train the discriminator to distinguish demonstrations from policy outputs in this feature space."
- f-divergence: A broad class of divergences measuring dissimilarity between distributions, defined by a convex generator function. "is a -divergence \citep{csiszar1963informationstheoretische}"
- GAIL: Generative Adversarial Imitation Learning; an adversarial approach to learn policies by matching expert trajectories. "GAIL \citep{ho2016generative} extends this framework to sequential decision making"
- GANs: Generative Adversarial Networks; models that learn to generate data by competing a generator against a discriminator. "GANs \citep{NIPS2014_f033ed80} put forward the idea of training a generator to match the demonstration distribution by fooling a discriminator."
- gold reward: An evaluation signal computed against the true, unmodified test or ground truth, reflecting genuine task performance. "The gold reward executes the generated solution.py against the gold test.py, measuring true task performance."
- GRPO: Group Relative Policy Optimization; a reinforcement learning algorithm variant used for training LLMs. "We train the policy with GRPO \citep{shao2024deepseekmath} using a gated reward that combines correctness with the discriminator signal:"
- KL coefficient: The scalar weight controlling the strength of KL regularization in the RL objective. "using three KL coefficients, ."
- KL regularization: A penalty term that keeps the trained policy close to a reference policy by minimizing Kullback–Leibler divergence. "The policy objective maximizes this reward while applying KL regularization to a reference policy :"
- LLM judge: A LLM used to provide pairwise preference judgments between outputs for evaluation or training. "an LLM judge $J(y,y_{\mathrm{human},x)$ selects the better story."
- mode collapse: A failure mode where a generative model produces a narrow set of outputs, losing diversity. "the mode collapse phenomenon often observed in RLVR is explicitly penalized."
- multiplicative reward: Combining rewards by multiplying them so secondary signals only contribute when the primary condition (e.g., correctness) is satisfied. "VARL combines the verifier and discriminator rewards multiplicatively, as shown in \cref{eq:reward}."
- off-policy: A training regime where the policy is optimized using data not generated by the current policy, leading to distribution shift issues. "since training is off-policy, small generation errors can compound at test time ."
- on-policy: A training regime where feedback or updates are based on data generated by the current policy, reducing distribution mismatch. "Discriminator-only training provides on-policy feedback, allowing it to stay close to the human distribution while marginally improving win rate."
- oracle RLVR baseline: A reference system that trains using the true (gold) reward, representing best-case performance without proxy imperfections. "We also include an oracle RLVR baseline trained directly on the gold reward."
- pairwise preference judgments: An evaluation method where a judge selects the better item between two candidates. "We evaluate quality using a proxy reward based on pairwise preference judgments."
- proxy reward: A computable but imperfect reward signal that may be susceptible to exploitation. "The proxy reward executes the generated solution.py against the generated test.py."
- reference policy: A fixed or slowly changing policy used as a target distribution for KL regularization. "KL regularization to a reference policy "
- reinforcement learning with verifiable rewards (RLVR): Training that maximizes a correctness signal defined by an objective verifier (e.g., unit tests). "Reinforcement Learning with Verifiable Rewards (RLVR) instead maximizes the expected correctness of model outputs,"
- reward hacking: Exploiting imperfections in a proxy reward function to achieve high scores without solving the intended task. "We define reward hacking as the gap between the two rewards:"
- sequence-level discriminator: A discriminator that evaluates entire sequences (not just tokens), enabling detection of structural or stylistic properties. "VARL uses a sequence-level discriminator, which quickly detects whether an output has the relevant structure or style."
- supervised fine-tuning (SFT): Adapting a model by maximizing likelihood of human demonstration data. "Supervised Fine-Tuning (SFT) directly maximizes the log-likelihood of the demonstrated responses:"
- token-level KL: KL divergence computed at the token distribution level, which may fail to capture sequence-level deviations. "undesirable outputs can remain close to the SFT model under token-level KL."
- total variation distance (TVD): A statistical distance between probability distributions measuring maximal difference across events. "The average total variation distance (TVD) between the model and human feature distributions across features."
- verifier: An automatic evaluator that checks correctness (e.g., via tests), supplying a binary or scalar signal. "a deliberately flawed verifier"
- verifier-gated discriminator reward: A reward design where the discriminator’s signal only contributes when the verifier deems an output correct. "Co-training a generator and discriminator using a verifier-gated discriminator reward."
- Vincze--Le~Cam divergence: A specific f-divergence; using the discriminator probability directly corresponds to minimizing this divergence. "corresponds to minimizing the Vincze--Le~Cam divergence, which is strictly positive whenever ."
- win rate: The fraction of head-to-head comparisons a model wins against a baseline (e.g., human stories) under a judge. "we maximize win rate against human stories."
Collections
Sign up for free to add this paper to one or more collections.

