clara

http://www.clara-rules.org/
2020-07-17T12:12:56.224600Z

@sekao each time there is a match it’s a new rule firing. The cause is whatever the combination of facts it was to cause the rule to fire.

2020-07-17T12:13:10.225100Z

Seems an odd thing you are trying to distinguish.

sekao 2020-07-17T15:48:27.227200Z

fair enough. the reason i'm interested in this is that it would potentially be a way to make updating facts within rules more ergonomic (avoiding the infinite loop problem). but it may not fit how clara works underneath.

2020-07-17T17:12:10.227600Z

@sekao I’d encourage you read http://www.metasimple.org/2017/12/23/clara-updating-facts.html

2020-07-17T17:12:59.229100Z

I wrote it a while ago but it was an attempt to basically dump as much info I could on the updating facts concept and how it interacts with clara and in general the automatic truth maintenance system model (which is what allows rules to be order independently expressed etc)

MatthewLisp 2020-07-17T21:40:41.229900Z

Hello clojurists users of Clara

MatthewLisp 2020-07-17T21:41:03.230500Z

I’m currently using Clara on a project and I’m kinda lost really

MatthewLisp 2020-07-17T21:41:25.231200Z

Lost in the designing of the rules and the facts

MatthewLisp 2020-07-17T21:41:45.231800Z

I wanted to know how you define what is a Fact?

MatthewLisp 2020-07-17T21:42:05.232400Z

What should be a fact in your system

MatthewLisp 2020-07-17T21:42:36.233300Z

Because this directly influence what you insert on right hand side of rules also

MatthewLisp 2020-07-17T21:45:26.237Z

Currently my rules are operating on a state map that represents a requisition from outside. I have multiple records but every record has the same data inside. The rules are pretty much looking whether I have key X or not on the map. It feels wrong, it feels that i don’t know how to design the facts