> 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/major-assets/usage.md).

# Usage

Major Assets Usage

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

Turn the indexed panel into decisions with a clear setup, focused comparisons, and repeatable checks.

What to look for:

* **Leader & laggard:** Highest vs. lowest line since base; persistent spread = durable trend.
* **Base recapture/failure:** Crosses of 100 often mark regime turns; confirm with breadth/vol.
* **Risk posture:** QQQ/SPY vs. TLT/T-Bills—if risk outruns safety, the tape favors beta.
* **USD effect:** DXY vs. ACWI/GLD—rising dollar + weak ACWI can pressure global risk.
* **Crypto beta:** BTC/ETH vs. QQQ—outperformance signals higher-beta appetite.
* **Liquidity lens:** Overlay US M2 to see whether leadership aligns with liquidity expansion.


---

# 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/major-assets/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.
