Support, Resistance and Floor Pivot Points
Why support and resistance are areas rather than promises, and how deterministic pivot formulas differ from AI-generated levels.
Understand observed zones, deterministic pivot levels and the limits of horizontal price references. This article explains the reasoning framework used by Trading.Red and the limitations a reader should keep in view.
What the terms actually mean
Support is an area where prior demand, positioning or order flow has previously slowed a decline. Resistance is an area where prior supply has slowed an advance. They are observations about past interaction, not physical barriers. Price can pause, reverse, gap through or ignore either area.
The more useful question is not whether a line will hold. It is whether price accepts or rejects the area. Acceptance usually involves closes and sustained trading beyond it. Rejection is better supported when price probes the area and then closes back inside the prior range.
Why Trading.Red uses zones
Market data contains spreads, gaps, different trading sessions and occasional provider adjustments. Treating one decimal value as perfect precision creates false confidence. Trading.Red therefore distinguishes an observed range from scenario levels and shows the data timestamp beside the analysis.
Repeated reactions can strengthen the relevance of an area, but repeated tests can also consume the orders that previously supported it. Context matters: a level tested during quiet trading is not equivalent to the same level tested after earnings or a broad market shock.
Deterministic floor pivots
A floor pivot uses the previous completed session's high, low and close. The central pivot is their arithmetic mean. First resistance is twice the pivot minus the prior low, while first support is twice the pivot minus the prior high. Because the inputs and formula are fixed, the result is reproducible and does not depend on a language model inventing a number.
Pivots are reference points, not forecasts. They do not know about overnight news, liquidity, corporate actions or the next session's volatility. A responsible interface shows them as one layer alongside price structure rather than as guaranteed targets.
How to evaluate a level
Check whether the source candle is complete, whether prices have been adjusted consistently, and whether the level belongs to the selected timeframe. Then compare distance to recent volatility. A level within ordinary noise is less informative than one that coincides with a confirmed swing, a moving average and a visible change in volume.
When evidence disagrees, the correct output is a lower-confidence or neutral state. Reversing labels merely to make a scenario look orderly would hide uncertainty and damage the audit trail.
Worked example: reproducible floor pivots
- Prior high: 108
- Prior low: 100
- Prior close: 104
Reading: The central pivot is 104, first resistance is 108 and first support is 100. Anyone using the same completed inputs obtains the same values; the calculation still does not predict which level will trade next.
Key takeaway
A technical label is a compressed description of market data, not knowledge of the future. Use the label to organize questions: which timeframe produced it, what confirmed it, which observation would invalidate it, and what data might be missing?