50-event ring buffer
Recent activity is held in a per-tab ring buffer; navigating away and back replays without re-fetching.
Capability · Application surface
The RCM application.
Forty-two operator surfaces across three console roles — tenant admin, platform operator, and EDI operator. Every action a back-office engineer would have done in the legacy system is here, as a UI surface with audit, scope, and a draft/publish lifecycle.
The surface inventory
38 operator surfaces.
Grouped by role. The tenant operator (customer-side billing leadership), the platform operator (the team running the platform), and the EDI operator (the people running the X12 plumbing) each have their own console — gated by a separate JWT scope and a separate auth flow.
Inside-the-tenant configuration. Every customer-side ops, billing, and compliance workflow has a UI here.
Select a surface on the left to inspect what it configures.
Real-time, not poll
The application is event-driven by default.
The legacy model is polling — refresh, query, refresh, query. The new platform streams events to the browser via Server-Sent Events. Every meaningful change in the system pushes to subscribed clients within ~1 second.
Unread counter + toast routing
Unread counters per surface; toast routing by severity. The ops team sees what changed, when, and what it affected.
1s → 30s exponential reconnect
The SSE stream reconnects with exponential backoff on transient network failure — no thundering herd, no infinite spinner.
Everything an analyst would have asked back-office engineers to do in the legacy system is here.
Keep going