Event Monitoring · External information
What the world is doing, as data.
An earthquake, a landfalling hurricane, a PERILS loss report, an ENSO advisory, the multiple the market is paying today — each a typed node with a date, a source and a derived reading. The desk prices against the record, not against a memory of last week’s news.
▶ Open the monitorRead the guide

What ships

Why it is a separate module

This module knows nothing about cat bonds, and the ILS module holds no C# reference to it. The seam is a set of camelCase property names read straight off the node — peril, classification, severity, occurredAt on an event; asOf and status on a climate snapshot; asOf, regime, averageMultiple and direction on a market one.

That contract is pinned by a reflection test on each record, so renaming a property fails a build here rather than silently emptying a page there. Install this module and the ILS decision context gets richer; leave it out and nothing breaks.

In this version

Records are authored in the repo or imported. No feed is fetched: the USGS, NHC, EONET and GDACS clients are the natural follow-up, and they belong behind IIoPool as genuinely-async leaves.

The module family

ILS is the decision process this feeds. Beside it sit Portfolio (the held book and its marks), PortfolioOptimization (RoRAC and pipeline ranking) and TaskManagement (work items and the team).

Contents

Reconnecting…
The server was updated. Reloading the page to pick up the latest version.