XIV · Anti-PatternsAnti-pattern✕

Agentic Debt

also known as Agentisk Skuld, AI Maturity Debt, Foundational AI Debt

Anti-pattern: deploy agents on top of an unconsolidated data foundation, weak governance, or missing MLOps infrastructure, so every subsequent capability — observability, retraining, compliance retrofit — pays compounding interest on the skipped foundational work.

Context

An organisation under competitive pressure decides to skip directly to agentic systems before completing the prior maturity stages (data consolidation, automation, classical the model, MLOps). The pilot demonstrates value, the executive sponsor is satisfied, and the agent ships. The data, governance, and observability infrastructure that would normally have been built in the earlier stages is now missing under a live agent.

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).

Forces

  • Competitive FOMO ('rädsla att missa något') pushes organisations to skip stages.
  • Pilot success is celebrated before the foundational debt comes due.
  • Each subsequent agent deployment re-pays the same foundational cost in a different shape, so the total bill is invisible from any single project's budget.

Example

A retail group ships an agentic customer-service product to keep pace with a competitor. The pilot works and rolls out. Six months later, the data team builds a customer-event pipeline retroactively to give the agent the order history it needs. Three months after that, a second agent for logistics needs a similar but differently-shaped pipeline, and the team builds it again. A third agent for finance needs MLOps for model rollback, also built from scratch. The CTO audits and finds the organisation has paid three foundational bills instead of one — that gap is the agentic debt. The fix is a foundation-first programme: consolidate data, build shared MLOps, freeze further agent rollouts until the foundation is in place.

Diagram

Solution

Therefore:

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.

What this pattern forbids. No useful constraint; the missing constraint is a mandatory maturity-stage gate before agent deployment.

And the patterns that stand alongside it, or against it —

  • complementsDemo-to-Production Cliff✕— Anti-pattern: ship a demo-validated agent straight into production without a frozen eval, cost ceiling, loop-detector, or named oncall, then act surprised when accuracy drops and cost runs away.
  • complementsAutomating a Broken Process✕— Anti-pattern: deploy agents on top of a workflow that is already dysfunctional, so the dysfunction is amplified at machine speed instead of resolved.
  • complementsPerma-Beta✕— Anti-pattern: ship the agent in 'beta' indefinitely so that quality regressions are someone else's problem.
  • alternative-toEval as Contract★★— Treat the eval suite as the contract the agent must satisfy; releases ship only if evals pass.
  • alternative-toDecision Log★★— Persist the agent's reasoning trace alongside its actions so post-hoc review can explain why.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance