01 / HARDCODED
Numbers that never move
- Tickers and P&L pasted in as static text at build time.
- Here: no hardcoded prices. If the feed dies, the panel says so and shows nothing.
Real bars in. One published rule set. A sized position out, and a governed agent to run it. Every figure here was computed when the page loaded — including the unflattering ones.
LIVE NOW
computing from live bars…
Three habits that look credible and tell you nothing. Each one is avoidable, and the avoidance is checkable in the code.
01 / HARDCODED
02 / UNGOVERNED
The signal card and every agent call the same evaluate(). It
sees bars up to i, never i+1 — the whole reason the record means
anything.
What you research is what gets scored, what gets sized, and what an agent may trade.
Search any listed symbol, pull real bars across eight ranges, read realised volatility and ATR as a percentage of price.
The rule set scores the latest bar and shows its four components and four cited reasons, not a bare number.
Size against your buying power and risk percent, then send the order to the connected venue with its stop and target attached.
Hand the same rules to an agent with a capital cap, a notional cap and a daily loss limit it cannot exceed.
running the history…
running the rules against live bars…
These lines are produced by the same code path a deployed agent runs, against live bars, at page load. Not a sample — reload and they change with the market.
A symbol, a parameter set, three hard numbers. Every sixty seconds it acts, or writes down why it didn't. No path through the code produces an order exceeding its limits.
Not a recording. The same calls the app makes, against the same endpoints, printing what comes back — errors included. Try quote BTCUSDT, signal ETHUSDT or health.
GET /api/quote?symbols= live prices
GET /api/bars?symbol=&range= real OHLCV
GET /api/signal?symbol= score, levels, sizing
POST /api/order routed to the configured broker
POST /api/agents a governed agent