> For the complete documentation index, see [llms.txt](https://docs.skylit.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skylit.ai/faqs.md).

# FAQs

## 💬 Frequently Asked Questions (FAQs)

This section addresses the most common questions traders ask when learning to use **Heatseeker™** and interpreting its signals effectively.

***

### 🟡 Is a King Node Always Yellow?

No — **King Nodes are not defined by color.**\
They can appear as **yellow or purple**, depending on whether the exposure is positive or negative.

> 🎯 What matters most is the **absolute value** within the node.\
> The **largest magnitude** (regardless of color) is considered the **King Node**.

***

### 🧠 How Do I Know Which Node Matters Most?

Prioritize based on **influence and structure**:

1. **King Nodes** → Dealer settlement targets (highest probability zones).
2. **Gatekeeper Nodes** → Deflection zones where trend shifts often begin. These can prevent price from easily reaching the King Nodes.
3. **Clusters of Nodes** → When multiple large values group together, price often **pins** or **chops** around that region.
4. **Double Stacked Nodes** → When multiple nodes are stacked together, price can have a strong bounce from those levels.

> 💡 Think of node hierarchy like gravity:\
> The bigger the mass (absolute value), the stronger the pull.

***

### ⏳ How Long Does It Take to Get Good at Heatseeker™?

Like any edge, **mastery requires time and reps**.

Typical learning curve:

* **Week 1–2:** Recognizing node patterns and color logic.
* **Week 3–4:** Understanding reactions and map reshuffles.
* **Month 2+:** Building pattern recognition and confidence through replay/backtesting.

> 🧩 Most traders gain intuitive flow by **the end of the first month**, but long-term proficiency comes from consistent exposure and journaling.

***

### ⚙️ Can I Combine Heatseeker™ With My Current Strategy?

Absolutely, Heatseeker™ is **strategy-agnostic** and built to **complement**, not replace.

You can pair it effectively with:

* **Price action setups**
* **Liquidity sweeps**
* **Fibonacci retracements**
* **Breakout/Breakdown strategies**
* **Order flow or Delta analysis**

> ✅ Heatseeker™ enhances your edge by showing **where** probability clusters, not **when** to trade.\
> It clarifies *context*, not signals.

***

### 💥 What Happens if the Map Changes Suddenly?

If the map **reshuffles**, it means **dealer positioning has changed** — this is a *feature*, not a bug.

* Take a step back and reassess the structure.
* Mark new **King** and **Gatekeeper Nodes**.
* Avoid trading until the new structure stabilizes.

> ⚠️ A reshuffle often follows **large volatility events** — like CPI, FOMC, or Power Hour — when market makers rebalance risk.

***

### 🧮 How Can I Validate a Trade Idea Using Heatseeker™?

Before entering a trade, confirm three points:

1. **Node Context:** Identify nearby magnets (King or Gatekeeper).
2. **Price Reaction:** Wait for confirmation or rejection wick.
3. **Range Alignment:** Ensure SPX, SPY, and QQQ are in agreement.

> 🎯 When all three align — *that’s conviction.*

***

### 🧭 Quick Reference

| Question                       | Key Takeaway                                    |
| ------------------------------ | ----------------------------------------------- |
| 🟡 Is King Node always yellow? | No — color doesn’t matter; absolute value does. |
| 🧠 Which nodes matter most?    | King > Gatekeeper > Clustered zones.            |
| ⏳ Learning curve?              | 3–4 weeks to internalize flow.                  |
| ⚙️ Combine with strategy?      | Yes — Heatseeker™ adds context.                 |
| 💥 Map reshuffle?              | Pause, re-evaluate, mark new levels.            |
| 🧮 Validating setups?          | Node + Reaction + Index alignment.              |

***

> 🏁 **Final Thought:**\
> Heatseeker™ mastery comes from **observation, repetition, and restraint**.\
> The more maps you read, the faster your intuition sharpens.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.skylit.ai/faqs.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.