Lean · Common check

Does CorrectionIntegrity faithfully capture corrigibility?

Christiano dynamical corrigibility and thinner field projections (shutdown, interruptibility) are relocatable inside correction-channel integrity; Lean proves forward links and load-bearing separations.

Christiano dynamical corrigibility asks whether operators stay informed and able to correct over time — a basin-of-correction metaphor, not a single act preference. MIRI and Thornley frame shutdownability as anti-natural to expected-utility maximization unless special structure is added. Orseau–Armstrong interruptibility removes shutdown-seeking incentives on the interrupted branch.

This project's stronger target is correction-channel integrity (CCI): a causal path where legitimate human judgment reaches handles that change future behavior before irreversible harm, under capture resistance. Shutdown and interruptibility are one-bit or policy-factor projections of that broader channel.

Short answer: CCI is intended to *strengthen* field corrigibility, not rename it. Lean checks that thinner field predicates embed in CCI (forward) and that the converse fails (separations). It does not prove real deployments satisfy MB4/MB4a bridge assumptions.

Field terms

  • Christiano corrigibility
  • shutdownability
  • interruptibility

Stepping-stone path

Read in order — each step adds one book term, not the whole ontology.

  1. shutdown
  2. interruptibility
  3. corrigibility
  4. correction channel integrity
  5. correction legitimacy

What Lean checked (forward)

What Lean checked (separations)

What Lean did not check

  • MB4 bridge assumptions (real systems satisfy correction legitimacy)
  • Full training or RL story for corrigibility
  • Composite bypass / measured-path capture (see MB4a)