Graphite pencil illustration of the Stagnant Miasma, a creeping fog settling over a codebase

The Stagnant Miasma doesn't attack. It settles. A faint, comforting haze that smells like familiarity — the patterns you already know, the tools you've already mastered. It whispers that what worked last time will work this time. AI tools reinforce those existing patterns, and the team's confidence in the old way grows while new ideas feel riskier.

Symptom
The architecture hasn't changed in three years and nobody's asked whether it should. The AI generates code that matches existing patterns 100% of the time. 'We've always done it this way' is the strongest argument in the room.
Why it matters
The Miasma is stagnation dressed as stability. AI models are backward-looking by nature — trained on historical data, reflecting past conventions. When a team uses AI exclusively to replicate what they've already done, the model validates their approach, confidence increases, and innovation slows. Then it stops.
What the chapter gives you
How to audit your context files for restrictive instructions, the team rituals that ventilate the fog, and why asking the AI to critique your architecture is different from asking it to extend it.

From Volume 1 of The AI Developer's Field Guide

Read the full chapter in The AI Developer's Field Guide.

Recognize this one in your codebase?

The book has the full chapter, the symptoms, and the interventions.