WIDECLARITY / DOCUMENTATION

Know the platform.
Build your perspective.

Find your tools. Follow a workflow. Understand the sources behind it.

Start here

WideClarity 0.1.11 beta. These guides match the Windows download, prepared for Windows x64 and updated on 31 October 2026. Install the app or take the tester walkthrough.

Start here: your WideClarity app

A practical map of the current tester build, from the globe to retained research.

WideClarity brings geographic context, source-linked reporting, weather, transport observations and retained research into one desktop app. Start in Intelligence to explore the world. Open Strategic Intelligence for the separate strategic globe, Explore for geographic projects, Daily briefing for current reporting, Tech news for technology coverage, or Reports for evidence-backed analytical writing.

Workspace is the project and research panel available from Intelligence navigation. It brings together investigations, event dossiers, asset imports, dependencies, monitoring, history, forecast comparison, source tools, sharing and recovery. You can create a project there without first opening Explore.

These guides cover WideClarity 0.1.11 for Windows, prepared for Windows x64 and updated on 31 October 2026. The download page supplies this build. Keep BETA-BUILD.json from your extracted app folder so a tester report identifies the exact source revision.

How to use it

  1. Download and extract the Windows beta, then open WideClarity.exe and create or sign in to your local account.
  2. Choose Get started on the first-launch welcome screen.
  3. Use Intelligence for your first place and source check.
  4. Open Workspace and create a project when you want to retain evidence or use research tools.
  5. Follow the ten-minute tester walkthrough, then use Find a guide for a specific task.

What changed in the current tester app

The major workflows added since the original website beta guides.

The app now has a separate Strategic Intelligence workspace and an analytical Reports library. Strategic Intelligence has its own globe, visual treatments and source controls. Reports supports manual authoring, claim-level evidence, editorial review, publication and retained revisions; it is separate from the globe's report feed and Daily briefing.

The expanded Workspace is organized into Research, Assets, Monitoring, Source data, and Settings and sharing. It includes project onboarding, retained investigations, event dossiers, asset dependencies, a bounded Query copilot, professional geographic imports, scheduled collection, history comparison, forecast comparison, source configuration, explicit snapshot sharing and verified backup/restore.

War view has richer theater navigation, report filters, source-dated statistics and separate reported-loss figures where a source supports them. Weather, map observations and satellite tools have expanded too. Some previews require tester access, and many feeds depend on provider coverage or configuration. The guides explain the actual prerequisites beside each workflow.

Version 0.1.11 also includes the WideClarity homepage video on the first-launch welcome screen. The media is bundled with the app. Choose Get started to enter the workspace; dismissal is remembered. The welcome respects reduced-motion settings and provides a background pause control.

How to use it

  1. Use the workspace overview to choose the right destination.
  2. Try the new tester walkthrough with a disposable project.
  3. Inspect source dates and status before interpreting any map or figure.
  4. Back up existing work before moving it to a newer build.

Your first ten minutes as a tester

Check the main journeys and leave with a saved, reopenable piece of work.

Use a small test project and a place you know. A useful first session checks navigation, source clarity, one retained record and reopening saved work. Available feeds will differ by network, provider setup and source policy; record an unavailable status as an observation rather than substituting a result.

Start with the globe, then try one research workflow. Workspace can create the project directly. In Investigations, retain a permitted source observation when one is available and add your own note. If collection is unavailable, a saved note and its reopen behavior still give you a useful persistence check.

For a broader pass, visit War view, Strategic Intelligence and the Reports library. Read the relevant guide before configuring a provider, publishing a local report or creating a sharing link. Use Backup and updates when you want a verified recovery copy of your work.

How to use it

  1. Record your build revision, launch the app and sign in.
  2. In Intelligence, search for a city, move the globe, enable one relevant layer and inspect its source and date.
  3. Open Weather and inspect a field, model, level and valid time at that place.
  4. Open Workspace, choose New project, give it a clear test name and open Investigations.
  5. Save a note and, if available, retain one source observation. Close and reopen Workspace to check that the project and saved record return.
  6. Open one other destination—War view, Strategic Intelligence or Reports—and record what loaded, what needed setup and any error.
  7. Send the shortest reproducible steps for any problem, together with your build revision and the visible source status.

Understand access, source status and missing data

Tell a working tool, a gated preview and an unavailable feed apart.

The app includes tools and source catalogs, but a catalog entry does not guarantee a usable feed. A source may need credentials, an allowed provider endpoint, geographic coverage, an eligible product or model, a supported package component, or permission under the build's source policy. Open source details and read the stated reason before retrying.

Explore and Flight Radar can present a tester preview-access screen. Use access supplied by the team. Unlocking a preview does not supply third-party credentials or turn incomplete source coverage into a live result. The Windows 0.1.11 download includes the separate embedded Strategic Intelligence runtime; no separate Node.js installation is needed for that package. A source-development checkout needs its own runtime preparation.

Keep observation time, publication time, collection time and forecast valid time distinct. An old observation collected now remains old. Static inventories, geographic context and susceptibility maps describe their own dated datasets. Estimated, illustrative or simulated displays should be read with the qualifications shown in their details.

How to use it

  1. Check the destination and source status before interpreting an empty screen.
  2. Read the source's observation, publication or valid time and geographic coverage.
  3. If setup is required, use the relevant connection or Workspace → Sources and providers guide.
  4. Ask the team for authorised tester access if a preview is locked. If Strategic Intelligence reports a missing runtime, confirm you extracted the complete 0.1.11 package.
  5. Include the exact state and provider name in a bug report when the expected source still fails.

Download and open the Windows beta

Download the ZIP, extract everything, then open WideClarity.exe.

The download page supplies WideClarity 0.1.11 for Windows x64, prepared for Windows x64. Use the download page and the tester access supplied by the team. The ZIP checksum on that page lets you check that the file arrived intact; BETA-BUILD.json inside the extracted app folder identifies its version and source revision.

You need Windows 10 or 11, 64-bit, and Microsoft Edge WebView2 Runtime. After the download finishes, open Downloads, right-click the ZIP and choose Extract All. Choose a new, empty folder, like C:\Apps\WC018, then click Extract. Inside that folder, open WideClarity and double-click WideClarity.exe. Keep the whole folder together, including _internal. Do not run the app from inside the ZIP or move the executable out on its own.

The Windows package includes Python and the prepared Strategic Intelligence runtime. You do not need to install Python or Node.js to use this ZIP. Developers working from source should instead follow the setup instructions at their checkout revision and use python -m apps.intelligence in the prepared environment.

How to use it

  1. On the download page, enter your tester access if asked and click Download for Windows.
  2. Wait for the download to finish, then open your Downloads folder.
  3. Right-click the ZIP → Extract All. Choose a new, empty folder, like C:\Apps\WC018, then click Extract.
  4. Open the extracted WideClarity folder and double-click WideClarity.exe.
  5. Create or sign in to your local account, then choose Get started. If the app reports WebView2 missing, install Microsoft Edge WebView2 Runtime and open it again.

Your first Intelligence session

Build a focused view, read its evidence and keep what matters.

Start in Intelligence and allow the globe and source status to load. Search for a country or city, enable a few useful layers, and choose a reporting window. Inspect a mapped record or report to read its attribution and date instead of treating every visible marker as a current event.

Use My world to follow places and topics for your personal Today briefing. Use Workspace when you want a retained project, evidence, notes, monitoring or analysis. The report feed, Today, Daily briefing and analytical Reports have different purposes; the workspace guide explains which one to use.

How to use it

  1. Launch the app, sign in to your local account and finish the welcome screen.
  2. Choose Intelligence and search for a place.
  3. Open Map layers and enable a small selection relevant to your question.
  4. Choose a report window, inspect one result and read its source and date.
  5. Follow a place in My world or open Workspace to retain research.

Choose the right workspace

Find Intelligence, Strategic Intelligence, Explore, briefings, Reports and Workspace.

Intelligence is the main globe for public reporting, layers, weather, personal views and War view. Strategic Intelligence is a separate strategic globe with its own source and display controls. Explore is the geographic project editor for places, drawings, measurements and saved map projects; a tester access screen may appear first.

Daily briefing presents its own dated reporting feed. Tech news is the technology feed. Reports is the account-scoped analytical library where you can read, author, review and publish evidence-backed reports. Publishing there retains a local account publication; it does not automatically upload a public article.

Workspace opens a project and research dialog from the persistent Intelligence navigation or the map/Explore entry points. Start at Overview, choose or create a project, then select a tool in Research, Assets, Monitoring, Source data, or Settings and sharing. On smaller windows, use the compact navigation and Workspace tool selector.

How to use it

  1. Use the WideClarity workspace navigation, or open its menu on a smaller window.
  2. Choose Intelligence for the main globe, Strategic Intelligence for the separate strategic runtime, or Explore for map projects.
  3. Choose Daily briefing, Tech news or Reports for the corresponding reading workflow.
  4. Open Workspace for retained research and source tools.
  5. In Workspace, select a project and choose a tool; project-dependent tools explain when a project is required.

Navigate the Earth globe

Rotate, zoom, reset and inspect location without losing context.

Drag the Intelligence globe to move across the world and scroll to zoom. Globe navigation provides Reset globe, Zoom in, Zoom out and Full screen. The coordinate display describes the map center. Altitude is an approximate virtual camera height above sea-level Earth and changes with zoom and viewport size.

Layers reveal different detail at different scales. An enabled infrastructure category can remain hidden above its camera-height threshold, and coverage can change as the viewport moves. Search for a named location, then zoom and wait for source status to settle before inspecting a record.

How to use it

  1. Drag the globe and scroll or use Zoom in / Zoom out.
  2. Search for a place to frame a specific area.
  3. Select a visible object or report to open its details.
  4. Use Reset globe, or H outside text fields, to return to the overview.

Keyboard controls

Navigate the active map and use the focused control's keyboard behavior.

On the active full Intelligence globe, / focuses search, L toggles layers, R toggles the report panel and H resets the globe. These shortcuts are suppressed while typing and while a supported tool owns keyboard focus. Escape dismisses the current supported panel or selection.

In an authorised Explore preview, Ctrl+Z undoes a project change and Ctrl+Shift+Z redoes it outside editable fields. Escape cancels drawing or a tour. A focused weather slider supports Left/Right and Home/End for the available source range.

How to use it

  1. Click the map before using globe shortcuts.
  2. Use Tab to reach tool controls and Enter or Space to activate buttons.
  3. Focus the weather timeline and use arrow keys to step source frames.
  4. Use Escape to leave the active tool; check unsaved-change prompts before closing Workspace.

Build a focused layer view

Combine map context while keeping source availability and display limits visible.

Map layers combines the base map, public reporting, infrastructure, environmental products, traffic, orbital categories and additional thematic sources. Find a layer searches the catalogue; grouped controls and related-layer presets help start a focused view. Layer selection and actual source availability are separate states. All available and category master checkboxes toggle available catalogue choices; a mixed state means only part of the group is enabled.

Many infrastructure categories have camera-altitude thresholds. Some source products need an explicit area, provider settings, access approval or a historical date. A source may contain more records than the map can display; inspect partial coverage and omitted-record notices before treating a count as a complete inventory.

How to use it

  1. Open Map layers or press L.
  2. Search a product name or expand its category.
  3. Enable the layers required for one question.
  4. Use Ships & ports or Strategic infrastructure for a grouped starting point.
  5. Zoom, inspect a record and read Map settings & source status or the source's detail.

What to know

  • Heavy orbital layers also have workload controls in Settings; lower display limits do not change the source's underlying inventory.
  • A bulk layer toggle does not bypass the Flight Radar preview gate, provider setup or source policy.

Filter reports by time and search

Use the 24-hour, 72-hour and seven-day windows correctly.

The Intelligence globe's Reporting window offers 24H, 72H and 7D for dated reporting. Enabled layers and search can narrow the view further. Widen the window or clear search when an expected item is missing, and inspect Sources before interpreting an empty result.

This control is separate from Country news's configurable reporting-window hours, the weather timeline, War view's cutoff and source-specific filters, traffic observation age, orbital-element age and annual economic statistics. Selecting 7D does not refresh a stale position or make annual statistics current.

How to use it

  1. Choose 24H for a recent reporting view, or 72H / 7D for a wider publication window.
  2. Enable the relevant reporting layer and clear restrictive search text.
  3. Open a record and inspect its publication and location details.
  4. Use the relevant workspace's own time controls for Country news, weather or War view.

Explore strategic infrastructure

Inspect attributed site inventories at the scale where their layers appear.

Infrastructure layers include airports, military-base reference records, power plants, ports, refineries, LNG terminals, dams, bridges, rail terminals, water infrastructure, offshore platforms, telecom sites and power-grid detail. These are source objects with overlaps and incomplete coverage, not a census of unique operating facilities.

Many site categories appear below roughly 2,500 km virtual camera altitude; power plants and strategic sites below 600 km; grid detail below 100 km. Zoom thresholds describe map visibility. Source inventory dates, coordinates and attribution describe the record; none by itself establishes current activity or operating status.

Use Workspace Facility records for retained project facility/grouping work and Asset dependencies for explicit sourced relationships. Map proximity does not automatically establish that sites depend on each other.

How to use it

  1. Enable Strategic infrastructure or a specific category.
  2. Search a site or country.
  3. Zoom below the category's stated camera threshold.
  4. Select the source record and inspect its inventory date and attributes.
  5. Retain dated evidence separately before making an activity or dependency claim.

Read an infrastructure record

Separate mapped attributes from present-day operational evidence.

Select an infrastructure object to open Airport details, Military base details or Infrastructure details. When several records share a point, Choose a place lets you select the intended record. Available fields can include operator, owner, coordinates, listed capacity, fuel, inventory year and original source attributes. Airport records can include identifiers, runways and radio frequencies.

Expand All source attributes and inspect Sources & links, including Original inventory, any official website, inventory date and coverage. Missing fields remain missing. Public inventory can be outdated or incomplete: a listed runway status, military installation or plant capacity does not establish current operation or activity. Center on this location frames the supplied coordinates.

How to use it

  1. Select a visible infrastructure point or search result.
  2. If prompted, choose the correct co-located place.
  3. Read the supplied fields and expand All source attributes when needed.
  4. Open Original inventory or the official website for source context.
  5. Compare current dated reporting separately before drawing an operational conclusion.

Use thematic source layers

Browse environmental, infrastructure, civic and operational products with their actual coverage.

The thematic catalogue now goes well beyond the earlier connectivity and exposure set. It includes land cover, connectivity and cables, energy and trade context, humanitarian and political reporting, industrial and civic inventories, measured stations, space weather, regional transport operations and specialist environmental products.

Catalogue entries can be a distinct product, a filter or another view of one dataset. They are not a count of independent live feeds. A factory inventory, annual pollutant release, current measured sample, forecast and static susceptibility map answer different questions; inspect each product's dates, units, geometry and source terms.

Use Workspace → Source guide to discover coverage and setup requirements without initiating collection. Sources and providers manages supported provider configuration. Facility inventories, Transport operations and Space weather provide dedicated bounded collection workflows as well as eligible map layers.

How to use it

  1. Search Map layers for the subject or exact product.
  2. Enable a product and inspect its source state.
  3. Read source IDs, reporting period, observation time, collection time and location precision.
  4. Use the dedicated Workspace source tool when you need explicit collection bounds or provider setup.

