obsidian-task-collector VS datascript

I agree with your issue of reification and I like the concept of a "wit."

I think we're getting there, too. See, for instance, https://github.com/nothingislost/obsidian-query-control — it renders the results of an embedded Obsidian query and you can interact with checkboxes. Likewise, a collaboration between dataview and the Task Collector plugin might let us manipulate different task statuses from a dataview query: https://github.com/ebullient/obsidian-task-collector/issues/...

Exciting times!

Try Task Collector plugin: https://github.com/ebullient/obsidian-task-collector

Hi pests, I don't think the criticism in the comments gives a full picture.

I wrote about a particular flavor of datalog, in common use today. [1] [2]. The earliest representation I know, which matches the syntax of my essay, was in SICP [3]

There's another, more academic form of datalog, which looks a lot more like prolog. Both have lots of similarities: both systems have a set of facts and rules. Both systems have can take a partially filled fact or rule, and find all matching facts. The more academic flavors of Datalog are useful for general logic, and particularly powerful for recursive questions. The variant I showed is more tailed for database queries.

[1] https://github.com/tonsky/datascript

There is also datascript as a similar option.

What's the use case for relic? Sounds similar to https://github.com/tonsky/datascript ?

This look nice !

Datascript seems to be another Datalog engine (in memory only)

https://github.com/tonsky/datascript

Inspired by past work: LINQ, inline-python, crepe, DataScript, Riffle.

An in-memory database like Datascript may be worth looking into. Otherwise you could take an indexing approach: put all the data into one big map indexed by some unique key, and have a bunch of supplementary indexes that are updated on insertion.