Invite People

Share 4 Engineers with your friends and help them get started!

Emails
Enter multiple email addresses by separating it with a comma.
Back
4Engineers
· Martin Fowler
AI summary

Context Anchoring is a pattern for reducing drift and repetition in AI-assisted work by externalizing key decisions and context into a living, shared document. Instead of burying goals, constraints, definitions, examples, style rules, and rationale inside ephemeral chats, teams maintain an anchor doc with stable sections/IDs that the AI must reference and cite in responses. This doc is versioned, iteratively refined after interactions, and used across sessions and tools (often via lightweight RAG or explicit prompt links), enabling continuity, faster onboarding, and more consistent outputs. Practical guidance includes starting small, clarifying ownership and review, requiring the AI to flag conflicts or gaps, and avoiding anti-patterns like pasting the entire doc into every prompt, allowing unreviewed AI edits, or letting anchors grow vague/stale.

What would your team include as the “must-have” sections in its first anchor doc, and how would you keep it current without adding process overhead?

Context Anchoring

This article was originally posted on martinfowler.com.

Conversations with AI are ephemeral, decisions made early lose attention as the conversation continues, and disappear entirely with a new session. Rahul Garg explains how Context Anchoring externalizes the decision context into a living document.

more…

Login to comment

Login
Report content
Reason Description