Monstra Heartbeat
Monstra runs live trading algorithms end to end: market data in, vectors computed, a tradable universe built, algorithms scored, signals produced, and performance measured — all shown here as it actually runs.
This page follows one path through the system, left to right: market data, vector computation, universe construction, algorithm evaluation, signal, and measurement. Every number here is either queried live or explicitly marked as not yet instrumented — nothing is invented. Click a stage below to jump to it.
The first stage: prices in
Everything downstream depends on this landing first. This is the same real timestamp the "Market data" pip in the strip above tracks — not a separate query.
Live vector refresh output
This feed reflects the real trading.Vector refresh wave, so this section shows the market-data pipeline actually computing features.
What each vector actually means
Six decimals per stock, defined precisely rather than left as bare numbers.
Momentum
Absolute price momentum across multiple horizons — higher means the stock has been going up, on its own terms, not relative to the market.
- Formula
- Weighted blend of 1m/3m/6m/1y returns (20/20/15/10%) plus momentum acceleration (1m-vs-3m, 3m-vs-6m) and 3-month trend slope, each min-max normalized to a fixed range (e.g. 1m return clamped to [-30%, +30%]).
From listed symbols to today's holdings
This funnel runs at two different scales, shown as two blocks below. The top block starts from a manually-rebuilt research-universe snapshot (as of 2026-08-13: 200 symbols listed) — a different, and currently much smaller, pool than the 7,129 live-safe tickers and 6,903vector-covered tickers the Vectors section above tracks continuously. Past the "scale shift" divider, the bottom block drops to a third scale: only the five showcased bots' own curated universes. These numbers are not meant to reconcile with each other — they measure different pools by design.
Each row is what survived the previous one. A row marked "No change" shows the same count as the row above it, with its reason shown inline rather than hidden behind a click. Rows with sample tickers can still be expanded for the exact rule and what it dropped.
Pass liquidity gate33
Five strategies, side by side
Same axes on every card — factor exposure is the weighted average of each bot's own current holdings' vector scores, not a declared target.
Momentum rotation within a fixed, theme-based universe — ranks names by trailing momentum and holds the top tier, with a benchmark filter and kill switch.
Latest signals by bot
Every row stays traceable by trading date, session, and run id.
Does it work, and how would we know
Each bot's equity, indexed to 100 at t0, against VOO on the same axis. Drawdown shares the x-axis beneath. Sample-size caveats are shown, not buried.
What this page doesn't claim
The thesis of this page is that an honest gap reads as competence, not as a failure. Everything below is real, current, and unresolved as of this writing.
Each bot's Measurement card carries its own source label (Live Trading, Paper, Backfill, or Mixed), taken directly from the stored performance source on each equity row — not inferred. A backfilled segment is a historical simulation, not a live track record.
The research universe (Universe construction, above) uses current-day listings and current fundamentals, not historical constituents. It is not survivorship-bias-free and there is no enforced lag between data availability and its use in a signal. This is stated plainly there, not buried here.
- Current wave progress meter — the vector refresh scheduler tracks per-ticker cadence but doesn't expose an in-flight percentage.
- Universe churn — the snapshot table this needs doesn't exist in this database yet; nothing has been frozen to diff.
- Gross-vs-net-of-costs on live segments — live equity already reflects real fills, but isn't separately decomposed into gross and assumed-cost components.
- A true "delisted" exclusion reason — the closest real signal is unsupported-exchange/security-type, which is a proxy, not a direct delisting flag.
Scheduling the universe rebuild and snapshot-freeze on a cadence, instead of by hand, would fix two things at once: the funnel and coverage numbers above would stop lagging (currently weeks old), and universe churn would go from unpopulated to real. That's the single highest-leverage gap on this page.