An agent acting on wrong memory is worse than one with none.
Every memory tool for coding agents has the same quiet failure mode: knowledge written weeks ago keeps getting recalled after the code it describes was refactored away. The store only grows, nothing re-checks it, and the agent confidently acts on stale facts.
We built Kage around one rule: memory has to prove itself. Every memory cites the files it's about, and it's checked against your repo three times:
On write - a memory citing a file that doesn't exist is refused. Hallucinated knowledge never enters storage.
On recall - if the cited code changed or was deleted, the memory is withheld and flagged instead of served.
