Reference document

The Atruvo
Platform Failure Modes Index.

30 named ways platform investments fail before AI rolls out. Built from 12 platform engagements. Each mode is documented, severity-scored, and tied to a published field note or a remediation pattern. Updated quarterly.

30

Failure modes

6

Categories

12

Engagements analysed

6

Catastrophic-tier

Methodology

12 anonymised platform engagements from 2022 to 2026. Each review documented failure modes by symptom, blast radius, and business impact. Modes appearing in multiple engagements were named and codified.

Severity scale

High
Critical
Catastrophic

How to use this

Scan the index for symptoms you recognise. Each mode links to the field note that explains it. To diagnose your own platform against the index, book a Platform Failure Map.

Visibility failures

The dashboards are green, but the system is degrading. Failure modes where the observability stack is structurally unable to see what is actually breaking.

Dashboards measure activity, not outcomes

Critical

Uptime, latency, and error rate look healthy. Nobody is measuring whether the system is producing the correct result.

Seen in 11 of 12 engagementsRead the field note

Silent drift below alert thresholds

High

P99 latency or accuracy slowly drifts over weeks. No threshold trips. SLO budget consumed before anyone notices.

Seen in 9 of 12Read the field note

Blast radius unmapped

Critical

Nobody can answer 'what else fails if this fails?' until the incident is already in progress.

Seen in 12 of 12

SLOs gamed against customer ground truth

Critical

Dashboard reports 99.95% attainment. Customers file tickets. Definition creep, aggregation, and synthetic monitoring hide the truth.

Seen in 10 of 12Read the field note

Verification debt cascade (DORA blind spot)

Critical

AI-authored code makes deployment frequency and lead time look favourable on the dashboard. The bottleneck moves to verification capacity, review queue depth by seniority, and rollback rate — places DORA does not measure.

Emerging — H2 2026 board reviews

AI monitoring is just uptime monitoring

Critical

The infra layer is monitored. Output quality and drift are not. AI degradation is invisible until customers report it.

Seen in 8 of 12Read the field note

Ownership failures

Every team thinks their part works. The failure lives in the seams between teams. Organisational failure modes that no amount of tooling can solve.

AI pipeline has no owner

Catastrophic

Data, ML, and Platform teams each confirm their part is green. The pipeline between them is broken and unowned.

Seen in 7 of 12Read the field note

AI strategy without operations plan

Catastrophic

Board approved roadmap, vendor selection, and budget. No on-call, no rollback plan, no cost controls, no fallback.

Seen in 14 of 14 strategy reviewsRead the field note

Wrong job description attracting wrong hires

High

Team is staffed with researchers who cannot ship to production, or platform engineers without AI context.

Seen in 6 of 12Read the field note

AI governance unowned by platform

Critical

Compliance, audit trail, and rollback are treated as policy documents, not platform features. Nobody operationally owns them.

Seen in 10 of 12Read the field note

Brittle services hidden from architecture diagrams

High

Architecture diagrams show critical services. On-call data shows different services pay the reliability cost. Engineering time is invested against the wrong systems.

Seen in 9 of 12Read the field note

Truck factor of one on the deployment pipeline

Critical

Only one engineer can deploy to a given environment. Tribal Ansible, undocumented credentials, named-person approval gates. Deployments wait when that person is on leave.

Seen in 7 of 12Read the field note

Cost failures

AI costs are being measured wrong. The visible costs are the smaller half. The real cost lives in the shared infrastructure that existed before the AI project started.

Data pipeline is the real AI cost

High

Business case focused on model and GPU costs. The data pipeline is 60-70% of total spend and nobody budgeted for it.

Seen in 12 of 12Read the field note

AI workloads hidden in shared compute

High

GPU, LLM API calls, and embedding jobs buried in 'general compute' line items. Nobody can attribute cost to a specific AI feature.

Seen in 11 of 12Read the field note

Capacity ceiling unknown until breached

Critical

Platform is running at 80% of an unknown ceiling. Adding AI workload pushes it over. Discovery happens during incident.

