## Core Insight Cognitive Debt is a distinct category from technical debt. Technical debt is about code quality — messy implementations, missing tests, tight coupling. Cognitive debt is about understanding — humans losing comprehension of what a program is supposed to do, even when the code itself is clean. In AI-assisted development, this gap widens rapidly: agents can produce code faster than humans can build and maintain mental models of system behavior. The code exists and may even be well-structured, but no human "has the plot" of what it does or why. ## Cross-Domain Applications - **Software Architecture**: Cognitive debt compounds with decision density. Even well-factored AI-generated code increases the state space that humans must reason about. The carrying cost is not in maintaining the code but in maintaining understanding of the code. - **Knowledge Management**: Parallels the problem of accumulating highlights and notes without synthesizing them — the information exists but understanding does not. A vault full of unprocessed captures creates cognitive debt in knowledge work. - **Organizational Management**: As organizations adopt AI tooling, the cognitive debt risk shifts from individual developers to entire teams — institutional knowledge becomes fragmented when AI handles implementation details that previously served as learning pathways. ## Trust Erosion as Compounding Carrying Cost Simon Willison adds a critical downstream dimension: cognitive debt doesn't just create an understanding gap — it erodes **trust** in the work and degrades **future decision quality**. Each decision built on code you can't fully trust compounds the uncertainty. This makes cognitive debt a *compounding* carrying cost, not a static one — the cost grows with every subsequent decision made on an untrustworthy foundation. ## Sources - [[3 Archives/Readwise/Documents/A wonderful description of Cognitive Debt -|A wonderful description of Cognitive Debt]] by Matt Pocock (2026-02-16) - [[Short musings on cognitive debt - I'm seeing this in...]] by Simon Willison (2026-02-15) ## Related Concepts - [[Decision Density as Scaling Constraint]] - [[WIP Decay Rate Framework]] - [[The Maintenance Blind Spot]] - [[Scale as Architectural Coherence]] ## Latent Connections - [[Cognitive Offloading Risk]] — Complementary: offloading creates the cognitive debt; this note describes the downstream trust and decision quality erosion (discovered Mar 19 2026)