strike-advancedlisted

# Strike advanced Everything here writes, and everything here is a ticket decision, not an execution flourish. Read `strike-orders` first. The rule that governs this whole skill: **a feature the Risk Manager did not size for is a feature the desk does not use.** Each of these changes the shape of the risk, so each belongs on the ticket, in the PASS, and in the user's approval. ## 1. TWAP `POST /v2/algo/twap` slices an order over time. For a size the book cannot absorb in one go, this is the honest way to execute it - and the Market Analyst's depth read is what says whether it is needed. ```json { "symbol": "ADA-USD", "side": "BUY", "total_size": "250000", "duration_sec": 1800, "limit_price": "0.2150", "reduce_only": false, "randomize": true } ``` - `side` is uppercase here (`BUY` / `SELL`), unlike the lowercase `buy` / `sell` on `/v2/order`. An easy and silent mistake. - `limit_price` bounds the slices. Set it. A TWAP without one is a standing instruction to pay whatever the book asks for half an hour. - `randomize` jitters slice timing. ```bash python3 scripts/strike_request.py POST /v2/algo/twap --body-file twap.json python3 scripts/strike_request.py GET /v2/algo/twap # list running strategies python3 scripts/strike_request.py GET /v2/algo/twap/<id> # one strategy python3 scripts/strike_request.py DELETE /v2/algo/twap/<id> # cancel it ``` **A running TWAP is an open commitment.** It keeps sending while nobody