The first demo was the extra-galactic use case with Nic talking us through the wokflow, with a live demo of the workflow going on in the background. They seem to have gone with Groovy as a scripting language for workflow, interesting choice...
Nic Walton and the AG extra-galactic workflow demo
...and indeed a good number of the people in the audience seem quite worried by the choice of Groovy as the scripting harness for the workflow engine.
We've slid into a long and detailed discussion about what should be user scripted and what workflow should provide natively. I'm very confused about why aplications which already has a workflow harness needs user scripting to stick them together? Surely that sort of thing should be entirely transparent to the user?