Rendered at 11:52:41 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
veqq 12 hours ago [-]
This looks really cool! After building various logic programming engines on top of Janet: https://codeberg.org/veqq/declarative-dsls I was considering something similar (though more bare bones). I'd love to talk to the maintainer to discuss certain design choices etc. Maybe I can wrap it instead of SQLite and Prolog directly as I was thinking.
tern 9 hours ago [-]
Ah, interested to dive in—and have a project it could integrate with.
I built a similar thing recently, for agents, aimed at enabling prolog queries over handles in markdown corpora (and code): https://github.com/flowerornament/anneal. A true slopwerk in comparison to this, however.
gobdovan 11 hours ago [-]
I'm developing a similar project, I also added scripts to it so it works like an hermetic/replayable system too. Do you use yours for anything cool? Maybe a truth maintenance system of sorts? Do the queries get unwieldy at some point?
veqq 10 hours ago [-]
What inspires your project etc.? I'm open to collaborating.
schmuhblaster 3 hours ago [-]
Awesome work! If I understand it correctly, it loads relevant subgraphs from the DB and then runs queries in Prolog on it? Or is it more similar to datalog?
snthpy 5 hours ago [-]
Looks cool. A somewhat adjacent question: what is the best, or what are common, approache(s) for handling time in knowledge graphs?
shaism 12 hours ago [-]
What would be a good use case for this?
Spooky23 8 hours ago [-]
Years ago I worked on an event system that correlated about 500k daily events to about 40 actionable daily events.
A big part of it used prolog to map artifacts to application to business and technical accountable individuals. So if a down storage device offlined a database and broke an app, the business user and storage guy would be called or paged.
My team does this with Splunk today. For probably 50x the compute and 10x the cost.
shaism 2 hours ago [-]
I see. Cool. So did you generate the inference / reasoning rules to map those 500k events to 40 by hand or are there solutions to automatically discover those rules based on past incidences?
I built a similar thing recently, for agents, aimed at enabling prolog queries over handles in markdown corpora (and code): https://github.com/flowerornament/anneal. A true slopwerk in comparison to this, however.
A big part of it used prolog to map artifacts to application to business and technical accountable individuals. So if a down storage device offlined a database and broke an app, the business user and storage guy would be called or paged.
My team does this with Splunk today. For probably 50x the compute and 10x the cost.