Community · E2 · artifact verified
Run a live crypto desk with Jev as the brain
A multi-bot OKX trading desk with Jev as the brain and code as the body: each tick reads market and account state, computes features in TypeScript, asks Jev typed questions, then holds or places and cancels real orders - dashboard as the glass.
01 · Role in the system
What Jev does here
Each tick follows the same split. Code computes the features - indicators, positions, exposure - as facts, and Jev answers typed questions over them: whether the setup justifies an entry, whether an open order still makes sense. The calibrated answers route to deterministic execution: hold, place, or cancel on the OKX API, with transport and client behavior covered by their own test suites. The desk runs multiple bots, and the dashboard renders what the brain decided and why. Unlike paper-trading experiments, the orders here are real exchange calls, which is why every judgment passes through typed questions and the body never acts on free text.
Real orders, typed questions, no free text in the loop
This desk is where the cluster's pattern meets real stakes: each tick computes features in TypeScript — indicators, positions, exposure — as facts, Jev answers typed questions over them, whether the setup justifies an entry and whether an open order still makes sense, and the calibrated answers route to deterministic hold, place, or cancel calls on the OKX API. The body never acts on free text, which at real-money scale stops being a stylistic preference.
Multiple bots share the split, transport and client behavior carry their own test suites, and the dashboard renders what the brain decided and why — the audit trail is the product's glass, not an afterthought.
Live risk with no track record to inspect
The limitations are the sharpest in the index and deserve to be read first: live orders mean live risk, the desk is single-operator and unaudited, there are no published drawdown statistics or track record, and crypto markets move faster than the tick loop on volatility spikes — a structural latency the typed-question design cannot remove.
The record's value is architectural honesty at the highest-stakes end of the directory: it demonstrates the full brain-and-body pattern under real exchange conditions while refusing to claim performance. Anyone replicating it inherits the safety shape — typed gates, deterministic execution, visible decisions — without inheriting any illusions about returns.
02 · Control boundary
Where Jev sits
Jev as the decision brain of a live trading desk: TypeScript features become facts, typed questions decide hold versus place or cancel, deterministic code executes on the exchange API, and a dashboard exposes each call.
Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.
03 · Known limits
What this evidence does not prove
- Live orders mean live risk; the desk is single-operator and unaudited.
- Crypto markets move faster than the tick loop on volatility spikes.
- 0 stars; no published track record or drawdown statistics.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- AtticusG3 ↗Community · github · public · checked 2026-10-04