H3XA
H3XA / Operational evidence

See the condition.
Understand the change.

H3XA turns independent observations into events, situations, and longitudinal operational history — revealing what is changing, where it is happening, and how unusual it actually is.

Open the operational workspace Open a place and a time Enter live picture Explore H3XA data The offering Who H3XA is for
Live / 01:06 ET
Global infrastructure integrityWorkspace
Active situations—
ElevatedWorkspace
Entities observed—
AssessmentsSituation records stay in the operational workspaceThe public page does not publish a stored stress head.
01/Model

From evidence to understanding

Observation
What was measured.
↓
Event
What happened.
↓
Situation
What belongs together.
↓
History
What it means relative to before.

H3XA preserves the evidence while manufacturing the analytical structure around it.

Source-owned
  • Observations
  • Measurements
  • Evidence
H3XA-derived
  • Baselines
  • Anomalies
  • Events
  • Situations
  • Stress
  • Trajectories
  • Recovery
  • Recurrence
02/Live

The operating picture is live.

Current conditions derived from continuously observed infrastructure behavior.

Stored situations and briefings are operational records. They are read in the workspace, not on this page.

Open the live picture
03/Correlation

One observation is not the story.

As within, so without.

Infrastructure rarely fails as a database row. Measurements arrive independently, at different levels of resolution and from different vantage points. H3XA determines which observations describe the same underlying condition.

04/History

Current conditions are only half the question.

H3XA keeps a longitudinal record of infrastructure behavior: stress over time, recovery, recurrence, and how unusual a condition is against that entity's own history. That record is the corpus. The public picture shows the current condition.

The corpus
05/Domains

Across the operating environment

TodayThe current operating picture.InfrastructureStress, situations, and integrity.DisruptionOutages and connectivity loss.IntelligenceVulnerabilities, techniques, and actors.

Different domains. One evidence model.

06/Method

Evidence before assessment.

01
Preserve the observation

Source evidence remains distinguishable from H3XA-derived analysis.

02
Show the derivation

Events and situations remain traceable to the evidence supporting them.

03
Represent uncertainty

Confidence is part of the assessment, not something hidden behind it.

Read methodology Evidence & provenance
07/Access

The picture / the corpus

Open a place and a time. The situation holds the episodes, the score, and the briefing. A period that was observed can be opened again.

Open Kazakhstan in October 2026 How to read H3XA
Public edition

The picture

  • Current conditions
  • Active situations
  • Selected evidence
  • Current entity state
  • Analysis
  • Methodology
  • Provenance
Explore H3XA Who H3XA is for
H3XA Data

The corpus

  • Stress(entity,t)
  • Historical situations
  • Entity histories
  • Recovery
  • Recurrence
  • Reliability
  • Historical trajectories
  • Machine-readable access
Request data access The offering

The operating picture is public.
The history behind it is a data product.

08/Corpus

An accumulating record

—Source objects
—H3XA snapshots
—Entities with history
—Derived situations

These aren't static catalog counts. H3XA's analytical corpus grows as conditions are observed over time.

09/Analysis

What the data is showing.

HOW TO READ H3XAStart with a place and a timeHow to read H3XA · 4 minSTRUCTUREThe record and the settingHow H3XA is structured · 5 minANALYSIS / INFRASTRUCTUREReading internet disruptions as geopolitical signalExplainer · 7 minANALYSIS / CONVERGENCEReading cross-domain convergenceAnalytical method · 6 minANALYSIS / CYBERHow to read a threat-intelligence graphResearch brief · 5 min

Observe what happened.
Understand what changed.
Remember what came before.

Enter H3XA Request data access
Evidence before assessment.