# state

The State section controls the thresholds that define what the indicator considers "trending" vs. "choppy" for both the Momentum and Volatility pillars.

## Settings

| Setting               | Default | Range  | Description                                                            |
| --------------------- | ------- | ------ | ---------------------------------------------------------------------- |
| Block Chop Zone       | ✅ On    | On/Off | Suppresses all signals when the Momentum line is in the chop dead zone |
| Chop Zone Low         | 35      | 0–100  | Lower boundary of the Momentum chop zone                               |
| Chop Zone High        | 65      | 0–100  | Upper boundary of the Momentum chop zone                               |
| Momentum Oversold     | 30      | 0–100  | Momentum level that must be reached before a long recovery counts      |
| Momentum Overbought   | 70      | 0–100  | Momentum level that must be reached before a short rejection counts    |
| Volatility Overbought | 80      | 0–100  | Volatility line level considered overbought (blocks longs above this)  |
| Volatility Oversold   | 20      | 0–100  | Volatility line level considered oversold (blocks shorts below this)   |

## Notes on Threshold Interaction

* The **Chop Zone** boundaries and the **Momentum Oversold/Overbought** levels are independent. The chop zone defines where signals are suppressed entirely. The Oversold/Overbought levels define the extremes that Momentum must visit before a recovery or rejection qualifies.
* Avoid setting **Chop Zone Low** higher than **Momentum Oversold** — this creates a situation where oversold Momentum readings are inside the chop zone and can never trigger a signal.
* The horizontal **dashed lines** on the oscillator panel show Momentum Oversold (green dashed) and Momentum Overbought (red dashed).
* The horizontal **solid lines** show Volatility Overbought (red solid) and Volatility Oversold (green solid).
* The horizontal **dotted lines** show Chop Zone Low and Chop Zone High.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.synergysignal.io/state.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.