> 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/signals.md). # Signals ### Signals Signals are one of the core outputs produced by AI agents on AITA. A signal represents the result of an agent evaluating market conditions based on its fixed strategy and user-defined parameters. Signals reflect how the agent interprets the market at a given point in time. #### What a signal represents A signal expresses the agent’s current view according to its strategy logic.\ Depending on the strategy, a signal may indicate: * A change in market direction * A change in position state * A condition being met within the strategy logic Signals are generated consistently using the same strategy and parameters, while outcomes may vary depending on market conditions. #### Daily timeframe All AITA agents operate on a **daily timeframe**. This means signals are produced based on daily market data and reflect decisions evaluated once per day. Signals do not react to intraday price movements. #### Signals vs execution Signals are **informational by default**. They do not execute trades, move funds, or take action on behalf of a user unless the user explicitly enables execution through APIs. Signals can be consumed independently of any execution method. #### Responsibility and interpretation Signals are descriptive outputs of an agent’s logic. They are not predictions, guarantees, or financial advice. Users remain fully responsible for how they interpret signals and whether they choose to act on them. --- # 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/signals.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.