Blocked chains
A blocker is rarely the end of the story. The project blocking you may itself be blocked by another, and that one by another. Synaps traces these chains across your whole portfolio and points you at the project at the very end - the one actually holding everything up.
Blocked-chain detection works in Graph View, with extra cues in Table View.
01. What a blocked chain is
When a Blocks link points from one project to another, and that second project is itself blocked by a third, you have a chain: A blocks B blocks C. The work in A cannot really move until C clears, even though nothing in A links to C directly.
Synaps walks these chains for you across every project, and it is cycle-safe - if two projects block each other, the trace stops cleanly instead of looping forever.
02. On the graph
In Graph View, the links that make up a chain are drawn in red. The cue is always on, so you can spot a deep dependency without hunting for it, and it intensifies when you focus a project at either end of the chain.
03. The root blocker
Hover any line that is part of a chain and its tooltip gains a Root blocker row, naming the project at the far end by its key. That is the project to chase: clear it, and the whole chain behind it is free to move.
This turns "something is blocked" into "escalate to this team" - without you tracing the links by hand.
04. In the table
Table View carries the same intelligence. A dependency that sits on a chain gets a red chain badge on its row, and the row's escalation tooltip names the root blocker. These cues are voiced for keyboard and screen-reader users, not just shown visually.