Each card below is a public method in your code that has an observable outcome — we call it a behavior. The color tells you how well it's tested: green = a test proves it breaks if you change it, amber = a test touches it but doesn't prove breakage, red = nothing tests it.

A flow is the sequence of methods that execute when a real request hits your system. Each box is a method you already saw in the Behaviors tab — but here they're connected as a call chain. Solid lines = hard-coded calls. Dashed = framework-derived. Green boxes pulse because a test proves they break if mutated.

This is the priority-gap worklist, ranked by blast radius and test weakness. It is separate from the coverage-status cards above: Reachable · no test signal is one strict coverage bucket, not the number of priority gaps.