Seen in 9 of 12

No agent budget boundary

Critical

Token consumption controlled per request, not per agent run. One stuck tool call burns a month of FinOps headroom in an hour. No max-iterations circuit breaker.

Trending in 2026 agent deployments

Architecture failures

The substrate underneath the AI was not measured before deployment. Cache layers, queues, retries, and scheduling assumptions that AI workloads break.

Platform substrate never measured

Catastrophic

AI bolted onto a platform with unknown cache layers, undocumented queues, and engineers on leave. Hidden failure modes detonate at week 8.

Seen in 8 of 12Read the field note

Kubernetes scheduling for GPU workloads

High

Cluster designed for CPU autoscaling cannot serve GPU AI workloads. Scaling takes 5 minutes. Cold start kills inference SLOs.

Seen in 5 of 12Read the field note

RAG infrastructure not scaled for production

High

Vector DB latency, stale embeddings, and retrieval drift all break differently from dev to prod. Each one looks like a model problem.

Seen in 7 of 12Read the field note

Stalled migration debt

Critical

Migration stalled at 60% for 18 months to 4 years. The last 40% is a different project than the first 60%. Reporting tracks against a plan that no longer reflects reality.

Seen in 4 of 4 stalled migrationsRead the field note

Multi-cloud without commercial justification

High

Multi-cloud strategy doubles platform cost without delivering the promised resilience. Adopted as a hedge against indecision, not a real risk.

Seen in 4 of 12Read the field note

Agent runtime without a production contract

Catastrophic

Platform built for stateless HTTP cannot host non-deterministic, long-lived, tool-invoking agent workloads. No token budget per run, no eval floor, no gateway SLO. Agents stall before reaching production.

Cited cause behind 88% of stalled enterprise agentsRead the field note

Portal without a paved road

High

IDP measures catalog coverage rather than developer outcomes. Adoption sits at 10% because developers correctly route around it. AI agents route around it too because it was built for humans clicking a UI, not machines invoking structured tools.

Building — 2023-2024 IDP cohort first ROI review

Resilience failures

Failure modes where the system is unable to degrade gracefully. Where rollbacks corrupt state. Where fallbacks are worse than failures.

Silent AI fallback is worse than hard failure

Catastrophic

When the model fails, the system silently returns cached or default results. Errors are hidden for weeks before customers notice.

Seen in 9 of 12Read the field note

Model rollback creates state inconsistency

Critical

Rolling back a model leaves embeddings, stored decisions, and downstream state from the new model in place. System breaks differently.

Seen in 6 of 12Read the field note

AI guardrails only check format, not facts

Critical

Guardrails pass 100% in dev. In production they let through 28% of wrong-but-well-formed answers because they never checked correctness.

Seen in 10 of 12Read the field note

Security and compliance failures

AI-specific security and compliance failure modes where the defence is in the wrong place, or the audit evidence does not exist.

Prompt injection defended at application layer

Critical

Each application implements its own regex filter. One gap exposes the entire org. The defence belongs at the platform gateway.

Seen in 11 of 12Read the field note

AI audit trail missing or incomplete

Critical

Inputs, outputs, model version, and confidence scores not stored. Compliance audit cannot prove what the model saw or returned.

Seen in 8 of 12

AI compliance audit will fail

Catastrophic

Strategy, governance, and policy all exist on paper. The platform cannot produce the evidence the audit will demand.

Trending in 2026 audits

AI security as policy, not platform

Critical

CISO writes correct policy. Platform has no AI gateway to enforce it. Each team implements badly. CISO blocks rollouts because policy is unenforceable.

Seen in 6 of 12Read the field note

How many of these are in your platform?

Find out in a Platform Failure Map.

One to two weeks. Risk-ranked findings against the 30-mode index. A prioritised remediation roadmap. No engagement required to start.

Bring your architecture diagram, cloud bill, or last incident summary.

I will tell you what is actually breaking.

30 minutes. No pitch. Ranked risks and a clear next step.