Apply it to one process or capability you have in mind. Pick how sensitive its data is, how critical it is and how far you would separate it. The map shows what stays open in the four dependencies and a decision to consider.
The decision is the model’s suggestion, not a conclusion for your organisation. No provider recommendation. Scores, effects and costs are assumptions for discussion, based on the CLDN sovereignty model. Your choices stay in this browser.
Your situation
Sensitivity
Process
How well can you ring-fence it?
How far do you separate it? (the seam)
Add
How far is what you chose
Second channel for the critical process
A prepared way to keep talking when the main platform is gone. Easy to set up; the work is deciding who switches and practising it.
Decision to consider
What it costs
Relative effort for each choice, split into retraining users and technical rebuild.
Plan across all four sensitivity levels, evidence per change, the twelve dimensions and why each item is open.
Plan across sensitivity levels
Each level keeps its own choices. Click one to edit it. Dots are the four dependencies, as designed: green within target, amber partly open, red open.
Sensitivity
Separated
Added
Day 2
Decision
Normal
Critical
Profile by dimension
0target: no requirement · result: no control (our extension)1Basic2Advanced3High: your own controlAnything someone else runs stops at 2, except data processing, data location and access in a service built or adapted for you, with extra effort.
Microsoft 365 tenant alonedesigned, with what you chosetarget◆ depends on the platform or on you
Your judgement for this level
Consequence
What you chose, and how far it is
Why it’s open
The twelve dimensions
Levels 1–3 come from the CLDN study. A service someone else runs stops at 2 on 9 of the 12 dimensions. The study mentions level 0 as “no requirement” and leaves it out; here it is also a result when a set-up doesn’t reach level 1. Sustainability is shown for completeness, outside the four dependencies and the counts.