Standard · Aggregation

Sovereignty is a property of the weakest link.

How the overall level is derived from the four domain levels — and why no averaging.

The rule§

The EDSO overall level of a service is the minimum of the four domain levels.
L_total = min(L_D1, L_D2, L_D3, L_D4)

Rationale§

EDSO does not add, does not average and does not weight. The choice of the minimum function is not an aesthetic but a structural decision. Sovereignty behaves like functional safety: a SIL chain is only as strong as its weakest link. A bridge with three strong pillars and one weak one is a weak bridge — regardless of how load-bearing the other three are.

Averaging would render weaknesses invisible in aggregation. A service with D1 = L3, D2 = L3, D3 = L3 and D4 = L0 would carry an average score of “2.25” — a politically comfortable result that achieves nothing in a crisis. A severed supply path remains severed, even if it is well documented.

Weighting would shift what cannot be shifted: sovereignty is multidimensional. The four domains measure orthogonal properties — they cannot be offset against one another. Sector-specific protection goals are therefore expressed via minimum levels per domain, not via weights.

Three worked examples§

Example A — Hyperscaler reseller with EU brand

D1D2D3D4Overall
L1L1L0L1L0

A brand label does not change a proprietary stack.

Example B — European provider with open-source stack

D1D2D3D4Overall
L2L2L2L2L2

A clean line across all domains — procurement-robust for DORA/NIS2.

Example C — Specialised sovereignty provider

D1D2D3D4Overall
L3L3L3L2L2

Even with three L3 ratings, the weakest domain determines the overall level.

Common objections§