Monitoring dashboards and feature experiences
The monitoring dashboard is the client workspace for viewing global signals, comparing monitoring domains, and moving from a map event to supporting evidence. It combines variant-focused views with shared maps, data panels, country workspaces, analysis tools, interactive search, named tabs, and account-aware controls. See the broader client experience and the web application shell for related surfaces.
Product scope
The dashboard turns live and reference data into one workspace for fast orientation and deeper review. A site variant changes the focus of the workspace without changing its core interaction model.
| Variant | Primary monitoring focus |
|---|---|
| Full | Geopolitical risk, conflict, intelligence, markets, and infrastructure |
| Tech | Technology activity, hubs, events, and technology risk |
| Finance | Markets, macro signals, financial centers, and market intelligence |
| Commodity | Resources, trade routes, ports, and commodity risk |
| Energy | Energy supply, infrastructure, chokepoints, and disruptions |
| Happy | Positive events, resilience, conservation, and human progress |
The same dashboard supports a broad default view and a focused personal view. Users can add, remove, reorder, collapse, resize, and scale panels. Variant rules and account access decide which content can appear. A shared panel contract gives each surface clear language for live, cached, stale, locked, and unavailable data.
References: src/…/panels.ts• L1164-1255 src/…/base.ts• L137-144 src/…/panel-layout.ts• L805-865 src/…/Panel.ts• L820-907
Monitoring domains
The dashboard presents monitoring domains as related views rather than isolated feeds. The map gives geographic context. Panels provide measures and lists. Detail views explain why a signal matters.
| Domain group | User-facing questions |
|---|---|
| News and intelligence | What is happening now, where, and across how many sources? |
| Conflict and security | Which places show conflict, unrest, cyber activity, alerts, or escalation? |
| Military and transport | What is moving through air, sea, and strategic routes? |
| Aviation and airspace | Which airports, flights, carriers, and airspace areas show status changes or restrictions? |
| Infrastructure and supply | Which cables, pipelines, storage sites, ports, and chokepoints matter? |
| Markets and economy | How are prices, sectors, currencies, debt, trade, and stress changing? |
| Climate and natural events | Where are fires, weather events, earthquakes, disease, and climate anomalies occurring? |
| Technology | Which hubs, firms, events, cloud regions, and readiness signals are active? |
| Displacement and movement | Where are people leaving, arriving, returning, or facing internal displacement? |
| Resilience and positive signals | Which places show resilience, recovery, conservation, or other positive change? |
Each domain can appear as a map layer, a panel, or a detail view. This lets a user move from “where” to “what” and then to “why” without treating one display as the full answer.
References: src/…/map-layer-definitions.ts• L60-132 src/…/panels.ts• L24-137 src/…/Panel.ts• L820-861
Aviation workspace
The aviation workspace gives the dashboard a focused view of airport operations and air movement. It combines airport status, flight boards, carrier performance, aircraft tracking, aviation news, and explicit flight-price searches in one panel.
The workspace refreshes operational data while keeping user searches separate from the live feed. Country focus applies to airports, flights, and news where the source can support that match. Carrier summaries, tracking, and price searches remain global because their data does not map cleanly to the selected country scope.
The aviation command bar provides a faster entry point for common questions. It accepts airport operations, flight status, route prices, aviation news, and tracking intents, then shows provider gaps, partial results, or synthetic demo data as distinct states.
References: src/…/AirlineIntelPanel.ts• L63-107 src/…/AirlineIntelPanel.ts• L209-245 src/…/AirlineIntelPanel.ts• L325-418 src/…/AviationCommandBar.ts• L10-18 src/…/AviationCommandBar.ts• L73-117 src/…/AviationCommandBar.ts• L124-287
Country workspace
The country workspace turns a map selection or country link into a focused review of one country. It combines current signals, news, facts, military activity, markets, infrastructure, energy, trade, economic measures, history, resilience, and decision-support views.
Country sections load independently. Each section can be ready, loading, locked, partial, or unavailable. This keeps a missing source from changing the meaning of evidence that is still usable.
The workspace keeps evidence and presentation separate. It preserves source dates, source tiers, corroboration, selected scenarios, and incomplete-section states. Compact atlas rows shorten long disruption text so the summary stays scannable while the full event remains available in the related asset view.
Country briefs extend this workspace into a shareable and exportable dossier. They combine an instability score, active signals, an intelligence brief, headlines, prediction markets, and nearby infrastructure. Structured data and evidence exports remain subject to the account’s export access rather than silently exposing gated data.
References: src/…/CountryDeepDivePanel.ts• L126-137 src/…/CountryDeepDivePanel.ts• L139-180 src/…/CountryDeepDivePanel.ts• L2150-2238 src/…/CountryDeepDivePanel.ts• L2598-2709 src/…/regional-energy-presentation.ts• L158-305 src/…/CountryBriefPage.ts• L392-519 src/…/CountryBriefPage.ts• L521-624 src/…/CountryBriefPage.ts• L711-813
Food price workspace
The food price workspace connects a global food price index with local market prices and country context. Users can compare food, cereal, meat, dairy, oil, and sugar trends, then select a country and market to inspect current prices and week-over-week movement.
The view keeps market observations separate from contextual reports. It shows source status, report dates, check dates, units, attribution, and missing baselines. A missing comparison therefore does not read as no change. Context reports can be expanded and reviewed by country without replacing the weekly market view.
References: src/…/FoodPricesCard.ts• L13-35 src/…/FoodPricesCard.ts• L46-84 src/…/FoodPricesCard.ts• L86-131
Consumer price workspace
The consumer price workspace compares essential and value baskets across selected markets. It also shows category movement, retailer spreads, source health, and a world view of official inflation.
Users can switch markets, time windows, tabs, and category filters. The world inflation view loads on demand and remains separate from market-specific data. Freshness and upstream gaps stay visible when collection is incomplete.
References: src/…/ConsumerPricesPanel.ts• L114-154 src/…/ConsumerPricesPanel.ts• L228-295 src/…/ConsumerPricesPanel.ts• L298-319
PizzINT indicator
The PizzINT indicator gives the dashboard a compact tension and venue-status signal. It combines a freshness-aware DEFCON-style level with evidence such as strikes, airport changes, military activity, sanctions, and paired regional tensions.
The indicator shows no data when the monitored venue set is unavailable. Stale readings lose their current-status color, and missing baselines remain distinct from normal activity. This keeps a small status surface from overstating what the underlying sources prove.
References: src/…/PizzIntIndicator.ts• L23-75 src/…/PizzIntIndicator.ts• L82-130 src/…/PizzIntIndicator.ts• L132-221
Dashboard composition
The dashboard combines a shared panel contract with a layout manager. The contract supplies common status, freshness, access, loading, retry, focus, collapse, resize, and persistence behavior. Each feature panel supplies its own domain view.
The layout manager uses the active variant and saved preferences to decide which panel shells appear. It can reserve space before data is ready, load visible or nearby panels first, and restore a panel to its saved position after its code and data are ready. Panel content updates use a stable content host, so controls remain active across data refreshes.
The main panel groups are:
- Orientation: map, live news, intelligence, strategic risk, and posture.
- Evidence: regional news, conflict, military, infrastructure, supply chain, displacement, country, and aviation views.
- Analysis: forecasts, correlations, market implications, risk scores, briefs, and signal quality.
- Domain tools: markets, macro context, heatmaps, energy, technology, climate, resilience, social activity, gold, food prices, regulation, conservation, and infrastructure cascade analysis.
- Personal tools: monitors, search, watchlists, custom widgets, exports, playback, and named workspaces.
This model lets a panel be a default feature for one variant, an optional feature for another, or a gated feature without changing the dashboard frame. Panels can own tabs, drawers, tables, charts, and map-linked actions while retaining the same loading, retry, access, and freshness language.
References: src/…/Panel.ts• L134-180 src/…/Panel.ts• L820-907 src/…/Panel.ts• L1694-1778 src/…/Panel.ts• L1858-1879 src/…/panel-layout.ts• L1802-1999
Dashboard tabs
Dashboard tabs are named panel workspaces. Each tab preserves a panel selection and order for the current site variant, while the active tab drives the live panel layout.
Users can switch, add, rename, and delete tabs. A separate option lets the user save the current panel selection as the starting point for new tabs or return new tabs to the variant defaults. The bar also supports keyboard navigation, team dashboards, country focus, and account-aware creation limits.
Existing workspaces remain usable when the account cannot create another tab. Tabs continue to work for the current session when browser storage is unavailable. Malformed stored tabs are ignored or reduced to a usable active tab rather than blocking the dashboard.
References: src/…/PanelTabBar.ts• L8-20 src/…/PanelTabBar.ts• L86-99 src/…/PanelTabBar.ts• L205-243 src/…/PanelTabBar.ts• L339-429 src/…/tab-store.ts• L7-20 src/…/tab-store.ts• L39-110
Panel filter choices
Panel filter choices are panel-owned selections that travel with a tab. A panel can save a choice such as a region, and the layout restores it when the panel mounts or when the tab becomes active.
The active tab applies its choices to mounted panels. A choice that the previous tab set but the new tab does not set is reset to the panel default. A panel that neither tab controls is left unchanged, so older browser preferences are not erased. The same bounded choices can be included in a shared team dashboard after validation.
References: src/…/panel-filters.ts• L12-96 src/…/panel-layout.ts• L1772-1816 src/…/tab-store.ts• L38-43 src/…/team-dashboards.ts• L81-85 src/…/team-dashboards.ts• L126-131
Map experience
The map is the dashboard’s shared geographic surface. It combines a base map with layers for events, assets, movement, infrastructure, markets, technology, displacement, aviation, and environmental or positive signals. Selecting a marker can open source context, focus related assets, or open a country or domain view.
The map keeps one user-facing state model while choosing a renderer that fits the device and available graphics support. A lightweight SVG map supports mobile and limited graphics environments. A high-volume desktop map supports dense layers. An optional globe provides a three-dimensional view of the same state.
Layer controls, time range, center, zoom, popups, and context actions remain shared across renderers. Clustering, marker budgets, glyphs, and zoom-aware disclosure keep dense views usable. A renderer switch keeps the current data and callbacks. A failed graphics path falls back to the SVG map with the current map state. The map also supports distance measurement, route views, orbital overlays, aircraft positions, and movement layers that preserve source meaning.
The following flow shows how map state becomes an interactive user experience.
flowchart LR
A[Variant and saved map state] --> B[Shared map state]
B --> C{Device and renderer support}
C -->|Mobile or limited graphics| D[SVG map]
C -->|Desktop high-volume view| E[Desktop map]
C -->|Globe mode| F[3D globe]
D --> G[Layers and markers]
E --> G
F --> G
G --> H[Popup, country view, or related panel]
References: src/…/Map.ts• L112-128 src/…/Map.ts• L381-444 src/…/Map.ts• L690-840 src/…/DeckGLMap.ts• L692-800 src/…/GlobeMap.ts• L555-761
Map movement layers
Movement layers show displacement as distinct geographic evidence. Refugee routes, internal displacement routes and regions, event-based displacement points, and cross-border reports keep their source, count, date, and route meaning visible rather than combining unlike measures into one total.
Coincident cross-border markers spread around their shared location so each report stays selectable. Route markers and local figures use different visual forms. Popups preserve the kind of movement, source, reporting period, and change value.
References: src/…/displacement-marker.ts• L12-51 src/…/displacement-marker.ts• L59-86 src/…/displacement-marker.ts• L89-134 src/…/cross-border-marker.ts• L7-24 src/…/cross-border-marker.ts• L27-47 src/…/cross-border-marker.ts• L68-96
Map popup
The map popup turns a selected marker into source context and next actions. It can show event, asset, route, flight, infrastructure, market, water, or country detail while keeping attribution and corroboration close to the claim.
Popup detail adapts to the device. Desktop popups stay within the viewport. Mobile uses a dismissible sheet. Some detail is loaded only after the user expands it, such as passive network context for an IP-based cyber marker or history for a chokepoint. A replacement or close cancels work owned by the old selection, and a new outside gesture can dismiss the popup without leaving stale overlay state behind.
Map-object popups can also show a satellite imagery row. The row starts with a small loading state, then adds the latest usable image, its date, the next pass, source credit, or a link to the full orbital evidence view. Dated events can offer a Pro-gated before-and-after comparison.
References: src/…/MapPopup.ts• L301-430 src/…/MapPopup.ts• L457-529 src/…/MapPopup.ts• L824-882 src/…/MapPopup.ts• L929-957 src/…/map-popup-imagery.ts• L26-105 src/…/map-popup-imagery.ts• L143-183 src/…/map-popup-imagery.ts• L254-322
Orbital monitoring experience
Orbital monitoring adds a point-based review flow to the shared map. A user can inspect satellite coverage, recent imagery, nearby events, and future collection opportunities without leaving the dashboard context. The experience keeps computed opportunity, confirmed archive evidence, and related ground signals as separate parts of the review.
Point evidence sheet
The point evidence sheet is a responsive workspace for one map point or searched place. It shows the latest usable image first, then supports image comparison, archive fallbacks, daily mosaics, weather frames, source credits, local or UTC time, sharing, and a link back to the selected map point.
The sheet also places nearby conflict, fire, unrest, outage, vessel, military-flight, and GPS-jamming signals beside orbital evidence. Independent loading and failure states keep a missing event feed from hiding satellite evidence. Processing, no-preview, stale-catalog, and partial-source states explain why a result is incomplete.
References: src/…/OrbitalWatchPage.ts• L616-691 src/…/OrbitalWatchPage.ts• L764-814 src/…/OrbitalWatchPage.ts• L888-985 src/…/OrbitalWatchPage.ts• L988-1027
Satellite pass analysis
Pass analysis turns a point and time window into a set of satellite opportunities. It separates confirmed imagery from likely imagery, reachable coverage, general overhead capability, and future collection windows so users can tell what has happened from what may happen next.
The analysis reports satellite outcomes, daylight spans, orbit age, viewing geometry, motion, and progress. The pass client cancels a superseded lookup and uses a worker when available. It falls back to yielding main-thread work when the worker cannot start. The same service can estimate the next open crossings for monitored reservoirs.
References: src/…/pass-client.ts• L17-57 src/…/pass-client.ts• L221-263 src/…/pass-client.ts• L289-323 src/…/pass-job.ts• L118-180 src/…/orbital-pass.worker.ts• L1-8
Orbital map context
The map provides geographic context for an open orbital review. It can mark the target point and draw a satellite ground track, coverage footprint, leading edge, and current swept area. The overlay follows map pan, zoom, and world wrapping, while the selected pass stays synchronized with the point sheet and other orbital surfaces.
References: src/…/Map.ts• L228-235 src/…/Map.ts• L5141-5159 src/…/Map.ts• L5161-5205 src/…/DeckGLMap.ts• L590-601 src/…/DeckGLMap.ts• L795-800
Reservoir water context
The reservoir workflow joins level change, radar water extent, the latest optical scene, and the next lidar pass. It is context for review rather than a single scored value. Each row keeps its own date and source state.
The water card loads by public reservoir identity and uses a rounded reservoir center for optical context. A missing reading is different from an unavailable source. The same distinction appears in reservoir map popups and keeps a failed read from looking like normal water levels.
References: src/…/water-card.ts• L14-42 src/…/water-card.ts• L64-120 src/…/water-card.ts• L123-145 src/…/MapPopup.ts• L23-40
Domain analysis panels
Domain panels turn related observations into focused review flows. They share the dashboard’s source, access, loading, and stale-data rules while keeping domain meaning separate.
| Panel group | User task |
|---|---|
| Energy and supply chain | Review prices, storage, chokepoints, assets, disruptions, and closure effects. |
| Markets and macro | Review quotes, breadth, yield curves, fund flows, currencies, calendars, gold, and market stress. |
| Consumer prices | Compare household costs, food prices, fuel, and inflation across places. |
| Conflict and events | Review violence, climate anomalies, fires, radiation, disease, social activity, and material filings. |
| Displacement and resilience | Compare origins, host countries, recent events, internal movement, resilience, and recovery. |
| Policy and trade | Review restrictions, tariffs, trade flows, barriers, customs revenue, and strategic commodities. |
| Cross-domain analysis | Inspect correlations, threat timelines, forecasts, and transmission paths. |
Scenario results stay distinct from current observations. Independent source tabs remain usable when another source fails. This prevents a missing input from looking like zero activity or a modeled result from looking like a measured fact.
Energy and supply chain panels
Energy panels connect market measures with physical systems. The energy complex combines oil and gas prices, production, inventories, storage, oil-stock cover, and LNG vulnerability. Asset panels and disruption logs connect a physical event to the affected infrastructure. Scenario controls explore closure effects without changing the current observation.
Supply-chain views add chokepoint status, shipping measures, economic indicators, minerals, and carrier stress. Expanded chokepoints can show transit history, bypass options, and a controlled closure scenario. These views keep unavailable transit counts and incomplete coverage distinct from a measured zero.
References: src/…/EnergyComplexPanel.ts• L17-68 src/…/EnergyRiskOverviewPanel.ts• L85-136 src/…/EnergyDisruptionsPanel.ts• L68-150 src/…/SupplyChainPanel.ts• L29-118 src/…/SupplyChainPanel.ts• L206-249 src/…/SupplyChainPanel.ts• L491-685
Route exploration
The route explorer turns an origin country, destination country, product class, and cargo type into a focused shipping review. Its views compare the current lane, ranked sea alternatives, land corridors, and country impact, while the shared map highlights the selected lane or a chosen bypass.
The flow uses the same access and freshness boundaries as other premium analysis. A free user can see the public route highlight and the access boundary. An entitled user receives modeled lane data, resilience context, impact data, and alternative corridors. URL state supports reopening or sharing the selected workflow.
References: src/…/RouteExplorer.ts• L83-171 src/…/RouteExplorer.ts• L188-266 src/…/RouteExplorer.ts• L301-353 src/…/RouteExplorer.ts• L432-443
Market and macro panels
Market panels provide several levels of review. Users can move from broad market quotes to breadth, yield curves, fund flows, earnings and economic calendars, foreign exchange, gold, and asset-specific research.
The market panel explains why a quote is unavailable instead of hiding the symbol. Rows with a usable series open a chart or stock research without losing dashboard context. Missing breadth, rate, valuation, or divergence readings remain missing rather than becoming zero.
References: src/…/MarketPanel.ts• L56-137 src/…/MarketPanel.ts• L151-224 src/…/MarketPanel.ts• L515-633 src/…/GoldIntelligencePanel.ts• L154-441 src/…/FxPanel.ts• L9-140 src/…/YieldCurvePanel.ts• L222-335
Event and public-signal panels
Event panels turn large sets into bounded lists or summaries. Violence types use separate views. Climate anomalies, radiation, fires, disease outbreaks, social velocity, and material events expose current signals with dates, severity, confidence, or source context.
Rows can focus the map when a location is known. Empty, partial, warm-up, stale, and degraded states remain distinct. A last-good list can stay visible when a later refresh fails.
References: src/…/UcdpEventsPanel.ts• L8-19 src/…/UcdpEventsPanel.ts• L60-162 src/…/ClimateAnomalyPanel.ts• L7-50 src/…/RadiationWatchPanel.ts• L21-51 src/…/MaterialEventsPanel.ts• L50-130
Positive-signal views
Positive monitoring views present resilience, recovery, conservation, and giving as evidence-backed signals. Giving views keep reported values, time periods, qualifiers, and source status separate from calculated aggregates so an estimate is not presented as a verified total.
Pro previews show a safe sample of gated depth only after access state is known. If entitlement is unresolved or degraded, the preview stays hidden rather than turning an access outage into an upgrade prompt.
References: src/…/giving-renderer.ts• L10-41 src/…/giving-renderer.ts• L77-114 src/…/ProPreviewSection.ts• L22-105 src/…/ResilienceWidget.ts• L121-187 src/…/ResilienceWidget.ts• L244-283
Data lifecycle
Dashboard data moves from source services into shared client state and then into the map or panels that need it. Source health travels with the data so the interface can distinguish current, stale, missing, disabled, partial, and failed results.
The main lifecycle is:
- The active variant, panels, mission preset, and map layers select the work.
- Loaders obtain live feeds, service responses, cached snapshots, and reference data.
- Shared state stores news, markets, predictions, geographic events, displacement observations, intelligence results, aviation data, and on-demand water observations.
- Panels and map renderers consume the relevant state.
- Freshness and source health appear where they affect interpretation.
The dashboard does not require every source to succeed before it can render. Partial operation is useful, but a quiet view must be read with its freshness and source status. Local storage is optional for boot and playback, so a browser that blocks IndexedDB can still use live dashboard features while historical snapshots remain unavailable.
flowchart TD
A[Feeds and service data] --> B[Data loading]
B --> C[Shared dashboard state]
C --> D[Map layers]
C --> E[Monitoring panels]
C --> F[Country and signal details]
B --> G[Freshness and source health]
G --> D
G --> E
References: src/…/data-loader.ts• L1-24 src/…/app-context.ts• L37-60 src/…/data-freshness.ts• L13-59 src/…/data-freshness.ts• L228-274 src/…/data-freshness.ts• L397-473 src/…/storage.ts• L39-103 src/…/AirlineIntelPanel.ts• L341-418 src/…/FoodPricesCard.ts• L61-131
Analysis and orbital workers
Background workers keep costly analysis away from the main UI thread. They support news clustering, cross-domain signals, and satellite pass analysis, with optional machine-learning work for embeddings, semantic grouping, sentiment, summaries, and entity extraction.
The dashboard treats advanced analysis as an enhancement rather than a requirement. Server-prepared insight data can appear first. Client analysis and simpler paths provide useful results when worker or model support is missing. Readiness, source age, and fallback state remain visible.
Orbital pass work follows the same boundary. The worker reports readiness, progress, results, errors, and cancellation. The client can use a main-thread fallback when worker support is unavailable, and it marks which path produced the lookup.
References: src/…/engine.ts• L29-116 src/…/InsightsPanel.ts• L309-433 src/…/analysis.worker.ts• L1-133 src/…/ml-worker.ts• L71-180 src/…/pass-client.ts• L128-218 src/…/orbital-pass.worker.ts• L1-8
Interactive workflows
The dashboard supports workflows that move beyond passive reading. These actions use the same state and access rules as ordinary controls, which keeps pointer, keyboard, and analyst actions aligned.
| Workflow | Result |
|---|---|
| Search | Finds panels, signals, map items, flights, and actions in the active dashboard. |
| Aviation command | Runs short operations, flight, price, news, and tracking queries. |
| Country exploration | Opens country risk, news, markets, infrastructure, energy, trade, and related evidence. |
| Monitor creation | Saves keywords and shows matching news with a monitor color. |
| Panel layout | Changes panel visibility, order, size, collapse state, and scale. |
| Dashboard tabs | Saves named panel workspaces and controls the starting panels for new tabs. |
| Mission presets | Applies a domain-focused panel set, map view, time range, and layer set. |
| Historical playback | Shows a stored dashboard snapshot and then returns to live mode. |
| Map control | Changes view, center, zoom, time range, visible layers, and measured distance. |
| Route exploration | Compares shipping lanes and alternatives while highlighting the selected path on the map. |
| Analyst chat | Streams a domain-focused answer with source status and optional dashboard actions. |
| Latest brief | Opens the account-scoped daily brief when it is ready. |
| Pro activation | Guides a new Pro account through brief, alert, and toolkit setup. |
Search experience
Search acts as a command deck for both navigation and evidence. It searches registered live sources and dashboard commands, then applies the current access, panel, renderer, and result visibility rules before showing an item.
Users can narrow the deck to All Intel, Signals, Map, Panels, or Actions. Desktop and mobile use different result bounds, while flight-prefixed searches can hand a callsign to a live flight lookup. A panel that is available but disabled can appear with an Add action instead of being hidden.
The search index keeps logical identity separate from changing display data. A refresh can therefore update a selected result without moving the user to a different target. Recent searches and idle examples are session entry points, not evidence results.
References: src/…/SearchModal.ts• L128-244 src/…/SearchModal.ts• L420-505 src/…/SearchModal.ts• L684-776 src/…/SearchModal.ts• L953-1035 src/…/search-engine.ts• L18-75 src/…/search-engine.ts• L137-267 src/…/search-scope.ts• L1-10 src/…/search-scope.ts• L33-99 src/…/search-types.ts• L3-77
Analyst chat
Analyst chat provides a premium conversational path across geopolitical, market, military, and economic domains. Quick actions and domain filters help users start with a bounded question, while streamed answers expose source chips and partial status as the response arrives.
The panel can optionally accept structured dashboard actions from the analyst. A user-controlled switch and pause state keep those actions explicit. Invalid, denied, skipped, and applied actions remain distinct, so a generated suggestion cannot silently change the dashboard.
References: src/…/ChatAnalystPanel.ts• L27-63 src/…/ChatAnalystPanel.ts• L146-236 src/…/ChatAnalystPanel.ts• L404-503 src/…/ChatAnalystPanel.ts• L517-619 src/…/ChatAnalystPanel.ts• L627-695
Latest brief
The Latest Brief panel is an account-scoped entry point to the daily editorial magazine. A ready response shows the issue date, greeting, thread count, and a signed link. A composing response tells the user that the issue is not ready yet. Access is handled as a separate locked state.
The panel refreshes when the account or entitlement changes and rejects results that belong to an older account. It can also offer a referral share action after the profile is available. The panel does not expose brief content while access or identity is unresolved.
References: src/…/LatestBriefPanel.ts• L39-71 src/…/LatestBriefPanel.ts• L105-209 src/…/LatestBriefPanel.ts• L224-345 src/…/LatestBriefPanel.ts• L447-493 src/…/LatestBriefPanel.ts• L536-661
Pro activation flow
The Pro activation interstitial guides a new subscriber through the highest-value setup steps. The flow can cover the morning brief, real-time alerts, the Pro toolkit, and account questions, then ends with a summary of what is ready and what remains.
Each step can be confirmed, skipped, failed, blocked by a browser permission, or unavailable on the device. The shell keeps those outcomes separate and ignores late results after the user leaves the step. This makes the exit summary and account record match the action that actually occurred.
References: src/…/ProActivationInterstitial.ts• L1-24 src/…/ProActivationInterstitial.ts• L340-495 src/…/ProActivationInterstitial.ts• L615-721 src/…/ProActivationInterstitial.ts• L763-883
Mission presets
Mission presets are named starting points for common monitoring tasks. A preset selects a map view, time range, panel group, and map layers, then adapts that selection to the active site variant and renderer.
Presets cover crisis review, supply-chain risk, energy security, news, markets, technology, positive signals, country watching, and a finance-only trading view. Unsupported layers are removed while preserving a usable map state.
References: src/…/mission-presets.ts• L22-40 src/…/mission-presets.ts• L55-398 src/…/mission-presets.ts• L419-476 src/…/mission-presets.ts• L512-586 src/…/mission-presets.ts• L624-641
Settings experience
Unified settings is the control surface for dashboard preferences, panel selection, source selection, notifications, billing, and account-linked tools. It keeps panel changes as a draft until the user saves them. Source changes apply when the settings session closes with a changed selection.
Panel settings cover variant categories, search, visibility, layout reset, saved layout, and per-panel scale. Source settings support region filters, search, select-all and select-none actions, and coverage presets. The source list is compared with its opening state when the overlay closes, so the host receives one refresh signal only when the final selection changed.
The settings surface also provides account-aware pages for plan and billing, API keys, embeds, connected MCP clients, notifications, and team seats. Account and entitlement changes rebuild the page shape and clear account-owned data before new data loads. Billing actions use the external billing portal.
Settings is a modal workflow with focus management, keyboard navigation, mobile history behavior, unsaved panel-change confirmation, and account-safe teardown.
References: src/…/UnifiedSettings.ts• L119-145 src/…/UnifiedSettings.ts• L280-305 src/…/UnifiedSettings.ts• L683-725 src/…/UnifiedSettings.ts• L739-818 src/…/UnifiedSettings.ts• L871-970 src/…/UnifiedSettings.ts• L1001-1052
Access and data quality
Access rules affect both what a user can open and what the dashboard can persist. Premium panels, tabs, map layers, orbital comparisons, and account tools show a gate or safe fallback when the account cannot use them. A shared map URL requests a view. It does not grant permission to change durable preferences.
Account-scoped services use the current signed-in identity and reject late results from an older account. This applies to entitlements, billing, settings data, team seats, API keys, embeds, briefs, analyst requests, and activation flows. Access state can be pending or unavailable, so the dashboard does not treat an unresolved check as either paid access or a confirmed denial.
Data quality is separate from access. An entitled user can still see stale, disabled, empty, partial, or failed source data. Country sections, resilience views, route intelligence, orbital evidence, and history wait for access to settle before requesting paid data and re-check access when account state changes.
References: src/…/entitlements.ts• L78-160 src/…/UnifiedSettings.ts• L693-725 src/…/RouteExplorer.ts• L225-266 src/…/ChatAnalystPanel.ts• L78-97 src/…/LatestBriefPanel.ts• L224-345 src/…/ProActivationInterstitial.ts• L950-1001 src/…/Panel.ts• L820-861
Change checklist
When these files or sections are changed, remember to consider these:
- When adding a panel, update the variant registry, layout registration, data-loading path, and access rule together.
- When changing panel content, preserve the stable delegated event path, immediate user-action rendering, focus state, freshness badge, and teardown behavior.
- When adding a dashboard tab action, keep the tab bar, tab state, active live layout, variant-scoped storage, team sharing, and tab-cap gate aligned.
- When adding or changing a panel-owned filter, keep the panel contract, tab persistence, tab-switch reset plan, storage normalization, and team-dashboard encoding aligned.
- When adding a map layer, define renderer support and source relationships before exposing it in layer controls, search, or analyst actions.
- When changing map state or viewport actions, preserve URL state, renderer switching, pending-action replay, human interaction authority, and settled-viewport behavior.
- When changing map popups, keep device layout, selected-item ownership, lazy detail, imagery rows, source links, localization fallback, outside dismissal, and route or asset actions aligned.
- When changing movement data, preserve source-specific marker meaning, renderer parity, marker offsets, popup ownership, and separate counts.
- When changing orbital point review, keep the point sheet, pass client, archive evidence, nearby-event context, image viewer, local-time control, and share-link state aligned.
- When changing orbital pass calculations, preserve worker and main-thread fallback behavior, lookup cancellation, progress identity, catalog age, pass tiers, and reservoir next-pass requests.
- When changing food or consumer prices, keep global indexes separate from local observations and preserve source dates, units, coverage, and baseline meaning.
- When changing aviation views or commands, keep airport scope rules, flight direction, explicit price searches, provider fallbacks, demo labels, and live tracking state distinct.
- When changing route exploration, keep query URL state, access gating, request generations, tab data, lane geometry, bypass overlays, and map cleanup aligned.
- When changing supply-chain scenarios, keep current observations separate from projected values and preserve the scenario control state across data-driven renders.
- When changing search, keep scope membership, command visibility, renderer executability, panel add behavior, result identity, mobile bounds, and live flight handoff aligned.
- When changing analyst control actions, preserve the user switch, pause state, action allowlist, current request generation, sanitized output, and applied or denied status.
- When changing account-scoped brief or activation flows, preserve identity checks, entitlement checks, abort ownership, late-result rejection, and honest ready/composing/blocked outcomes.
- When changing settings sources, preserve the opening-session baseline and the single close-time callback. Do not replace it with a refresh on every toggle.
- When changing settings account pages, team seats, or billing controls, keep entitlement gates, account resets, active-page normalization, request generations, portal handoff, and failed-open recovery distinct.
- When changing country brief exports, keep machine-readable formats and evidence bundles behind their separate access checks and preserve the source and evidence fields in exported data.
- When changing positive-signal or giving views, keep verified, partial, cached, legacy, and unverified source states separate from calculated summaries.
Important failure modes
| Trigger | Consequence | Guard |
|---|---|---|
| A renderer switch or viewport request finishes after a newer request starts | Old map work can overwrite the current renderer, center, layer state, or selected target. | Renderer and viewport generations accept readiness and replay state only for the active request. |
| A layer has no path in the active renderer | A control, search result, or analyst action can imply data that the map cannot show. | Layer definitions and executable predicates limit actions to supported renderers. |
| Dense map data exceeds the useful marker budget | Important markers can crowd the view or slow interaction. | Clustering, ranking, category glyphs, truncation disclosure, and fallback keep the view bounded. |
| A movement value mixes a stock, route, or event figure with another source measure | A user can read unlike counts as one comparable total. | Marker kinds retain source, date, route, and figure meaning. |
| A source is stale, disabled, empty, partial, or failed | A quiet panel can look like a current all-clear state. | Freshness state, source coverage, and unavailable messages stay visible. |
| A popup detail or imagery response belongs to an older marker | Details for one selection can appear on another selection. | Popup-owned cancellation and current-selection checks reject stale results. |
| A localized provider value is unknown | A label can become blank or a raw machine term can be mistaken for a translated term. | Display helpers fall back to the original value and keep raw values for data use. |
| A passive cyber lookup runs before the user asks for it or outlives its popup | Popup opening can incur needless network work or show details for another marker. | The lookup starts on expansion, uses a bounded request, and checks that the popup remains connected. |
| A newer orbital point lookup replaces an older one after its result arrives | Passes or imagery for the previous point can appear in the current evidence sheet. | The point sheet and pass client use an open sequence and cancellation boundary. |
| Orbit elements are too old or invalid for a satellite | A computed opportunity can look like a current prediction even though its source orbit is not usable. | Satellite outcomes expose old or invalid elements, and rows show orbit age or stale catalog state. |
| The orbital worker cannot start or stops during a lookup | Satellite coverage can disappear or block the dashboard if the calculation has no alternate path. | The client falls back to yielding main-thread work and exposes the computation path and failure state. |
| A reservoir request fails with no cached snapshot | A water panel can show no readings as if the system had checked and found normal levels. | The water card separates unavailable from an empty dataset and keeps usable snapshots distinct. |
| A country or account request finishes after the selection or entitlement changes | Evidence for one region or account can appear in another view or in a gated card. | Request sequences, account checks, and current-selection checks reject stale results. |
| A route query finishes after the user changes the countries, product, or cargo | Old lane data or map highlights can appear for the new query. | Route generations invalidate older lane, resilience, impact, and map updates. |
| A route has no modeled geometry or the selected bypass lacks ports | The explorer can promise a map path that cannot be drawn. | The flow keeps a public route fallback and requires usable endpoints before drawing a bypass. |
| A tab change leaves a panel-owned filter from the previous tab | A panel can show the prior workspace’s selection. | The filter apply plan resets keys previously applied by the old tab when the new tab does not set them. |
| A supply-chain transit count is absent but represented as zero | No observed feed can look like a measured empty corridor. | The view checks the published-count flag and labels upstream unavailability separately. |
| A supply-chain scenario result is treated as current status | A projected closure can be read as an observed disruption. | Scenario values use separate projected labels and remain tied to the active scenario controls. |
| A food or consumer price has no baseline or coverage is incomplete | A missing comparison can look like no price movement or complete market coverage. | The view marks missing baselines, source dates, pending markets, and source health. |
| A flight-price provider has missing credentials, no results, or synthetic data | A quote can look live when it is only a fallback or demo estimate. | Provider errors, degraded results, and demo data use separate user-facing states. |
| A search result refresh changes its subtitle or payload while it is selected | Keyboard selection can move to the wrong target or dispatch old data. | Search identity uses the logical result target and resolves the latest registered payload. |
| An analyst action is invalid, denied, paused, or generated after the request is obsolete | A chat response can change dashboard state without clear user authority. | The action parser, control switch, pause state, and request generation classify the result before applying it. |
| A brief or activation response belongs to a former account | One user can see another user’s brief or activation status. | Auth transitions clear sensitive state, abort old work, and require the current account before rendering. |
| A settings source changes and the overlay closes without propagation | The dashboard can wait for the normal refresh interval before using the new source set. | Settings compares opening and closing source signatures and notifies the host once for a changed session. |
| A country brief export is opened while entitlement is pending or changes after the menu opens | A structured or evidence export can bypass the intended access boundary. | Export access is checked when options are shown and again when the user clicks the format. |
Key files
| File | Why to read it |
|---|---|
| src/App.ts | Shows how dashboard context, loading, layout, refresh, and event handling connect. |
| src/…/app-context.ts | Defines shared state for maps, panels, data, overlays, and workflows. |
| src/…/panels.ts | Defines the cross-variant panel catalog, defaults, labels, and access helpers. |
| src/…/panel-layout.ts | Explains panel creation, deferred mounting, layout state, access updates, filter choices, and teardown. |
| src/…/Panel.ts | Defines shared panel status, freshness, access, focus, filter choices, collapse, resize, scale, retry, persistence, and content lifecycle. |
| src/…/PanelTabBar.ts | Shows named workspace controls, team sharing, focus controls, keyboard behavior, rename and delete actions, and tab-cap notices. |
| src/…/tab-store.ts | Defines variant-scoped tab persistence, saved starting panels, and normalized panel choices. |
| src/…/mission-presets.ts | Shows how monitoring missions select panels, map views, time ranges, and layers. |
| src/…/Map.ts | Illustrates the mobile-safe map, layer controls, marker budgets, movement layers, orbital context, and map evidence. |
| src/…/DeckGLMap.ts | Shows dense desktop layers, clustering, aircraft and infrastructure views, orbital overlays, and graphics recovery. |
| src/…/GlobeMap.ts | Shows the three-dimensional map surface, marker selection, globe overlays, and renderer-specific performance behavior. |
| src/…/MapPopup.ts | Shows device-specific map detail, source context, lazy history, imagery, cyber lookup, and popup ownership. |
| src/…/CountryBriefPage.ts | Shows country dossier presentation, signal and evidence updates, sharing, printing, and gated exports. |
| src/…/OrbitalWatchPage.ts | Shows point-based satellite evidence, pass opportunities, nearby events, imagery states, and review controls. |
| src/…/pass-client.ts | Shows lookup windows, worker selection, cancellation, progress, fallback, and reservoir crossing requests. |
| src/…/SupplyChainPanel.ts | Shows chokepoint, shipping, minerals, stress, history, bypass, and scenario review. |
| src/…/RouteExplorer.ts | Shows route query state, premium gating, tabbed route analysis, and map lane integration. |
| src/…/MarketPanel.ts | Shows market quote states, chart and research entry points, heatmap views, and physical-market comparisons. |
| src/…/FoodPricesCard.ts | Shows local food observations, context reports, market selectors, and source status. |
| src/…/AirlineIntelPanel.ts | Shows airport operations, flight status, tracking, aviation news, and explicit price workflows. |
| src/…/AviationCommandBar.ts | Shows aviation intent parsing, command history, provider fallbacks, and degraded-price messaging. |
| src/…/ChatAnalystPanel.ts | Shows domain-focused streaming analysis, source status, sanitized output, and optional dashboard controls. |
| src/…/LatestBriefPanel.ts | Shows account-scoped brief states, entitlement handling, refresh behavior, and magazine handoff. |
| src/…/SearchModal.ts | Shows the command deck, scope controls, keyboard behavior, mobile surface, and live flight handoff. |
| src/…/search-engine.ts | Defines shared search matching, ranking, result bounds, and logical identity. |
| src/…/UnifiedSettings.ts | Shows panel and source controls, session-level source propagation, account pages, and teardown. |
| src/…/ProActivationInterstitial.ts | Shows post-checkout setup steps, permission outcomes, progress, and the exit summary. |
| src/…/data-freshness.ts | Defines source health, panel freshness, coverage, and intelligence-gap states. |
| src/…/storage.ts | Defines local baselines and snapshots and their graceful degradation when browser storage is blocked. |
| src/…/engine.ts | Shows cross-domain signal clustering and optional language-model assessment. |
| src/…/ml-worker.ts | Shows worker readiness, model recovery, and the boundary between optional ML and core dashboard data. |
| src/…/entitlements.ts | Defines reactive account access and pending or unavailable verification states used by gated surfaces. |