Websocket-first runtime and dataflow
KapitaalBot processes data as long-lived WebSocket chains toward state and route decisions. REST is strictly limited (e.g. WebSockets token); trading and user data use WS v2.
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).
Reconnect behaviour
After reconnect: new auth token, resubscribe, snapshots where required (L2/L3), and reconcile from exchange truth (including the executions channel).
Interpretation for operators and visitors
- Note: raw market ingest and metrics live primarily on the ingest pool; execution, safety, and order truth live on the decision pool. Never attribute observability to the wrong database — see docs 01 (architecture) and 02 (ingest).
- Public observability shows the functional chain (freshness, counters, aggregates), not internal multiplex details or venue rate limits.
- See `01_ARCHITECTURE` and `02_DATA_INGEST` for processes ↔ DB pools.
← Knowledge · Dashboard · SPEC · Docs · FAQ