MemPalace vs Statewright

MemPalace is an open-source persistent memory system for LLMs that takes a philosophically different approach from every summarization-based alternative: it stores conversations verbatim, forever, and retrieves them with semantic precision. Where systems like MemGPT or standard RAG pipelines compress memories into lossy summaries, MemPalace treats exact wording as sacred — because often the specific phrasing of something a user said six months ago is the thing that matters. The storage architecture uses a hierarchical "memory palace" metaphor: people and projects are wings, topics are rooms, individual memories are drawers. Semantic retrieval is scoped to sub-trees rather than doing a flat vector search across everything, which dramatically reduces false positives and improves precision at depth. The system claims a 96.6% score on LongMemEval — the highest publicly reported score among free tools — and integrates with any OpenAI-compatible API endpoint. Verbatim storage does mean storage costs grow linearly with usage, and there's no built-in forgetting mechanism yet (which some see as a bug and others as a feature). But for personal assistants, coding agents, and any application where "you told me X last Tuesday" accuracy matters, MemPalace's approach to memory is architecturally more honest than the alternatives.

Statewright takes a provocative stance on AI agent reliability: instead of making models smarter, restrict what they can do. The framework lets you define explicit state machines that determine which tools an agent can access at each phase of a workflow. During planning, agents get read-only tools. During implementation, edit tools unlock. During validation, only test commands are available. The philosophy is captured in a single line from the README: "Agents are suggestions, states are laws." The core engine is written in Rust for deterministic, zero-LLM evaluation of state transitions. Plugin layers integrate with agents via MCP (Model Context Protocol), enforcing tool restrictions at the protocol level across most major platforms. The framework is Apache 2.0 for its core engine, with FSL licensing for extended features (converting to Apache 2.0 in 2029, self-hosting allowed for developers and teams now). The team published SWE-bench results showing models jumping from 2/10 to 10/10 success rates on five tasks when Statewright constraints were applied—a striking claim that has the HN crowd both skeptical and intrigued. This is genuinely novel territory: rather than prompt engineering or fine-tuning, it's architectural guardrails enforced at runtime. For production agent deployments where agents interacting with dangerous tools (databases, file systems, APIs) need hard constraints, this fills a real gap. 53 stars so far, but the HN traction suggests it's about to pop.