QData. Dashboard Roadmap
Currently shipping (as of M7 close)
- Home page with system status strip, recent events feed, modality bar, and thread tracker
- Events explorer with multi-axis filtering at
/events - Per-event detail pages with sources, related events, entity rails
- Company, people, and investor index and detail pages
- Capital flow visualization with four charts at
/capital - Newsletter archive with rendered and raw views
- System status page at
/status - Source health, citations index, tags index, and modality timeline at
/sources,/citations,/tags,/modalities - Open threads tracker at
/threads - Full insider data at
/insiderwith pure-play and parent-company toggle - Methodology and roadmap at
/methodology,/roadmap - Full-text search at
⌘K(Pagefind 1.5.2, post-build static index) - Corrections audit log at
/corrections - RSS feeds for newsletters at
/feed.xml,/newsletters/daily/feed.xml,/newsletters/weekly/feed.xml - JSON API at
/api/events.json,/api/companies.json,/api/people.json,/api/investors.json,/api/citations.json - Custom domain at
quantum-data.comwith GitHub Pages deployment
Phase 1 institutional rigor
Spec-evolution enforcement runs on the routine side as a pre-Step-7 corpus shape check (dashboard/scripts/validate-corpus.ts). The script validates every committed daily/*.json, weekly/*.json, master list, state file, and last_run record against the Zod schemas in dashboard/src/lib/schemas/. Routine commits that produce shapes the dashboard cannot consume fail before they reach main, closing the four-incident drift window observed across W17–W19.
Phase 2 (post-day-90 backtest)
After the 90-day calibration backtest completes (anchor date 2026-04-25, gate around 2026-07-24), score-aggregating analytics views unlock:
- Score distribution histograms
- Momentum index visualization
- Predictive validity tracking
- Calibration drift over time
The current dashboard explicitly avoids these views to prevent shipping analytics built against a calibration that may shift.
Phase 3 (post-MVP)
- Authentication and access tiers
- Paywall integration for RSS / JSON API consumers
- Subscriber management
- Comments and discussion features
Deferred syndication surfaces
- Events RSS feed — per A.2, RSS is the newsletter syndication surface; the events stream is the JSON API. An events RSS feed (one item per published event) is deferred to post-day-90 when calibration-shift risk is bounded.
- Operational JSON endpoints — per A.3 (a), the MVP API ships five derived surfaces (events, four entity master lists, citations). State snapshots, insider transaction streams, and rejection logs are operational artifacts; their endpoints are deferred until a downstream consumer requests them.
Out of MVP
- Real-time updates — static rebuild on commit covers the cadence.
- Interactive event editing — corrections flow through the spec §13 mechanism (new event with
type: "correction"andsupersedes_event_id). - Newsletter editing — newsletters are immutable published artifacts.
Day-90 backtest progress
Live counter visible at /status. The backtest validates that the scoring rubric is internally consistent before Phase 2 analytics views ship.