Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-07 · high
A second project skips vector embeddings entirely to keep that memory readable and auditable instead of buried in a blob.
Why now: Both repos are active as of August 7, with Cambium's repository pushed that same day.
Cambium proposes a governance standard for the corpora that AI agents write to over time, per its GitHub repository. Once an agent's memory store becomes a product's source of truth, nobody's tracking where each fact came from or whether it's still accurate. Nobody's tracking who approved the change that put it there, either. Cambium's schema covers exactly that: provenance, review, and drift.
The project, from developer KimGLee, sits at 204 stars after a push on August 7.
It's not alone. bybit-exchange/kaas, an MIT-licensed knowledge-base compiler with 88 stars, turns notes and transcripts into a queryable Markdown wiki exposed over MCP. It skips embeddings entirely, per its repo.
That's the detail worth sitting with. Vector databases became the default way to give an LLM memory because they're fast to query. A float in a vector doesn't tell you why the agent believes something, the way a provenance record does.
kaas gives up embeddings for a wiki a person can actually read. Cambium gives up an unstructured blob for a schema built around who wrote what and who reviewed it.
Neither project says how it handles conflicting edits when two agents write to the same document at once. And neither has the adoption yet to prove the pattern generalizes past its own repo.
Skipping embeddings on purpose is the tell. Vector stores win on retrieval speed and lose on the thing agent memory needs most once it's editing itself: an audit trail. Watch whether more agent-memory tools drop embeddings the way kaas already has, trading speed for something a human can actually read.
Each link below shares sources, entities, or timing with this story.
Claude Code uses MCP / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Claude Code uses MCP); both cover August, MCP, MIT; reported by the same outlet (github.com).
Claude Code uses MCP / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses MCP); both cover August, MCP; reported by the same outlet (github.com).
Cursor uses MCP / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Cursor uses MCP); both cover MCP, MIT; reported by the same outlet (github.com).
Linked by a graph relationship (Cursor uses MCP); both cover Markdown, MCP; reported by the same outlet (github.com).
Claude Code uses MCP / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude Code uses MCP); both cover August, LLMs; overlapping topics (agent, august).
Claude Code uses MCP / Shared entity: MCP / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses MCP); both cover MCP; reported by the same outlet (github.com).
Anthropic released MCP / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Anthropic released MCP); both cover MCP, MIT; reported by the same outlet (github.com).
OpenCode supports MCP / Shared entities / Same source domain / Shared topic
Linked by a graph relationship (OpenCode supports MCP); both cover August, MIT; reported by the same outlet (github.com).