> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/investing/market-structure-and-rotation/investor-tool/usage.md).

# Usage

Investor Tool Usage

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2Fgit-blob-b4d65087716bb13f50cf1885ef783d6213683a02%2Fdocs-investor-tool-002.png?alt=media" alt=""><figcaption></figcaption></figure>

Turn drift into a plan by reading baseline slope, respecting dispersion, and letting anchors guide your execution.

**Playbook**

* **Regime by slope:** Rising MA → bias to accumulate on pullbacks; falling MA → favor patience, hedges, or trims.
* **Trade the stretch:**
  * Near **Upper Band** → look for distribution, take partials, or require momentum confirmation to add.
  * Near **Lower Band** (if enabled) → watch stabilization for staggered adds.
* **Anchor confluence:** Intersections of **Year WVAP** with **Quarter/Month WVAPs** often mark high-probability reaction zones.
* **Intraday awareness:** On intraday charts, “years” map to ≈252 bars/year; interpret the MA as a long sample of trading sessions.
* **Portfolio cadence:** Use MA slope + band touch + WVAP retest as a three-point checklist for scaling decisions.

**Parameter guidance**

* **MA Period (Years):** 2–3 for business cycle sensitivity; 5–10 to smooth secular noise.
* **Multiplier:** 1.2–1.8 for equities/indices; 1.6–2.4+ for crypto; 1.0–1.4 for low-vol defensives.
* **Anchors:**
  * **Year:** Strategic fair-value magnet.
  * **Quarter/Month:** Tactical pullbacks within the yearly path.
  * **Week/Day:** Swing/active trading precision.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.candelacharts.com/investing/market-structure-and-rotation/investor-tool/usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
