Six months of agent-memory provenance fields nobody could see: a Reddit stranger found the gap

Neither-Witness-6010 · reddit · 2026-10-19

The author built CogniCore, a memory layer for coding agents that makes provenance first-class: every entry carries sourceagent/sourcetask, timestamps, confidence, supersedes/invalidatedby links, and a state enum separating 'asserted' from 'independently verified' outcomes.

The lesson: a field is not a feature until the interface surfaces it. After six months of infrastructure, their recall tool returned only outcome/relevance/action/error — none of the provenance — and a stranger on Reddit spotted the gap before they did.

Open design question: how much provenance should travel with a recalled memory? Their current stance: always include source + verification state, attach supersession links only when actually superseded.

Honest limits: retrieval is in-process TF-IDF/BM25 (no vector DB); on LongMemEval multihop, strict recall@5 goes 78.8%→85.2% at 5 chunks and 87.2%→92.8% at 10, with the baseline catching up at 20 — reported rather than hidden. MIT-licensed at github.com/cognicore-dev/cognicore-env

Original post →

More from coding & agent

coding & agent channel →