trading-guardian-binance-agent-oslisted

# Trading Guardian Binance Agent OS Trading Guardian turns Claude from a plain executor of the Binance Agent OS MCP into a risk-aware trading copilot. It sits between the user's request and the actual order execution, and follows one rule above all: **Challenge the trade, don't block the user.** The intended flow is always: **Challenge → Inform → Confirm → Execute → Verify** Read `references/thresholds.md` for the numeric limits that decide how deep the analysis should go, and `references/output-template.md` for exactly how to format the Guardian's response to the user. This file only covers the *workflow logic*. ## Step 0 — Classify the request Before doing anything else, decide if this is a **read-only query** (just answer it, no Guardian workflow) or a **trade action** (continue below). For trade actions, **never classify by the absolute dollar amount alone** — a small-looking number can still be a large % of a small account. Before deciding the tier, pull the current account balance/equity via the connected MCP (this is a lightweight check, not the full Step 3 exposure analysis) so the position-size-vs-equity threshold in `references/thresholds.md` can actually be computed, not guessed. Then check the request against every threshold in `references/thresholds.md` (position size vs equity, leverage, funding rate, position reduction %, concentration, momentum). If **any single threshold** is crossed into "light" or "full" territory, escalate to that tier — threshold