The thoughts are still swirling around in my head a bit, but given the current
targets that Antlr4 supports, I fear that .otto file parsing will need to be
handled in JavaScript or C++.
There's a big question in my mind on how to express what requires a runtime and
access to the working directory, and what should live "outside" of that.
Still uncertain.
Including an example to help tinker with the user interface for modeling a
process for a mock heroku-based web application.
What's missing right now for sure is the concept of credentials and how those
might fit into the world. That will require more thought.
The syntax is at the moment heavily inspired by Declarative Pipeline from
Jenkins, but not actually compatible.
R Tyler Croy