Syrup can overcome the von Neumann bottleneck that stops traditional software systems from scaling. It does this by strictly separating the specification, identification and execution phase of Workflows in a distributed setup. Although the phases are explicitly separated, this doesn't mean that each phase can't be expressed in terms of one another. For example, Workflows can be dynamically compiled by other Workflows in Syrup. This Lisp-like flexibility gives developers a chance to maximize concurrency and the distribution of Workflows even further.
Note that Syrup doesn't follow the more complex standards such as Wf-XML, BPML and XPDL. Instead it provides the basic building blocks to implement any of the standards - and hopefully more.
Paul could you please take a look at it and comment? Just shoot any ammo you've got - don't spare any!
Anyway, I've put a lot of effort in making the framework capable of doing anything with a *minimal* set of primitives. I'm not sure if I hit the absolute minimum, but at least the goal should be that it can be grasped by business people with minimal effort! Because one of my goals, and I know it's also one of yours, is to make systems KISS and enjoyable for people to work with. The only thing that may be tricky to explain in one minute is the self-adaptiveness of Syrup (like Lisp macros are difficult to grasp at first sight).
I've been off this Wiki for a while - I know - but I was lurking it almost every week. I really liked that the maker of Erlang, Joe, added some stuff to this Wiki - COOL!