SPEC: KapitaalBot Runtime
Deze pagina is de canonieke publieke technische specificatie van KapitaalBot. De focus ligt op systeemgedrag, operationele architectuur en latency-eisen. Broncode, gevoelige tuningwaarden en private accountdetails blijven bewust buiten scope.
1) Gebruikte techniek / stack
| Component | Spec | Public note |
|---|---|---|
| Language | Rust | Core runtime and execution logic |
| Databases | PostgreSQL | Role-separated data paths (ingest / decision / research where applicable) |
| OS / Runtime | Linux (Ubuntu class) | Service-oriented runtime on dedicated host(s) |
| Process control | systemd services | Deterministic startup/restart and health supervision |
| Exchange integration | WebSocket-first | Live market + execution channels, snapshot/export driven website |
| Observability export | Read-model JSON snapshots | Public and tiered observability without direct DB exposure |
2) Runtime / architecture specs
KapitaalBot werkt als timing-aware, multistrategy route-selection engine met live route-state, regime-routering, position-context, execution choke en feedbackgedreven explainability.
spec.runtime.diagram.desc
3) Latency specification
Onderstaand overzicht maakt expliciet onderscheid tussen latency-targets, geobserveerde ranges en vertraagde/background-paden.
| Tier / Path | Target latency | Observed latency | Why it matters |
|---|---|---|---|
| Hot path (ranking → choke → submit) | Sub-second class | Runtime-dependent, monitored continuously | Direct impact on execution viability and stale-decision risk |
| Warm path (route-state refresh, explainability updates) | Seconds class | Low-seconds class under normal load | Controls decision freshness and interpretability |
| Tier 1 public observability | Delayed by design | Delayed snapshots | Prevents real-time strategy leakage while preserving transparency |
| Tier 2 analytical observability | Near-operational delay | Snapshot cadence dependent | Supports deep diagnostics without exposing account-sensitive internals |
| Tier 3/admin and private operator paths | Operationally immediate | Internal-only | Used for sensitive account/runtime control and forensic analysis |
4) Public safety boundary
- WEL: functionele werking, architectuur, beslislogica op hoog niveau, outcomes, explainability.
- NIET: broncode, exacte private thresholds, gevoelige allocator/sizing details, accountspecifieke data.