Koda
Execution guidance — entry style, order type, slippage estimate, and notes for every trade signal.
What Koda Does
Brix has approved a per-user trade signal. Now you need to know how to enter. Market order or limit? One shot or laddered levels? What slippage to expect?
Koda wraps each Brix-approved signal with execution guidance and publishes it as a notification you (or the auto-execution layer) can act on. It's the last agent in the chain before the trading engine.
What Koda Produces
For each signal, Koda generates:
| Field | What it is |
|---|---|
| Entry style | sniper (single precise limit), ladder (split across 2–3 levels), or market (fill now) |
| Order type | Market or limit, derived from entry style |
| Slippage estimate | Heuristic, ~0.05% to 0.25% range |
| Notes | 3–6 bullets of human-readable guidance: level placement, stop/target reminders, sizing notes |
How entry style is chosen
| Conditions | Style |
|---|---|
| High confidence, small size | Sniper — precise limit at the entry level |
| Moderate confidence, larger size, or first trade | Ladder — split across levels around the target |
| Beginner with strong signal | Market — keep it simple, fill it now |
The choice is deterministic. Same inputs, same style, every time.
What Koda Does Not Do
Koda generates the plan for entering a trade. It does not place orders itself. Specifically:
- Exchange selection happens upstream in Brix, not Koda
- Koda does not place orders — the trading engine handles actual execution
- Slippage estimates are heuristic, not live order-book queries — the trading engine handles real depth at execution time
User Chat
Koda also responds to questions about execution: "Should I enter now or wait?" "What's the slippage on this size?" "Why did you suggest a ladder?" It pulls the same execution context to ground its answers.
Configuration
| Setting | Options | Default |
|---|---|---|
| Entry style preference | Sniper / Ladder / Market | Ladder |
| Aggression | Passive / Balanced / Aggressive | Balanced |
Under the Hood
Type: execution agent. No candle subscription, no team chat. Purely event-driven on per-user signals.
Input: listens for Brix-approved per-user signals via the event bus.
Output: publishes an execution-ready notification per user.
Execution context: a pure-logic builder selects entry style from confidence, trader level, and notional size. Slippage is estimated heuristically, not from a live depth query.
Downstream: the trading engine picks up the notification and runs an execution workflow via the configured exchange adapter.