Q
Why isn't decay enough?
Decay handles low-relevance aging. Drift handles high-relevance wrongness — the dangerous case where the old fact keeps winning retrieval.
Glossary · Drift Detection (Git-Anchored Invalidation)
Drift Detection (Git-Anchored Invalidation).
The codebase is the ground truth.
Direct answer
Content-anchored invalidation binds memories to the code spans that justify them; when git history moves underneath, affected nodes are flagged LowConfidence or demoted. This solves the staleness problem decay alone can't: a highly-retrieved fact (your auth scheme, your employer) becomes confidently wrong the day reality changes. Drift checks run per session and at session end; anchors, not timestamps, decide.
In Anvaya
How We Implement It.
01Drift Detection (Git-Anchored Invalidation)Anvaya's Invalidation service checks anchors against git diffs each session; drifted nodes drop confidence and stop packing until re-corroborated.
Questions
Asked About Drift Detection (Git-Anchored Invalidation).
Q
What is an anchor?
The file span, symbol, test, or commit a node cites as evidence. Move the span, trip the check.
Q
How does this compare to editing CLAUDE.md?
Manual edits rely on humans noticing. Anchors notice automatically, every session, against git truth.
Stop Starting From Zero.
One binary. 11+9 Rust crates. 545 tests. Hand-written HNSW index. Three transport modes. Four providers, Ollama, Anthropic, OpenAI, Siemens. Zero API keys required to start. Mind remembers everything after the first session.