Back to Worldmonitor

Local backend parity matrix (desktop sidecar)

docs/local-backend-audit.md

2.5.234.3 KB
Original Source

Local backend parity matrix (desktop sidecar)

This matrix tracks desktop parity by mapping src/services/*.ts consumers to sebuf domain handlers and classifying each feature as:

  • Fully local: works from desktop sidecar without user credentials.
  • Requires user-provided API key: local endpoint exists, but capability depends on configured secrets.
  • Requires cloud fallback: sidecar exists, but operational behavior depends on a cloud relay path.

Architecture

All JSON API endpoints now use sebuf-generated handlers served through a single catch-all gateway (api/[[...path]].js). Handler implementations live in server/worldmonitor/{domain}/v1/. The desktop sidecar runs the same handler code locally via an esbuild-compiled bundle.

Remaining non-sebuf api/*.js files serve non-JSON content (RSS XML, HTML, redirects) and are not part of this matrix.

Priority closure order

  1. Priority 1 (core panels + map): LiveNewsPanel, MonitorPanel, StrategicRiskPanel, critical map layers.
  2. Priority 2 (intelligence continuity): summaries and market panel.
  3. Priority 3 (enhancements): enrichment and relay-dependent tracking extras.

Feature parity matrix

PriorityFeature / PanelService source(s)Sebuf domainHandler pathClassificationClosure status
P1LiveNewsPanelsrc/services/live-news.tsNon-sebuf (YouTube)api/youtube/live.jsFully local✅ Local endpoint available; channel-level video fallback already implemented.
P1MonitorPanelNone (panel-local keyword matching)NoneNoneFully local✅ Client-side only (no backend dependency).
P1StrategicRiskPanel cached overlayssrc/services/cached-risk-scores.tsintelligenceserver/worldmonitor/intelligence/v1/Requires user-provided API key✅ Explicit fallback: panel continues with local aggregate scoring when cache feed is unavailable.
P1Map layers (conflicts, outages, AIS, military flights)src/services/conflict/, src/services/infrastructure/, src/services/maritime/, src/services/military/conflict, infrastructure, maritime, militaryserver/worldmonitor/{domain}/v1/Requires user-provided API key✅ Explicit fallback: unavailable feeds are disabled while map rendering remains active for local/static layers.
P2Summariessrc/services/news/newsserver/worldmonitor/news/v1/Requires user-provided API key✅ Explicit fallback chain: Groq → OpenRouter → browser model.
P2MarketPanelsrc/services/market/, src/services/prediction/market, predictionserver/worldmonitor/market/v1/, server/worldmonitor/prediction/v1/Fully local✅ Multi-provider and cache-aware fetch behavior maintained in sidecar mode.
P3Flight enrichmentsrc/services/military/militaryserver/worldmonitor/military/v1/Requires user-provided API key✅ Explicit fallback: heuristic-only classification mode.
P3OpenSky relay fallback pathsrc/services/military/militaryserver/worldmonitor/military/v1/Requires cloud fallback✅ Relay fallback documented; no hard failure when relay is unavailable.

Non-parity closure actions completed

  • Added desktop readiness + non-parity fallback visibility in ServiceStatusPanel so operators can see acceptance status and per-feature fallback behavior in desktop runtime.
  • Kept local-sidecar strategy as the default path: desktop sidecar executes sebuf handlers locally via the esbuild-compiled bundle and only uses cloud fallback when handler execution or relay path fails.

Desktop-ready acceptance criteria

A desktop build is considered ready when all checks below are green:

  1. Startup: app launches and local sidecar health reports enabled.
  2. Map rendering: map loads with local/static layers even when optional feeds are unavailable.
  3. Core intelligence panels: LiveNewsPanel, MonitorPanel, StrategicRiskPanel render without fatal errors.
  4. Summaries: at least one summary path works (provider-backed or browser fallback).
  5. Market panel: panel renders and returns data from at least one market provider.
  6. Live tracking: at least one live mode (AIS or OpenSky) is available.

These checks are now surfaced in the Service Status UI as "Desktop readiness".