What to know

  • Operational source layers support manual collection and retained evidence workflows; the separate RSS monitoring process does not automatically schedule every layer.

Read disaster and environmental context

Keep alerts, measurements, forecasts and static susceptibility distinct.

Environmental context includes GDACS assessments, earthquakes and volcanoes, fires and floods, drought perspectives, measured stations, satellite-derived products and static susceptibility. Each has its own source coverage, dates and quality. A selected map symbol can be a report or regional reference rather than an exact event location.

Static landslide susceptibility describes a published categorical tendency, not today's landslide probability. MODIS burn products retain source burn dates, uncertainty and QA; an unburned or invalid cell is not a missing positive event to invent. Source gaps and unavailable products remain visible.

How to use it

  1. Choose the specific environmental product in Map layers.
  2. Inspect its legend, source period and freshness.
  3. Open a feature to review quality, dates, geometry qualification and original attribution.
  4. Retain missing coverage and uncertainty when capturing the observation for an investigation.

What to know

  • The reporting window does not replace a product's own historical month, observation time or forecast validity.

Read conflict context and open War view

Keep public reports, historical places and delayed troop context distinct.

The globe retains distinct layers for Conflict & security, Hot zones · war monitoring, Places & sites · history, Military reports · 7 days and Troop context · ≥7 days old. The labels distinguish public reporting, historical geography and delayed context. Protests, Riots, Labour strikes, Armed conflicts, Reported attacks and Political unrest are separate event-reporting categories.

For the dedicated conflict workspace inside the globe, open War view from Map layers. It presents source-dated control/frontline assessments and reports with theater, date and coverage controls. Read location precision, source period, claim attribution and cached status. Published reports, belligerent claims, historical estimates and assessed control have different scopes; a connected source does not establish that an attack is ongoing.

How to use it

  1. Enable the specific globe reporting or historical-context layer you need.
  2. Read its time qualifier before selecting a record.
  3. Open War view for source-dated control, frontlines and theater reports.
  4. Read the source dates, location precision and coverage limitations.
  5. Follow original citations and keep claims distinct from independently established facts.

Inspect WorldCover land-cover classes

Read original categorical land cover rather than current land-use activity.

Land cover uses ESA WorldCover 2021 v200 at its native 10 m class resolution. Enable it from Map layers, adjust opacity or visible classes, and click a location to inspect the original categorical result. Class colours identify land-cover categories rather than numerical intensity.

WorldCover is a dated land-cover dataset. It does not establish present ownership, land use, crop condition or recent change. Raster display and point inspection have separate source states; no-data and a missing source response are not an inferred class.

How to use it

  1. Find Land cover in Map layers.
  2. Enable the product and read its dataset/legend.
  3. Adjust opacity or class visibility.
  4. Click a point to inspect the original class.
  5. Record the 2021 edition and source attribution in any retained evidence.

Inspect measured station histories

Load bounded dated samples with units, datum and quality flags.

Supported river gauges, tide gauges and weather stations open measured time-series details. Select a parameter and UTC interval, then Load observations. The chart and table retain measured values, units, source quality/provisional flags, datum and requested coverage.

Intervals are bounded to at most seven days in the station detail. A chart connects retained samples; it is not proof of continuous coverage between them. Different station datums must not be compared as absolute elevations, and missing samples are not zero.

How to use it

  1. Enable a supported gauge or station layer.
  2. Select a station and its observation detail.
  3. Choose a parameter and Start/End UTC within the supported interval.
  4. Choose Load observations or Cancel.
  5. Inspect the dated table, datum, quality and original source before retaining the result.

Read static landslide susceptibility

Use categorical source imagery with explicit dates and limits.

The static landslide-susceptibility layer displays validated categorical source pixels with their original classes and no-data. Opacity, Refresh and Cancel control the bounded viewport request. Sample-point and raster products remain separate views of their stated source.

This is susceptibility context, not an active landslide detection, current probability or live warning. Unknown dates remain unknown. Do not substitute it for an unavailable landslide nowcast or infer an event from a high class.

How to use it

  1. Search Map layers for landslide susceptibility.
  2. Choose the static raster product and read its source legend.
  3. Set the view and wait for the bounded source image.
  4. Use opacity, Refresh or Cancel as needed.
  5. Retain its static character and actual source date in analysis.

Open the Strategic globe workspace

Open the bundled Strategic globe and learn what to check if it cannot start.

Strategic opens a complete globe application inside WideClarity. It has its own data-layer browser, map sources, location search, media panels, scene tools and voice controls. The surrounding workspace keeps the current account identity.

The Windows 0.1.11 download already includes the prepared Strategic runtime and its Node executable. Extract the entire ZIP and keep its files together. You do not need to install Node.js, npm or Python to open Strategic in this packaged app. Opening the tab does not install packages or download a runtime.

Leaving the tab or hiding the application removes the embedded browsing context and stops its WebGL, polling and media work. Returning opens it again. Switching accounts discards the previous account's embedded view and runtime ownership.

How to use it

  1. Open Strategic from the WideClarity workspace navigation.
  2. Wait for Opening your strategic globe to finish.
  3. Use the location tray to search a place name or coordinates, then open Data Layers for the information you want to inspect.
  4. If it cannot open, read the message and select Try again. If the installed app reports missing preparation, check that you extracted the complete current ZIP and report the message with your build version.

What to know

  • If running a GitHub source checkout, prepare it separately with Node.js 24.14 or later in the 24.x line, or Node.js 26.x, plus npm, then python scripts/prepare_strategic_intelligence.py from the repository. An already prepared checkout can rebuild an outdated interface once with its installed dependencies; dependency changes still require preparation. Packaged apps do not rebuild themselves.
  • Commercial-pilot builds omit Strategic; the website's 0.1.11 tester build includes it.
  • A globe opening successfully does not establish that every external provider is connected. Read each feed's status, date and attribution.

Choose Strategic layers and read their status

Select information explicitly and distinguish loaded observations from unavailable feeds.

Open Data Layers to browse and search the available groups. Searching changes the visible choices; it does not select a layer or start its feed. Enable the layers you actually need and inspect their source and quality information.

The embedded runtime includes controls for flights, military-related flight data, satellites, traffic, CCTV, street-level imagery, radio, bikeshare, transit, AIS vessels, military awareness and installations, rocket launches and local ADS-B. It also has weather and recent-imagery surfaces. Presence in the layer browser does not promise observations at every location or a working provider connection.

Use location search and the map to narrow the area before enabling several expensive layers. Layer-specific panels expose their own transport, date, source and error states. Keep an unavailable or empty feed distinct from an area with no reported observations.

How to use it

  1. Open Data Layers and search the subject you need.
  2. Enable a layer with its selection control.
  3. Open its associated panel and read the provider, dates and status.
  4. Move or zoom the globe to the area you are testing and compare the map with the panel.
  5. Disable layers when they are no longer useful.

What to know

  • Provider credentials, quotas, coverage and network access can limit a layer.
  • The Strategic layer browser is separate from the layer browser in the Intelligence globe.

Connect Strategic providers

Add the credentials needed by a feed and understand the keyless defaults.

Provider Settings, presented by the Power up control when available, adds credentials for the embedded globe. Settings belong to the current account's runtime directory. Server-side credentials stay in that runtime; Google Maps, Cesium ion and Mapillary browser tokens are exposed to the browser by design and should have the provider's appropriate restrictions.

Google Maps unlocks photorealistic 3D tiles, place search and Street View. Cesium ion enables its imagery and terrain options. Mapillary enables its street-level imagery. Without Google photorealistic access, the normal Esri/OpenStreetMap fallback remains usable. The optional Google short-lived tile-token endpoint is unavailable in this integration.

AISStream needs a key for its vessel feed; NASA FIRMS needs a map key for active-fire detections. TomTom supplies real traffic, while the keyless traffic mode is a simulation. OpenSky credentials increase available polling credits; anonymous access is supported. Launch Library credentials increase its request allowance. The OpenAI entry is for Strategic voice control through an API key or supported ChatGPT sign-in.

How to use it

  1. Open Provider Settings in Strategic.
  2. Read the row describing what a provider unlocks and obtain your own credential if needed.
  3. Paste the credential in its matching field and select Save keys.
  4. Allow the local runtime to restart, reopen the layer and check its actual source status.

What to know

  • Credentials used elsewhere in the desktop environment are not automatically borrowed by Strategic.
  • A saved key can still fail because of provider restrictions, entitlement, quota or network access. Check the displayed error before reporting a missing feed.
  • Provider Settings is a local runtime feature and can be unavailable in unsupported serving contexts.

Inspect CCTV and street-level imagery

Open available cameras and imagery while keeping capture dates and source limits visible.

CCTV has its own enable control, camera selector, nearest-camera lookup, previous/next navigation and Focus action. Coverage, auto-hop and projection are separate controls. The source badge and metadata identify what the panel actually loaded.

Camera calibration exposes heading, pitch, field of view, range, mount height and north/east offsets. Save cal retains an adjustment and Reset cal restores it. These controls position a camera presentation; they do not establish that catalog coordinates or a live image are exact.

Street Level has provider chips, imagery-type and date filters, source attribution, capture date and a provider link. Open an available image from the map or use Open street view when offered. Expand enlarges the viewer, Fit preserves the whole image, Fill crops it and Follow connects the globe camera to the image's viewing direction.

How to use it

  1. Enable CCTV or Street Level from Data Layers.
  2. For CCTV, enable the camera feed and use Nearest or the camera selector, then Focus.
  3. For Street Level, choose a provider, adjust imagery/date filters and open an available image.
  4. Read the source and date before using the image as evidence; inspect empty or error states if no image appears.
  5. Close or disable the media view when finished.

What to know

  • Imagery and camera coverage vary by location, provider and credentials. A still image is not necessarily current live video.
  • Calibration controls and source quality labels should be included when reproducing a visual alignment problem.

Create scenes and choose a visual preset

Capture a repeatable globe sequence and keep display treatments distinct from sensor data.

Scene Director lets you choose a recipe, create a scene, capture or update shots and review the shot list. Start, Stop and Next control the sequence. Export presets and Import transfer supported scene definitions; Run log downloads the sequence log.

Visual Presets offers Normal, CRT, NVG, FLIR, Anime, Noir and Snow, plus a separate Map Source choice. NVG and FLIR are simulated visual treatments of the rendered scene. They do not provide night-vision or thermal sensor observations.

Location search accepts place names or coordinates. You can pin the location and visual-preset trays to keep them open while composing a scene. Scene playback and display presets do not make a provider feed more current.

How to use it

  1. Use Location to move the globe to your starting view and choose the relevant layers.
  2. Open Scene Director and select New or an existing scene recipe.
  3. Position the globe and select Capture shot; use Update shot for a selected shot you want to revise.
  4. Run the scene with Start and inspect the shot sequence; use Stop or Next as needed.
  5. Use Export presets to keep the scene definition and Run log when recording a playback issue.

What to know

  • Scene presets are definitions and view settings, not a promise that external live data is recorded into the export.
  • For a neutral inspection view, use Normal. Include the selected map source and visual preset in visual bug reports.

Use Strategic voice controls

Try the globe's implemented voice interface with the required provider and microphone access.

Strategic includes a voice dock, help, captions/results and an error tray, alongside model and session-cost controls for supported voice sessions. Voice can request supported globe actions and report results in context. It needs the corresponding voice provider access; opening Strategic alone does not start a microphone session.

The realtime voice session supports push-to-talk. A deliberate hold of Space on supported map surfaces can activate it, while text-entry fields and modified shortcuts have their own handling. Follow the current help hint and inspect the caption/result card to confirm what the app heard and did.

Strategic voice is separate from the Reports editorial library. Reports currently has no automatic audio narration or prose generation. Do not expect publishing a report to create an audio version.

How to use it

  1. Configure supported voice access in Strategic Provider Settings.
  2. Open the voice control and read its help and current model/cost settings.
  3. Start a session or use the supported push-to-talk gesture, granting microphone permission when the browser requests it.
  4. Give a bounded request, then inspect the resulting caption and action/result card.
  5. End the session when finished and record any provider or microphone error shown by the app.

What to know

  • Provider access and network availability determine whether a voice session can connect.
  • A session estimate is a model of usage, not a guarantee of the provider's final bill.
  • This guide documents implemented controls; it does not claim every natural-language request or audio backend will work in every installation.

Open War view and choose a theater

Explore source-dated conflict layers using one set of theater and map controls.

In the Intelligence globe, open the layer browser and select War view. The panel combines the Theater selector, geographic focus, report directories, source dates and layer visibility. It offers published assessments and reported incidents rather than a uniform live battlefield picture.

Choose a theater and use Locate to fit it. Featured-area shortcuts include Ukraine, Donbas, Southern Ukraine, Black Sea, Strait of Hormuz, Persian Gulf, Gulf of Oman, Marib, Taiz / Hudaydah, Red Sea and Saudi Arabia where the catalog provides them. Geographic focus and Show can narrow a theater further.

Use Layers & source dates to choose available overlays, adjust Overlay opacity and inspect the semantic legend. Minimize leaves the map usable while reducing the controls. Selecting a map feature or a report card opens the same dated source details.

How to use it

  1. Open Intelligence, open the layer browser and select War view.
  2. Choose a Theater or featured-area shortcut and select Locate.
  3. Choose a Geographic focus and select Show when a closer view is useful.
  4. Enable the available layers you need and read their source dates and notices.
  5. Select a feature or report to inspect its source, date and qualification; minimize the panel for more map space.

What to know

  • Unavailable geometry means missing qualified coverage, not an absence of conflict.
  • Naval and military movement reports are delayed regional publications, not live unit or vessel tracking.

Filter War view by source date

Use UTC cutoffs and report windows without confusing them with a historical replay.

Date cutoff (UTC) and Use date restrict War view to qualified source records through the selected day. Later records and undated geometry are excluded. Latest available removes the cutoff; it means the newest available source coverage, not independently verified current control.

Recent maritime events can use the past 24 hours, 7 days or 30 days. Conflict reports & strikes offers these windows plus Available source edition. An available edition may be historical. The map and directories preserve the dates and precision reported by each source.

Automatic public maritime checks pause while a date cutoff is active and while the view is inactive. Return to Latest available to use current report checking. War view's date controls filter retained/source records; there is no dedicated War time-playback timeline in this panel.

How to use it

  1. Open War view and choose a theater.
  2. Enter a valid day up to today in Date cutoff (UTC), then select Use date.
  3. Read the time note and layer reasons; a layer may have no qualified snapshot for that cutoff.
  4. Use the report-period selector for a narrower report window where offered.
  5. Select Latest available to leave the cutoff and inspect current source-check status.

What to know

  • A recent-period gap does not establish zero fighting or zero incidents.
  • Publication date, occurrence date and retrieval time are different fields. Preserve them when describing a report.

Check recent maritime reports and freshness

Review UKMTO reports, automatic checks and newly received records in supported theaters.

Recent maritime events uses public incident reports with original UKMTO occurrence dates. Attack reports, suspicious activity and advisories retain distinct classifications. The live controls check published reports; a connected status does not mean an attack is ongoing.

