> 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/order-safety.md).
# How order safety works
Every order passes the same safety checks, whether you place it by hand or a strategy does.
Every order in TradeSurge passes the same layered checks before it reaches the venue. Manual trades and automated trades use the same path, and automation gets no special powers. This page explains each layer and what it protects.
## An entry never fires from one tap
Every new entry shows a confirm card first. The card expires after a short time and ignores double taps. Reduce-only actions (close, flatten and the kill switch) can be single tap.
## Every entry carries a resting stop
Your stop is placed on the exchange with the entry. Your protection survives even if TradeSurge goes down mid-trade.
## Hard caps sit above your settings
| Name | What it means |
| -------------------------- | ------------------------------------------------ |
| **Per-order notional cap** | The largest single order allowed. |
| **Daily notional cap** | The most you can trade in one day. |
| **Max open positions** | How many positions can be open at once. |
| **Max leverage** | The highest leverage an order can use. |
| **Risk dial** | Your risk per trade, the ceiling for every size. |
## Pre-send checks
Before an order is sent, TradeSurge checks the instrument's tick and step size and that margin stays at or below 95% of equity. Market orders are checked against the top of the book before sending. Fills can still slip. A failed check rejects the order with a reason.
## Circuit breakers (coming soon)
Each account will have a daily loss limit in R. When it is hit, new entries will stop for the day. A global breaker will be able to pause everything at once.
## Exits are never blocked
Close, flatten and the kill switch always go through as reduce-only orders. No check can veto a trade that lowers your risk.
## Every step is on the record
Every command shows its outcome: executed, failed or expired, with a reason. Every step is written to an audit log. No AI output can reach the order path.
## 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/order-safety.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.