[d0liver]

A lot of your framing has to do with what's expected of the system. Like, scaling from 100 users to 100M is an expectation not a property of the software. Making that library _more_ secure is also an expectation. Expectation becomes debt when your current expectation exceeds the limits of the system. When that happens it's largely because someone, often not a developer, changed the expectations. When that happens the difference between the expectations and actual system has to reconcile somehow and that's usually via some "shortcut" and there's some associated cost.

So, within your framing, the point is just that when things change (due to no fault of your own) the whole organization has to adjust expectations or you have an organizational issue.