Live reports can check every minute, every 2 minutes or every 5 minutes. Check now performs a manual source check. Status distinguishes checking, source connected, partial, cached, unavailable, overdue and paused states. Automatic checks stop during a UTC date cutoff or while the view is inactive.

New reports only and Mark seen help inspect arrivals after the initial baseline. The first successful complete check establishes what was already present; cached, incomplete or cutoff results do not invent new arrivals. Show 30-day maritime attacks sets the report filter and fits the matching reports.

How to use it

  1. Choose a supported maritime theater, such as Iran & Strait of Hormuz.
  2. Read Recent maritime events and the current source-check status.
  3. Choose Period and Type, then use Check now or enable Live reports at your preferred interval.
  4. Use New reports only to inspect arrivals and Mark seen when reviewed.
  5. Select a report or Show selected reports on map, then open its original source and dates.

What to know

  • Delayed naval and movement reports are separate context and do not become live tracking when Live reports is on.
  • Report display rings emphasize records; they are not attack footprints, weapon ranges or minefields.
  • Cached records keep their original event dates. A successful refresh does not make an old incident current.

Read conflict, naval and military reports

Use report directories and inspect the original source behind each mapped record.

Conflict reports & strikes lists the available source edition or a selected recent period, with report categories and counts. Fit reports shows the matching geography; Latest report opens the newest available record. Counts describe source reports, not deaths, combat units or ongoing attacks.

Military reports is a directory of delayed regional naval and movement publications. Filter naval vessel type, movement type or movement domain when those controls are available. Select a card to read the same detail panel used by a map selection.

The detail panel retains the report classification, actor, region, dates and date precision, source location precision, source citation and available retrieval/cache information. A grouped map marker opens the individual records that share it. Its number is a count of grouped source reports, not current vessels or active attacks.

How to use it

  1. Choose the theater in War view.
  2. In Conflict reports & strikes, select Report period and Report type, then use Fit reports or Latest report.
  3. For naval or movement context, browse Military reports and apply the available filters.
  4. Select a card or grouped marker and inspect its report record, source and citation.
  5. Use Show on map if you want to locate that record, then follow the source link for the original account.

What to know

  • Where only a publication date is known, the UI says so; it does not manufacture an observation or movement time.
  • Regional reference coordinates should not be read as exact vessel or troop positions.

Read War overview and loss statistics

Keep belligerent claims separate from historical event and fatality datasets.

War overview combines distinct source scopes. For Ukraine & Russia, the loss section presents claimed Russian losses from a belligerent's source report. Report change shows the change since the previous source report; Cumulative shows the source's claimed cumulative totals. More equipment categories expands the remaining reported categories.

Read the actual Source report date and any notice that the selected day has no report. A delayed or cached source report retains its date and status. A negative change is identified as a source correction rather than treated as a battlefield gain.

Historical conflict context separately shows source-recorded events, estimated fatalities, civilian fatalities and unknown-attribution fatalities, with the source period and attribution. These are not interchangeable with the belligerent's daily claims. Statistics not available from connected sources are explicitly listed.

How to use it

  1. Open War view, choose a theater and inspect War overview where available.
  2. Read the source report date, claim label and any cached or delayed notice.
  3. Switch between Report change and Cumulative only within that source's scope.
  4. Expand More equipment categories and Historical conflict context when needed.
  5. Use Refresh statistics to request an update, then check its resulting date and status.

What to know

  • Comparable daily Ukrainian military personnel/equipment losses are not supplied by this connected claim source.
  • Unavailable values are unknown, not zero. The app does not infer casualty ratios, ammunition expenditure or financial cost from these reports.

Interpret Ukraine, Hormuz and coastal map symbols

Read boundaries, uncertainty and reference geography at the precision supported by the source.

Ukraine territorial overlays are dated source assessments. A Source territorial boundary can be derived from a territorial polygon and can include a coast or international border. It is not automatically an independently geolocated fighting line. The source catalog notes that Russian territory has no qualified control feed.

Reported conflict locations can be precise, approximate, administrative, regional, waterbody references or unknown. The legend and selected record retain these distinctions. Event radii are primarily screen-space emphasis; numeric location uncertainty is shown only when the source supplies it. They are not weapon or blast radii.

Iran & Strait of Hormuz separates recent maritime reports, delayed naval context, June 2026 source-reported strikes and geographic reference. Country outlines and static maritime corridors are context, not military control, safe routes or passage availability. The Coastal palette belongs to the Intelligence globe's map appearance and changes presentation rather than source meaning.

How to use it

  1. Choose Ukraine & Russia or Iran & Strait of Hormuz and enable the relevant layers.
  2. Read the map legend and Layers & source dates before interpreting a boundary or symbol.
  3. Select a report to inspect its location and date precision, original source and qualification.
  4. Toggle Event radii to compare emphasis with the underlying records where the control is available.
  5. Include the source date, layer, precision label and chosen palette when sharing a screenshot or filing a map issue.

What to know

  • Grouped reports and display rings must not be counted as present-day forces or attacks.
  • Static reference geography with unknown boundary vintage is excluded from date-cutoff views.

Read and verify a globe report

Inspect public reporting in the globe drawer and follow its original source.

Inside Intelligence, the Reports tab lists public reporting eligible for the enabled layers, search and reporting window. Select a headline to open Report details, including the supplied source, publication date and location qualifier. Center on this location appears when coordinates are available. The top-level Reports workspace is a separate analytical workspace; this guide covers the globe's reporting drawer.

A location can be a country-level reference or other geographic context rather than a verified incident address. Read the original source before relying on a claim. A collected or cached report can remain readable when its provider is offline, and related headlines do not establish independent confirmation. Use Country news for its dedicated publisher and language filters.

How to use it

  1. Open Intelligence and the Reports drawer, using Reports or R outside text fields.
  2. Choose the Reports tab, then select a headline.
  3. Read Published, Source and the location qualifier.
  4. Use Read original source to inspect the publisher's account.
  5. If the list is unexpectedly empty, widen the reporting window, clear search and inspect Sources.

Understand source status and freshness

Read provider health, collection times and coverage before interpreting missing or older data.

The Intelligence drawer's Sources tab separates report availability from provider health. Connected, Partial coverage, Cached data, Unavailable, Not requested and Disabled · Source rights review required describe different states. Reports available · provider status unknown means collected reports exist without a current provider-health claim. Last successful collection and Last check are separate from each report's publication date.

Read the source-specific detail and attribution links. Aircraft receiver coverage, received AIS messages, indicative shipping corridors, dated orbital elements, weather models, disaster assessments and annual economic statistics have different meanings and refresh patterns. Country news also provides its own Coverage & source status. Previously collected reports may remain available during an outage; source-policy restrictions can omit blocked records from visible briefings and exports.

How to use it

  1. Open Sources in the Intelligence drawer.
  2. Find the relevant source and read its status, detail and collection/check times.
  3. Compare those times with the selected record's publication, observation, forecast or reference date.
  4. Follow attribution links when you need the provider's definitions and coverage.
  5. Use Refresh for a transient failure; read setup requirements and cooldowns before trying again.

Build your personal Today briefing

Read a personal 24-hour briefing shaped by followed places and topics.

Today inside the Intelligence drawer combines Across the world, Following your world and New since your last visit. A chosen home city adds weather when viewing the present. Follow places and topics in My world to personalize the briefing. It uses a publication window of the previous 24 hours and retains attribution when related headlines are grouped.

New since your last visit measures when a development was observed on this computer, rather than when it was published or verified. Your first visit establishes the comparison baseline. During Observed history replay, Today shows archived reporting for the selected time and omits current home weather. Copy briefing exports the available source-linked reading list.

How to use it

  1. Open My world and follow a few places or topics.
  2. Select Today in the Intelligence drawer.
  3. Read the publication window, source dates and any cached/unavailable notice.
  4. Open a development for detail or choose Copy briefing.
  5. Return on a later visit to compare newly observed developments with the previous baseline.

Open the dedicated Daily briefing

Read the separate world-report workspace and its cited developments.

Daily briefing in the main workspace navigation loads the world report. It presents dated key events with source links, any tracked natural events, a report date and an update time. It is separate from Today, the personal briefing inside Intelligence, and has its own Refresh and unavailable states. Read any degraded-source message alongside the report.

When offered, Write a narrative summary makes an optional model call and caches the resulting narrative for the day. This action requires a connected Anthropic key and an available source/model configuration; the application can ask you to finish a current turn first. The narrative identifies its model and generation time. Treat the narrative as generated commentary and verify material claims against the linked sources.

How to use it

  1. Choose Daily briefing from the main workspace navigation.
  2. Read the report date, update time and any source limitation.
  3. Open source links attached to a key event.
  4. Use Refresh to request a new collection.
  5. If you choose Write a narrative summary, read the resulting model/date label and verify its claims against the cited reporting.

What to know

  • A source-rights policy can disable this workspace. A missing key or provider failure should be reported as that state, rather than interpreted as an empty news day.

Copy an attributed briefing

Copy the personal briefing with publication dates and original source links.

Copy briefing in Today places a text version of Across the world and Following your world on the clipboard. It includes the briefing timestamp, headline, publication date and attributed source URLs, preserving original headline/date differences where the grouped record contains that metadata. Duplicate groups are omitted from the second section.

This is a source-linked reading list rather than a full article export, project backup or proof of independent verification. The current source policy applies to the export. If clipboard access fails, the app offers selectable Briefing text to copy; review it before sharing, especially if your followed places or topics reveal a private workflow.

How to use it

  1. Open Today inside Intelligence.
  2. Choose Copy briefing.
  3. Read the copy confirmation.
  4. If clipboard access is unavailable, select and copy the offered text manually.
  5. Paste into your destination and check that the dates and source links remain intact.

Explore and filter Tech news

Filter technology reporting, save stories and inspect how the app ranks them.

Tech news is a dedicated workspace with 24-hour, 72-hour and seven-day windows. Filter by category, importance, search text, Verified only, New only or saved stories. Save on a story toggles a local bookmark. Search includes the headline, summary, mentioned companies, technologies and category; filter combinations can narrow the list to zero.

Open a story to inspect its publication time, original source, verification label, related coverage and score components. The drawer separates From the source (fact) from Calythe's read (analysis, not verified). The app's verified/corroborated labels and ranking scores are its processing results, not independent guarantees. Follow Read the original at the publisher before relying on a claim.

How to use it

  1. Choose Tech news in the main workspace navigation.
  2. Set a time window, category or importance and enter a search when useful.
  3. Open a story and inspect its source date, verification explanation and score breakdown.
  4. Choose Save to bookmark a story and use the saved-stories filter to find it again.
  5. Use Refresh or clear restrictive filters if the list is empty.

What to know

  • Bookmarks use local window storage. The New only filter compares publication times with the stored previous-visit timestamp. Feed requests can be unavailable or disabled by source policy.

Filter Country news and inspect event locations

Choose publishers, languages and topics while keeping source country separate from event geography.

Country news is a dedicated tab in the Intelligence drawer. Open the globe Settings panel for News settings: choose countries or individual sources from the searchable directory, enter comma-separated language codes or topics, then set the reporting window, report / map pin limit and refresh interval. Country selections describe the publisher's country; they do not mean every returned story happened there. Settings are retained for the local account.

Select a report to read the publisher, source country, event country, supplied publication/update dates, language, topic and location precision. Reports without valid supplied coordinates and declared map precision stay in the feed. Use Read original report and Publisher website to verify the source. Coverage & source status distinguishes a listed source from a working connected feed, and pagination keeps the current bounded result set manageable.

How to use it

  1. Enable the news layer and open Country news in the Intelligence drawer.
  2. Open Settings → News settings and browse Countries or Sources; use the directory search and page controls to find an entry.
  3. Set languages/topics and the reporting window, report / map pin limit and refresh interval, then choose Apply settings.
  4. Use Refresh now, read Coverage & source status and move through report pages.
  5. Select a report, inspect its source and location precision, and use Show event location on map when offered.
  6. Choose Reset filters when a narrow selection hides expected reporting.

What to know

  • The window supports 1–168 hours, the report / map pin limit 1–500 and the refresh interval 30–86,400 seconds. The feed states when results were limited. An empty result does not establish that no events occurred.
  • Collection pauses when the relevant workspace is inactive, the news layer is disabled or the document is hidden. A source directory entry is not a guarantee of complete or live coverage.

Find and read analytical Reports

Browse the account's editorial library, open an overview and follow the full analysis.

Reports is an account-scoped editorial library in the WideClarity workspace navigation. On a small screen, open the workspace menu first. It is separate from the live Daily Briefing. Publishing here retains a publication in your account; it does not automatically upload it to a public website.

Search report titles and central questions, then filter by Country, Topic, Report type, Editorial status and publication date. Country/topic tags open related-report views. The library shows the published edition and whether a newer working revision is still in draft or review.

A brief overview and full reading mode use the same retained document. The reader includes executive findings, chapter links, timeline, actors, conditional scenarios, sources and methodology, plus statistics or location sketches when supplied by the author. Citations and revision history are available from the reading view.

How to use it

  1. Open Reports from the workspace navigation.
  2. Enter a search or choose filters and select Apply filters; use Clear filters to reset.
  3. Open a report and read its author, current-as-of date and publication edition.
  4. Use the overview, full reading mode and chapter links to follow the argument.
  5. Open citation details and revision history to inspect the evidence and publication record.

What to know

  • An empty library is normal for an account with no reports. Select Create report to begin.
  • Reports currently supports manual authoring. Automatic prose generation, update watchers and audio narration are not included.

Draft an analytical report

Build a structured argument from typed claims, evidence and explicit uncertainty.

Create report starts a blank working document. Set a title, central question, author, countries, topics, report type and information-current-as-of date. Save draft preserves incomplete work; completion is required for the later review transition.

Write paragraphs as typed claims: facts, attributed claims, analytical interpretations or forecasts/scenarios. Assign claims to the appropriate chapters and choose 3–5 executive findings. A factual or attributed claim needs a supporting citation or an explicit unverified label.

Complete the seven chapter headings and methodology, then add an event timeline, actor interests/constraints and conditional scenarios where useful. Scenarios hold assumptions, a plausible development and observable watchpoints. They are labeled conditional, not predictions, and no probabilities are generated.

How to use it

  1. Open Reports and select Create report.
  2. Complete the report identity and current-as-of information.
  3. Add your source records, then write typed claims and attach the evidence relationships.
  4. Assign claim paragraphs to chapters and select 3–5 executive key findings.
  5. Add relevant timeline entries, actors, statistics, locations and scenarios, and explain the method and limits.
  6. Select Save draft while working; use Save and review when the document is complete.

What to know

  • Manual report production does not require generation-service credentials.
  • Saving changes to a reviewed document clears its review, so review the final version before publication.

Attach sources and inspect citations

Preserve provenance, support locations and the difference between support, contradiction and context.

Source records distinguish factual reporting, datasets, expert commentary, official statements/filings and visual assets. Retain the original publisher URL, publication/event dates where known and the actual retrieval timestamp. Add the original reporting origin for syndicated material when you can establish it; leave unknown dates unknown.

Citations connect a claim to a source with a document location and a relationship: supports, contradicts or contextualises. Open a citation in the reader to inspect the publisher, link, dates, location, permitted excerpt and relationship. A successful evidence check confirms required structure, not that a claim is true.

