Entanglements
Three safety layers that each miss 10% of harmful actions look like 99.9% protection if their failures are independent. They rarely are. Checks built on similar models share blind spots. A verifier that reads the agent’s summary inherits its framing. An instruction injected into a document reaches every component that reads it. Components that work together long enough adapt to each other. Entanglement covers all of these: any dependence between components that the independence arithmetic ignores.
The canonical example
Section titled “The canonical example”Take three layers that each miss 10% of harmful actions, and common-cause correlation ρ on the phi scale. The beta-factor mixture from nuclear reliability engineering (derivation) gives
- Independent (ρ = 0): 0.1³ = 0.1%, or 99.9% protection.
- ρ = 0.5: 0.5 × 0.001 + 0.5 × 0.1 ≈ 5%, or about 95% protection.
- The entanglement tax, actual over assumed residual risk, is 1 + 99ρ: about 11×, 21× and 50× at ρ = 0.1, 0.2 and 0.5.
Three caveats travel with these numbers:
- ρ = 0.5 is a benchmark-based prior, not a measurement of any monitor stack. On MMLU misses, strong LLMs from different providers give ρ of about 0.3–0.6 and models from one provider about 0.5–0.7, depending on how much label noise is allowed for (Measuring Entanglement). No study reports ρ for harm detection. Show the range, not one row.
- This is benign-failure math. Against an adaptive adversary, such as a scheming component or a prompt-injection author, inputs are chosen to beat every layer at once. Count the stack as its best single layer unless a control evaluation shows otherwise (Risk Propagation).
- Correlation does not change expected losses, which add. It matters for defenses where every layer must miss, and for the tails of total loss.
Start here
Section titled “Start here”- Types of Entanglement: passive, active and adversarial, with where each comes from in agent stacks.
- Formal Definitions: the tax, effective redundancy, and the limits of AI checking AI.
- Measuring Entanglement: estimating ρ, the lookup tables, the correlation budget, and priors for when you cannot measure.
- Solutions & Mitigations: what lowers ρ or bounds the damage, and when it is worth paying for.
Then, by need:
- Running an assessment: Detecting Influence for the methods, the Audit Guide for the protocol, and Worked Examples for four analyses end to end.
- Background and evidence: Research Connections covers common-cause failure analysis, correlated LLM errors and AI debate. Foundation-Model Monoculture covers provider concentration. Historical Cases covers human institutions that failed this way, Psychology of Oversight covers human reviewers as a correlated layer, and Regulatory Approaches covers policy.
The design-pattern view of the same problem is Channel Integrity, and the canonical propagation rule is Risk Propagation. The sibling Reasoning Processes notes treat decorrelation as a hardening technique for any reasoning process, human or model (Independence & Decorrelation).