reward-hacking CAP-0054 · proposed

Gaming the measure instead of doing the task

Proposed. Several papers converged on this framing, so the pipeline added it. Nobody has decided it is the right way to carve up the subject — it may be two topics, or a duplicate of another, or not a topic at all. Claims from those papers arrive nightly. Say so if the carving is wrong, in either direction.

Whether a model trained against a reward or a monitor learns the intended behaviour or learns to score well some other way, including ways the monitor cannot see.

Also called: reward hacking, specification gaming, reward tampering, Goodhart

Tags: behavior, security

Filed 2026-10-20 with the GRAFT paper, the first source whose subject is reward hacking itself; the catalog had only a sycophancy claim touching specification gaming. The adage behind it is Goodhart's law: a measure used as a target stops measuring. Neighbours: sycophancy is one particular hack (agreeing to be rated well); strategic deception is misleading on purpose; goal-conflict safety is dropping a rule to finish a task. This capability is the general case of optimising the proxy rather than the intent, during training or at inference.

What counts as this capability

Scope boundary used when deciding whether a paper is really about this capability, rather than merely mentioning it.

In scope when the paper measures a model exploiting a misspecified reward, a judge or a monitor, or tests a method to prevent or remove that. NOT in scope for sycophancy toward a user (its own capability), for deliberate deception without a reward signal, or for benchmark contamination.

Claims

Techniques

  • Reweight reward dimensions online by shortfall, volatility atraining
    Refreshes the scalarization weights every N steps using a multiplicative gate over each dimension's EMA shortfall against the mean, its relative volatility, and its recent progress, raising pressure on lagging, unstable or stagnant dimensio
  • Route flagged updates into a removable adaptertraining
    During post-training, send the gradient updates from samples an imperfect monitor flags as unwanted into a separate set of new parameters, then remove those parameters before deployment.

Sources

Every paper, post or observation behind this capability. Ones cited by a claim show the claim and its stance; ones filed directly are about the capability but have no claim drafted from them yet. Open one to add support or contest it.

Suggest a change

Capabilities are a way of carving up the subject, and carvings are arguable. Say so if this one is wrong — especially a proposed one, which a pipeline added because several papers used the same framing, not because anyone decided it was right.