What it is
A dependency is a typed link between two tasks — blocking, parent-child, or related. Everview computes a health status for blocking dependencies based on how much schedule slack exists between the two tasks: Violated, Tight, Constrained, or Safe, from most to least at-risk.
How to read it
Safe means there's comfortable slack between the blocking task and the one waiting on it. Constrained and Tight mean the slack is shrinking — the dependent task's schedule has little room left to absorb delay. Violated means the blocking task is already scheduled to finish after the dependent task needs it, an active scheduling conflict. Dependency lines on the canvas connect the tasks' ports directly, so you can trace a chain visually.
What to do about it
Treat Violated dependencies as immediate scheduling problems, not something to note for later. Constrained and Tight dependencies are worth checking before they become Violated, especially on tasks that sit on the critical path — the chain of dependent tasks with the least slack across a project. A cluster of Tight or Constrained dependencies in one area is worth raising in Spotting Delivery Bottlenecks with Operation View.