The manual source editor does not fetch full text. A short excerpt, up to 2,000 characters, needs explicit editor-attested permission; otherwise use a document location and link. Duplicate canonical source URLs are rejected. Declared origins group syndicated material, while independent corroboration is not inferred simply from different publishers or URLs.

How to use it

  1. In the report editor, add a source with its category, publisher, title, original URL and known dates.
  2. Record the actual retrieval time and original reporting origin when known.
  3. For each relevant claim, attach the source, supporting location and evidentiary relationship.
  4. Use an unverified label when a factual or attributed claim lacks supporting evidence.
  5. Open the reading view and click the citation to verify that its source and qualification are understandable.

What to know

  • Source registry entries describe possible institutions and access requirements; they do not mean a connector is installed or reuse rights have been granted.
  • Source URLs cannot contain credentials or target local addresses. Retrieved titles and text are displayed as data.

Review, publish and revise a report

Publish the reviewed document and preserve earlier editions while a new revision is in progress.

Save and review validates the complete document and opens the review stage. Review the reading view, claims, evidence, uncertainty and source rights before choosing Publish reviewed report and entering a publication note. Editing after review invalidates that review.

A publication is an immutable retained snapshot of the full report and evidence. To update it, choose Edit working copy and Start revision. The library and ordinary reader keep the last published edition until you review and publish the revision.

Revision history opens each retained edition and shows the editor's change note, publication timestamp, changed fields and snapshot hash. The current version has account ownership controls, but no separate multi-user editorial role service or enforced independent second reviewer.

How to use it

  1. Save a complete draft and select Save and review.
  2. Resolve any validation issues and read the report as a reader would, including citations and uncertainty.
  3. Select Publish reviewed report and add a clear publication note.
  4. For a later change, open Edit working copy and select Start revision.
  5. Edit, save and review the working copy, then publish the next edition with a change note.
  6. Open revision history to confirm both editions remain readable.

What to know

  • Publishing is local to the account; it is not automatic public distribution.
  • If the report changed in another window, reload the current record before saving or publishing to avoid overwriting newer work.

Add statistics and location context to Reports

Keep measures comparable and qualify every plotted location.

A statistical observation retains its value, unit, period, geography, dataset and source. Specify whether it is an observation, estimate or forecast, its nominal/real price basis where relevant and its total/per-capita basis. Assign it to the chapter where it supports the analysis.

The reader groups only commensurable measures and draws bars against a zero baseline. An attributed accessible data table accompanies the visual, so a reader can inspect the underlying values instead of relying on bar length alone.

Locations use WGS84 longitude and latitude, a source and a reported, approximate or disputed qualification. The reader provides a location sketch, legend and accessible coordinate list. It does not infer territorial boundaries or incident areas from those points.

How to use it

  1. Open Timeline, actors, statistics, locations and scenarios in the report editor.
  2. Add a statistic and complete its value, unit, period, geography, dataset, measure and comparison bases.
  3. Choose the statistic source and chapter.
  4. Add a location only when it helps the argument, entering longitude/latitude, qualification, source and chapter.
  5. Open the reading view and check the chart's attributed data table and the location coordinate list.

What to know

  • Avoid comparing measures with different units, periods or bases as though they describe the same quantity.
  • A location sketch is source-qualified context, not a military assessment or automatically generated boundary.

Import an NBP exchange-rate observation

Import one dated Table A currency observation and keep unavailable dates explicit.

Reports includes a bounded NBP connector for one Table A exchange-rate observation by three-letter currency code and effective date. It uses api.nbp.pl over outbound HTTPS and requires no API key. This connector does not provide general NBP macroeconomic data.

The import preserves the exact effective date, value, unit and dated source. Repeating the same import reuses the retained observation rather than adding a duplicate. It modifies an editable working copy; start a revision before importing evidence into a published report.

A non-publication day, unsupported currency/date, unavailable network or invalid response leaves report/source data unchanged. Weekends can have no Table A observation. GUS BDL, Eurostat and other registry links are not equivalent installed import adapters.

How to use it

  1. Open an editable report working copy and save any local changes before importing.
  2. Find Import NBP exchange rate in the source section.
  3. Enter the three-letter currency code and an effective date up to today.
  4. Select Import NBP observation.
  5. Inspect the imported dated source and statistic, or read the unavailable/no-observation message and choose another date if appropriate.

What to know

  • Outbound access to api.nbp.pl must be permitted. A restricted environment can block the connector while manual authoring remains available.
  • The commercial-pilot profile blocks unreviewed automated source use. Connector availability depends on the profile and network policy; no live success is promised by this guide.

Follow places and topics in My world

Choose the places and topics that shape your briefing and alerts.

My world in the Intelligence drawer brings together followed places, topics, an optional home city, weather units, alert preferences and history storage. Search Find a city or country to follow, inspect the matching place, then choose Follow. You can also follow from a city or country profile. Start with three to five relevant places or topics so the personal briefing remains useful.

The current app supports up to 20 followed places. Unfollow with the remove control beside a place and toggle topic buttons under Your topics. Preferences and observed history are scoped to this account and saved on this computer across restarts when persistent storage is connected. Read the storage status; session or browser backup availability does not guarantee that a persistent save succeeded.

How to use it

  1. Open My world from the drawer tab or globe toolbar.
  2. Search for a city or country and select Follow on the correct result.
  3. Choose topics under Your topics.
  4. Optionally choose a home city and weather units.
  5. Review the storage status, then open Today or Alerts to use your selection.

What to know

  • Reload saved preferences retries the stored state. If saved account data cannot be read, automatic saving can pause to protect existing data; recover it before retrying Refresh.

Set a home city and weather units

Add optional home weather and choose metric or imperial display.

In My world, search for a city and choose Home, or open its profile and choose Set as home. Home city is separate from Follow: choose the actions that match the briefing and weather you want. The current city's weather can appear in Today and its profile. Remove the home city with the control beside its entry.

Use Weather display → Units for Metric · °C, km/h, mm or Imperial · °F, mph, inches. Device location is optional and requested only after Use approximate device location. If location permission is declined or unavailable, select a city manually. Home weather can remain unavailable while other reports work; read its provider status rather than assuming a zero value.

How to use it

  1. Open My world and search for a city.
  2. Choose Home on the correct result, or Set as home in its profile.
  3. Choose Metric or Imperial under Weather display.
  4. Open Today to inspect the home forecast.
  5. Use the remove control to clear the home city, or choose another city to replace it.

Configure followed-place and topic alerts

Use the local alert inbox, priority thresholds and optional desktop delivery.

My world → Alert preferences controls Followed-place and topic alerts, Grouped digest or Priority delivery, a High severity and above or Severe only threshold, and quiet hours in device time. Open Alerts to read matching developments, open their details and mark an item or the entire inbox read. A first collection establishes the baseline rather than sending a flood of alerts for existing reports.

Enable desktop alerts requests the window's notification permission and selects priority delivery. Desktop delivery requires support, permission and an open active app session; it is not a notification service that runs after the app closes. Eligible priority events queued during quiet hours can be delivered after quiet hours while the session remains open. The inbox remains available when desktop permission is declined.

How to use it

  1. Follow places or topics in My world.
  2. Under Alert preferences, enable alerts and choose Grouped digest or Priority.
  3. Set the priority threshold and optional quiet hours.
  4. Choose Enable desktop alerts only if you want system notifications, then respond to the permission prompt.
  5. Open Alerts to review source-linked items and use Mark read or Mark all read.

What to know

  • Source availability and collection activity determine which developments can be observed. Closed-app push delivery is not implied by desktop alert permission.

Revisit locally observed event history

Replay reports this account collected on this computer without mixing in current layers.

The Observed event history toolbar control opens a replay slider. It shows when collection began and the available local coverage, retaining up to 30 days / 5,000 observed report snapshots within the storage bound. Choose a collected time to inspect what was available then. This is an archive of observations made by this app, not a complete historical news service or proof that an event occurred at collection time.

Current weather, fronts and infrastructure are hidden during replay so present-day context is not presented as historical data. Today and place profiles use archived reporting while replaying; current home weather and annual profile statistics are omitted. Now or closing the history panel returns to the present. My world offers Clear observed history where the source policy permits it; the current UI explains when account data controls are required instead.

How to use it

  1. Use Observed event history in the globe toolbar.
  2. Read the collection start and available coverage.
  3. Move the slider to a collected time and inspect dated reports or Today.
  4. Choose Now, or close the history panel, to return to current reporting.
  5. Check My world → History storage before clearing any local archive.

What to know

  • A first session may not yet contain enough history for replay. Account storage errors can pause saving to preserve previous data.

Save and restore globe views

Restore a named globe position with layers, palette, weather field and land-cover settings.

Saved views in the Intelligence drawer saves the camera position, enabled layers, palette, selected weather overlay and reporting window. Land-cover selection, opacity, version and reference year are also retained. Name a loaded globe view and choose Save current view; the app supports up to 12 named views with names up to 60 characters. Each saved card can be opened, renamed or deleted.

Opening a view returns to the present and requests the currently available data for those settings. It does not freeze report content or save every forecast model, altitude or timeline frame. Wait for the save confirmation; if persistent storage is unavailable, a change can fail to save across restarts. Saved views belong to the account's local personal state and are distinct from an Explore project's camera/tour data.

How to use it

  1. Frame a place and choose layers, colors, weather and reporting window.
  2. Open Saved views, enter a name and choose Save current view.
  3. Wait for the saved confirmation.
  4. Select the view's card to restore it at the present time.
  5. Use Rename / Save name or Delete to manage the library.

Read city and country profiles

Inspect a city's weather or a country's annual statistics alongside attributed reports and mapped sites.

Open a city or country profile from My world's search, followed places or home entry. Follow personalizes your briefing; Locate centers the map. City profiles offer Set as home and current weather. Country profiles offer Compare and Economy & population, using dated annual World Bank observations where available. Public conflict context appears when a matching cited context record exists.

Latest developments draws matching collected reports from the seven-day window. Selected mapped infrastructure is a representative airport/base shortlist, with city selections using a nearby 100 km area; it is incomplete and does not establish current operation. Read source links and years rather than interpreting a profile as a complete country assessment. During replay, the profile is marked Archived reporting and current weather, economy and conflict context are omitted.

How to use it

  1. Open My world and select a searched or followed city/country.
  2. Choose Follow, Locate, Set as home or Compare as appropriate.
  3. Read weather or annual statistics with their source status and reporting dates.
  4. Open a development or selected mapped site for detail.
  5. Use the original citations to verify claims or missing coverage.

Compare two countries

Compare two countries using independently dated World Bank annual observations.

Compare in the Intelligence drawer opens Two perspectives. Choose Country 1 and Country 2, or use Compare in a country profile to preselect the first side. The table includes GDP in current US dollars, population, annual GDP growth, consumer price inflation and unemployment as a modeled ILO estimate. Each value keeps its own unit, reporting year and available source link.

These are annual historical observations, not live rankings or forecasts. The app identifies different reporting years, cached figures and missing indicators. A blank value remains Unavailable rather than being inferred. Use Try again for a failed country catalog or Retry annual statistics when offered; one country's unavailable data does not make the other country's figures current.

How to use it

  1. Open Compare inside Intelligence, or choose Compare in a country profile.
  2. Choose Country 1 and Country 2.
  3. Read each indicator's value, unit, reporting year and estimate label.
  4. Check the different-year notice and source links before comparing periods.
  5. Use the offered retry control if a catalog or annual-statistics request fails.

Organize work in Workspace

Create a project and find the research, asset, monitoring and recovery tools.

Open Workspace in the Intelligence navigation. Its sidebar groups tools under Research, Assets, Monitoring, Source data, and Settings and sharing. Use Find a tool to jump to a panel.

Create and select projects inside Workspace. Investigations, Event dossiers, Query copilot, Asset imports, Asset dependencies, Facility records and Sharing require a project. Monitoring, History, Forecast comparison, source browsing and Backup and updates can open without one.

Explore has a local preview access gate in the current GitHub app. Ask the test organizer for access to its map tools. Workspace project creation, imported-data review, saved analysis and reports remain available without unlocking Explore. Showing an imported page on Explore requires the map to be unlocked, loaded and displaying the same project.

How to use it

  1. Sign in and open Workspace from the Intelligence navigation.
  2. Choose New project, enter its name and choose Create project, or select an existing project.
  3. Choose a tool in the sidebar or search Find a tool.
  4. Use Open project in Explore for drawings or map-specific work. Use current map selection refreshes the record available for capture.

What to know

  • Projects and retained records belong to the signed-in account. Check the Project selector before saving.
  • Supported unsaved drafts trigger a discard prompt when changing tools or projects.

Capture an observation as project evidence

Retain source attribution, dates, location precision and privacy choices.

Investigations stores source captures separately from your notes and conclusions. A saved capture remains unchanged when a live feed updates. Source facts can include measurements, units, provisional status and date qualifiers.

New captures are private by default and excluded from sharing previews. Unchecking Private capture only makes that new capture eligible for a later explicit preview; it does not publish it or change earlier captures.

How to use it

  1. Select a source record on a supported Intelligence or Explore map, then open Workspace and choose the project.
  2. Choose Use current map selection if the selected record is outdated.
  3. Open Research → Investigations and confirm the title and source facts.
  4. Review Private capture. Include retained source text is available only when the selected record supplies it and source permissions allow retention.
  5. Choose Capture selected evidence, then inspect Saved evidence and Dates, location and retained capture.

What to know

  • Source dates, location precision and content hash are distinct from the time you saved the capture.
  • Read permitted snapshot appears only when retained text exists and current policy permits access.
  • Source-policy restrictions can prevent capture, later access or export. Metadata does not grant reuse rights.

Write findings and export an attributed report

Create notes, PDF/DOCX reports or a Calythe research package.

Investigations separates Analyst note, Analyst conclusion and AI synthesis entries. AI synthesis is a saved-text label; choosing it does not call a model. Edit entry saves a revision.

Reports include checked evidence and saved notes, plus explicitly selected saved analysis. Choose an offline saved-geography schematic or a Current attributed map capture when the host supplies one. A Calythe context package downloads attributed context; it does not send a message or start AI research.

How to use it

  1. Open Workspace → Research → Investigations with the project selected.
  2. Choose Entry type, write Notes and findings and choose Save note.
  3. Check the evidence to include, using further pages when needed. Review Include saved analysis choices.
  4. Enter a Research question and Known coverage gaps. A question and selected evidence are required for a Calythe package.
  5. Choose Download PDF, Download editable DOCX or Export Calythe context package.
  6. Open the downloaded file and inspect its attribution, dates, map and coverage gaps.

What to know

  • Current attributed map capture is disabled when no map image is available; the offline schematic remains usable.
  • Exports normalize source links and label the change while saved captures remain unchanged. Recognized credentials or capability links can block export.
  • Review supporting evidence when including saved analysis.

Organize evidence into event dossiers

Group claims, inspect reporting lineage and retain organization history.

Event dossiers organizes existing project evidence locally without fetching sources or calling a model. Suggested groups are uncertain candidate event identities. Copied or syndicated reports do not become independent corroboration simply by appearing in one dossier.

