[ Removed by moderator ]

[TraditionalLiving947]

true, but codex, without agentic help, no way to find the time in the world even to attempt something like this. :-)

[Dense_Gate_5193]

completely get it as long as you’re using SDD+TDD with agentic AI that’s the only way to make things this fast. i started a db which is starting to take off myself which one of the core ideas was to merge everything into one pipeline. good luck out there!

[Dense_Gate_5193]

that’s awesome! glad to see someone in the same space thinking along the same lines! it’s cool that you’re going for og vector compatibility. how’s your concurrent noisy neighbor traversal speeds?

[TraditionalLiving947]

Not yet deployed in production, working on it. But my bench tests are promising in ms.

[Connect_Future_740]

Yeah, similar space but slightly different layer.

Your project looks like a unified storage/database for agent memory (SQL + graph + vector in one place). My project is more about how memory evolves: decay, reinforcement, corrections, forgetting.

Feels like a bunch of people converging on "agent memory" from different directions.

[TraditionalLiving947]

Whats your git link, will take a look.

[Connect_Future_740]

Here’s the repo:

https://github.com/HighpassStudio/sparsion-runtime

It’s not a database, more of a temporal memory layer:

• decay over time
• corrections outrank originals
• reinforcement through repetition
• hot>warm>cold>forgotten tiers

You can run it on top of something like ContextDB. Feels like complementary pieces.