9 ms·
That is precisely how the dreamcoder [0] ai agent I built also works. It has an event sourced architecture in SQLite and it resolves queries using recursive CT
by mickeyp 1mo ago
That is precisely how the dreamcoder [0] ai agent I built also works.
It has an event sourced architecture in SQLite and it resolves queries using recursive CTEs (and sneaky projections to speed things up) to deliver exactly that. Identical, stable message chains to AI and complete introspection.
Bonus points include a constraint-satisfaction solver for the tiling window manager so windows never shrink too small to read. And many other keyboard-friendly features.
[0] https://www.dreamcoder.ai/ https://www.dreamcoder.ai/
[1] https://www.dreamcoder.ai/assets/graph.webp https://www.dreamcoder.ai/assets/graph.webp
- dominotw 1mo agowhy dont you mention that its your site instead of prenteding like something you discovered to swelljoe below. they stealth edited it after my comment. see other examples. https://news.ycombinator.com/item?id=49289293 https://news.ycombinator.com/item?id=49289293 https://news.ycombinator.com/item?id=49120753 https://news.ycombinator.com/item?id=49120753
- SwellJoe 1mo agoThey say "I built" in the first sentence. Seems pretty clear to me that it's their site and they're proud of it?
- rsalus 1mo agoI'm curious, how does the context management work with event sourcing? What kind of events are you storing and how do you decide when to hydrate a new projection?