Sequencing
Roadmap
P0 to P3, in the order the specification puts them. Everything before LAUNCH is load-bearing; P3 does not block the launch.
-
P0
Foundation
Database schema. The TradingView webhook endpoint. Signal persistence with the raw payload preserved. Multi-timeframe state per asset, strategy and timeframe. Nothing can be built before signals arrive and survive a restart.
-
P1
The page people see
Homepage, market data ingestion and normalisation, and signal history. The first point at which the product is worth showing anyone.
-
P2
Derivatives
Server-side perp venue integration, funding, open interest and the rule-based perp interpretation — moving the direct browser calls in this preview behind one cached, rate-limited API, and adding the liquidation feed, which needs authenticated venue access. This is the part that explains a move rather than just reporting it.
-
LAUNCH
V0.1 ships
Everything above, working, honest about what it is.
-
P3
After launch
Shareable signal cards. A Telegram channel. Confluence alerts when multiple timeframes agree. Performance analytics. And CATSCAN, the contract-risk screen — previewed in the terminal today, and always labelled
[PREVIEW — NOT IN V1.0].
P3 does not block launch. Anything a command surfaces from beyond V1.0 is labelled in the output itself.
Not in V1.0 — explicitly out of scope, by specification
This list is part of the product, not an admission. A signal display that cannot touch your funds has a much smaller blast radius than one that can, and saying so plainly is the point.
- wallet connection
- automatic trading
- custody
- copy trading
- user accounts
- paid subscriptions
- portfolio tracking
- custom user indicators
- AI trading agent
- strategy marketplace
- backtesting UI
- multi-token support
- proprietary charting engine
- mobile app
- social feed