---
title: "The Anatomy of Corruption and Corrigibility"
url: "https://toddpaulbrownjr.com/corrigibility/"
author: "Todd Paul Brown Jr."
description: "A field guide to diagnosing corruption and failure modes in information systems: what a system is really optimizing, and whether it can still be corrected."
kind: "guide-index"
updated: "2026-09-26T02:50:11+00:00"
---

# The Anatomy of Corruption and Corrigibility

Every system says what it's for. Its dynamics say something else. This is a guide to reading the gap between the two, and to telling a system that has drifted but can still be corrected from one that has quietly disabled its own correction.

It applies the same questions to software, AI models, companies, public institutions and the people inside them, because the failures rhyme. A metric that replaces the thing it measured. Growth that stops answering to what it feeds on. Correction machinery that has been captured and now reports that everything is fine. A critique that can't reach the one system that most needs it.

## What it is, and what it isn't

It's a diagnostic instrument: a vocabulary for failure shapes, operational tests for each one, and an audit you can run on an organization you care about. It's good at recognizing shapes and weak at predicting specific sequences, and it says so. The final chapter lays out its own limits, including the uncomfortable one: the book is subject to its own concepts.

It isn't a moral verdict on anyone. You won't find "evil" or "wrong" here. The words are "misaligned", "self-undermining", "consuming what it depends on". The stakes carry the weight, and you supply the ought.

## How to read it

Part I sets the stance. Part II names four pathologies. Part III turns them into instruments you can use. Part IV applies them to AI systems, public institutions, workplaces and, last, to you. If you only read one chapter, read [Sucralosis](/corrigibility/sucralosis/). If you want the tools, go to [Markers and Tests](/corrigibility/markers-and-tests/). If you build AI systems, start with [AI Systems](/corrigibility/ai-systems/).

The coined terms are defined in the [glossary](/corrigibility/glossary/), and what changed between drafts is in the [changelog](/corrigibility/changelog/). How the book got written, by debugging a philosophy the way you'd debug code, is [its own story](/corrigibility/how-this-was-written/).

This is a working draft, published on purpose. When a claim changes, the changelog says so.