malkhut(docs): OrderType integration status documented
README updated with: - Integration Status section for OrderType - state.py: 17 values, backward compatible - order_types.py: standalone standardized taxonomy - ExchangeProfile.available_order_types per venue - CWM transition: passes action.order_type to venue adapter - Agent/adversary: check is_type_available before placing
This commit is contained in:
@@ -1231,6 +1231,15 @@ but semantics are identical. A `LIMIT` on BingX = `LIMIT` on Binance = `LIMIT` o
|
|||||||
(same fill behavior). Only the API string differs. The venue adapter translates
|
(same fill behavior). Only the API string differs. The venue adapter translates
|
||||||
normalized → exchange-native at submission time.
|
normalized → exchange-native at submission time.
|
||||||
|
|
||||||
|
#### Integration Status
|
||||||
|
|
||||||
|
- `state.py` OrderType: **17 values** (5-layer taxonomy, backward compatible)
|
||||||
|
- `order_types.py`: **Standalone standardized taxonomy** with exchange mapping tables
|
||||||
|
- `ExchangeProfile.available_order_types`: per-venue list of supported normalized types
|
||||||
|
- `action_menu.py`: uses `OrderType.MARKET`, `OrderType.LIMIT`, `OrderType.POST_ONLY`
|
||||||
|
- CWM transition: passes `action.order_type` to venue adapter
|
||||||
|
- Agent/adversary code: check `is_type_available(type, exchange)` before placing
|
||||||
|
|
||||||
#### Standards Referenced
|
#### Standards Referenced
|
||||||
|
|
||||||
- FIX 4.4: Tag 40 (OrdType), Tag 59 (TimeInForce), Tag 18 (ExecInst)
|
- FIX 4.4: Tag 40 (OrdType), Tag 59 (TimeInForce), Tag 18 (ExecInst)
|
||||||
|
|||||||
Reference in New Issue
Block a user