The rust is the protection

Cor-Ten steel, the material holding up half the bridges in this part of the country, was engineered to rust on purpose. The oxide layer that forms on its surface isn't decay. It's armor: a patina that seals the steel underneath, cuts maintenance to nearly nothing, and gets better-looking with weather. The rust is the protection. Untreated rust is the problem.

That distinction is the entire reason this practice exists, and the reason it's named after Cleveland instead of something with "synergy" in it.

The systems that run mid-market businesses (the ERP from 2009, the order-entry app nobody dares touch, the scheduler that only Dave understands) are weathering steel. They've carried load for fifteen years. They are not failures with deferred cleanup; they're successes with deferred maintenance. And right now, every one of them is about to have enormous heat applied to it, because AI is arriving whether the foundation is ready or not.

Heat forges strong material and warps weak material. The research is unambiguous about which way it goes for software: AI pointed at disciplined systems compounds them, and AI pointed at tribal knowledge and untested code ships defects faster than teams can catch them. The tools don't decide the outcome. The substrate does.

So the work is the unglamorous kind: treating the steel. Documenting what's tribal, testing what's hoped-for, cutting clean seams where there were only screens. Done right, a system's age stops being corrosion and starts being protection: twenty years of encoded business rules, finally in a form that machines can be trusted to operate.

That's what Shop Notes will be about: field reports from inside the machines everyone else abandons. We like it in there.