The honest state of the build
Financial software has a bad habit of describing plans in the present tense. This page exists so you can tell the difference. Anything not in the first column is not something you can use yet.
Running in production
Deployed to the Quantivo development environment and verified end to end.
- AWS environment on ECS Fargate with PostgreSQL 17 and a Valkey cache, private networking, and immutable image deploys
- Private owner authentication with secure cookie sessions, super-admin enforcement, and a route guard that blocks any pre-session data request
- Point-in-time S&P 500 universe with sourced membership history and effective-dated snapshots
- Bitemporal instrument master covering venues, listings, aliases, and typed instrument relationships
- Truth statement persistence with nine PostgreSQL triggers enforcing append-only lineage
- One-time historical statement importer with two-phase audit and full manifest verification
- Data lineage API with input manifests, content hashing, and authenticated access logging
- Deterministic technical-analysis engine with unit-tested indicator math
Being built right now
Active development with tickets open and code in review.
- Checkpointed live ingestion of public Truth Social statements so posts land within seconds
- Market-data vendor selection, licensing, and exchange entitlements — the gate for live prices
- Entity resolution mapping statement references onto instruments, sectors, and proxies
- Statement exposure graph covering direct, sector, macro, and proxy relationships
- Alert rule evaluation against freshness-checked data, with cooldowns and delivery audit
- Market-calendar-aware outcome measurement so every claim gets scored
Planned, not started
Specified and prioritised, but no implementation yet. The site will keep saying so.
- Options chain intelligence, IV rank, and the long-call contract optimizer
- Backtest reality models for fills, costs, liquidity, and options lifecycle
- Walk-forward and out-of-sample validation with statistical overfit controls
- Portfolio DNA: structured onboarding, behavioural layers, and expectancy coaching
- Governed alternative-data connectors with licensed collection and deduplication
- Billing, subscription tiers, and multi-tenant customer workspaces
- Production Kubernetes environment promoted from the development stack
The one thing blocking most of it
Almost everything in the second and third columns depends on licensed market data. Prices, options chains, and fundamentals all require vendor agreements and exchange entitlements, and the terms materially change what can be shown, stored, exported, and redistributed. That decision is being worked through deliberately rather than quickly, because getting it wrong means rebuilding the data layer later.
Until it lands, every module that needs market data will keep reporting unavailable rather than showing you a plausible-looking number that came from a fixture.