Problem: common, high-level step sequences are not standardized or abstract enough

[jrwdunham]

There are too many ways being used currently to do the following:

1. Perform some action, typically initiating a transfer/ingest
2. Make a series of decisions until something happens:
   • an AIP is created
   • an AIP is available for review
   • a particular micro-service has completed
3. Perform some second action, given the system/AIP is in the state guaranteed by (2)

We need a clear and memorable way of expressing, with minimal specification, common steps. For example:

When the user makes standard decisions to go from decision point "<DECISON_POINT_A>" to "<DECISON_POINT_B>"

or:

Given a processing config with standard decisions to go from decision point "<DECISON_POINT_A>" to "<DECISON_POINT_B>"

Where "to go from" implicitly assumes a particular sub-chain of the workflow, and "standard decisions" are defined how?