Context Anchoring
Practice of externalizing decision context into persistent, version-controlled documents that survive across AI sessions to guide consistent behavior.
Category: AI
Tags: ai, context-engineering, context-management, ai-context-patterns
Explanation
Context anchoring is the practice of externalizing decision context into living documents that persist across AI-assisted development sessions. The concept was described by Martin Fowler's team at Thoughtworks in their work on reducing friction with AI.
## The Core Problem
AI conversations are ephemeral. Decisions made early in a session fade as the context window fills. Research (Liu et al., 2023) shows models perform worse on information buried in the middle of conversations. Worse, the *reasoning* behind decisions fades faster than the decisions themselves. Developers end up keeping conversations running far too long, not because long sessions are productive, but because closing the session means losing context that exists nowhere else.
## Two-Layer Solution
Context anchoring solves this by capturing context in two layers:
- **Priming documents** (project-level): tech stack, architecture patterns, naming conventions. Relatively stable, updated quarterly. Shared across all features. This is essentially what CLAUDE.md files and AI agent skills provide in tools like Claude Code.
- **Feature documents** (feature-level): specific decisions, rejected alternatives, constraints, open questions, implementation state. These evolve rapidly with each session and enable coordination across developers and AI sessions.
## The Litmus Test
The key question: "Could I close this conversation right now and start a new one without anxiety?" If discomfort emerges, context is trapped in the wrong medium.
Context anchoring is a context hygiene practice that directly combats context drift and context rot. By externalizing context into version-controlled documents, it becomes reviewable, shareable, and durable. It is also a form of progressive disclosure at the project level: priming documents provide always-on context while feature documents load on demand.
Related Concepts
← Back to all concepts