A couple of questions: 1. Which parts are open source? Will it require a commercial license? 2. I once worked on an already-existing credit card chargebacks s

A couple of questions: 1. Which parts are open source? Will it require a commercial license? 2. I once worked on an already-existing credit card chargebacks system that was horrifically complex, with all kinds of variations and rules and states that play out over weeks or even months. The logic was scattered all around a Rails app, sometimes in clear chunks of business logic, but sometimes something like an `expired?` accessor on a chargeback variant would know the expiry period for that type of chargeback, etc. I toyed with the idea of trying to pull all the logic out into some kind of non-code representation. Possibly a state machine diagram, possibly a giant spreadsheet (because with real-world payment processing, you can get just about any response when you're in any state, whether it seems valid or not, and you have to choose to do _something_!). Possibly a state machine diagram for the normal path but with a spreadsheet representation for the full cross-product of weird state transitions. Alas (or thankfully), I moved to a different project before I could undertake anything ambitious. Would Stately let me do that? Move the knowledge of a hideously complex real-world, extended process that had been painstakingly gathered for years and encoded in logic scattered around an application, and let non-programmer, business-level people use that representation to understand and even tweak parameters of the process?