How H3XA builds an operational picture
H3XA keeps collection, normalization, correlation, and interpretation distinguishable. This page documents the trust model users should apply to every analytical surface.
Source observations
Records remain attributable to their originating feed or publisher. Source-reported claims are not silently promoted to facts.
Normalized facts
Identifiers, times, places, entities, and STIX objects are normalized so records can be compared without erasing source lineage.
Relationships
Links between objects carry their own evidence and should be treated separately from the objects they connect.
Assessments
Interpretation is explicit. Confidence, ambiguity, contradiction, and temporal validity belong with the assessment rather than being hidden in presentation.
Interpretation rules
A dense operational view can create false certainty. H3XA therefore treats volume as volume, correlation as correlation, and assessment as assessment. A map marker, relationship edge, or repeated indicator is not by itself proof of intent, attribution, or causality.
Freshness and time
Each source has its own collection and publication latency. “Current” means the newest available evidence from that source, not necessarily an observation made at the present instant. A period that was recorded stays open. A period that was never collected is not reconstructed later. Open a place and a time → How to read it →
Provenance
Analytical views provide a path back to the contributing source objects. Derived relationships and summaries remain distinguishable from source-reported material. The record is the infrastructure situation. Outage notes from NetBlocks, Cloudflare, and Internet Society Pulse name a place and a month, and they stay off the score. Air, the catalog, and other domains are the setting. The record and the setting →
Uncertainty
Conflicting observations remain visible until resolved. Missing evidence, weak corroboration, and model-generated inference lower confidence rather than disappearing from the interface.
What H3XA does not publish
H3XA's public methodology describes the principles behind its analytical products without publishing a reconstruction guide. Exact scoring weights, thresholds, and implementation details belong to internal technical documentation, not the public surface.