Dossiers retain attributed claims, supporting evidence, time distinctions, source locations, reporting lineage and possible disagreements. No lexical conflict flagged is not proof of agreement. Private evidence makes the entire dossier private.

How to use it

  1. Capture project evidence, then open Workspace → Research → Event dossiers.
  2. Inspect Suggested event groups and Explain this suggestion. Read saved evidence before Save candidate dossier.
  3. For uncertain groups, use Manually organize selected unassigned evidence and confirm the original captures.
  4. Open a saved dossier and inspect claims, chronology, locations, lineage and unresolved disagreements.
  5. Add supported notes, corrections, disagreements, lineage clarification or qualified event time, selecting its supporting evidence.
  6. Use Merge existing dossiers or Split into separate events when needed. Inspect Immutable organization history before reversing an action.
  7. Optionally enable Automatic organization and apply its setting. Reconcile existing evidence now processes retained captures; future supported collection hooks can organize later evidence.

What to know

  • Automatic organization is off by default. Reversing dossier changes pauses it.
  • Merges and splits retain immutable history; incompatible newer edits block reversal.
  • Publication, observation, collection and event time remain distinct, including unknown/day-only precision.

Preview a query or project action

Use explicit targets, coverage checks and action confirmation.

Query copilot interprets bounded local plans for a project. Templates cover retained evidence, dossiers, potential exposures, project snapshots, retained replay/comparison, supported forecasts and map actions. It is not an unrestricted chat agent or automatic web research.

Choose a project feature, imported feature or registered asset. Time requests require explicit choices such as timezone, time basis or UTC valid instant. Preview identifies coverage gaps, source requests and unsupported choices before execution.

How to use it

  1. Open Workspace → Research → Query copilot. Choose a template or enter a supported request.
  2. Choose its project/imported/registered target, loading additional imported features if necessary.
  3. For a point query supply radius. Confirm calendar timezone and time basis; enter exact snapshot/source IDs or forecast choices where needed.
  4. Choose Interpret and preview. Resolve clarifications and read the plan. Read-only retained queries show results during preview.
  5. For an executable plan choose Run interpreted action and review the confirmation. Map changes additionally need the validated host preview and confirmation.
  6. Name useful queries, check the persistent-save confirmation and choose Save new reusable query. Load saved choices and preview against current data before rerunning.
  7. Undo a persistent action through its retained receipt, or Undo last map action while the map still matches its saved result.

What to know

  • Missing collections remain missing. Date-only publications are excluded from exact 72-hour publication-instant queries.
  • Map actions need a validated available host bridge. An unavailable bridge applies no map change.
  • Download selected evidence for Calythe research downloads an attributed package after explicit selection; it does not start external research.
  • Show selected analysis IDs for report export prepares IDs; central report/context export remains in Investigations.

Register assets and directed dependencies

Build a sourced registry from project or imported features.

Asset dependencies retains copies of project/imported features and explicit directed links. Direction is upstream supplier/supporting asset → downstream dependent asset. Geographic proximity never establishes a dependency.

Link provenance is User declared, Source supported or Suggested. Suggestions remain inactive until accepted. Assets/links default to private and inherit supporting-source and evidence restrictions.

How to use it

  1. Open Workspace → Assets → Asset dependencies with a project selected.
  2. Under Register original assets, select Saved project features or an imported dataset, then choose the original feature.
  3. Enter its name, notes and optional public attribution, review privacy and choose Save asset.
  4. Register another asset. Under Explicit directed link choose upstream and downstream assets.
  5. Choose relation/provenance, add dates, notes and supporting saved evidence, then Save directed link.
  6. For a reviewed suggestion choose Accept suggested link. Inspect graph and full paged asset/link lists.

What to know

  • Original drawings/imports stay unchanged; editing a registered asset keeps its original reference.
  • Editing a suggestion clears its acceptance and requires re-acceptance.
  • Graph and geographic-position views are offline schematics, not survey maps. Marker positions do not prove footprints, centroids or dependency.

Save a potential downstream exposure

Trace evidence through explicit active dependency paths.

Potential exposure traces a saved event assignment through your active explicit dependency graph. Assign saved upstream evidence to an asset; geometry alone does not make that assignment. An optional saved alert must explicitly target that exact upstream asset.

Results are immutable snapshots of graph paths, assets, sourced links and cause evidence at calculation time, preserved after later graph edits. They do not confirm upstream or downstream disruption. Read actual-disruption and coverage qualifiers.

How to use it

  1. Register assets and active directed links in Workspace → Assets → Asset dependencies.
  2. Under Compute potential downstream exposure choose the upstream asset and saved upstream evidence.
  3. Optionally choose an explicitly targeted saved alert. Load more evidence/alert pages when needed.
  4. Set Maximum dependency hops from 1 to 8, then Compute and save potential exposure.
  5. Inspect Immutable exposure snapshots, retained paths, provenance, dates and hop-limit warnings.
  6. Download selected exposure context (JSON), or select saved analysis in Investigations for a central report.

What to know

  • Inactive suggestions do not drive exposure; proximity does not substitute for an edge.
  • A hop limit means some paths are outside coverage.
  • A context download does not create a share, call AI or send a message.

Import a KMZ, Shapefile or GeoPackage

Preview layers, CRS, attributes and rejected rows before publication.

Asset imports accepts local KMZ, a ZIP containing a Shapefile set or GeoPackage. Upload stages the source; publishing creates an immutable chunked dataset without changing project drawings. Upload limit is 64 MiB; normalized publish limit is 60 MiB. Split larger data first.

The importer does not fetch source URLs, embedded remote resources, map layers or transformation grids. Supply the actual horizontal CRS using a known EPSG code or supported WKT. Do not guess an unknown CRS. Altitude/measure dimensions require explicit flattening to XY; vertical CRS conversion is unavailable.

How to use it

  1. Open Workspace → Assets → Asset imports with a saved project selected.
  2. Choose the local KMZ, zipped Shapefile set or GeoPackage and Upload local file.
  3. Select source layers and review each CRS. Supply the actual EPSG code or source WKT where unknown.
  4. If needed open Attribute mapping, encoding and dimensions. Rename fields with a JSON object, explicitly exclude fields, choose name/source-ID fields or set DBF encoding.
  5. Choose Prepare selected layers. Inspect geometry, attributes, progress and rejection reports, including further report pages.
  6. If accepting a subset acknowledge rejected rows. Check the layers/CRS/attributes/rights confirmation and Publish dataset atomically.
  7. Resume through Unfinished and recent imports → Open import, or Cancel import / remove staging.

What to know

  • Unsupported CRS/geometry, corrupt archives or invalid attributes can reject an import or rows; correct options/source and prepare again.
  • Example field mapping: {"NAME":"name"}. A detected DBF .cpg is used; otherwise the displayed default is UTF-8.
  • Staging previews cannot be placed on Explore.

Review, map and export a GIS dataset

Page through saved geometry or export the complete dataset.

Saved datasets have a paged attribute table and WGS84 geometry schematic without a live basemap. The count shows how much is currently visible. Download complete GeoJSON exports the saved dataset, not just its current page.

Show this page on Explore map requires a published dataset page and the matching account/project open in active unlocked Explore. It displays at most 50 features from that page, without adding them to project drawings or placing the entire dataset on the map.

How to use it

  1. Open Workspace → Assets → Asset imports and Refresh datasets and imports.
  2. Choose a saved dataset and Open selected dataset; More datasets extends the catalogue.
  3. Inspect the schematic and table, using Previous features and Next features.
  4. Choose Download complete GeoJSON for the full dataset.
  5. For map placement unlock/open Explore and the same saved project, then return to the Workspace dataset page.
  6. Choose Show this page on Explore map. Clear imported page from map removes its temporary display.

What to know

  • Schematic, paging and full export work without unlocking Explore.
  • Map controls remain disabled for staging, mismatched project/account, unavailable map or no saved page.
  • Imported features are available through saved references in Asset dependencies and Query copilot.

Group records that describe the same facility

Confirm a facility match while keeping original records and corrections.

Facility records groups existing registered project assets after your review. Start by registering imported or drawn features in Asset dependencies. This tool preserves original source snapshots, dependency edges and disagreements rather than erasing apparent duplicates.

Uncertain candidates are prompts for inspection, not verified identity matches. A confirmed group retains exact member snapshots and an explanation, and can be undone back into original records.

How to use it

  1. Register the relevant features through Workspace → Assets → Asset dependencies.
  2. Open Assets → Facility records with that project selected.
  3. Review original attributes and source dates, including Uncertain candidates.
  4. Select 2 to 20 original records that you have checked, give the facility a name and explain why they describe the same place.
  5. Choose Confirm selected records as one facility.
  6. Inspect Retained groups and corrections → Inspect exact original records, attributes and source dates.
  7. If the grouping is wrong, choose Undo grouping / split into original records. Saved groups can be selected in investigation report/context exports.

What to know

  • Already grouped records cannot be selected into another active group in this form.
  • If current member records later change or disappear, original grouping snapshots remain available and the change is flagged.
  • Nearby positions or similar names alone do not establish a confirmed match.

Create a monitoring rule

Watch supported news sources by topic or a saved geographic target.

Monitoring saves rules, collection status and an evidence-linked inbox for your account. Rules watch topics or targets offered by the picker, including followed targets, saved project features and supported selected or registered assets. Geographic targets are saved snapshots; editing the original geometry does not silently rewrite a rule.

Choose one to four registry sources and an interval from 300 to 86,400 seconds. Optional comma-separated keywords match any supplied term. Numeric thresholds can use matching report count, publication age in minutes or distance from the target in kilometres.

How to use it

  1. Open Workspace → Monitoring → New monitoring rule.
  2. Name the rule, choose Target snapshot and enter topic text when using Topic. The topic news matches all news.
  3. Select one to four Registry sources, set the interval, and add optional keywords, radius or threshold.
  4. Leave the rule enabled and choose Inbox for normal testing.
  5. Choose Save rule and inspect Rules and source health. Request check queues an enabled rule for the independent service.

What to know

  • Saving a rule does not start the independent collector.
  • Radius and area rules use exact/city precision by default. Optional explicit GeoRSS coordinate references have unknown incident precision and do not establish asset impact or incident extent.
  • Local test log delivery requires operator configuration. It is not email or push delivery.

Keep scheduled monitoring running

Understand the independent local collector and check its health.

Monitoring uses a separately started local process. It can collect while the desktop window is closed, but the computer must remain awake and the service must stay running. Saving a schedule does not create a cloud job; no AI model is required for collection.

An operator starts the source service with python -m gui.intelligence_monitor_service --database <existing intelligence-workspace.db>. A packaged Intelligence executable also supports --monitor-service --database <existing intelligence-workspace.db>. Use the actual database used by the app, not a new empty file. Optional --once performs one due cycle and exits.

How to use it

  1. Save an enabled monitoring rule.
  2. Have the operator start the independent service against the same workspace database.
  3. Open Workspace → Monitoring and choose Refresh.
  4. Confirm Service running and its last checked time. Review the rule's next run, last successful collection and per-source state.
  5. If the heartbeat is unavailable or the service is stopped, restart it and refresh before treating an empty inbox as a successful check.

What to know

  • Closing the service, sleeping the computer or shutting it down prevents collection.
  • A source outage and a successful check with no matches are separate states.
  • This module does not automatically install an operating-system service or remote host.

Review alerts and captured evidence

Read why a rule matched and inspect the saved source record.

Each alert links to captured evidence and explains the match, uncertainty and source dates. A geographic match may refer to a report location rather than a verified incident footprint.

The inbox is paged, and the unread count applies to the current page. Rules and source health show check status independently of the alerts on screen.

How to use it

  1. Open Workspace → Monitoring → Inbox.
  2. Read the rule name, match reasons, uncertainty, publication date and collection time.
  3. Choose View captured evidence to inspect its saved summary, capture time, storage permission and location precision.
  4. Open the attributed source if needed, then choose Mark read.
  5. Use Older alerts and Previous alerts for other pages. Use Saved rules to inspect source health.

What to know

  • An empty page does not prove nothing happened. Check the heartbeat, source state and rule settings.
  • Day-only publication dates retain day precision; unknown time is not converted into an incident time.

Replay and compare retained collections

Inspect what was actually collected and preserve coverage gaps.

History archives retained collections; it does not reconstruct unlimited past data. Monitoring can populate it. Capture selected observation retains one normalized record with its original collection time and partial coverage. Import my old personal observations imports supported existing personal observations into this account's history.

Compare chronological collections from the same source. Added, changed and removed records are separated from Not observed when incomplete coverage cannot establish removal. Exact-instant replay returns a retained collection or nearby earlier/later collections without interpolation.

How to use it

  1. Open Workspace → Monitoring → History and choose Refresh.
  2. Apply Collection source filter if needed. Choose Later snapshot, then an available Earlier snapshot of the same source.
  3. Choose Compare snapshots and page through changes. Read Not observed separately from Removed.
  4. Choose Replay selected collection to inspect the exact capture and coverage.
  5. For a direct time check, enter Replay source ID and Replay instant as an ISO UTC instant, then choose Check retained observation at instant.
  6. Open Retention and storage to inspect usage, save a retention policy or prune expired collections.

What to know

  • Retention supports 1–3,650 days and a 1–512 MiB snapshot-payload quota. Full quota rejects new collections and preserves existing snapshots.
  • Reducing retention can expire older collections. Deleting a collection removes its replayable observations.
  • Restricted records do not establish an empty source collection.

Compare two forecast models

Compare supported models at aligned locations and UTC valid times.

Forecast comparison aligns two explicit supported models by field, canonical units, altitude/pressure level, sample coordinates and UTC forecast valid time. Available fields and model pairs come from the app's catalogue and active source policy.

Delta means right minus left. Missing values remain missing. A comparison is refused if either adapter returns a different model than requested, or if field, units, level or sampled coordinates cannot be aligned. Initialization age is separate from retrieval age; unknown initialization times stay unknown.

How to use it

  1. Open Workspace → Monitoring → Forecast comparison and Refresh catalogue.
  2. Choose Forecast field, two different models and Altitude / pressure level.
  3. Enter coordinates or choose Use selected observation location.
  4. Optionally enter UTC forecast valid time as an ISO instant; choose the accumulation window for accumulation fields.
  5. Choose Compare forecasts. Review source, stale state, model initialization and retrieval age before reading the table.

What to know

  • Different initialization runs are labelled even when valid forecast times align.
  • The comparison does not interpolate locations. Pressure-level altitude labels are approximate.
  • An empty or restricted catalogue means no supported pair is available under current policy.

Check sources and configure a provider

Find coverage, permissions, setup requirements and connection status.

Sources and providers separates provider setup from source policy. Saving a key or enabling a provider does not override source restrictions or create an adapter that is absent. Credentials are kept in the operating-system credential store and are never read back into the form.

Source guide explains how to read layers and provides searchable source attribution, coverage, inventory dates, temporal semantics and rights links. A filtered parent inventory is labelled as a filter, not an additional independent source.

How to use it

  1. Open Workspace → Settings and sharing → Source guide. Expand the guidance and Browse source attribution and coverage.
  2. Search by source, layer name or coverage and inspect the original Source and Rights and attribution links.
  3. Open Sources and providers, search for the provider and expand its card.
  4. Read coverage, access, quota, adapter availability and any policy restriction before entering settings.
  5. Enable the provider if appropriate, enter required public settings and your authorized credentials, then Save settings.
  6. Choose Test connection and read the returned state. Reopen the corresponding source panel to inspect actual data.

