Technical debt

The accumulated cost of structural and code quality decisions that prioritized short-term convenience over long-term maintainability. Structural technical debt in a robotics codebase specifically refers to wrong package boundaries, undeclared coupling, duplicated logic, and naming inconsistencies that slow down every future development activity. Like financial debt, it accrues interest: a small debt at month one is a large debt at month twelve.

The accumulated cost, usually paid in slower future engineering work, of choosing a faster, less complete solution now over a more thorough one, with the implicit or explicit intention of improving it later. A concept popularized by Ward Cunningham in the early 1990s, and the direct conceptual source for process debt in this topic.

The accumulated cost of past shortcuts (integration, data, infrastructure, and process debt). For AI it is prioritized by impact on AI rather than general IT health, then contained, repaid incrementally, modernized opportunistically, or strategically replaced.

The future cost incurred by choosing the fast, expedient option now rather than the right one; coined by Ward Cunningham in 1992, where the "interest" is the compounding extra effort every later change requires.

the accumulated cost, in money, time, and risk, of systems built or maintained in ways that make future change harder. Like financial debt, it charges interest: every AI initiative pays it until you address the principal.