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

# Signal Engine & Scoring

## Core signal condition

Execution is triggered only when price velocity, volume acceleration and remaining time all cross their thresholds **simultaneously**. A single factor — a volume spike without price movement, or price movement without volume confirmation — is not enough to fire.

<figure><img src="/files/LHrzUWugNzrzhujB3bPe" alt="Execution logic: price velocity AND volume acceleration AND time remaining"><figcaption></figcaption></figure>

## Signal scoring: how the system detects edge

The Signal Engine computes a **composite Signal Score** on every data tick. Execution fires only when the score exceeds a calibrated threshold — reducing false positives while maintaining speed.

<figure><img src="/files/Tce2wCRxnDzVGYqyIPV5" alt="Signal score computation from price velocity, volume acceleration and liquidity imbalance"><figcaption></figcaption></figure>

Weights are calibrated per market type: 5-minute markets prioritise price velocity (speed is critical), 15-minute markets weight volume confirmation higher.


---

# 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://docs.polygoatbot.com/signal-engine.md?ask=<question>&goal=<endgoal>
```

`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.