technical debt · upkeep
Ask PrometheusWork that was not done when it could have been, which narrows the range within which a system can persist without breaking.
Technical debt (noun) means: Work that was not done when it could have been, which narrows the range within which a system can persist without breaking. It emerges from maintenance, window, neglect, drift: The phrase reports that a system is drifting toward a wall because maintenance was skipped, not because parts broke — the model assumes the system is stable, but the range has silently narrowed. In the EmergenceLexicon it sits at computed level 16, chaining down to the four foundations (space, time, energy, pattern).
ordinarily means: Shortcuts taken in software that cause problems later.
Examples
- In 2019, Capital One’s cloud misconfiguration—unfixed for months—led to a breach exposing 100 million records. computing
- The 2010 Deepwater Horizon rig explosion followed years of deferred safety upgrades to save $2.7 million per well. engineering
- By 2007, Detroit’s water system had 60,000 unmaintained service lines, doubling lead levels in homes. institutions
Emergence
- The debt is not in the code — it is in the difference between what the system can tolerate and what it is asked to do.
Chain to foundations
full chain as text (259 steps)
- technical debtL16
- maintenanceL14
- windowL7
- neglectL15
- driftL11
- boundaryL2
Neighborhood
Concepts that depend on this one above; what it is built from below.