Re:
by anuptalwalkar on Thursday August 27, 2026 @07:59PM
(#49472770)
The policy layer you’re describing lives in the harness, and yes, it changes over time. What I wanted to showcase is polign_db underneath with typed records, hybrid index, attached to your bucket. You can swap your memory design without migrating the storage or spawn nodes to access it quickly.
I see your point on observability. I haven’t baked it into polign yet, but I have been thinking about ‘how’ I would do it a very user friendly way. Glad to have a conversation about it.
Adoption of a system sans functional observability and mutation is of little utility. There's no reason to use a system that cannot be altered in design cycles (or larger model-release cycles), when memory systems aren't that complicated to begin with. RAG, Vector, simple KV, append-only buffers, are all in competition and used at different scales for good reasons.