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

# Strategy Lab

Replay a baseline against historical market data.

## Strategy Lab

Strategy Lab replays a clearly labeled baseline against historical public candles.

### Review each run

Each run presents its test window, assumptions, costs, trade record, and saved output. Compare results with buy-and-hold over the same period.

Historical simulations are experiments. They cannot predict future performance.

### Work with uncertainty

Use a test to understand how a rule behaved under a specific dataset. Do not treat a positive result as proof that a strategy will work later.

{% hint style="warning" %}
Past performance does not indicate future results. Tidelight does not provide investment advice.
{% endhint %}


---

# 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.tidelight.app/use-tidelight/strategy-lab.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.