> That is if A and B seem to depend on each other you have some sub tasks in each that need to be pulled out. That produces subtasks without cycles, giving you

> That is if A and B seem to depend on each other you have some sub tasks in each that need to be pulled out. That produces subtasks without cycles, giving you a way forward. Assuming you still want to maintain shared information about the tasks which contain subtasks, those tasks still have a dependency cycle between them though, which is correct because tasks are often like that - they need to move forward together.