Provenance on the note
A note can record the source files it depends on and the commit it was reviewed against. That stamp is what turns 'is this still true?' from a guess into a check.
Memory health
Memory that tells you when it's gone stale.
A wiki or note system that goes stale silently is worse than no system at all — because agents and humans will confidently act on out-of-date facts. Setup is easy; keeping memory true as the code changes is the real problem. This is how Memophant solves it.
Drift detection
When a note's source files change past its recorded commit — and the changes are substantive — Memophant flags it for review on the dashboard instead of letting it rot silently.
Freshness at a glance
A freshness read across each tier shows what's current, what's aging, and what needs eyes — so you fix knowledge before an agent trusts the stale version.
On the dashboard
Stale notes surface where you'll see them.
Drift doesn't hide in a log. When code moves past a note's recorded commit, a 'Needs your eyes' call-out appears on the dashboard and in the activity feed, linking straight to the tier with a remedy — update it, or dismiss it.
- Per-tier drift call-outs link to the exact place to fix
- Tuned to fire only after substantive change — not every commit
- Acknowledge at HEAD to clear the flag once you've reviewed
- The activity feed keeps a running log of what drifted and when
Why it matters
The unsolved problem isn't capture. It's upkeep.
Anyone can write a note. The hard part is noticing when it stops being true. Without drift detection, a stale architectural note is a trap: an agent reads it, believes it, and ships the wrong thing. Provenance plus drift turns your memory into something you can keep trusting as the codebase evolves underneath it.
Knowledge that stays honest as the code moves.
The memory layer that flags its own staleness before an agent acts on it.