This is possible because I have exhaustive knowledge of the product, having worked on it for many years as an IC (and watched several other people struggle to manage it before I took the wheel). I imagine I'm a scenario where a manager and team are more disconnected, and nobody is really passionate about the product, that milestones would feel a lot more muted.
The other issue is you could meet a perfectly sane looking alien civilization, but lose track of them, and before you check in again (say after 100 years) they could be a completely different civilization. Just imagine if the USA can go from far Obama to Trump in a year (or a day), how far you might get in 100 years.
Combine the high latency communications and impossible defense against a good offense (near light speed weapons) leads to the dark forest hypothesis.
If your civilization can annihilated in a single strike, the only civilizations that survive have the strategy to a) avoid being detected and b) destroy anyone who has detected them (which results in destroying everyone, to eliminate uncertainty).
The idea being that assuming the actual survival of your species is at the top of your moral pyramid, all kinds of atrocities in its defense are justifiable.
Hinsen has created his own DSL, Leibniz (https://github.com/khinsen/leibniz ; http://dirac.cnrs-orleans.fr/~hinsen/leibniz-20161124.pdf), which he believes is a better alternative to Common Workflow Language. This reproducibility challenge is in support of this agenda in particular, which is worth keeping in mind; it is not an unbiased thought experiment.
CWL is intended for stringing together other programs. It is useful for reproducibility in that it attempts to provide a fairly specific description of the runtime environment needed to execute a program, and also abstracts site-specific details such as file system layout or batch system in use. CWL platforms such as Arvados also generate comprehensive provenance traces which are vital for going back and reviewing how a data result was produced.
Leibniz seems to be a numerical computing language for describing equations, which is more similar to something like NumPy or R. It seems like an apples-and-oranges comparison.
The original call-out is weird, because CWL did not exist 10 years ago so you can't yet answer the question yet of whether it facilitates running 10 year old workflows.