What to know

  • Leave a saved credential field blank to keep it; use Remove saved to delete it. Backups include public settings but exclude secrets, so another computer needs credentials entered again.
  • Adapter installed does not guarantee current live-source availability. Adapter unavailable means setup alone cannot enable collection.
  • Credential forwarding for Explore satellite imagery is currently disabled; custom XYZ endpoints support public tiles only.

Inspect dated facility inventories

Collect a bounded inventory and read its original attributes and dates.

Facility inventories browses dated source records in a chosen geographic view. Inventory status, capacity, reporting year and collection time are not interchangeable with verified present activity. Missing records are not zero capacity or proof of inactivity.

The source detail preserves available facility identifiers, inventory period, source dates, coordinate method, precision, units and capacity caveats. Filters of a parent inventory do not count as independent sources.

How to use it

  1. Open Workspace → Source data → Facility inventories.
  2. Choose Source inventory and enter West, South, East and North WGS84 bounds.
  3. Choose Collect selected inventory, then read its state, coverage, legend and any required provider settings.
  4. Open a source-record button to inspect dates, attributes, units, precision and original source/terms.
  5. Use Refresh to collect again or Cancel collection to stop a pending request.

What to know

  • West must be less than east and south less than north; this form accepts a non-wrapped bounding box.
  • The Workspace request is bounded to 100 records. Check source coverage and limits before interpreting the displayed list as complete.
  • Provider setup and source-policy approval remain separate requirements.

Inspect transport operations for a geographic view

Collect qualified regional road, aviation, transit and port records.

Transport operations collects a selected source product for explicit WGS84 bounds. The current catalogue includes DriveBC, METAR/TAF/SIGMET, FAA airport programs, Washington work zones/freight, NaPTAN, WPI attributes, MBTA vehicle/ferry positions and alerts, plus setup-required WSDOT bridge/WSF terminal adapters. Coverage is regional and product-specific.

Read Coverage and setup boundaries. Vehicle locations are not complete trip status, route-only alerts may stay unmapped, WPI depths are not clearance, and inventories or activity counts do not automatically establish congestion, actual routes or individual port calls.

How to use it

  1. Open Workspace → Source data → Transport operations.
  2. Select the product and read its coverage and setup boundaries.
  3. Review the product's default West/South/East/North view or enter your own valid non-wrapped bounds.
  4. Choose Collect this view. Read state, mapped count, source-row count, excluded conflicts, missing geometry and whether output is capped.
  5. Open mapped or Unmapped record buttons and inspect the original attributes and source link.
  6. If a matching saved project and supported native map bridge are active, choose Show on native map. Otherwise collected source details remain available.

What to know

  • The collection request is capped at 250 records; missing or unmapped output is not evidence of no activity.
  • Setup-required products need the exact bounded settings and authorized access in Sources and providers, plus applicable policy approval.
  • Reported bridge/port values do not establish safe passage or route permission. Original uncertainty and accuracy flags remain relevant.

Read NOAA space-weather products

Separate forecasts, estimates and observations and inspect their own dates.

Space weather offers Aurora probability forecast, Planetary Kp forecast and estimates, NOAA space-weather scales and GOES solar X-ray flux. These are different products with distinct time qualifiers; global indicators do not locate an outage.

Record details preserve available observation/issue/valid dates, probability, units, satellite, energy band, quality and provisional flags. Read the source state and stale marker before interpreting a value.

How to use it

  1. Open Workspace → Source data → Space weather.
  2. Choose Space weather product; changing it requests that product. Use Refresh to retry or Cancel to stop a request.
  3. Read the returned state, stale-data notice and legend.
  4. Use Previous and Next to page through source records and inspect dates, qualifiers, measurements and Original source.
  5. For aurora probability only, choose Show aurora layer on map when a matching saved project and supported active map bridge are available.

What to know

  • The Workspace loader requests a bounded 300-record selection; the panel labels bounded source selection when provided by the source.
  • Forecast probability, estimated Kp and observed flux are not interchangeable measurements.
  • Unavailable, setup-required and disabled states are shown without inventing replacement records.

Create and revoke a read-only snapshot share

Review exactly what a local viewer link exposes.

Sharing creates an immutable read-only snapshot of explicitly selected project content. Private captures are excluded and source permissions still apply. Later project edits do not silently change a saved snapshot.

The link addresses a separate local read-only viewer, normally http://127.0.0.1:8766. It works while that service runs and is not automatically a public link. An operator can start the source viewer with python -m gui.intelligence_share_service --database <existing intelligence-workspace.db>. Packaged Intelligence also supports --share-viewer. Another computer requires separately configured hosting and HTTPS.

How to use it

  1. Open Workspace → Settings and sharing → Sharing with the project selected.
  2. Choose Load project content and check named features and eligible nonprivate evidence, paging as needed.
  3. Choose whether to include feature descriptions and permitted evidence text.
  4. Choose Preview exact content. Inspect its summary and Exact snapshot, including geometry and selected text.
  5. Set an optional expiry within one year, check the read-only access confirmation and choose Create share.
  6. Copy the private link immediately; it is returned only once. Use Existing grants → Revoke to block future access.

What to know

  • Changing selections invalidates the preview.
  • Keep the capability link private. A localhost link is not a hosted URL.
  • Revocation cannot recall already downloaded copies.

Save and verify a backup before updating

Download a private workspace backup and verify the saved file.

Backup and updates covers the current account's projects, saved views, appearance and retained records. Accounts, credentials, provider secrets and share grants are excluded. Store the private backup somewhere you control.

Downloading does not establish update readiness. Select the downloaded JSON file and verify it against current workspace state; later changes can invalidate readiness. Check for updates shows the published release and its notes. In version 0.1.10 and later, choose Install update & restart to download and install a verified compatible release. Backups remain a separate step before changing app versions.

How to use it

  1. Open Workspace → Settings and sharing → Backup and updates.
  2. Choose Preview backup and inspect included projects, records and saved views.
  3. Check I reviewed the backup scope and choose Save backup file.
  4. Select that downloaded JSON under Verify or restore a file, then choose Verify downloaded file.
  5. Choose Refresh backup readiness, then Check for updates; read the release notes and the checklist.
  6. Save your work and stop standalone monitoring/viewer services before choosing Install update & restart. For a manual installation, close the old desktop and extract into a new folder. Preserve existing config, account and credential stores.
  7. After restart, inspect projects, preferences and retained history.

What to know

  • Verification/restore accepts JSON files up to 256 MiB.
  • Workspace backup does not include sign-in or provider credentials; preserve their existing stores separately when replacing or moving the app.
  • This backup covers the main Intelligence workspace. It does not back up the separate Strategic runtime or its provider configuration.

Preview a restore and retain its rollback receipt

Review conflicts before restoring account data.

Merge keeps existing content and rejects conflicts. Replace matching IDs replaces matching items and preserves unrelated content. Restore is staged for review; it stays unavailable if the installation lacks its required helper.

A completed restore supplies a receipt. Preview rollback explains which affected records would be recovered or removed. This rolls back a restore's data changes, not an application binary or installer.

How to use it

  1. Open Workspace → Settings and sharing → Backup and updates and select the saved backup JSON.
  2. Verify downloaded file, then choose How to handle existing content.
  3. Choose Preview restore and read the overview, conflicts and helper-availability message.
  4. If the preview can apply, check its confirmation and choose Apply staged restore.
  5. Keep the Restore receipt ID and reopen projects to inspect the result.
  6. If needed, enter the receipt under Undo a previous restore, choose Preview rollback, review its scope and confirm Apply rollback.

What to know

  • Restore applies to the signed-in account and preserves unrelated projects.
  • If the workspace or preview changes, preview again.
  • Keep a verified backup before testing replacement or restoration.

Switch between Weather only and Weather + Intelligence

Choose focused weather or the combined map experience.

Settings → Globe experience offers Weather only and Weather + Intelligence. Weather only conceals and suspends unrelated reporting, traffic, orbital and project activity while preserving the appropriate map and weather experience. Return to the combined mode for geographic project geometry, reports and transport context.

The mode choice is remembered. It changes presentation and activity; it does not create missing weather observations, grant source permission or unlock the Explore preview.

How to use it

  1. Open Settings on the globe.
  2. Select Weather only for a focused weather map.
  3. Open Weather and choose a field.
  4. Return to Weather + Intelligence for combined context.

Find the right weather product

Choose by quantity, time and coverage instead of treating every catalogue entry as a live feed.

The current catalogue has 106 entries covering radar and satellite, wind and pressure, temperature and sun, rain and snow, clouds and visibility, waves and sea, air quality, warnings, soil and drought, extreme forecasts and fire danger. Search or expand a group, then read the field's capability and source note.

Configured product support still depends on the selected model, altitude, geography, time, provider response and source policy. Some catalogue entries remain explicitly unavailable. A similarly named product elsewhere in the thematic catalogue can measure a different quantity and does not silently enable an unsupported weather field.

How to use it

  1. Open Weather from the globe or Map layers.
  2. Use Find a weather layer or browse a category.
  3. Choose the exact quantity and read its description.
  4. Check enabled model/level choices, source coverage and valid time.
  5. Use Display & sources for controls supported by that product.

What to know

  • Catalogue support describes implemented integration, not a promise that all products are currently available worldwide.

Choose forecast model and altitude

Use only model, pressure and flight-level choices qualified for the selected field.

Model choices are product-specific. The catalogue includes Best match, ECMWF IFS, NOAA GFS, DWD ICON, UK Met Office, DMI HARMONIE and ECMWF IFS HRES where supported. For example, a regional cloud product and the 0–100 cm plant-available-water index can use different models from standard wind.

Near surface and supported pressure surfaces are different levels. Approximate pressure-level heights are not terrain-following or exact aircraft altitude. Aviation imagery has separate flight-level controls. Compare the same quantity, units, location, level and valid time; model run/initialisation time is separate.

How to use it

  1. Select a weather field.
  2. Expand Display & sources.
  3. Choose an enabled Forecast model and Altitude or Flight level.
  4. Check the displayed source and valid time.
  5. For a saved side-by-side comparison, use Workspace → Forecast comparison and its supported model pairs.

Explore weather time and playback

Use source frames, forecast ranges, speed and looping with clear timestamps.

The timeline offers observed radar and seven-day rain/cloud forecast presets as well as the current field. Forecast Range can be 24 hours, 3 days, 7 days or Full source; availability still stops at the actual returned source horizon. Previous/next buttons, day controls and the slider select available times.

Play supports 0.5×, 1×, 2×, 4× and 8× speed, with optional Loop. The return button reads Now for forecasts and aviation products, or Latest for observations. It returns to the appropriate current/default source frame. Playback buffers imagery and can hold a source gap; moving the camera pauses playback while coverage updates. Detailed model frame mode uses individual frame selection rather than timeline playback.

A timestamp may mean an observed acquisition, composite publication, forecast valid time or advisory time. It is not automatically a model run time. Weather time is separate from the globe's 24H/72H/7D reporting filter.

How to use it

  1. Choose the field or Observed radar/Rain forecast/Cloud forecast preset.
  2. Select Range for a forecast and inspect actual coverage.
  3. Use the slider, previous/next or day controls to choose time.
  4. Set Speed and Loop, then Play.
  5. Choose Now or Latest, depending on the product, to return to the current/default available frame.

What to know

  • With the slider focused, Left/Right steps frames and Home/End selects the range endpoints.

Inspect weather at a point

Read a supported numeric sample or image context with its time and source.

Click a location while a weather field is active to open its inspector. A supported forecast can show a numeric sample and a bounded forecast sequence at the point; a detailed native frame also identifies its model run. Field units, valid time, coverage and source remain part of the result.

Imagery and some specialist products have no numeric point value. Image colour is not automatically a measured scalar, and an empty pixel is not zero. Source gaps can hold a prior forecast and are labelled; use a supported numeric field for a numeric comparison.

How to use it

  1. Activate the required weather field.
  2. Select a location on the map.
  3. Read value, units, time and source together.
  4. Inspect the point forecast where provided.
  5. Close the inspector or press Escape to clear the selection.

Adjust weather units, labels and flow

Use supported display controls without implying extra source detail.

Display & sources contains units, opacity, Flow particles, Map values, Contour lines and supported isolines. Isolines can follow the current layer or supported pressure, temperature, geopotential-height and freezing-altitude fields. Radar also offers High source-tile detail or Auto to match the display.

Controls depend on the selected product. Flow represents a supported direction field rather than tracked air/water parcels; reduced-motion preferences can suspend it. City labels or interpolated colour do not create additional source measurements. Companion isolines may be unavailable at the selected time.

How to use it

  1. Open Weather → Display & sources.
  2. Set units and opacity.
  3. Enable supported Map values or Contour lines.
  4. Choose an isoline quantity and check its status.
  5. Adjust Flow particles and radar detail as needed for readability.

Read precipitation, snow and accumulations

Distinguish forecast amounts, probabilities and exact intervals.

Hourly precipitation, showers, probability, snowfall, snow depth and precipitation categories describe different things. Modeled thunderstorm categories do not replace a lightning-density observation. Snow depth is not new snowfall.

Supported accumulation controls offer 3, 6, 12, 24 or 72 hours. Forward accumulations use genuine source forecast intervals; missing required intervals do not become a valid total. Some separately titled variants describe trailing windows, so read the title, unit, interval and valid time together.

How to use it

  1. Select the precise precipitation or snow field.
  2. Read its unit and source description.
  3. Choose an enabled Accumulation window when offered.
  4. Select the timeline time and check the represented interval.
  5. Keep unsupported or incomplete coverage visible in comparisons.

Use radar and satellite imagery

Choose observed imagery with its source footprint, cadence and processing.

Radar uses RainViewer composites. Regional display smoothing and higher-detail tiles improve presentation while retaining the source's acquisition time and geography; they do not recover missing radar observations or supply a new numeric reflectivity reading. Missing radar coverage is not clear weather.

Satellite choices include a three-hour geostationary infrared mosaic, regional Meteosat visible/infrared products and original Calythe blue enhancement. Regional ten-minute imagery retains its Europe/Africa footprint and transparency; the global composite has source gaps and polar masks. NASA daily imagery remains a separately dated source where offered.

Publication time for a composite is not a per-pixel acquisition timestamp. Blue enhancement is display processing, not a numeric cloud-top-temperature product. Read the selected product's cadence, footprint, source and cached state.

How to use it

  1. Choose Weather radar or a satellite entry.
  2. Select an imagery variant when offered.
  3. Read the current frame time and coverage.
  4. Use the timeline to compare original available frames.
  5. For radar, try High or Auto image detail in Display & sources.

What to know

  • Imagery products do not provide universal numeric point measurements.

Inspect waves, swell and sea conditions

Read marine quantities and source coverage without filling ocean gaps.

Waves & sea includes waves, primary/secondary/tertiary swell, wind waves, corresponding periods and directions, sea-surface temperature, supported total currents and derived deep-water wave power. Height, period, speed and power are different quantities; read units and derivation.

