mmflow Charts
Capability status
A launch-readiness matrix for what mmflow Charts and Data currently ship. This page is about mmflow capability status, not competitor claims.
SDK package surface
Five npm packages are prepared for RC review with package dry-run, examples, export audits, and release checks.
Data quality
History and replay surfaces report source, coverage, freshness, partial, stale, and unavailable states.
Replay stack
Replay supports candles, events, trades, footprint bars, and sparse orderbook snapshots over bounded windows.
Measured performance
The benchmark route measures this browser/session; public claims should be based on reproduced runs.
What currently ships
Statuses are intentionally conservative: Shipped means available in the app/docs today, RC-ready means package release review is prepared, Bounded means coverage is honest but intentionally limited, Docs-only means documentation exists without a new runtime surface, and Planned means outside this release-candidate scope.
Package publishing is prepared for RC review but not performed by this PR.
Examples use intended public package names and local workspace packages until registry publish.
Consumers own their feed freshness, normalization, and subscription lifecycle.
Anonymous and keyed quotas apply; source availability is surfaced through status metadata.
ChartScript is intentionally constrained to safe formula-style indicators.
No cloud drawing persistence is included in this release-candidate scope.
Replay export is a config manifest, not a market-data export.
Archive/source coverage can be archive, source, mixed, partial, unavailable, or stale.
Recent trade retention limits apply; this is not a full historical tick warehouse.
Sparse snapshots only; no full L2 delta reconstruction or tick-perfect book replay.
Status checks are cheap probes, not persisted incident management or complete monitoring.
Launch-readiness caveats
Phase 19 does not publish packages, create tags, deploy production infrastructure, add cloud replay sessions, add billing/auth, add trading execution, or add a full market-data warehouse. The bounded history and replay APIs remain honest about archive, source, mixed, partial, stale, and unavailable states.