Here is an example of what we use for business logic on selecting a driver for delivery from the pool (it is slightly simplified - it's essentially the set of basic operations, ifs, cycles, and set of input data, process variables, and output data).
Take a look here https://www.evernote.com/l/AA9s6U867f1GvLgIr3iOHrzJgrjkRxWe0nUB/image.png
We maintain this in the versioned diagram that can be pushed to Lambda + API gateway, and essentially the platform code relies on that endpoint to provide a response.
For the project we are using it for, it allows us to make adjustments to the process without depending on engineering; another use case is pricing -- override and experimentation.
Again, the engineering team thinks it is cool and wants to productize it. I would really appreciate any feedback or ideas.