One situation
H3XA opens on a place and a month. Kazakhstan in October 2026 is one situation. The episodes, the stress score, the public reporting for that month, and the briefing are the record you keep. Changing the month opens another period of the same situation, when that period was stored.
The record is infrastructure
The record is built from infrastructure measurements: connectivity observations, anomaly rates, and corroborating traffic and routing. Those measurements become episodes. The stress score is H3XA's assessment of the episodes, and the briefing cites the model and the derivation behind it. Public reporting for that month is read from outage notes that name the place: NetBlocks, Cloudflare, and Internet Society Pulse. Those notes stay beside the score. A period that was never collected is left empty.
The setting sits beside it
Air tracks, the reference catalog, physical hazards, headlines, and dependencies can be read with the same place and the same month. They are collateral. They describe the setting of the situation. An entry joins the setting when it names the place and falls in the month. Otherwise the slot stays empty.
A shared month is not a cause
Two things can be true in the same week without one explaining the other. A storm, a flight track, a catalog technique, or a headline can sit next to an outage. The assessment of cause stays on the record: a class, a confidence, and the alternatives. The setting does not move the score.
What you can hand someone
The picture is the current situation. The corpus is the periods already stored. The briefing is the pack that ties a score back to its observations. The setting is there so a reader can see what was nearby, and can see that nearby is not the same thing as derived.
- The record: episodes, stress, outage reporting for the month, and the briefing
- The setting: air, the catalog, hazards, and dependencies in that same window
- The assessment: class, confidence, and the alternatives