[ellieh]

agreed - we actually have a dependency system in the works too!

you can define + declare ordering with dependency specification on the edges of the graph (ie A must run before B, but B can run as often as you'd like within 10 mins of A)

[nine_k]

There of course should be a way to override the dependency, by explicitly pressing a big scary "[I know what I'm doing]" button.

Another thing is that you'll need branches. As in:

  - Run `foo bar baz`
  - If it succeeds, run `foo quux`,
    Else run `rm -rf ./foo/bar` and rerun the previous command with `--force` option.
  - `ls ./foo/bar/buur` and make certain it exists.

Different branches can be separated visually; one can be collapsed if another is taken.

Writing robust runbooks is not that easy. But I love the idea of mixing the explanatory text and various types of commands together.