Earlier quoted context omitted.
Not GP or specifically Airflow user; but my approach is to have a fixed job graph, and unnecessary jobs immediately succeed. And indeed, jobs are external executables, with all the skip/no skip logic executed therein. If nothing else, it makes it easy to understand what actually happened and when - just look at job logs.
I’m working on similar system. My plan is to have multiple terminal states for the tasks: Closed - Passed Closed - Failed Closed - Waived When you hit that Waived state, it should include a note explaining why it was waived. This could be “parent transaction dropped below threshold amount, so we don’t need this control” or “Executive X signed off on it”. I’m not sure about the auto-skip thing you propose, just from a…
I find embedding logic into DSLs usually quite painful and less portable than having a static job graph and all the logic firmly in my own code.