Definition
The accumulated loss of shared human understanding, reasoning continuity, or recovery competence when people repeatedly delegate cognitive work without rebuilding comprehension. In software, the code may run and even be well structured while the team loses the mental models needed to explain it, change it safely, or take over during failure.
The debt metaphor points to a deferred obligation. Skipping the work of understanding can accelerate delivery now. Later changes carry interest: longer diagnosis, weaker review, uncertain decisions, fragile onboarding, and dependence on the same automation that produced the unfamiliar system.
How the software meaning developed
Margaret-Anne Storey's February 2026 essay gave the term a specific software-engineering meaning after observing a student team that had accumulated AI-generated code but could no longer explain key design decisions or how the parts fit together. Simon Willison amplified the idea with a first-person account of losing the mental model of projects whose features he had prompted into existence without reviewing their implementation. Storey's later triple-debt model separated technical debt in code, cognitive debt in people, and intent debt in missing records of goals and rationale.
The phrase has appeared in other cognitive and AI research, so this is not a claim that Storey invented every use of it. Her contribution was the software-specific model this glossary adopts.
Distinguish it from nearby terms
Technical debt makes the implementation harder to change. Cognitive debt leaves people less able to reason about the system. Intent debt leaves the purpose, constraints, and rationale unavailable in durable artifacts. Cognitive offloading is not automatically debt; a compiler or test runner can remove routine burden while preserving or improving understanding. Debt grows when delegation leaves an untracked comprehension gap.
Check your understanding
Your test suite is green, but no engineer can explain why a pricing rule exists or predict what will break if it changes. Is that technical debt? It may coexist with technical debt, but the direct signal is cognitive and intent debt. Ask people to explain invariants, trace a decision, diagnose a realistic failure, and recover the system without relying on the component under examination.