> ## Documentation Index
> Fetch the complete documentation index at: https://docs.polychads.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Trading

> Order ticket behavior, checks, and execution expectations.

Trading happens from the market page. The order ticket should stay close to the chart, orderbook, positions, activity, and related context so the trader does not make a decision from a detached modal.

## Preflight checks

The terminal checks the trade path before submission.

* market status and outcome availability
* selected wallet and account session
* balance and minimum order constraints
* token-level neg-risk and tick-size context
* allowance or approval state where needed
* upstream order route and retry handling

## Order ticket rules

| Rule                 | Behavior                                                                            |
| -------------------- | ----------------------------------------------------------------------------------- |
| Minimum size         | The ticket should explain disabled actions with plain copy.                         |
| Market order default | Quick Buy contexts should default to market order behavior.                         |
| Resolved market      | The ticket should show a closed-state panel, not active order controls.             |
| Balance refresh      | Cash and wallet balances should refresh after confirmed funding or transfer events. |

## Responsibility

The terminal is execution tooling. It does not provide investment, legal, or tax advice. Traders are responsible for order decisions, position sizing, and jurisdictional compliance.