---
title: "How It Breaks — Context Infrastructure"
description: "Most failures are slow, not sudden."
canonical: "https://press.getalchemystai.com/books/context-infrastructure-build-ai-that-understands-your-business/how-it-breaks"
last_updated: "2018-10-20"
book: "Context Infrastructure"
label: "Chapter 28"
---

# How It Breaks

Most failures are slow, not sudden. Each has an early warning a team lead can watch for.

| Failure | Early warning | Fix |
| --- | --- | --- |
| **Over-segmentation** | Searches return dozens of tiny fragments | Merge into 500 to 2,000-word documents |
| **Metadata bloat** | Slower queries; fields out of sync | Keep five fields or fewer; move descriptions into content |
| **Taxonomy sprawl** | Arrays of seven or more tags; near-duplicate tag names | Steward approval for new tags; quarterly clean-up |
| **Stale sources** | Correct-looking answers that cite last year's policy | Review dates in metadata; owner per source |
| **Semantic drift** | Teams disagree with the agent's definition of a term | Scoped definitions with owners and versions |
| **Over-trusting grounding** | High-impact answers acted on without review | AI-assist mode for clinical, financial and contractual steps |
| **Write-back left off** | Retries perform no better than first attempts | Turn on write-back; check the next call's trace for the last outcome |
| **Pilot scope creep** | Every week brings one more custom request | Fixed scope parameters; changes go through the plan |

---

- Previous: [Chapter 27: Scorecard](https://press.getalchemystai.com/books/context-infrastructure-build-ai-that-understands-your-business/scorecard.md)
- Contents: [Context Infrastructure](https://press.getalchemystai.com/books/context-infrastructure-build-ai-that-understands-your-business.md)
- Next: [Chapter 29: Grow the Team](https://press.getalchemystai.com/books/context-infrastructure-build-ai-that-understands-your-business/grow-the-team.md)
