DRIFT SYSTEMSHIDDEN DEPENDENCIES.
DISCOVERED OPPORTUNITIES.
The Reinsurance surface is where external structural movement becomes institutionally consequential for reinsurers: accumulation, portfolio, underwriting, technical risk, enterprise risk, actuarial, claims and cross-class ownership decisions.
Territories are surface-specific navigation labels, not canonical Domains.
Each function 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.
| Function | Surface question | Guard from this dependency | Create with this dependency | Decision question |
|---|---|---|---|---|
| 01 / PRIORITY · Accumulation / Exposure Management ↗ | Does the accumulation boundary stop at the data centre? | 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 ↗ | Does the diversification assumption survive a shared grid dependency? | 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 · Treaty / Specialty Underwriting ↗ | Does the underwriting boundary survive when separate risks share the same grid dependency? | 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 ↗ | What physical mechanism, operational dependency and mitigation would have to exist for the risk to be real? | 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 ↗ | Does the risk boundary stop where the business lines do? | 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 ↗ | Does the correlation assumption survive a shared grid dependency? | 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 ↗ | Does the event definition survive when one grid disturbance reaches several policies at once? | 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 ↗ | If no existing desk owns the whole dependency, where should the cross-class RDM-03 decision live? | 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? |
Each function may already cover the component risks. The test is where the dependency could connect exposures, assumptions or decisions that appear separate in the public footprint; whether and at what threshold that connection becomes material internally; and whether it is already recognised or controlled for. Public evidence establishes the mechanism and the institution's public footprint. It does not establish how the institution treats that dependency internally.
Develops the institution-specific consequence position: what the dependency puts under pressure, which exposures or decisions it connects, and what the institution should guard.
Develops the institution-specific opportunity position: what recognising the dependency could help create across decisions, products, services, structures, capabilities or market position.
Two complete positions from one dependency and shared evidence base: what the institution should guard, and what it could create.