Agentic Debt

Problem

Every later capability the agent needs — production monitoring, retraining when the model drifts, compliance audit trails, cross-team observability — costs multiples of what it would have cost to build the foundation first. The Swedish HiQ coinage 'agentisk skuld' names this as a distinct failure shape: not the demo-to-production cliff (a one-time deployment failure) but a recurring interest payment on every agent deployment afterwards. The team builds the missing data pipeline retroactively for agent #1, again for agent #2 with different requirements, and again for agent #3, paying the same foundational work three times in less-coherent forms. Industry reporting independently corroborates this as 'the model sprawl' (OutSystems: 94% of organisations cite sprawl as increasing technical debt) and 'hidden technical debt of agentic engineering' (The New Stack).

Solution

Don't skip foundational stages under FOMO. Run the maturity-stage assessment first: data lineage and quality, automation infrastructure, classical-ML observability and retraining pipelines, MLOps for deployment and rollback. Only then deploy agents. If the organisation has already taken on agentic debt, name it, quantify it, and stage repayment: build the missing foundation as an explicit programme before launching additional agents. Use eval-as-contract, decision-log, and cost-observability as the minimum survival kit. Distinguish from demo-to-production-cliff: the cliff is a one-time deployment failure on a single agent; agentic debt is the compounding cost paid on every subsequent agent deployment.

When to use

• Never. Cite when an organisation proposes agent deployment without completing prior maturity stages.
• Demand a maturity-stage assessment (data, automation, classical model, MLOps) before sign-off.
• If debt has already accrued, name it, quantify it, and stage repayment before the next agent.