Research: anti-drift lint rules between docs and memory (2026-04-18)
Migrated from Plane work item DASHE-13 on 2026-04-18. Original Plane workspace retired; this is the canonical home.
Anti-drift lint rules between docs and memory
Section titled “Anti-drift lint rules between docs and memory”Concrete checks a scheduled Lint agent would run to catch docs↔memory drift.
Promotion triggers (memory → docs)
Section titled “Promotion triggers (memory → docs)”- Memory entries with
importance ≥ 4ANDhit_count ≥ 5— signal: this learning matters enough to go canonical
Auto-archival (memory)
Section titled “Auto-archival (memory)”- Memory entries older than 30 days with
hit_count = 0— auto-compact or delete (unused, not worth keeping)
Broken provenance
Section titled “Broken provenance”- Docs with
source_refspointing to files that no longer exist in git → flag for cleanup
Redundancy (memory ↔ docs)
Section titled “Redundancy (memory ↔ docs)”- Memory entries duplicating a known doc section (BM25 similarity > 0.85) → flag as redundant
Stale docs signal
Section titled “Stale docs signal”- Docs with
updatedolder than any memory write on the same topic → review whether the doc has gone stale
Who runs it
Section titled “Who runs it”Scheduled LLM-as-judge weekly pass — a dedicated Review-E variant or a cronjob. Per Evidently / Arize guidance: “strict separation between generation and evaluation” — use a different model from the agents that authored the content.