REINSURANCE · DESK / PROTODESKRDM-03

CROSS-CLASS DEPENDENCY OWNER /

This is the explicit protodesk. RDM-03 may create a decision territory that sits between established functions: no single team owns the whole dependency, yet several teams own fragments of the evidence and consequence.

OBSERVEDLarge-load / disconnection events

MODELLEDWider system propagation

INFERREDCross-exposure correlation

UNPROVENInsured consequence

RDM-03 / DESK ANATOMY

GUARD & CREATE

EACH ROW SHOWS A SEPARATE DECISION PATHWAY THROUGH RDM-03: WHAT THIS DESK MAY NEED TO GUARD FROM THE DEPENDENCY, WHAT THE DEPENDENCY COULD HELP IT CREATE, AND WHICH DECISION MAY CHANGE.

#	Decision area	Guard from this dependency	Create with this dependency	Decision question
01	DEPENDENCY BOUNDARY	Each function may see only the part of RDM-03 that touches its own remit.	A shared dependency object can create one bounded question without collapsing functional responsibilities.	What is the minimum common object that all affected desks need to recognise?
02	FRAGMENTED OWNERSHIP	Exposure, underwriting, engineering, actuarial and CRO teams may each own different links in the chain.	A protodesk can coordinate the decision without pretending a new department already exists.	Which existing owners hold the evidence needed to determine RDM-03?
03	DECISION OWNER	Evidence can circulate while no one owns the decision to act, test or kill.	A named decision owner can prevent the dependency from becoming an orphan risk.	Who has authority to decide whether RDM-03 changes anything?
04	CROSS-CLASS VIEW	Class-by-class management can obscure a dependency inherited by several books.	A cross-class view can reveal common exposure without requiring a new class taxonomy.	Where could RDM-03 connect decisions across classes?
05	EVIDENCE HANDOFF	Technical evidence may not travel cleanly into underwriting or portfolio decisions.	A defined handoff can preserve evidence state, uncertainty and falsifiers across desks.	What evidence must move between desks for the RDM-03 decision to remain intact?
06	ESCALATION TRIGGER	Teams may escalate based on interest or seniority rather than evidence.	A common trigger can define when the dependency deserves cross-functional attention.	What evidence threshold should activate cross-class review?
07	INTERVENTION OWNER	Even if the dependency survives, the best intervention may belong to a different team from the risk owner.	Separating dependency ownership from intervention ownership can expose new internal or commercial options.	Who should own the response if RDM-03 survives?
08	PROTODESK TEST	Creating a permanent structure too early would harden an unproven hypothesis into organisation design.	The protodesk can remain temporary until repeated decisions prove that a durable territory exists.	What repeated evidence would justify turning this protodesk into a recognised decision function?

Decision area

Guard from this dependency

Create with this dependency

Decision question

DEPENDENCY BOUNDARY

Each function may see only the part of RDM-03 that touches its own remit.

A shared dependency object can create one bounded question without collapsing functional responsibilities.

What is the minimum common object that all affected desks need to recognise?

FRAGMENTED OWNERSHIP

Exposure, underwriting, engineering, actuarial and CRO teams may each own different links in the chain.

A protodesk can coordinate the decision without pretending a new department already exists.

Which existing owners hold the evidence needed to determine RDM-03?

DECISION OWNER

Evidence can circulate while no one owns the decision to act, test or kill.

A named decision owner can prevent the dependency from becoming an orphan risk.

Who has authority to decide whether RDM-03 changes anything?

CROSS-CLASS VIEW

Class-by-class management can obscure a dependency inherited by several books.

A cross-class view can reveal common exposure without requiring a new class taxonomy.

Where could RDM-03 connect decisions across classes?

EVIDENCE HANDOFF

Technical evidence may not travel cleanly into underwriting or portfolio decisions.

A defined handoff can preserve evidence state, uncertainty and falsifiers across desks.

What evidence must move between desks for the RDM-03 decision to remain intact?

ESCALATION TRIGGER

Teams may escalate based on interest or seniority rather than evidence.

A common trigger can define when the dependency deserves cross-functional attention.

What evidence threshold should activate cross-class review?

INTERVENTION OWNER

Even if the dependency survives, the best intervention may belong to a different team from the risk owner.

Separating dependency ownership from intervention ownership can expose new internal or commercial options.

Who should own the response if RDM-03 survives?

PROTODESK TEST

Creating a permanent structure too early would harden an unproven hypothesis into organisation design.

The protodesk can remain temporary until repeated decisions prove that a durable territory exists.

What repeated evidence would justify turning this protodesk into a recognised decision function?

THE REINSURANCE QUESTION

IF NO EXISTING DESK OWNS THE WHOLE DEPENDENCY, WHERE SHOULD THE CROSS-CLASS RDM-03 DECISION LIVE?

This is the governing question for this decision territory. The matrix above decomposes it into the smaller consequences, opportunities and questions that can be tested independently.

THREE BUYING OPTIONS

CONSEQUENCE REPORT.
OPPORTUNITY REPORT.
OR BOTH.

01 / CONSEQUENCE REPORT

GUARD FROM THIS DEPENDENCY.

THIS DESK RECEIVES: OWNERSHIP, EVIDENCE HANDOFF, ESCALATION LOGIC AND THE CROSS-FUNCTIONAL DECISION PATH IF NO SINGLE EXISTING DESK OWNS RDM-03.

€25KFIXED

02 / OPPORTUNITY REPORT

CREATE WITH THIS DEPENDENCY.

THIS DESK RECEIVES: A SHARED DEPENDENCY OBJECT, COORDINATED DECISION PATH AND POTENTIALLY A NEW CROSS-CLASS DECISION TERRITORY.

€25KFIXED

03 / BOTH

GUARD + CREATE.

Two complete positions from one dependency and shared evidence base.

€40KFIXED · SAVE €10K

OTHER REINSURANCE DESKS / PROTODESKS

Accumulation / Exposure Management Portfolio / Aggregate Management Treaty / Specialty Underwriting Technical Risk / Engineering CRO / Enterprise Risk Actuarial / Analytics Claims / Loss Scenario

RDM-03 evidence boundary: initiating events observed; wider propagation modelled; correlation inferred; insured consequence unproven. GUARD, CREATE and DECISION QUESTION rows are outside-in decision views, not claims about any institution's actual portfolio, models or internal position.

This desk is also published as a function of the Reinsurance surface: Cross-Class Dependency Owner →