Interesting you bring this up. Actually, our implementation was intentionally de-coupled from the product and it's based on auth API endpoints. (So yes, for something beyond basic conditional logic, this needs to be enabled first.)
Before a call, this diagram comes with manifest of what data has to be supplied into it. So once it's called, all prep data is there. Whatever happens inside is data manipulation and some basic operations. The output of it is also described in the contract.
Very similar to how customized pricing/rating engine might work (as, in fact, I was PM for one of such).
Your project seems fun, too. I'm pretty sure you are going after some specific use cases.
Before a call, this diagram comes with manifest of what data has to be supplied into it. So once it's called, all prep data is there. Whatever happens inside is data manipulation and some basic operations. The output of it is also described in the contract.
Very similar to how customized pricing/rating engine might work (as, in fact, I was PM for one of such).
Your project seems fun, too. I'm pretty sure you are going after some specific use cases.