> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/concepts-and-reference/glossary.md).
# Glossary
Every TradeSurge term, defined in one or two sentences.
TradeSurge uses a small, fixed vocabulary. Each term below means the same thing on every screen and in every page of this manual.
## Account
A single trading account at one prop firm. It has its own balance, firm rule set, phase, status and risk dial.
## Autotrade
Deploying a strategy version to selected accounts so it trades for you (coming soon). It will pass the same checks as manual trading and have no special powers.
## Breach Guard
The protection that acts before a firm limit is hit. At the safety margin it blocks new entries, flattens if needed and pages you. You cannot turn Breach Guard off from the app.
## Circuit breaker
Coming soon. A daily loss limit in R per account, plus a global pause. When it trips, new entries will stop.
## Compliance
Pre-trade enforcement of a firm's Rules & Limits, plus the history of any breaches.
## Expectancy
What a strategy makes per trade on average, in R. It is the only profitability number TradeSurge uses.
## Firm
A prop firm and its rules. The Firm Catalogue holds every firm we track.
## Kill switch
One action that flattens every position on every account. It works from the web Terminal.
## Phase
Where an account is in a firm's programme: evaluation (phase 1 or 2) or funded.
## Profit target
In evaluation, the firm's target to pass. In funded, a goal you set before the next withdrawal.
## Promotion ladder
The steps an automated strategy will climb before trading full size: demo, then micro, then normal (coming soon). Each step has its own size ceiling.
## R
The amount you risk on one trade. A +2R trade made twice what it risked.
## Risk dial
The per-account setting for risk per trade. The engine sizes every trade within it.
## Rules & Limits
A firm's daily drawdown, maximum drawdown, profit target and daily reset for one account.
## Strategy
Code you upload, in Python or Pine Script, that produces trade signals.
## Surface
A place you control TradeSurge from. The web app and Telegram both talk to one engine. Trading from Telegram is coming soon.
## Surge score
A 0 to 100 score built from expectancy in R and consistency. Win rate cannot move it. In beta.
## Terminal
The screen for trading by hand. One order is copied to every selected account with per-account sizing.
## Trade-scoped key
A venue key with read and trade permission, and withdrawals and transfers disabled.
## Trading day
A distinct day with at least one trade. Firms often require a minimum before a payout.
## Venue
Where an account lives, such as Bybit, MetaTrader 5 or MatchTrader.
## Next steps
---
# 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.tradesurge.co/concepts-and-reference/glossary.md?ask=&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.