NewBeebots
Three paper-first trading bots use Jev Choice and Score decisions over compact market snapshots.
Added to Jevfast
NewHow it uses Jev
On each configured tick, each bee compacts market and bot state into a Jev request. A Choice selects an allowed strategy action and a Score expresses conviction; the engine applies its own risk checks before execution, with paper trading as the default.
What Jev decides
Illustrative bee decisionExample answers · not a recorded Jev response · Source ↗
Question 1 · action
YOUR APP
INSTRUCTION
Pick the next move from the strategy-generated menu.
STATE
Compact snapshot containing UTC time, bot identity and coin market/position rows. Available actions depend on strategy and snapshot.
JEV · CHOICE
- WAIT
- HOLD
- CUT_LOSS
- BREAKOUT_<COIN>
Question 2 · conviction
YOUR APP
INSTRUCTION
Score the strength of the signal.
STATE
Compact snapshot containing UTC time, bot identity and coin market/position rows. Available actions depend on strategy and snapshot.
JEV · SCORE
0
App workflow
- Tick and snapshot
The engine gathers the current market and bot state for three bees.
- Build action menu
Each bee strategy offers only currently allowed candidate actions.
- Ask Jev
Jev chooses an action and returns a conviction score for each bee.
- Check risk and execute
The engine may veto a choice; paper trading is the default execution mode.
Why it is interesting
The model only chooses from actions assembled by the current strategy and state, while a separate risk layer controls execution. This keeps a fast typed decision distinct from trading permissions.