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

# Divergence engine

Pure arithmetic. The model never gets to invent the dots.

The divergence engine finds what is unusual. It is pure arithmetic over the factor store and the mechanism graph, and it runs at every anchor. The "hidden dots" the desk talks about are found by measurement; the model only describes them.

## Three kinds of flag

**Extreme state.** A factor whose 365-day percentile is at or above the 95th, or at or below the 5th. Funding at the top of its year, depth at the bottom of its year, liquidations at a yearly high.

**Broken relationship.** A channel in the mechanism graph whose two ends are moving against the documented mechanism. Only edges where both ends are measured factors can be checked this way, so this flag grows in reach as the graph gains factor-to-factor channels (for example, liquidations to depth, or stablecoin float to spot volume).

**Structural signature.** The flagship question of Market State: is this move spot-led or leverage-led?

| Signature        | Fires when                                                                 |
| ---------------- | -------------------------------------------------------------------------- |
| **Leverage-led** | The funding regime is elevated and open interest is historically elevated. |
| **Spot-led**     | Funding is not elevated and open interest is calm.                         |
| **Fragile**      | The move is leverage-led and funding is stretched.                         |

When the inputs for a signature are missing or have too little history, the signature is recorded as **indeterminate**, never guessed.

## Properties

* **Deterministic.** The same store at the same anchor always produces the same flags.
* **Point-in-time.** Flags are computed only from what was captured by the anchor, and stored with it, so the record shows what the engine saw then.
* **Feeds everything.** Flags appear on the live pulse, in the evidence of every answer, in the context the model narrates, and as conditions a watch can describe.


---

# 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.scanbylens.xyz/the-engine/divergence.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.