Execution quality and fill feedback
Execution outcomes and fills are the source of truth for order lifecycle; WS method responses are at best ACKs. Publicly you see aggregated quality (status mix, fill side, latency), not order-level tuning.
Core definitions
Route-state
The current aggregated decision context where routes are evaluated on viability, timing, and risk suitability.
Timing-aware ranking
Route prioritization based on time sensitivity, data freshness, and execution viability, not on isolated signals.
Explainability
Public cause/effect explanation of why routes win or are rejected (why-no-trade, route wins, reject reasons).
Interpretation for operators and visitors
- Orders/fills are persisted on the decision pool; never blindly join with ingest-only tables.
- Read fill quality as operational measurement toward route evaluation, not as a signal to copy the strategy.
- See `04_EXECUTION_ORDERS` and `05_PROTECTION_EXIT` for lifecycle and position protection.
← Knowledge · Dashboard · SPEC · Docs · FAQ