Skip to content

Hardening: Overview

The opening of Part III: given the Core Model’s quantities, how do you engineer good values of them? One objective — eliminate confident error — and six families of mechanism that achieve it, each developed on its own page. This overview states the objective, maps the families onto the two axes, gives the threat-coverage picture and the composition algebra that span families, and notes the machine affordances that let every mechanism run at superhuman intensity.

The only epistemic state that can hurt a judge without bound is being confidently wrong. A calibrated process turns that open-ended tail risk into a bounded one the judge can price, so the safety-relevant target is tail calibration, P(false∣asserts≥c)P(\text{false}\mid \text{asserts} \ge c) for cc near 1, rather than accuracy. A process can always hedge or abstain, so “never confidently wrong” is achievable where “accurate” often is not [heuristic]. Calibration develops this, including its limit: a deceiver that lies rarely, on the decision that matters, can stay calibrated everywhere else. Every family below is a way to make confident error rare or expensive.

A hardening mechanism moves a process on one of the two axes — it makes validated information cheaper, or it makes the output costlier to corrupt. The six families sort onto those axes, and the sort explains the Catalogue’s empty quadrant:

FamilyWhat it doesPrimarily buys
Calibrationmake stated confidence match realitycheaper trustworthy bits (the output self-rates)
Verifiability asymmetrymake checking cheaper than producingcheaper validated bits
Independence / decorrelationmanufacture genuinely independent signalscheaper validated bits + higher corruption cost
Invariance / low sensitivityoutput insensitive to controllable inputshigher corruption cost
Incentive-compatibilitymake honesty the best strategyhigher corruption cost
Deterrenceoff-equilibrium penaltieshigher corruption cost at low information cost

The non-obvious structural point: most corruption-resistance is bought with verification, which costs real information-extraction work every time the process runs — so it raises both axes together and never reaches the cheap-and-incorruptible corner. Deterrence is the partial exception: bonds, clawbacks, and tamper-evidence cost little on the honest path beyond the audits that detect cheating, which makes it the most promising route into the empty quadrant, and makes identity/track-record infrastructure (which sets the maximum enforceable penalty) unusually leveraged. Each family is developed on its own page, with its mechanism, its limit, its constructions, and worked bounds.

Sorting the families by the threats they close shows both the coverage and, more usefully, where there is none. (Primary defenders listed; many threats are addressed weakly by several families.)

ThreatPrimary defending familiesWhere coverage is thin
Sybil / identity forgeryDeterrence, Invarianceneeds identity infrastructure to bind bonds
Prompt-injection / framingInvariance, Calibration—
Persuasion / sycophancyIncentive-compatibility, Verifiability, Calibrationclaims that never resolve
CollusionIndependence, Incentive-compatibilityshared-training correlation
Sandbagging / capability-hidingIndependence, affordances (read-state)interpretability is unreliable
Resolution-criteria gamingDeterrence, Incentive-compatibilitywho defines the criteria
Selection / optional-stoppingVerifiability, Deterrence—
Correlated errorIndependence (weakly)no clean AI-specific defense yet
Goodhart-after-publicationDeterrence, externally-grounded familiesstyle-mimicry of high-tier forms
CalibrationVerifiabilityIndependenceInvarianceIncentivesDeterrenceThreatWhere coverage is thinSybil / identity forgeryneeds identityinfrastructure to bindbondsPrompt-injection / framing—Persuasion / sycophancyclaims that neverresolveCollusionshared-trainingcorrelationSandbagging /capability-hiding+ read-state affordanceinterpretability isunreliableResolution-criteria gamingwho defines the criteriaSelection /optional-stopping—Correlated errorno clean AI-specificdefense yetGoodhart-after-publication+ externally-grounded familiesstyle-mimicry ofhigh-tier formsPrimary marks222+1 weak234cheaper validated bits4 of 15both2 of 15higher corruption cost9 of 15Axis it mainly buysprimary defendernamed as weak onlyblank: not primary CalibrationVerifiabilityIndependenceInvarianceIncentivesDeterrenceThreatSybil / identityforgerythin: needs identityinfrastructure to bindbondsPrompt-injection /framingPersuasion /sycophancythin: claims thatnever resolveCollusionthin: shared-trainingcorrelationSandbagging /capability-hiding+ read-stateaffordancethin: interpretabilityis unreliableResolution-criteriagamingthin: who defines thecriteriaSelection /optional-stoppingCorrelated errorthin: no cleanAI-specific defenseyetGoodhart-after-publication+ externally-groundedfamiliesthin: style-mimicry ofhigh-tier formsPrimary marks222+234cheaper validated bits: 4 of 15both: 2 of 15higher corruption cost: 9 of 15primaryweak only (+ in totals)
Coverage leans on the corruption-cost axis: 9 of the 15 primary marks belong to Invariance, Incentives and Deterrence, 4 to Deterrence alone. Correlated error is the one threat with no primary defender; Independence, the family meant to supply decorrelation, is named only weakly. Blank cells mean “not a primary defender”, not “no effect”: the page notes that many threats are addressed weakly by several families.

