01 / CONSEQUENCE REPORT
GUARD FROM THIS DEPENDENCY.
Develops the institution-specific consequence position: what the dependency puts under pressure, which exposures or decisions it connects, and what the institution should guard.
€25KFIXED
MONACO 2026 · RDM-03PUBLIC EVIDENCE ONLY
SURFACE 01 / REINSURANCE
REINSURANCE. ONE HIDDEN DEPENDENCY.DIFFERENT DECISIONS.
RDM-03 · SYNCHRONISED LARGE-LOAD / BULK-GRID DEPENDENCYRDM-03 may connect reinsurance exposures currently treated as independent. We develop two separate decision views: what the institution should GUARD, and what recognising the dependency could help it CREATE.
DEPENDENCY RDM-03 DISCOVERED & MODELLEDPUBLICLY UNRECOGNISED
We identified the mechanism, mapped the dependency and modelled its wider propagation. The component risks may already be recognised. RDM-03 is the connection between them.
OBSERVEDLarge-load / disconnection events
MODELLEDWider system propagation
INFERREDCross-exposure correlation
UNPROVENInsured consequence
RDM-03→Reinsurance→DESK→DECISION→GUARD / CREATE
RDM-03MECHANISM RATIFIED · PRS 80
Synchronized data-centre load-protection as a potential new bulk-grid contingency class.
A grid disturbance can trigger the near-simultaneous withdrawal of gigawatt-scale computational load across a dense cluster. When many large loads react in the same direction at the same time, assets and exposures that appear separate may begin sharing the same contingency.
Repeated gigawatt-scale load-withdrawal events are observed. Wider system propagation is modelled. The possibility that separately insured assets or books could become correlated through the same grid-side dependency is inferred. Portfolio-scale insured consequence remains unproven.
Synchronized large-load protection behaviour can cause exposures still treated as separate to begin sharing the same contingency.
Our public-evidence review has found no evidence that RDM-03 is currently treated as a distinct reinsurance dependency class. Initiating events are observed. Wider propagation is modelled. Cross-exposure correlation is inferred. Insured consequence remains unproven.
OBSERVEDLarge-load / disconnection events
MODELLEDWider system propagation
INFERREDCross-exposure correlation
UNPROVENInsured consequence
WHERE DOES RDM-03 CHANGE A DECISION?
Each desk sees the same dependency through a different decision. GUARD FROM THIS DEPENDENCY shows what existing value, assumption or capability is under pressure. CREATE WITH THIS DEPENDENCY shows what recognising the dependency could make newly possible.
THE DESK TEST
WHERE DOES YOUR CURRENT DECISION FRAMEWORK ASSUME INDEPENDENCE THAT RDM-03 MAY INVALIDATE?
Each desk may already cover the component risks. The test is where RDM-03 could connect exposures, assumptions or decisions that appear separate in the public footprint; whether and at what threshold that connection becomes material or decision-relevant internally; and whether it is already recognised or controlled for.
Public evidence establishes the RDM-03 mechanism and the institution's public exposure footprint. It does not establish how the institution treats that dependency internally.
| Desk | Guard from this dependency | Create with this dependency | Decision question |
|---|---|---|---|
| 01 / PRIORITY · ACCUMULATION / EXPOSURE ↗ | Independence, accumulation boundaries, aggregate confidence and capacity discipline. | Dependency-aware aggregation, better portfolio steering and more discriminating capacity decisions. | Where could RDM-03 connect reinsurance exposures currently treated as independent? |
| 02 / PRIORITY · PORTFOLIO / AGGREGATE MANAGEMENT ↗ | Diversification assumptions, aggregate view, concentration limits and portfolio resilience. | New portfolio views, steering logic and capacity deployment options built around the dependency. | Does RDM-03 change the portfolio's aggregate view, concentration limits or where capacity can be deployed? |
| 03 · UNDERWRITING ↗ | Risk selection, attachment, wording, structure, pricing and cedant differentiation. | Sharper differentiation, new structures, pricing logic and dependency-aware underwriting responses. | Could RDM-03 alter attachment, wording, structure, pricing or cedant differentiation across relevant books? |
| 04 · TECHNICAL RISK / ENGINEERING ↗ | Mechanism integrity, protection assumptions, resilience, redundancy and engineering confidence. | Engineering assurance, mitigation, control options and new technical services around the dependency. | What physical mechanism, operational dependency and mitigation would have to exist for the risk to be real? |
| 05 · CRO / ENTERPRISE RISK ↗ | Enterprise resilience, capital, cross-class risk ownership and decision accountability. | New governance, escalation, cross-functional controls and strategic response options. | If the mechanism crosses classes and functions, who owns the enterprise consequence and the decision to act? |
| 06 · ACTUARIAL / ANALYTICS ↗ | Model confidence, assumptions, data quality, scenario adequacy and correlation treatment. | New variables, scenarios, analytics, monitoring and dependency-aware modelling capability. | Which assumptions, scenarios or data fields would have to change if correlation is materially different from today's treatment? |
| 07 / SECONDARY · CLAIMS / LOSS SCENARIO ↗ | Causation, coverage logic, event definition, loss aggregation and claims confidence. | New loss-pathway maps, claims scenarios, cross-policy views and recovery / response clarity. | What loss pathways, business-interruption chains or cross-policy interactions would appear if the dependency propagated? |
| PROTODESK · CROSS-CLASS DEPENDENCY OWNER ↗ | Ownership, evidence handoff, escalation, cross-class coherence and decision control. | A shared dependency object, coordinated decision path and, if needed, a new cross-class decision territory. | If no existing desk owns the whole dependency, where should the cross-class RDM-03 decision live? |
CONSEQUENCE and OPPORTUNITY remain separate reports. GUARD and CREATE are the simple decision layer. Commission either report on its own, or both against the same RDM-03 evidence base.
02 / OPPORTUNITY REPORT
CREATE WITH THIS DEPENDENCY.
Develops the institution-specific opportunity position: what recognising the dependency could help create across decisions, products, services, structures, capabilities or market position.
€25KFIXED
03 / BOTH
GUARD + CREATE WITH THIS DEPENDENCY
Two complete positions from one dependency and shared evidence base: what the institution should guard, and what it could create.
€40KFIXED / SAVE €10K
BOTH · €40K →ONE DEPENDENCY.
TWO DECISION PATHS.
THE COMMISSIONED WORK DEVELOPS THE INSTITUTION-SPECIFIC CONSEQUENCE OR OPPORTUNITY POSITION AGAINST THAT PUBLIC-FOOTPRINT MATCH. NO CLAIM IS MADE ABOUT INTERNAL PORTFOLIOS, MODELS OR POSITIONS WITHOUT EVIDENCE.
The same dependency can be mapped independently across the 10 canonical decision surfaces: GOVERNANCE, FINANCE, INTELLIGENCE, AI, CAPITAL, MARKETS, SCIENCE, MEDIA, INDUSTRY and REINSURANCE. Each surface has its own desks, decisions and buying path.