What is KapitaalBot?
KapitaalBot is not a plain-vanilla momentum, breakout, or scalping bot. It is a timing-aware, multistrategy, multiregime execution engine that judges, for each market, horizon, and route, what is responsible, explainable, and economically tradable at that moment.
The core is not one indicator, one playbook, or one favourite coin. The core is a live selection process that lines up multiple candidate routes, tests them for data freshness, tradability, regime, safety, and execution context, and only admits routes that are genuinely executable under current conditions.
Canonical definition
KapitaalBot is a route-selection and execution engine with the following properties:
Timing-aware selection
KapitaalBot does not only ask whether a market is interesting, but when a route is viable within a concrete horizon. Time is not an afterthought; it is a first-class part of selection.
Multistrategy
The system is not built around a single strategy. Different route families and entry logic can coexist, provided each honours its own economic and operational constraints.
Multiregime
Not every market should be read the same way. KapitaalBot accounts for regime differences and is meant to adapt route choice instead of forcing every symbol through one generic filter stack.
Execution-first truth
Operational truth does not live in a research snapshot or a static dashboard, but in live execution state, the current market-data layer, valid universe/epoch context, and the actual execution blockers.
Explainability by design
KapitaalBot must be able to say not only why a trade was taken, but especially why a trade was not taken. That includes:
- why-no-trade
- first blocker
- blocker chain
- route wins
- reject reasons
- dominant execution constraint
Safety and position context as constraints
KapitaalBot is not designed to trade at any cost. Positioning, exposure, data quality, market freshness, and execution safety come before opportunism. Not trading beats trading on bad or inconsistent truth.
What KapitaalBot is in practice
KapitaalBot is a system that tries to determine:
- which symbols are actually tradable right now
- which horizons currently show meaningful movement
- which route makes sense in that context
- which blocker stops a candidate
- whether execution is still economically and operationally justified
- and how all of that can be explained for operators and forensics
So KapitaalBot is not a “coin picker”, but a live decision layer between market data and execution.
What KapitaalBot explicitly is not
Not a single-strategy indicator bot
KapitaalBot should not rely on one generic edge formula or one fixed setup rolled out unchanged across every market.
Not a symbol-first or feed-first dashboard model
A dashboard is observability, not the source of truth. Truth should come from the live runtime, execution state, and valid market-data context.
Not a research snapshot as trading SSOT
Research, backtests, and edgeboard-style layers can help calibration and analysis, but not as the dominant live selector truth.
Not a black-box signal machine
A candidate without a clear account of why it wins or loses does not fit KapitaalBot’s design intent.
Not investment advice or a signal service
KapitaalBot is an internal trading system and observability/execution framework, not a public advisory product.
Where KapitaalBot is heading
KapitaalBot is evolving toward a foundation in which:
- live hot state drives selection
- horizons are measured explicitly
- tradability is first-class
- route-specific economics is applied only after the right context
- explainability is standard, not optional
- and cold start / fast start stay responsible without structurally blinding the rest of the market
In other words: KapitaalBot is moving from a collection of loose decision layers toward a coherent, production-grade selector and execution base.
How this page fits the canon
This page states the core definition. For operational observability, use Dashboard. For stack and latency, use SPEC. For contractual detail, use Docs. For cause-and-effect questions, use FAQ.
Dashboard · SPEC · Documentation · FAQ · Knowledge