In principle, yes. The stated goal of this project is to be a versatile tool.

I would be very interested in those features. We’re currently evaluating datalevin for a project, and right now we’d have to reify everything to support our recursive hypergraph

I can certainly adjust roadmap if there are compelling and concrete use cases. However, this is just one of my side projects, not my day job, so I always welcome contributions. I may get more time to work on this if my company exited or failed. We will see in 18 months 🙂

For sure! We also have a workaround via reification for now, and our tech search isn’t fully complete yet either. This is mostly me adding a data point that there’s someone out there interested in these features, and that there’s a possibility that we might be interested in helping to contribute these features if everything works out. Out of curiosity, where do the hypergraph and reasoner features sit right now on your roadmap? I’ve been really impressed with Datalevin’s development so far, with the addition of the new query optimizer it’s heading in directions that distinguish it from the other available options in really interesting ways.

In order to handle more clause types, e.g. (or ...) etc. hypergraph need to be considered, so this is part of the ongoing effort to expand the optimizer's reach. "As a production rule engine with truth maintenance" is 2.0.0 on the roadmap. But can be moved earlier, as it will position Datalevin more uniquely. OK, it is now 1.0.0.