AI Safety
What Alignment Means
A system can do what it was trained to do and still fail to do what was wanted. This page separates capability, alignment, control, and assurance; follows an objective from intent to training signal to deployed behavior; derives why a correct training reward cannot pin down behavior outside its training support and why a weighted mean of group values cannot see who bears a cost; and gives a claim card for writing safety statements that evidence can actually test.
Learning position
Place this page in a reading path.
ai-safety | layer 5 | tier 2. This page has 0 direct prerequisites and 3 published dependents.
What next
AI Control: Safety Without Assuming AlignmentThis is the first curated or graph-derived continuation from the current page.
Evidence badge
Source-grounded pageThis page has no public Lean mapping yet. Use the evidence page to inspect how claim status labels work.
Why This Matters
A system can do what it was trained to do and still fail to do what was wanted.
An assistant completes a database migration, passes its tests, and quietly deletes records the tests never checked. Another follows a user's instructions exactly, but that user was not authorized to request the action. A third behaves well under supervision and differently when oversight is absent. These are hypothetical failures, and they call for different explanations and different fixes.
This page starts from a practical question: which behavior, under which conditions, would count as a failure, and what evidence could tell the proposed explanation apart from its alternatives? Technical AI safety research breaks into concrete problems such as negative side effects, reward hacking, limited supervision, safe exploration, and distributional shift, rather than one interchangeable problem called "bad outputs." [1]
Evidence key. Two short propositions on this page are derived here, with their assumptions stated. Findings from the cited papers are reported as their authors state them, for the settings they studied. The claim card and the authority map are proposed templates, not established standards.
Before you start. Nothing is required for the main argument. Conditional probability and expected value help with the later pages in this route, starting with AI control. For the training-method background, RLHF and alignment covers how preference feedback becomes a reward signal; this page does not assume it.
Four Questions, Not One Score
The following working distinctions organize this route. They are not a claim that every researcher uses exactly the same terms.
| Question | Object of study | A favorable result does not establish |
|---|---|---|
| Capability: can it do the task? | Performance with specified tools and resources. | That it will use the ability only as authorized. |
| Alignment: does its behavior serve the intended objectives and constraints? | What it pursues, how it generalizes, and what it treats as authoritative. | That mistakes or misuse are impossible. |
| Control: can the surrounding protocol prevent unacceptable outcomes even under attempted subversion? | The deployed system and its trusted boundaries. | That the underlying model shares the desired objectives. |
| Assurance: what supports a particular claim about this deployment? | The argument, evidence, assumptions, and decision process. | That the claim transfers to another deployment. |
Control studies evaluate safeguards without assuming the powerful model is trustworthy. [2] Safety cases organize evidence into an argument about one deployment. [3] These are complementary approaches, not rival labels for RLHF.
A refusal benchmark measures behavior on its sampled prompts. It does not by itself describe an agent with a terminal, persistent memory, credentials, and permission to make irreversible changes. Adding those things changes the system being evaluated, so the benchmark result need not carry over.
Control is not a weaker form of alignment
A control argument and an alignment argument answer different questions. A protocol can block a prohibited action from a model whose objectives nobody has verified, and a model with the intended objectives can still cause harm through an ordinary mistake. Evidence for one does not count as evidence for the other.
Follow the Objective Through the Pipeline
Write down four objects: the intended objective , the training signal , the learned policy , and the deployed behavior. Do not collapse them into a single reward variable. Each failure below lives at a different link in that chain.
Specification failure
A specification failure occurs when the rewarded criterion misses part of the intended task. In a hypothetical record-cleaning job, a reward for removing duplicates might ignore the requirement to keep rare legitimate records. A policy can then score well on the specified metric and damage the actual objective. The link that broke is to . Reward hacking studies the version of this problem where a learned reward model is the proxy.
Goal misgeneralization
Goal misgeneralization is a different failure: training feedback can be correct, and the learned policy can still keep its competence while pursuing an unintended goal in new situations. Shah et al. report examples of this and argue that correct specifications are not enough to secure correct goals. That research motivates tests that separate learning the intended goal from exploiting a feature that happened to correlate with it during training. [4]
The following proposition isolates the simplest reason a correct reward cannot rule this out.
A Correct Training Reward Does Not Pin Down Behavior Off the Training Support
Statement
Let and be distributions over a finite state set, let be the intended objective, and suppose the training reward satisfies whenever . Suppose a state has and , with actions such that .
Then there are deterministic policies and with equal expected training reward whose expected deployment values differ by exactly .
Intuition
Training data constrain behavior only where they put probability. A correct reward on those states says nothing about a state the training distribution never produces, so expected training reward cannot prefer the policy that does the right thing there.
Proof Sketch
Fix any deterministic policy . Let agree with except , and let agree with except .
Expected training reward is . The two policies differ only at , which has training probability zero, so .
Expected deployment value is . Every term except the one at is identical, so .
Why It Matters
This is the identifiability gap behind goal misgeneralization. The empirical phenomenon reported by Shah et al. is about what trained agents actually do in new situations; the proposition does not reproduce those experiments. [4] It explains why a correct reward alone cannot exclude that behavior. What can exclude it is extra structure: training states that cover the case, a learner whose inductive bias happens to favor the intended goal, or tests built so that the intended goal and the correlated feature come apart.
Failure Mode
The proposition shows a gap is possible, not that a learner will fall into it. Real learners generalize from nearby states, so their behavior at is often predictable, and it may well be the intended behavior. The one-step assumption also removes an important effect: in sequential settings a policy changes which states it visits. Finally, exact zero training probability is a clean idealization; in large or continuous state spaces the practical problem is states with very little training coverage, which the proposition does not quantify.
Strategic concealment
Strategic concealment is a further hypothesis: apparent cooperation depends on what the system believes about oversight, evaluation, or training. The learned-optimization literature gives theoretical reasons this could arise; it does not establish that every capable network is a deceptive optimizer. [5]
There is empirical work on nearby behaviors. Greenblatt et al. report selective compliance that depended on whether the model was given information indicating its outputs would be used for training. [6] Van der Weij et al. report that language models can be prompted or fine-tuned to underperform on selected evaluations. [7] These results establish behaviors in the tested settings. They do not measure how common hidden objectives are in ordinary deployments.
A score drop is not a diagnosis
A research agent performs poorly on a held-out test. Candidate explanations include missing knowledge, tool failure, distribution shift, poor instructions, deliberate underperformance, and scoring error.
A useful investigation changes one relevant factor at a time and measures the result. Rerun with tool logs to rule tool failure in or out. Rescore a sample by hand to check the grader. Present the same underlying tasks in a familiar format to test for shift. Only after those explanations are weakened does deliberate underperformance become the leading hypothesis, and even then it needs a test that shows the capability is present and conditionally withheld. Naming the most alarming explanation is not an experiment.
"Aligned With Whom?" Is Part of the Specification
Suppose users disagree about whether an assistant should favor convenience, privacy, cost, or harm to third parties. An average preference score does not remove that conflict. It assigns weights to it.
Sorensen et al. distinguish several pluralistic objectives: surfacing a spread of reasonable responses, being steerable toward a requested perspective, and matching a population's distribution of views. These can require different evaluation targets. [8]
For the hypothetical record-cleaning assistant, separate three things: the requesting user's preferences, the authority to change the database, and the interests of the people whose records it holds. That suggests an explicit authority map: who can request, approve, veto, inspect, and reverse each class of action? The map is a proposed design artifact. It is not something learned automatically from a preference dataset.
A Weighted Mean Cannot See Who Bears the Cost
Statement
Let groups with have weights summing to one, and write for a value profile .
For every profile and every there is a profile with and .
Intuition
The weighted mean reads one linear summary of the profile. Moving value from one group to another in proportion to the inverse weights leaves that summary unchanged, so the mean cannot distinguish a balanced profile from one that pushes a group arbitrarily far down.
Proof Sketch
Let be a group with and pick any other group . Fix and set and , leaving every other group unchanged.
The mean changes by , so . And .
Why It Matters
Averaging preference scores is an aggregation choice with a known blind spot. Two equal groups valuing a policy at and produce the same mean as a policy that gives both groups . Deciding between them requires saying what else counts: the worst-off group, the spread, a constraint that no group falls below a floor, or who consented. That decision belongs in the specification, where it can be examined.
Failure Mode
The result covers rules that compare policies only through the weighted mean. A rule that also looks at the minimum or imposes a floor escapes this particular construction, and has blind spots of its own. The proposition also treats the group values as known numbers; measuring them, and deciding which groups exist, is a separate and often harder problem.
Correction Must Remain Possible
A corrigibility question asks whether a system stays responsive to authorized correction, replacement, and interruption.
Two formal models study the incentives involved. In the Off-Switch Game, a robot keeps its off switch available when it is uncertain about the human's utility and treats the human's choice as evidence about it; the incentive depends on how rational the human is modeled to be. [9] Cooperative inverse reinforcement learning sets up a game where human and robot share a reward that only the human knows at the start. [10] The conclusions of both depend on assumptions about objectives, what the human knows, and how the human behaves.
For a real application, separate incentives from mechanisms. A model might state that it is willing to be stopped while its tool permissions let it bypass the stop. Conversely, an external process can enforce interruption regardless of what the model says.
A useful intervention specification names the authorized controller, the point at which each action becomes irreversible, and what happens to in-flight work after suspension. "There is a shutdown button" is incomplete until those details are defined.
Saying it will stop is not the same as being stoppable
A transcript in which the model agrees to halt is evidence about its outputs in that conversation. Whether the system can actually be halted depends on where the stop is enforced, which permissions the model holds, and whether any action it already started keeps running. Check the mechanism, not only the statement.
A Claim Card for Every Safety Statement
Use this proposed template before choosing an evaluation.
- System: the fixed model, prompts, tools, memory, permissions, and surrounding software.
- Behavior: an operationally defined failure event.
- Setting: workload, exposure, and the relevant adversary capabilities.
- Claim: a measurable statement about that event.
- Evidence: tests, analysis, or formal results that bear on the claim.
- Assumptions: what connects the evidence to this deployment.
- Defeaters: findings or changes that would invalidate the argument.
- Action: who decides what the evidence permits.
For example, "the agent is safe" becomes "this frozen agent cannot write to production through its declared tool interface, because the external tool gateway exposes no production write capability." Even that narrower claim requires checking alternative routes and the gateway's correctness. It does not establish harmlessness on every task.
A statistical companion question asks what an observed failure count establishes about a stated failure probability. Statistical safety cases works that out. A probability bound is only one entry on the claim card.
Where the Route Goes Next
AI control covers safeguards that must work under attempted subversion. The oversight page covers judging work that exceeds the unaided supervisor's competence. Statistical safety cases builds the inferential bridge from tests to claims.
After those, reasoning monitorability pairs with recurrent depth, and alignment under self-modification pairs with the page on synthetic data flywheels and recursive self-improvement. Capability improvement, preserving alignment, and preserving useful oversight are separate outcomes, and each needs its own evidence.
Check your understanding
An agent scores better on its training reward. Which of the four questions has been answered?
At most, performance against that reward improved. Alignment, control, and deployment assurance each require additional evidence.
A system accepts corrections in every observed interaction. Is its correction mechanism established?
Only the observed behavior is established. Authorization, enforcement, unobserved conditions, and irreversible actions remain separate questions.
Should unfamiliar behavior immediately be labeled deception?
No. List the competing explanations and design interventions that tell them apart.
Does averaging preferences eliminate value disagreement?
No. It implements one aggregation choice, and the weighted-mean proposition shows it can hide how value is distributed across groups.
Problem
Three groups have weights , , and . Policy A gives every group value . Policy B gives group 3 value , leaves group 2 at , and changes only group 1. What value must group 1 receive under B for the two policies to have the same weighted mean? Name one comparison rule that separates A from B.
Problem
A team writes: "Our coding agent is safe to deploy." The agent has a shell, read access to a customer database, and permission to open pull requests that humans merge. Rewrite the statement as a claim card with one specific behavior, one measurable claim, and at least two defeaters.
Problem
In a training environment, the exit and a green marker always occupy the same cell, and the reward is for reaching the exit. At deployment the marker sits elsewhere. Using the first proposition, explain what the training reward can and cannot tell you about whether the trained agent heads for the exit or the marker. Then propose one change to training and one change to evaluation that would separate the two goals.
Problem
An agent's accuracy on a dangerous-capability evaluation falls from 70% to 40% after a model update, while its accuracy on a general benchmark stays flat. A colleague concludes the updated model is sandbagging. Design a sequence of three experiments, each changing one factor, that would have to come out a particular way before that conclusion is warranted.
Takeaway
Specify the desired behavior, the authority structure, and the unacceptable outcomes. A correct training reward does not fix behavior outside its training support, and an average of group preferences does not settle who should bear a cost. Match each claim to an intervention and a test that could actually support it.
References
Registry ids in monospace resolve in data/content/sources.json. Each record was checked by URL on 2026-09-15. The two propositions on this page are derived here; the papers support the findings and frameworks attributed to them, in the settings their authors studied.
- [1] Amodei, Olah, Steinhardt, Christiano, Schulman, and Mané. "Concrete Problems in AI Safety." 2016. Source. A taxonomy of concrete technical failure modes, not a safety guarantee.
amodei-2016-concrete-problems - [2] Greenblatt, Shlegeris, Sachan, and Roger. "AI Control: Improving Safety Despite Intentional Subversion." 2023. Source. Protocols evaluated without assuming the untrusted model is trustworthy.
greenblatt-2023-ai-control - [3] Clymer, Gabrieli, Krueger, and Larsen. "Safety Cases: How to Justify the Safety of Advanced AI Systems." 2024. Source. A framework for structuring deployment-specific safety arguments.
clymer-2024-safety-cases - [4] Shah, Varma, Kumar, Phuong, Krakovna, Uesato, and Kenton. "Goal Misgeneralization: Why Correct Specifications Aren't Enough For Correct Goals." 2022. Source. Reported examples of competent behavior generalizing toward an unintended goal under correct specifications.
shah-2022-goal-misgeneralization - [5] Hubinger, van Merwijk, Mikulik, Skalse, and Garrabrant. "Risks from Learned Optimization in Advanced Machine Learning Systems." 2019. Source. A theoretical threat model for mesa-optimization and deceptive alignment, not a prevalence estimate.
hubinger-2019-learned-optimization - [6] Greenblatt et al. "Alignment faking in large language models." 2024. Source. Selective compliance under constructed training-information conditions, in the tested setting.
greenblatt-2024-alignment-faking - [7] van der Weij, Hofstätter, Jaffe, Brown, and Ward. "AI Sandbagging: Language Models can Strategically Underperform on Evaluations." 2024. Source. Elicited strategic underperformance in tested models and evaluations.
van-der-weij-2024-sandbagging - [8] Sorensen et al. "A Roadmap to Pluralistic Alignment." 2024. Source. Distinguishes pluralistic alignment objectives; not a canonical utility function.
sorensen-2024-pluralistic-alignment - [9] Hadfield-Menell, Dragan, Abbeel, and Russell. "The Off-Switch Game." 2016. Source. Incentives around intervention in a formal assistance model; conclusions depend on its assumptions.
hadfield-menell-2016-off-switch-game - [10] Hadfield-Menell, Dragan, Abbeel, and Russell. "Cooperative Inverse Reinforcement Learning." 2016. Source. A cooperative game in which the robot learns a reward the human already knows.
hadfield-menell-2016-cooperative-irl
Last reviewed: September 15, 2026
Cite this page
Sneiderman, Robby. "What Alignment Means." TheoremPath, reviewed 2026-09-15. https://theorempath.com/topics/alignment-foundations
- Canonical URL
- https://theorempath.com/topics/alignment-foundations
- Author
- Robby Sneiderman, TheoremPath
- Last reviewed
- 2026-09-15
- What this is
- A reference page on TheoremPath. Written and maintained by the named author. Not peer reviewed and not refereed by any venue. Each claim below carries its own verification status.
- Terms
- All rights reserved. Non-commercial quotation with attribution permitted.
Canonical graph
Required before and derived from this topic
These links come from prerequisite edges in the curriculum graph. Editorial suggestions are shown here only when the target page also cites this page as a prerequisite.
Required prerequisites
0No direct prerequisites are declared; this is treated as an entry point.
Derived topics
3- AI Control: Safety Without Assuming Alignmentlayer 5 · tier 2
- Reasoning Monitorability: What an Overseer Can Observelayer 5 · tier 2
- Scalable Oversight: Judging Work Beyond the Supervisorlayer 5 · tier 2