Coverage depends on the product and provider. Tidal and non-tidal current variants have no qualified menu feeds. A missing coastal cell or land pixel is uncovered data rather than calm seas. An AIS ship observation supplies separate transport context, not a marine forecast.

How to use it

  1. Open Waves & sea in Weather.
  2. Choose the exact height, period, direction, temperature or current product.
  3. Check source, units and valid time.
  4. Select an ocean point when numeric inspection is supported.
  5. Read gaps and source limits before comparing coasts.

Read air quality and atmospheric products

Distinguish modeled surface concentration, indices, mixing ratios and total columns.

US AQI, PM2.5/PM10, nitrogen dioxide, surface sulphur dioxide, ozone, dust, aerosol and carbon monoxide are different quantities. Most are modeled atmospheric forecasts rather than local station measurements. US AQI uses its own index bands; carbon monoxide is a source-standardized near-surface mixing ratio in ppbv.

Total ozone uses qualified NOAA GFS whole-atmosphere model output in Dobson units with native model/run context. It is distinct from CAMS surface ozone and from the unsupported total-column SO₂ menu entry. A missing pollutant frame is not clean air.

How to use it

  1. Choose the exact pollutant, index or column quantity.
  2. Read its title, unit and definition.
  3. Check surface versus full-column scope and model/valid time.
  4. Inspect source and coverage; use Detailed model frame only where qualified.
  5. For actual measured air-quality stations, use the dedicated station layer and its observation timestamps.

Read warnings, storm tracks and avalanche bulletins

Open the original issued guidance and respect its validity and coverage.

Weather warnings · NWS maps latest active warnings with supplied polygon geometry for the United States and NWS-served territories/marine areas; warnings without geometry are counted separately. Hurricane tracker · NHC uses current NHC/CPHC advisories for the Atlantic, eastern Pacific and central Pacific. It is not a worldwide cyclone archive. Forecast lines connect issued forecast points, while center-track uncertainty cones appear only where supplied for a matching advisory.

Avalanche danger uses official Tirol, South Tyrol and Trentino bulletins. The map summarizes the maximum issued EAWS danger across elevation bands and earlier/later periods. Select a region for those distinctions and the official bulletin. Future bulletins remain hidden until valid, expired ratings disappear and unreported/out-of-season regions have no data. A regional overview does not describe every slope; a storm center-track cone is not a hazard area.

How to use it

  1. Open Weather and select Weather warnings · NWS, Hurricane tracker · NHC or Avalanche danger.
  2. Check the stated coverage and current validity/source time.
  3. Select a polygon, storm feature or avalanche region for detail.
  4. Open the official warning, advisory or avalanche bulletin for its full scope and instructions.
  5. Treat absent mapped geometry as missing or out-of-scope coverage rather than an all-clear.

Use detailed native model frames

Select qualified source frames while keeping decoder and coverage requirements visible.

Forecast detail offers Standard timeline and Detailed model frame for eligible products. Native support is checked for the selected field, model and level; the app uses dated manifests and qualified frames. The model run and valid time remain distinct.

Native decoding and staged specialist deliveries depend on the installed build and configured source. Missing, unqualified or unsupported combinations remain unavailable. Detailed model output has provider-defined resolution and is not a guarantee of higher observational accuracy.

How to use it

  1. Select a field with native-frame support.
  2. Open Display & sources → Forecast detail.
  3. Choose Detailed model frame.
  4. Select an enabled model/level and published time.
  5. Read the frame status; return to Standard timeline when the native combination is unavailable.

Resolve missing, cached or setup-required weather

Use source states to recover without substituting another quantity.

A configured product can fail for the current region, model or time. Read partial, cached, outside-footprint, unsupported, setup-required and provider-error messages. Dated cached output can remain after a transient failure with its original age. A source-policy denial can remove an observation.

The weather catalogue explicitly retains unqualified products such as lightning density, thermals, tidal/non-tidal current variants, extreme-forecast indices and several soil, drought and fuel-moisture quantities. A related source layer is not automatically an equivalent weather integration. Source guidance explains required adapters, permissions or qualification.

Refresh respects provider cooldowns and retries; repeated clicking is not a way around access or rate limits. Provider credentials belong in supported secure settings, never browser URLs or public reports.

How to use it

  1. Read the exact field's state and coverage note.
  2. Check model, level, time and footprint.
  3. Use Refresh for a transient problem, then respect the retry message.
  4. Try a supported quantity only when it answers your question.
  5. Use Source guide and Sources and providers for permitted setup.

Read aviation icing and turbulence products

Use qualified flight-level imagery with its issued and valid times.

Icing and turbulence use NOAA WAFC Washington WAFS products with product-specific flight-level selection. The regular Forecast model selector does not choose an alternative aviation model. Read the selected flight level, issue/run context, valid time and footprint. These products are separate from the public Flight Radar preview and its received aircraft positions.

Aviation imagery is not a universal numeric point observation or a complete briefing. Missing or expired source frames remain unavailable. Open the official product guidance and retain its coverage and validity limits.

How to use it

  1. Choose Icing or Turbulence in Weather.
  2. Select an enabled Flight level in Display & sources.
  3. Choose a qualified time and inspect its legend.
  4. Read issue/validity/source details.
  5. Use official guidance for the underlying advisory context.

Distinguish soil, drought and fire products

Compare the same quantity, depth and status instead of substituting related indicators.

Surface soil moisture, ground temperature, evapotranspiration and the ECMWF IFS 0–100 cm plant-available-water index describe different quantities. The plant-available index is not simply volumetric water content. Read depth, model, unit and source definition.

The additional thematic catalogue includes a separately named GFS 0–40 cm volumetric profile and GWIS KBDI. The profile derives thickness-weighted water from 0–10 cm and 10–40 cm source layers; it is neither plant-available water nor an anomaly/drought classification. These products do not silently enable the unqualified similarly named weather-menu entries.

Several moisture-anomaly, drought-intensity, fire-weather and fuel-moisture products remain unsupported or setup-dependent. Use Source guide and product states to identify the exact integration and qualification rather than assuming a related index is equivalent.

How to use it

  1. Choose the exact quantity and depth in Weather or Map layers.
  2. Read units, model, forecast/observation status and valid time.
  3. Inspect the product's source/coverage note.
  4. Compare only compatible depth and definitions.
  5. Keep unsupported or pending-live-qualification limits visible.

Browse the Flight Radar preview

Request preview access before using public civilian aircraft observations.

Flight Radar is currently marked unstable and opens behind an access-code preview gate. Authorised access is local to the active account/workspace and is not a permanent unlock. Enabling aircraft or helicopters does not bypass this gate.

Once authorised, the civilian browser uses public adsb.lol observations. Search callsign, registration, model, operator or identifier; filter inferred categories and reported air-object types, altitude and sort order. Map display options include All available or limits of 500, 1,000 and 5,000.

Receiver coverage and viewport scans can be partial. Source-flagged military or privacy-restricted broadcasts are excluded. Model/operator categories are evidence, not verified flight purpose; routes and airports are not supplied by this broadcast feed.

How to use it

  1. Open Flight radar.
  2. Use authorised preview access if offered; otherwise leave the feature locked.
  3. After access, search and choose category/object-type filters.
  4. Set altitude, sort and display limits.
  5. Check coverage and observation age before interpreting gaps.

What to know

  • Ask the test coordinator for preview access rather than including codes in screenshots or bug reports.

Inspect and follow an aircraft or ship

Understand last-received position, trail and identity evidence.

Select an aircraft or received ship observation from the map or its browser to open Traffic details. Aircraft detail includes available callsign/registration/model, altitude and reference, ground speed, vertical speed, heading/ground track, observation age, source and category evidence. Center aircraft, Follow aircraft and Show/Hide trail control the view; the trail contains observations collected while this app was open.

Ship detail includes received MMSI/IMO/callsign, self-reported AIS type, observation time, position, speed, heading and reported destination where supplied. Center ship and Follow received positions use new received reports, with following unavailable when the current view cannot support it. Positions are not predicted beyond the latest observation. A tanker type does not prove carried cargo; military AIS type is self-reported, and missing type/ownership stays unknown.

How to use it

  1. Open Flight radar or Ship radar and choose an observation, or select its map symbol.
  2. Read the timestamp and source alongside the supplied identity and movement fields.
  3. Choose Center aircraft / Center ship to frame the report.
  4. Use the relevant Follow control and stop following when finished.
  5. For aircraft, toggle the observed trail and inspect category evidence before interpreting a flight purpose.

What to know

  • Aircraft broadcast coverage and AIS receiver/transmission coverage are incomplete. Route/airports are not supplied by the aircraft broadcast feed. No reports does not establish empty airspace or sea.

Filter received AIS ship reports

Keep browser limits, map limits and source coverage separate.

Ship browser searches name, MMSI and IMO and filters reported cargo, tanker, passenger, military AIS 35, fishing, tug/support, pleasure, other and unknown categories. Map limits are 100, 300, 1,000 or 2,000; the browser independently lists 25, 50, 100 or 200 results.

The browser reports collected, matching, enabled-by-layer and allocated-to-map counts separately. A record can match a search while its layer or viewport prevents drawing. Reports cover a bounded collected region; pan and inspect source status for another area.

Unknown type means incomplete identity, not unavailable position coverage. Military means self-reported AIS type 35, not verified service. Tanker does not establish actual cargo.

How to use it

  1. Connect a permitted AISStream key through Traffic sources.
  2. Open Ship browser.
  3. Search a name/MMSI/IMO or choose reported categories.
  4. Set separate browser and map limits.
  5. Select a report and read its observation time and source.

Connect or disconnect AISStream

Store maritime credentials through the active account's secure connection controls.

Public ship observations require your own authorised AISStream API key. Traffic sources provides an AISStream password field, Connect ship feed and Disconnect. The local backend uses the current account's secure credential store.

A connection does not establish complete global coverage. Receivers, transmissions, provider limits, bounded collection and source policy determine returned observations. Keep the key out of projects, URLs, screenshots and support reports.

How to use it

  1. Obtain an AISStream key permitted for the intended use.
  2. Open Traffic sources/Air & sea traffic.
  3. Enter the key in AISStream API key and choose Connect ship feed.
  4. Check connection status and pan to the intended region.
  5. Use Disconnect to remove the connection through the app.

Interpret shipping corridors

Use static routing geography separately from live AIS positions.

Global shipping corridors draws a static indicative maritime routing network from Eurostat SeaRoute / MARNET. Enable it in Map layers and select a visible connection to read the dataset date, attribution, license and methodology link. It can provide geographic context beside received ship observations.

These lines are routing connections rather than a ship's current voyage, measured trade volume or navigational advice. Changing the reporting window does not make the static network current. Use received AIS positions for dated vessel observations and the corridor's own source date for the network.

How to use it

  1. Enable Global shipping corridors under the air/sea traffic layers.
  2. Pan and zoom to the maritime connection of interest.
  3. Select a visible corridor and read its source and dataset date.
  4. Open Dataset & methodology for its definitions; inspect AIS reports separately.

Choose satellites and Starlink on the map

Browse inventory, select objects and distinguish catalogue metadata from usable orbits.

Satellite catalogue is a searchable inventory with category, country/source code, operator/source code, orbit regime, orbital-element status and map-selection filters. Group or sort records; use category masters or Select matching/Clear matching for explicit map selection. Category masters cover the entire category, independently of browse filters.

Catalogue membership, source metadata, usable orbital elements and drawn objects have distinct counts. Positions are propagated estimates from dated source elements, not receiver observations or verified operational status. Older and unavailable elements remain labelled, and an unpositioned identity can remain browsable.

Starlink offers All available or one of the latest published launch groups. Apply the chosen group and use its view action. Settings → Layer performance controls workload, labels, selected orbit trail and update frequency; full selection can still be culled by the globe view or lack usable elements.

How to use it

  1. Open Satellite catalogue from the globe tools.
  2. Search name, NORAD number, operator or country.
  3. Refine filters and inspect element age/source attribution.
  4. Select records, a category or all matching records for the map.
  5. For Starlink, choose All available or a launch group, apply it and open the view.
  6. Refresh source elements when needed and check older/cached labels.

What to know

  • Separate catalogue, usable, selected and visible counts; none is a count of currently operational satellites.

Use the Explore project preview

Create local geographic work after authorised preview access.

Explore is currently a gated preview in Intelligence. It shows an instability notice and requires authorised access before its geographic tools initialise. Unlocking is temporary for the current owner/account context; switching accounts resets access.

Once available, projects hold geometry, folders, camera settings and tours in the current account's local storage. New, Duplicate, Delete and Project name manage projects. Wait for Saved and use Retry save on failure. Projects are not automatically cloud-hosted.

Workspace can create/select a geographic project independently of opening the Explore map. Its Open in Explore action still respects preview access and project-save checks.

How to use it

  1. Choose Explore and use authorised preview access if available.
  2. Choose Weather + Intelligence for project tools.
  3. Open Projects → New and name the project.
  4. Add features or camera views.
  5. Wait for the saved revision before switching projects or closing.

What to know

  • If access is unavailable, use Workspace project workflows that do not require the Explore map and report the restriction to the coordinator.

Draw places, paths and areas

Create and edit geographic geometry with undo and coordinate checks.

The Explore toolbar provides Select, Place, Path / distance and Area. Open a project, choose a geometry tool and click positions; use Finish for a path or area. Select the feature to edit its name, description, color, folder and source URL. Visible vertex handles can be dragged, and Edit coordinates / source exposes the GeoJSON geometry with an Apply geometry action.

GeoJSON uses WGS84 coordinates in longitude, latitude order, within ±180 and ±90. The app validates geometry, including polygon rings and holes, rather than silently accepting invalid shapes. Undo and Redo revise project edits. Keyboard Ctrl+Z / Ctrl+Shift+Z (or the platform equivalent) works outside text fields; Escape cancels drawing or the current tool.

How to use it

  1. Open or create an Explore project.
  2. Choose Place, Path / distance or Area and add positions.
  3. Use Finish for a path or area, then Select the feature.
  4. Edit attributes or drag the visible vertex handles; use Apply geometry after a coordinate edit.
  5. Use Undo / Redo and wait for the save status before leaving.

What to know

  • These project tools require authorised Explore preview access. Provider setup is separate from the preview gate and does not unlock it.

Measure geographic distance and area

Read geodesic map measurements in metric or imperial units.

Explore calculates geographic path length and polygon area from the selected feature's coordinates. Choose Metric or Imperial under Measurement units; path display uses distance and area features use area. Multi-line and multi-polygon geometry is also measured when valid. Polygon holes are subtracted and invalid or self-intersecting geometry is rejected.

The measurement model uses a WGS84 authalic sphere and shortest great-circle edges. Results are approximate geographic measurements, not survey boundaries, road routes or terrain-following distances. A drawn path over a hill measures mapped segments rather than the walking distance over the surface. Correct the geometry before interpreting a surprising value.

How to use it

  1. Create or select a path or area feature in Explore.
  2. Read its measurement in the feature panel.
  3. Choose Metric or Imperial under Measurement units.
  4. Refine the vertices or GeoJSON geometry and check the revised result.

What to know

  • These project tools require authorised Explore preview access. Provider setup is separate from the preview gate and does not unlock it.

Organize project features with folders

Keep large geographic projects readable and control visibility.

