anchor-based-context-recovery

Context recovery uses documentation anchors—stable markers embedded in your codebase docs—to re-establish your position without re-reading entire files. Search for anchors like `<!-- anchor: validation-rules -->` to restore knowledge of architecture and constraints after context changes or feature switches.

Anchors survive file renames and refactors because they're defined in documentation, not code paths. By referencing anchors instead of file locations, your context remains valid even as the underlying structure changes.

Anchor discovery locates relevant documentation anchors across your repo docs, then targeted context extraction pinpoints exact line ranges and code locations referenced by those anchors, letting you jump directly to what you need.

Yes. When context compacts, phase-guided verification uses documented anchor sections to re-establish where you were. Search anchors relevant to your current task to restore alignment with existing patterns and constraints.

Direct code search breaks when files move or refactor. Anchors remain stable because they're documentation-based reference points. This approach keeps you aligned with architecture intent rather than brittle file paths.

Anchors use standard HTML comments—`<!-- anchor: name -->`—in your existing docs. No special tools or dependencies required; they work with any documentation format that supports comments.