...
This is a concept, not a Python design, just yet. It makes sense to look at existing workflow management packages to see whether their data models can accommodate this. This is especially relevant because we want to be able to persist the graph and reconstruct it, so that the Pre-flight phase can be separated from the "submit units of work" phase.
The intent is for this graph to be usable by all concrete Activators (e.g., the Level 2 / DRP production system) as the input for their construction of a concrete execution plan. It is at that stage, then, that a concrete Activator could determine, e.g., that it was going to wrap up 100 CCDs' worth of ISR-SuperTask "Jobs" into a single batch job. The concrete Activator would then be responsible for building the resulting batch-job-level aggregate DAG.