---
type: "synthesis"
spans: ["s24", "s25", "s28"]
tags: ["arc", "failure-modes", "debt"]
id: "arc-debt-and-decay-patterns"
sources: ["cross-day"]
---
# Debt and Decay Patterns Across the Series

The series catalogs a remarkably consistent family of *debt-and-decay* failure modes — what happens when you take AI-driven shortcuts at the *wrong* layer. Each video names a specific debt; together they form a typology.

## The debt typology

| Debt name | Where it accrues | Day | Mechanism |
|---|---|---|---|
| [[concept-shadow-agents|Shadow agent debt]] | Org infrastructure | S24 | Each team builds its own RAG/MCP/integration; no governance; brittle, unverifiable, expensive to consolidate. |
| [[concept-vibe-coding|Vibe coding debt]] | Codebase | S25 | Code shipped without understanding; future maintainers can't reason about it. |
| [[concept-archaeological-programming|Archaeological programming]] | Codebase + cognition | S25 | Future devs have to *excavate* opaque AI code. [[entity-addy-osmani]]'s term. |
| [[concept-experiential-debt|Experiential debt]] | Builder's mental model | S25 | The creator no longer understands their own product. Most insidious — invisible until break. |
| [[concept-thin-wrappers|Thin wrapper decay]] | Business | S28 | UI moat replicable in a week with [[entity-replit|Replit]]/Cursor/Claude Code; structural decay. |

## The shared mechanism

In every case, the same three-step pattern produces decay:

1. **AI accelerates a layer of work** (integration, coding, building) so dramatically that the natural friction that once forced understanding disappears.
2. **A debt accumulates silently** in the layer above (governance, architecture, mental model, moat).
3. **The debt becomes visible only at scale or under stress** — when the org needs unified governance, when the codebase needs to be modified, when the wrapper needs to defend against a competitor.

## The shared antidote: deliberate friction

Across the series the antidote is identical in shape: **deliberately reintroduce the friction that AI removed**, but at a *higher leverage layer*.

- S24: [[action-build-mcp-infrastructure]] + [[action-translate-okrs]] reintroduce *intentional* infrastructure friction.
- S25: [[action-shift-altitude]] (drop into the weeds when needed) + [[action-reflect-mode]] (build/reflect separation) reintroduce *cognitive* friction.
- S28: [[framework-strategic-litmus-test]] + [[action-apply-litmus-test]] reintroduce *strategic* friction — refuse to ship until you've identified what survives 10× AI.

## The lesson

This arc is the negative-space companion to [[arc-incompressible-human-residuals]]. The residuals describe what humans *must keep doing*; the debts describe what happens when humans *let AI do it instead*. They are two views of the same boundary.

See also [[arc-success-at-wrong-metric-generalized]] (these debts often hide behind successful proxy metrics), [[arc-managing-not-doing]] (the new manager identity exists to prevent these debts).