Score methodology

Five independent components

The engine evaluates earthquakes, asteroid activity, space weather, volcanic activity, and severe weather through five pure component functions. Each function accepts a typed normalized input and returns a score on the same bounded scale plus supporting facts. It does not fetch data, write records, or depend on a specific upstream provider.

Component rules and weights belong to an immutable algorithm configuration with an explicit version. A published snapshot records that version, so a later rule change cannot silently reinterpret an older score. Aggregation is deterministic: the same normalized inputs, timestamps, and configuration produce the same result.

Freshness, completeness, and unavailable sources

Every component carries availability and freshness state. A missing component is not a score of zero, and a stale observation is not treated as current. Completeness describes how much of the configured score has usable input; it is presented alongside the result rather than hidden inside a reassuring headline.

When required volcano or asteroid production input is unavailable because no source has passed the source-rights gate, the production score follows the provisional or incomplete-data path. Reasons to Chill may explain genuinely low values from available components, but it cannot claim that an unavailable hazard is safe.

How to interpret the result

Status bands are communication aids, not forecasts of catastrophe. They summarize configured observations at a point in time and should be read with component detail, timestamps, completeness, and source notes. Historical fixtures test the algorithm against controlled scenarios; they do not turn the score into a prediction of future events.