A memory server remembers your conversation. That is not the same as knowing your code.
The Model Context Protocol has no memory primitive and no memory extension, and its July 2026 revision deprecated two of the three client features it used to have. So every memory over MCP is a server implementing one with ordinary tools — and what those servers remember is the right thing for them to remember. Conversation is personal, stated and durable. Knowing a codebase is shared, derived and perishable. Same word, opposite requirements, and a remembered fact about code does not decay into silence but into a confident wrong answer.
The wiki cannot fail. That is what is wrong with it.
Documentation with no build has no failure mode. Nothing breaks when it stops being true, so it decays into a confident wrong answer that reads exactly like a right one — which is worse than no documentation, because a new joiner cannot tell the difference. What changes when the document is an artefact with a build, a provenance record naming the commit it describes, and a way to be seen failing.
33 of 79 false positives on a code review benchmark were real defects
The Martian Code Review Bench offline set scored this run at 48.0% precision. A benchmark judge matches each comment against 173 human-written goldens, so a correct finding the annotator never wrote down is counted false by construction. All 79 false positives were opened in the source at the reviewed commit and given a verdict: 33 are real defects the gold set does not contain, 38 are genuinely wrong, 8 could not be settled from the code. Every verdict is published with its code and a pinned permalink, so any of them can be disputed with the same evidence in view.
Introducing Celmis
Self-hosted code intelligence over a symbol graph: what it does, what it refuses to claim, and how to run it on one machine.