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

# Overview

Tally's features beyond the quote and the buy are **modules**. Each follows the same shape, which kept a team of agents from stepping on each other and kept every module switchable.

| Layer      | Where                                           | Rule                                                                                        |
| ---------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------- |
| Logic      | `packages/mod-<name>`                           | Pure TypeScript with tests. No UI, no network on the request path.                          |
| Collection | `apps/worker/src/jobs/<name>.ts`                | Writes snapshots to the store; has an interval, a timeout and independent failure handling. |
| View model | `apps/web/modules/<name>/` and `/api/vm/<name>` | A typed state (loading, empty, stale, degraded, normal) plus a plain unstyled component.    |
| Page       | `apps/web/app/...` and `components/`            | Renders view-model states. Never computes them.                                             |
| Switch     | `FEATURE_<NAME>`                                | Off means the route answers 404 and the worker is not started.                              |

## The modules

| Module                                                                   | What it does                                                                | Page                 |
| ------------------------------------------------------------------------ | --------------------------------------------------------------------------- | -------------------- |
| [Receipts](/product-modules/receipts.md)                                 | Verifies a transaction onchain and shows shares received against the floor. | `/receipt/[hash]`    |
| [Portfolio and statements](/product-modules/portfolio-and-statements.md) | Holdings in shares across issuers, activity, a statement export.            | `/portfolio`         |
| [Radar and Flow](/product-modules/radar-and-flow.md)                     | Integrity grades for every token and per-issuer trade-flow panels.          | `/radar`             |
| [Guardian and the Telegram bot](/product-modules/guardian.md)            | Alerts about tokens you hold.                                               | `/guardian`, the bot |
| [Selling and Migrate](/product-modules/selling-and-migrate.md)           | Sell to USDT, and move a position between issuers.                          | Trade, Portfolio     |
| [Pies](/product-modules/pies.md)                                         | Basket buying from a budget and weights.                                    | `/pies`              |
| [Autopilot](/product-modules/autopilot.md)                               | Policy and decisions in shadow mode. Nothing executes.                      | `/dev/autopilot`     |

## Honesty rules every module follows

* A number that cannot be verified is shown as unknown with the reason, never guessed.
* A stale module shows its last good data and its age. Raw worker errors are not shown to visitors.
* Data from a recording is labelled as a recording.
* A module says what it did not do: for example, Receipts reports amounts only when the chain has confirmed 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tallyprotocol.xyz/product-modules/overview.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.