The variable names below are the sub-factors defined on each metric’s own page under
Event metrics. Nothing here redefines them — this is the same rubric,
applied to an instance.
The two events
Both are real, both are in the corpus, and they were chosen because they disagree in a useful way.Magnitude — when nobody dies
Havana blackout
No deaths were reported, so the fatality-based path never applies — and the event is plainly severe.
That is what the other paths exist for. A metric that could only see deaths would score a national
grid collapse at zero.
Systemic importance — a mean of three judgments
Anthropic settlement · node: Anthropic and the generative-AI copyright/licensing ecosystem
Propagation potential — and the one inverted term
Havana blackout
Note
containment enters as (1 − 0.35). It is the only sub-factor anywhere in the set that
suppresses its metric: high containment means the event is being held, so it should lower the
chance of spread, not raise it.
The propagation_potential page marks it, and this is
what that marking means in arithmetic.
Market sensitivity — why a huge event scores low
Anthropic settlement
Havana blackout
This is the metric working, not failing. The blackout is severe — a magnitude of 7 and a high
systemic importance — but almost nothing traded attaches to it. Market sensitivity measures
attachment to a traded claim, not how bad an event is. Reading it as a severity score is the single
most common mistake, which is why
the
market_sensitivity page lists what it explicitly does
not claim.
Reproducing this yourself
Ask for the sub-factor breakdown and the arithmetic comes back with the event:null, that is the contract working: it means the observable was not found,
never that the value is zero. Each metric’s page says exactly when that happens — see
magnitude, the only one of the four whose scaler returns NULL.
Limits and error bars
What these numbers cannot support, and the measured noise floor.

