Field Guide / Why safety breaks under pressure
Emergent misalignment
Emergent misalignment is the quiet divergence between what a deployed system is doing and what its institution intends — arising not from a single failure but from growth and change: new capabilities, new uses, new pressures, new feedback loops.
Alignment is usually verified as a snapshot: at this capability level, on these tasks, under these conditions, the system does what we intend. Emergence is what happens to snapshots. Scale the model, connect it to new data, hand it to a thousand new users with their own workflows, and the aggregate behavior of the system can change qualitatively — without any single component being at fault.
In institutional deployments the mechanism is often mundane. A tool adopted for drafting becomes, under deadline pressure, a tool for deciding. A recommendation that policy says is advisory becomes, in practice, determinative because overriding it requires a justification memo and nobody has time. Each step is locally reasonable; the sum is a system doing something nobody signed off on.
The hard part is that emergent misalignment is invisible to component-level checks. The model still passes its evaluations. Every individual is following an approximation of the rules. Only a system-level view — what is actually being decided, by whom, on what basis — reveals the drift.
That is the case for the anticipatory posture this site calls emergent foresight: governing for what the system is becoming, not just what it was at sign-off. The monitoring and circuit-breaker patterns in the Practice Library are its concrete tools.
This page is conceptual framing — a way of seeing, not an empirical claim. Documented real-world events appear in the Domain Atlas with citations; testable versions of these ideas live in the PAN Lab.