How Confident Should You Be? covered calibration - how much to trust outputs when the system is nominally healthy. This post covers recovery design: when outputs are wrong, how quickly does your organization notice, route the pain to the right owner, and convert the incident into learning that changes the system? Without that loop, "organizational memory" is just storage.
The Other Dimension introduced the four readiness components - ownership clarity, failure-mode awareness, confidence calibration, and recovery design. The Invisible Line focused on ownership. This post builds the first of the three that remained: failure-mode awareness - not as a testing checkbox, but as an organizational habit.
Rethinking Assumptions argued that our dev tools were built for a world where humans were the scarce resource - tickets, PRs, and linear workflows made sense when changes were expensive. This post breaks a parallel assumption: that capability in AI-assisted software work is the same thing as readiness to operate safely at that level. It is not. You need a second dimension.