The standout is correlated error. Every aggregation, ensemble and panel defense assumes independence, and shared training pipelines erode it. Engineering has met this before, in N-version programming (Knight & Leveson 1986), and prices it with common-cause models such as the beta factor (Independence has the details). Those models measure correlation; they do not remove it. No family here removes it for AI reasoners, which makes this row a research priority.

The family pages treat constructions as atoms, but real systems are stacks. Model a hardened stack as an AND/OR attack tree (Mauw & Oostdijk 2005): an attacker needs one successful path, so the stack’s corruption cost is the cheapest path, with costs summed over AND nodes and minimized over OR nodes. A pipeline in which corrupting any one stage corrupts the output is an OR node, so without randomization it inherits the cheapest stage; checks that must all be defeated form an AND node, and their costs add. Randomized escalation with probability pp to an expensive stage adds roughly p⋅Cexpensivep\cdot C_{\text{expensive}} to every path that must survive escalation; this is the inspection-game frontier made compositional, and the same mechanism the Process Catalogue bets on for the empty quadrant. Whether real stacks behave this way is unmeasured.

The cross-cutting multiplier: machine-oversight affordances

Section titled “The cross-cutting multiplier: machine-oversight affordances”

The Process Catalogue lists processes evolved for humans — who have rights, privacy, fatigue, and exist as single un-forkable instances. None bind for an AI reasoner, and the slack may be the largest untapped resource here. The affordances are not a seventh family; each lets you turn one of the six cranks harder than any human process allows:

AffordanceTurns up which familyExample construction
Reset / re-runIndependencemind-wiped re-derivation
Fork mid-reasoningIndependencecheckpoint-fork cross-examination
Decorrelated resamplingIndependenceconfession-as-invariant interrogation
Sandboxed information dietInvariancereject conclusions resting on un-logged retrievals
Narrow, fixed action spaceInvariancelower the Lipschitz constant by removing levers
Full logging / no privacyDeterrencetamper-evident reasoning trace, free
Forced bets / bondsDeterrence + Incentivesset the enforceable penalty BB
Read internal state(all, weakly)activation-honesty cross-check — [speculative]

The “read their minds” affordance is the highest-leverage and the least reliable: truth appears linearly represented in activations (Marks & Tegmark 2024; Goldowsky-Dill et al. 2025), but chain-of-thought is often unfaithful (Chen et al. 2025), deception survives safety training (Hubinger et al. 2024), and training against an honesty probe can induce evasion (Cundy et al. 2025). Use it as corroboration, never as the load-bearing check.

A capstone — one fully-worked hardened stack on a real task — is planned but not written; Chapter 18, Certification and Gyms, is where its measurements would live.

  • Are six families the right cut, or do calibration and verifiability collapse into one (both make the output self-checkable), and does independence belong under invariance?
  • Which families compose multiplicatively and which merely add the weakest link?
  • Is there a single inequality the whole Part is special cases of — corruption cost as a function of sensitivity, enforceable penalty, and effective independence?
  • What closes the correlated-error row, the one threat with no clean defender?