Blog

One technical-buyer post per hard-won mechanism. Written for the engineer or security/trust lead who wants the why behind the store, each post links to its research explainer and trust proof map.

• Your agent’s memory is a compliance time bomb
• Human-in-the-loop, not “ask the model nicely”
• Tamper-evident audit: why your memory store needs a hash chain
• Reference-faithful retrieval, no LLM in the loop
• What Mem0’s own docs say about lock-in
• OWASP 2026: our control matrix is the sales doc
• The honest ceiling
• From twelve products to one (a preview of Profiles), Shipped in v1.21.0, see docs/configuration.md for the real knobs; preview kept for the record.
• Agent memory for a contact center: what has to be true before you trust it, BPO / support-center buyer
• DeepSeek Harness (dsh) meets Brain Server: agent memory as an MCP server, dsh / agent-harness interoperability
• The loop runs: what it means for an engine to ask permission, v1.28 FirstLight / Anvil / Settle
• The 500 that proved the audit chain works, failure post-mortem, fail-closed evidence
• Dual-era MCP without the handshake tax, MCP 2026-07-28 + 2025-11-25 interoperability
• Four copies of sha256_hex, what happened when we let a machine audit our own repo
• Prompt injection made stateful, and the memory layer that was built for it, the 2026 memory-poisoning research, and the architectural answer
• Two people have to say yes, approval fatigue and the two-principal quorum
• The redirect that never happens, bearer safety and manual-redirect transport
• Signatures with a stated ceiling, signed pin acks, TOFU limits stated plainly
• Visible mixing beats pretend isolation, the included_global flag and honest tenancy
• Why I built the governance layer, the operating thesis, 2026-09-11
• The week runtime enforcement got a standard, OWASP Top 10 2026 + Agent Control Standard v0.1, updated for v1.28.81
• Local judgment vs rented judgment, the System-1 port is Laya, not Jev — v1.28.92
• The loop learned clinical discipline, the 1.32.7 diagnostics loop and what it buys — v1.28.92
• Two frontends, one contract, shipping a second GUI while the first is still served — the parity fixtures and wire gate that make it safe
• A gate that refuses everything is not a gate, anti-vacuity pins, and the red-proof that stayed green
• Delete is a verb, not a promise, four layers between deleting a row and deleting the bytes, and what SQLite keeps by default
• Catch it on the way in, because it comes back every turn, why the injection screen sits at the write seam, and what fail-open costs

Positions and one-liners live in the media kit.