JEV Trading Command Center
Research simulated trades with typed Jev decisions, bounded execution receipts and a visual command center.
Added to Jevfast
How it uses Jev
Jev makes a final Choice between executing one bound candidate plan and waiting. The state includes market evidence, six-model analysis, account data and risk checks. Code validates the response and creates an expiring, single-use receipt; risk checks can still veto execution, and PaperBroker simulates the order.
What Jev decides
Source-defined routing example (illustrative)Example answers · not a recorded Jev response · Source ↗
Question 1 · final decision
YOUR APP
INSTRUCTION
Execute only the bound candidate plan, or wait. Do not invent a different plan.
STATE
Representative repository-owned test plan: make_plan sequence 1 creates PLAN-0001 for a BTCUSDT long setup. Production state also includes the decision snapshot, candidate plan, market evidence, advisory votes, account and risk precheck. The resulting options are EXEC_PLAN-0001 and WAIT. No live market values or response is claimed.
JEV · CHOICE
- EXEC_PLAN-0001
- WAIT
App workflow
- Prepare evidence
The scanner builds a candidate plan and obtains advisory analysis; those votes cannot authorize an order.
- Ask for the final choice
The worker sends the bound plan, market snapshot, account and risk evidence to Jev.
- Validate and simulate
The application validates probabilities and the receipt, rechecks risk and uses PaperBroker for simulated execution.
Why it is interesting
The integration separates advisory model votes from the final typed decision and deterministic risk vetoes. Its public interface videos use synthetic demo data, so they show the application rather than measured trading performance.