You've probably had this experience: you ask Claude to write a feature, it produces something that looks completely reasonable, you paste it in, tests pass — and then three weeks later you're staring at that code trying to remember why it works that way. Not because the code is wrong. Because you don't own it. That's the quiet problem with a lot of AI-assisted development right now. The velocity is real. The debt is real too — it just doesn't show up for a while. What AI debt actually looks like Traditional technical debt is usually about shortcuts: skipped tests, tight coupling, a quick fix that became permanent. You know it's there because you made the tradeoff consciously. AI debt is sneakier. The code looks clean. It often passes review. But no one on the team — including the person who "wrote" it — can walk through it confidently. When something breaks at 2am, the fastest path to a fix is asking Claude to debug code that Claude wrote, which Claude no longer has context for.…