What we're building

## Problem On a shared machine (multi-user Windows install, family gaming PC), the tray can silently inherit a previously-paired session into a different OS user's context. The same problem exists wh

## Problem Parsed log entries today don't record which RSI channel (LIVE / PTU / EPTU / Tech-Preview) or build number they came from. Cross-patch analytics ("my K/D over the last three LIVE patches")

## Problem StarStats currently can't reliably detect when Star Citizen is running, and has no concept of session length, kill/death counts, or mission completions. Any approach that touches game memo

## Problem The org-side surface is today a thin member-list — there's no role model, no per-class sharing controls at the org level, no member detail page, no live location map, no admin tooling to s

## Problem Users who livestream or screen-share Star Citizen sessions risk leaking their StarStats live-sharing surfaces — open transactions, current location, fleet inventory — to the stream audienc

## Problem Users link their RSI profile and arrive at a StarStats account with no associated org record, even though their RSI profile names a primary public org. There's no concept of "this org exis

## Problem Individual users see their own deaths and kills, but there's no way to infer killer ↔ victim pairings across the user base — and a naive approach would leak identifying info about who kill

## Problem The tray and web companion currently authenticate independently, and there is no first-class concept of "the same user on two machines". A user who runs the tray on a desktop and a laptop

## Problem Today's notification mechanisms are ad-hoc — roadmap subscriber updates, org events, and sharing notices each ship through their own surface, with no unified inbox, no cross-surface mute,

## Problem The tray Settings → Sync indicator reports the device as disconnected / sync as not working, but the device is in fact paired and actively pushing events to the server. The component's sta