Live data from Hacker News

Show HN: A lightweight, stateless database for agent memory

polign.com

11–18 of 18 posts

Re: Show HN: A lightweight, stateless database for agent memory

#11

Earlier quoted context omitted.

Thanks, is the concern being non-starter on the trust side? the binary makes zero outbound calls. It talks to your bucket and nothing else, and that's verifiable with egress monitoring. I'm putting up a security page that spells it out. Open-sourcing parts of it isn't off the table. I kept the core closed for now to understand the interest in it.

Harnesses are not a solved problem, yet. There are multiple kinds of memory that are user in them, conceptually. Working, Procedural, Semantic, etc. depending on harness design and architecture. Observe-modify is an integral part of harness development that continues to evolve and change, model to model. Adoption of a system sans functional observability and mutation is of little utility. There's no reason to use a s…

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.

Re: Show HN: A lightweight, stateless database for agent memory

#16
I tried to make a memory system in Claude Code (make it behave like a human from the perspective of memory) using markdown files and indexing plus hooks. But, retrieval is not as good as a human and since keywords are ambiguous, it doesn't behave as intended.

Re: Show HN: A lightweight, stateless database for agent memory

#18

I tried to make a memory system in Claude Code (make it behave like a human from the perspective of memory) using markdown files and indexing plus hooks. But, retrieval is not as good as a human and since keywords are ambiguous, it doesn't behave as intended.

Yes, its likely the keyword search problem. I had decent experience (including benchmark and recall testing) to use the hybrid search. You can check my demo - https://demo.polign.com which has about 12.5 million wikipedia passages working with hybrid search.
Post reply on HN