Explore folders organize places, paths and areas in a project. Enter New folder name and choose Create folder, then assign a selected feature using its Folder control. Folders can be renamed, nested and hidden. Folder visibility also controls descendants, so a feature can remain hidden when its own visibility is on but an ancestor folder is hidden.

Deleting a folder moves its features and child folders to the deleted folder's parent rather than deleting the geometries. Use Project export to keep the complete folder hierarchy alongside camera settings and tours. Geometry-only exports serve a different interchange purpose.

How to use it

  1. Create a folder in the Explore project panel.
  2. Select a feature and set its Folder.
  3. Rename or choose parent folders to organize larger projects.
  4. Use folder and feature visibility to focus the map.
  5. Export Project when sharing the organized workspace.

What to know

  • These project tools require authorised Explore preview access. Provider setup is separate from the preview gate and does not unlock it.

Import project geometry or a professional GIS dataset

Use the ordinary project importer or the separate reviewed GIS path.

The ordinary Explore Import file accepts JSON/GeoJSON, basic KML, CSV and portable project files. It previews incoming features before Add to project. Portable projects reopen as new local projects with geometry, folders and tours, excluding ownership and credentials. This path retains its 8 MiB file and 1,000-feature import bounds.

Professional GIS imports is a separate Workspace → Asset imports path for KMZ, complete zipped Shapefile sets and GeoPackage feature tables. It provides layer/CRS/field mapping, validation, publication and bounded dataset browsing. It does not remove the ordinary geographic project's feature limit.

Use the importer matching your format. Do not rename extensions to bypass validation. Raster datasets and unsupported geometry/CRS conversions need a separate supported workflow; professional GIS is not arbitrary archive extraction.

How to use it

  1. For simple geometry, open the authorised Explore project and choose Import file.
  2. Review the ordinary preview and add or cancel it.
  3. For KMZ/Shapefile/GeoPackage, open Professional GIS imports or Workspace → Asset imports.
  4. Choose the source layer and review CRS, mappings and validation before publication.
  5. Use the dataset's explicit page/overlay controls rather than assuming every retained row is drawn at once.

What to know

  • Explore map access is gated; the Workspace Asset imports service remains a distinct workflow.

Export project, GeoJSON, KML or map image

Choose between a full portable workspace and geometry-only interchange.

Files and portable sharing provides Project, GeoJSON, KML and Map image. Project creates a portable .explore.json containing geometry, folders, camera, basemap/layer choices and tours, with regenerated identifiers for a new local copy. GeoJSON and KML are geometry interchange formats and do not retain the complete project experience. Map image captures the loaded map with attribution when source permissions allow it.

Configured imagery requires explicit map-image export permission; a screenshot cannot add resolution absent from the source. Account export is a separate, broader account-data action that can now include Explore projects and investigation workspace records, while provider secrets remain excluded. Use the direct Project export when you need a focused portable geographic project, and inspect the resulting file before sharing.

How to use it

  1. Wait for the project and chosen map source to load.
  2. Open Files and portable sharing.
  3. Choose Project for the portable workspace, or GeoJSON / KML for geometry interchange.
  4. Choose Map image only where its source permits export.
  5. Open the exported file to verify the expected content before sharing.

What to know

  • These project tools require authorised Explore preview access. Provider setup is separate from the preview gate and does not unlock it.

Build and play a camera tour

Sequence geographic views for a local walkthrough.

Camera tour in an Explore project sequences saved geographic views. Frame a place, optionally select a feature, then choose Add this view. Name the tour, add more steps and choose Play. The step list lets you return to a view or remove a step; playback displays its current step and any stored description.

Stop or Escape ends playback at the current camera. Reduced-motion preference skips animated transitions. Tours are retained in a Project export; geometry-only GeoJSON/KML export does not carry the complete walkthrough. Tour views describe camera positions, not a time-series recording of live source data.

How to use it

  1. Open a project and frame the first view.
  2. Optionally select a feature and choose Add this view.
  3. Repeat for other locations and set Tour name.
  4. Choose Play, then Stop or Escape when finished.
  5. Export Project to retain the tour in a portable copy.

What to know

  • These project tools require authorised Explore preview access. Provider setup is separate from the preview gate and does not unlock it.

Choose imagery, street detail, terrain and buildings

Match your geographic question to the source’s actual resolution.

Explore → Map and elevation offers NASA Blue Marble · 500 m, OpenStreetMap street map, NASA MODIS · dated 250 m observations and Licensed imagery · server configured. Read the selected source's readiness and coverage. Automatic detail above photograph resolution adds optional street vectors; those are mapping, not higher-resolution photography. MODIS Observation date uses advertised archive dates and can contain clouds or missing swaths.

Elevation terrain uses public DEM tiles and Buildings with mapped height uses recorded map data. Use Overhead, Tilt and North to inspect the view, allowing for source/runtime limits. This Explore project's map is separate from Strategic Intelligence's imagery and camera/street-image tools; do not assume those layers or a collaboration service are part of a portable Explore project. Use Sources and providers for supported custom imagery/geocoder setup.

How to use it

  1. Open an Explore project and Map and elevation.
  2. Choose a Surface and read source readiness and resolution.
  3. Optionally enable Automatic detail, Elevation terrain or Buildings with mapped height.
  4. For MODIS, choose an advertised Observation date or use Older / Newer.
  5. Use Retry map sources if metadata fails and inspect coverage before interpreting a blank region.

What to know

  • These project tools require authorised Explore preview access. Provider setup is separate from the preview gate and does not unlock it.

Configure permitted imagery and place search

Use supported source settings and keep provider permissions explicit.

Workspace → Sources and providers includes Configured Explore imagery and Configured Explore geocoder. Imagery needs an allowed HTTPS XYZ tile template, attribution and maximum zoom; the geocoder needs a permitted Nominatim-compatible URL and attribution. Save one provider card and test its connection independently.

Provider settings can override the existing deployment environment configuration. Main Intelligence provider credentials use the backend secure store. The current interface states that credential forwarding for Explore imagery is disabled; custom XYZ endpoints support public tiles only. Saving a key does not establish that credentialed imagery is working. Source policy can still block a configured service.

No unrestricted public geocoder is silently enabled. Source setup does not unlock the Explore preview, grant an imagery licence or guarantee its native resolution/coverage.

How to use it

  1. Obtain permission for the provider and intended use.
  2. Open Workspace → Sources and providers.
  3. Find the imagery or geocoder card and enter its supported settings.
  4. Save that card and test the connection.
  5. After authorised Explore access, use Retry map sources and inspect attribution/readiness.

Adjust map appearance and panel positions

Use remembered colours and restore usable panel layouts.

Settings → Colors provides Bright water and Classic palettes. Bright-water palettes emphasise oceans, lakes and rivers with subdued land; palette changes alter presentation rather than source classifications. Map layers → Map settings & source status includes Border intensity.

Eligible tool panels can be moved on supported desktop layouts, with positions retained for the current layout context. Use Settings → Reset panel positions if a panel becomes inconvenient. Compact/mobile layouts apply their own accessible bounds; changing colour does not fix source availability. Panel move handles also support arrow keys, Shift for larger steps, Enter to save, Escape to cancel and Home to reset.

Workspace → Backup and updates includes explicit appearance backup and a separate Apply saved appearance and reload action. Restoring data does not silently overwrite the active browser presentation.

How to use it

  1. Open Settings → Colors and choose a palette.
  2. Adjust Border intensity in Map settings & source status if needed.
  3. Move supported floating panels by their header or focus their move handle for keyboard controls.
  4. Use Reset panel positions to recover the standard arrangement.
  5. Save appearance through Workspace backup/recovery before changing builds when you need to preserve it.

Move to a newer tester build safely

Install this updater-enabled release once, then install future releases from the app.

The website release is WideClarity 0.1.11, prepared for Windows x64. Check BETA-BUILD.json in your extracted app folder to identify your current version and source revision. Check for updates compares your app with the published Windows beta. If a newer compatible release is available, choose Install update & restart. The app downloads and verifies the package, then restarts into the new version.

Before updating existing work, open Workspace → Backup and updates, preview and save a backup, then verify the downloaded file. If you are using 0.1.9 or older, close it and extract the complete 0.1.11 Windows beta into a new writable folder once. Those older versions cannot install updates themselves. Keep a pre-upgrade backup until the new version starts and your data checks out.

From 0.1.10 onward, the in-app updater installs a verified release only after you choose Install update & restart. If an update fails, read the result and keep using the previous app; the download page remains available for a manual installation. Local state stays separate from the app folder, under %APPDATA%/Calythe Intelligence on Windows. Older builds may not understand new backup record types; restore with a compatible build and keep the pre-upgrade copy.

How to use it

  1. Record the source revision of the current app and the replacement build.
  2. Save and verify a Workspace backup before upgrading existing data.
  3. For 0.1.9 or older, install 0.1.11 once from the download page into a new writable folder.
  4. For later updates, choose Check for updates, read the release notes, then choose Install update & restart.
  5. Let the app finish and restart. Check the displayed result and reopen your saved project.

Manage your local account and data exports

Choose account export, project export or a verified Workspace backup for the task.

Settings → Account provides profile, session, sign-out, export and deletion controls. Export downloads wideclarity-account.json. In the current app this can include available app settings, personal Intelligence state, Explore projects and account-scoped Workspace records, alongside identity and session metadata. Export can fail when a required store cannot be read; do not assume a failed export contains a complete copy.

For a restore workflow, use Workspace → Backup and updates: it previews supported content, saves a portable backup and verifies the downloaded file before restore. Explore's portable project export is useful for an individual geographic project. These files have different purposes and should not be substituted for each other.

Signing out ends the account's active requests. Account deletion has an optional app-data clearing choice; read it before submitting. Keep provider credentials out of exports you intend to share, and review exported settings, places and evidence for private information.

How to use it

  1. Open Settings → Account to review profile and session controls.
  2. Use Export when you need the account data export.
  3. Use Workspace → Backup and updates for a validated recovery copy.
  4. Use a portable Explore project export for a single map project.
  5. Review deletion scope and keep a verified backup before intentionally removing local data.

Understand local data, providers and sharing

Know which action retains local work and which action sends or exposes it.

Accounts, personal preferences and retained project/research state are scoped to the local account and computer. Provider requests still reach the relevant internet services for maps, reports, forecasts and observations. The strategic runtime has its own visible provider and retention controls; read those before enabling optional features.

Workspace Sharing creates an explicitly selected, read-only snapshot for the app's independent viewer. It does not silently host a public website or keep a shared snapshot synchronized with later project edits. Review the selected content and access link before sharing, and use revocation when it should no longer be available.

Use credential controls for provider keys and keep them out of source URLs, notes and project descriptions. Main Intelligence provider keys use the backend secure credential store, which integrates with Windows Credential Manager. Strategic Intelligence has separate provider settings and storage; use its own controls for those keys. Device location is optional and requested through the location action. Backups, report exports, account exports, screenshots and logs may contain your places, notes and evidence; review them before sending.

How to use it

  1. Use a manually chosen home city if you do not need device location.
  2. Configure optional provider credentials through their supported controls.
  3. Preview the exact content before exporting or creating a share snapshot.
  4. Treat share links and private backups as access to the selected information.
  5. Review screenshots and logs before sending a tester report.

Troubleshoot launch, missing data and unsaved work

Use the visible failure and the build's prerequisites to choose the next step.

For a Windows launch problem, check Windows 10/11 x64, Microsoft Edge WebView2 Runtime, the complete extracted app folder and the intended build revision. The 0.1.11 ZIP includes the embedded Strategic Intelligence runtime. If it reports missing bundled files, extract the complete package again into a new short folder. Source-development launch has separate environment and runtime-preparation instructions.

For a blank map or feed, read source status, check network access, time/window filters, geographic bounds, layer visibility and zoom. A preview-access screen, missing credential, unsupported product, provider cooldown and a temporary request failure have different remedies. Use the relevant Retry or source controls after addressing the stated prerequisite.

Keep unsaved work open when a save fails. Workspace protects drafts during tool/project changes and provides Retry where supported; Explore also displays save/recovery state. If storage cannot be read, avoid deleting it as a first troubleshooting step. Preserve a verified backup or export when available, then give the team the exact error and build identity.

How to use it

  1. Read and record the complete visible error and the workspace name.
  2. Check the runtime, preview access or provider prerequisite it identifies.
  3. Check source dates, filters, bounds and layer zoom before interpreting missing objects.
  4. Use the appropriate Retry, refresh or save control when the prerequisite is resolved.
  5. If the problem remains, preserve your data and send a reproducible tester report.

Send a useful tester report

Include the build revision, exact steps and source state so the team can reproduce it.

Send questions and tester feedback to calythe.dev@gmail.com or the team's agreed private channel. Include the app's source revision, operating system, workspace, shortest reproduction steps, expected result and actual result. For Windows packages, attach BETA-BUILD.json; for source runs, record the main commit you launched.

For a source or map issue, include the provider/product, location or bounds, selected filters, observation or valid time and the exact status. For weather include the field, model and level. For Reports or Workspace include the tool and action that failed, with enough non-sensitive context to recreate it.

For Windows startup failures, the included tester instructions describe running WideClarity.exe with --selftest selftest.json from the package folder and collecting the process exit code. The Windows log is %APPDATA%/Calythe Intelligence/logs/intelligence.log. Review diagnostic files and screenshots for private content; do not send provider keys, passwords or access codes.

How to use it

  1. Reproduce the issue and write the shortest reliable sequence.
  2. Record the exact source revision and operating system.
  3. Copy the visible error and relevant source/date/filter settings.
  4. Attach a screenshot and, for a packaged build, BETA-BUILD.json.
  5. Review attachments for private information and send them through the agreed tester channel.

Control dense orbital workloads

Choose performance settings while preserving source-count distinctions.

Settings → Layer performance provides Lightweight, Balanced and Full profiles, an object cap where applicable, position updates per second, object labels and selected-object orbit trail. Full retains all valid source objects without a cap; lower profiles limit work for dense selections.

The status distinguishes catalogue, tracked, visible and computed objects and shows session measurements when available. These are observations of the current session, not a hardware requirement or guaranteed FPS. Selected objects still need usable source elements and can be outside the visible globe.

How to use it

  1. Open Settings → Layer performance.
  2. Choose a profile appropriate for the current selection.
  3. Adjust update frequency, labels and selected trail.
  4. Read object counts and measured session status.
  5. Reduce workload or selected categories if interaction becomes slow.

Find the related Calythe product

Keep the WideClarity Intelligence workflow and the Agent product separate.

These guides document WideClarity's Intelligence application: Intelligence, Explore, Strategic Intelligence, Daily briefing, Tech news and Reports, together with its investigation tools. Calythe Agent is a related product with its own conversation, coding, team and connector workflows. Use the AI page's existing Calythe link to explore that product separately.

WideClarity can expose specific optional provider-backed actions, such as a narrative summary, without including the full Agent conversation workspace. Follow the guide for the action you are using and its provider/source requirements. For Agent accounts, model connections, permissions and automation behavior, use that product's own setup information.

How to use it

  1. Use the WideClarity documentation for the Intelligence application and its investigation workspaces.
  2. Open the website's AI page to find the related Calythe product link.
  3. Read that product's own setup guidance before configuring its models, connectors or permissions.