The data strip

The data strip is Nexma's intelligence dashboard. It sits across the bottom of the workspace, presents 100+ live data feeds in a compact strip, and renders the selected feeds onto the Globe. Every feed is a Codex file; every feed reads, writes, and renders through the same pipeline.

What the strip shows

• Operational feeds. Weather, lightning, wind, ocean currents, river gauges,

air quality, pollen, UV.

• Movement feeds. Flights, ships, trains, bus fleets, fleet vehicles.
• Threat and intel feeds. Earthquakes, tsunamis, cyclones, volcanoes, floods,

active wildfires.

• Cyber feeds. Threat scanner, network intel, exposure scanner, abuse

intelligence.

• Economic and political feeds. Sanctions, court records, ad library, public

procurement.

• Environmental feeds. Deforestation, emissions, climate anomalies, sea ice,

glacial retreat.

• Custom feeds. Project-specific feeds from internal systems, equipment

telemetry, or partner APIs.

The catalog grows continuously; feeds can be enabled per workspace.

Codex-first

Every feed writes to the Codex when fresh data arrives:

A reactive layer renders any GeoJSON feed onto the Globe automatically. There is no per-feed UI code; adding a new feed requires:

1. A catalog entry.
2. A data handler that fetches and writes to the Codex.
3. A chart configuration for non-spatial visualizations.

Pinning

Right-click any entity on the Globe — a flight, a vessel, a sensor reading — to pin it to Jax's chat. Pinned entities become spatial context chips that travel with the next message. Jax can then read the entity's state and reason about it.

Seed-then-serve

Live external APIs are not called at request time. A scheduled worker fetches each feed on its native cadence and caches the result; the browser reads from the cache. This keeps the strip responsive at thousands of concurrent users without spending API budget per view.

Temporal slider

The strip carries a timeline scrubber. Sliding the scrubber re-renders all time-aware feeds at the chosen instant. Useful for after-the-fact incident review and for forecasting against future-dated feeds.

Limits

• Update cadence is per-feed (most feeds are 30s–5m fresh; some forecast feeds

are hourly).

• Some feeds are gated by region or by enterprise plan.
• The data strip is not a SCADA replacement — it is observational, not

control-authority.