EdgePulse is a filter, not a signal generator. The mistakes below all share one root: treating it as something it isn't.
Trading Tier 1 Early signals as entries
Tier 1 is a heads-up. Primary Edge just crossed zero and no companions have confirmed. Use it to begin observing; a higher tier still needs to satisfy the location, invalidation, and risk conditions in your plan.
Ignoring Counter Edge
When Primary pushes up but Counter also pushes up (failing to inverse-confirm), the broader complex isn't on the move you're seeing. Respect the counter.
Taking Full Stack signals against the rest of your stack
A Full Stack long when price is below FLB zones and Surge is red is EdgePulse disagreeing with everything else. The white diamond doesn't override the rest of the stack.
Forcing Pro mode on unsupported symbols
You can set Mode to Pro, but EdgePulse will still run Standard because companion data doesn't exist. Trust the badge, not your input.
Disabling companions to clean up the panel
Turning off a companion lowers the Full Stack threshold artificially. A 'Full Stack' with only Primary + one companion is much weaker than true four-way alignment.
Overriding Trade Shield for a Full Stack
The white diamond can look compelling, but it does not supersede Trade Shield. Treat an active warning as a configured rule condition rather than overriding it because one setup looks attractive.
Disabling Signal Confirmation to catch more signals
Confirmation filters pending states that do not maintain alignment for the configured window. It changes which signals qualify; it does not establish what the filtered signal would have earned or lost.
Treating EdgePulse as a standalone system
EdgePulse can remain noisy during chop and may not capture every fast directional move. Use it as one filter alongside Surge, Key Levels, FLB zones, and Trade Shield.