> For the complete documentation index, see [llms.txt](https://aitaprotocol.gitbook.io/aita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aitaprotocol.gitbook.io/aita/core-concepts/backtesting-vs-live-execution.md). # Backtesting vs Live Execution ### Backtesting vs Live Execution Backtesting and live execution serve different purposes on AITA. Both are based on the same strategy and parameters, but they operate in fundamentally different environments. Understanding the distinction is essential for interpreting performance and managing expectations. #### Backtesting Backtesting evaluates how a strategy and its parameters would have behaved when applied to historical market data. Backtesting: * Uses past data to simulate strategy behavior * Helps users understand historical drawdowns, volatility, and behavior * Is performed under defined assumptions and constraints Backtesting is descriptive. It shows how a strategy reacted in specific historical conditions, not how it will perform in the future. #### Live execution Live execution applies the same strategy and parameters to current market conditions. Live execution: * Operates in real-time market environments * Is affected by current liquidity, volatility, and market structure * Reflects practical constraints such as capital availability and execution conditions Live outcomes may differ materially from backtested results. #### Why results can differ Differences between backtesting and live execution can arise due to: * Changing market regimes * Liquidity conditions * Slippage and execution constraints * Capital requirements and account limitations These factors exist independently of the strategy logic itself. #### Interpreting results responsibly Backtesting provides context and understanding, while live execution reflects real-world behavior. Neither backtesting nor live execution guarantees outcomes. Backtesting does not account for future liquidity, slippage, or behavioral changes. Historical behavior does not predict future performance, and users remain responsible for how they interpret and act on both. --- # 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, and the optional `goal` query parameter: ``` GET https://aitaprotocol.gitbook.io/aita/core-concepts/backtesting-vs-live-execution.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.