Constrain flows to be DAGs?

Should the UI constrain nodes to be within a DAG? At present feedback is permitted in the UI, and generates multiple new inputs/outputs.

If flows were DAGs it would be possible to allow to user to automatically rerun the entire flow on making a change in a parent node.

(This project is great BTW. I found it by searching for front end libraries for graph editing because I wanted to make something very similar).

Start by tracing the UI flow editor and how feedback currently creates multiple inputs and outputs. Compare that behavior with the proposed DAG constraint and the automatic rerun idea, then clarify the intended scope with maintainers. The issue names no files or tests, so completion would require an agreed design and implementation plan.

Written by the indexing model from the issue text.