Back to Developer Letters
February 16, 2026roadmaprisk-evolutionmobile-companion

Roadmap Note: Risk Evolution and Mobile Boundary

Why we split web and mobile scope, and how Risk Evolution becomes a core module.

Why this split matters

The web product is the research surface. Mobile is a companion for monitoring and alerts. Without this boundary, teams tend to duplicate heavy analysis screens in both places and slow down.

Current boundary

  • Web: deep analytics, overlap breakdown, exposure explorer, risk evolution.
  • Mobile: read-only status, alerts, weekly digest, quick benchmark context.

What shipped recently

  • Risk Evolution v1 screen.
  • Overlap snapshot scaling tables.
  • Initial lifecycle tables for instruments/listings/corporate actions.

Next execution steps

  1. Add more attribution drivers inside Risk Evolution.
  2. Harden corporate action ingestion paths.
  3. Keep mobile focused on signal quality, not chart density.
Roadmap Note: Risk Evolution and Mobile Boundary | Developer Letters | Portwise | Portwise