Sovereignty Index
SOVEREIGNTY INDEX
(A+ Strategic Framework — Core System Anchor)
1. Executive Summary
Sovereignty is not independence.
It is measured autonomy under pressure.
Most institutions believe they are sovereign.
They are not.
They depend on:
```txt
Single vendors
Single regulators
Single revenue streams
Single knowledge holders
```
The Sovereignty Index quantifies this.
It answers one question:
```txt
If external conditions shift violently,
how long can this institution act
on its own authority?
```
If the answer is days, you are not sovereign.
You are renting time.
2. Operating Logic
2.1 — Dependency Axial
Every institution operates across four dependency axes:
```txt
FINANCIAL — Who funds you? How diversified?
OPERATIONAL — Who runs your infrastructure?
REGULATORY — Who controls your licence to operate?
INTELLECTUAL — Who holds critical knowledge?
```
Each axis is scored 0–100.
```txt
0 = Total external dependency
50 = Shared control
100 = Full internal sovereignty
```
The composite score is the Sovereignty Index.
```txt
SI = (F + O + R + I) / 4
```
A score below 40 is institutional fragility.
A score below 25 is existential exposure.
2.2 — Survival Horizon
The Survival Horizon is a time-based stress test.
```txt
Question: If your largest external dependency
disappeared tomorrow,
how many days can you operate?
```
Categories:
```txt
CRITICAL — 0–7 days
FRAGILE — 8–30 days
STABLE — 31–90 days
SOVEREIGN — 91+ days
```
Each dependency axis gets its own Survival Horizon.
The shortest horizon is the binding constraint.
An institution is only as sovereign as its weakest axis.
2.3 — Dark Node Simulation
A Dark Node is any dependency you do not see.
Most institutions map obvious dependencies:
```txt
Known vendors
Known regulators
Known revenue sources
```
They miss:
```txt
Shadow IT providers
Informal knowledge brokers
Regulatory chain dependencies
Sub-vendor concentration
```
The Dark Node Simulation forces disclosure.
```txt
Step 1 — Map every first-order dependency
Step 2 — Map every second-order dependency
Step 3 — Identify nodes with no backup
Step 4 — Classify as Dark Nodes
Step 5 — Stress test each Dark Node independently
```
If a Dark Node fails and you had no contingency, it was always the real risk.
2.4 — Volatility Coupling
External volatility is not the threat.
Coupling to external volatility is the threat.
```txt
Loosely coupled — External shock absorbed internally
Tightly coupled — External shock transmitted directly
```
Measure coupling per axis:
```txt
LOW — Shock absorbed in 48 hours
MEDIUM — Shock absorbed in 2 weeks
HIGH — Shock not absorbed; requires external resolution
```
High coupling on any axis reduces the Sovereignty Index by a penalty factor.
```txt
SI_adjusted = SI - (10 × number of HIGH-coupled axes)
```
3. Application Playbook
Step 1 — Conduct Dependency Inventory
Deliverable: Complete register of all first-order and second-order dependencies across all four axes.
```txt
Financial: List all revenue sources, credit facilities, funding partners
Operational: List all infrastructure providers, SaaS platforms, logistics
Regulatory: List all licences, regulators, compliance dependencies
Intellectual: List all key persons, proprietary systems, undocumented processes
```
Step 2 — Score Each Axis
Deliverable: Numerical score (0–100) for each dependency axis.
```txt
Scoring criteria:
Diversification — How many alternatives exist?
Substitutability — How fast can you switch?
Internal capability — Can you do it yourself?
Contractual control — Do you own the terms?
```
Step 3 — Calculate Survival Horizon
Deliverable: Days-to-failure for each axis under sudden dependency loss.
```txt
For each dependency:
Remove it from the model
Estimate time to failure or degradation
Record the binding constraint
```
Step 4 — Run Dark Node Simulation
Deliverable: List of hidden dependencies with risk classification.
```txt
Conduct interviews with operations, finance, IT, legal
Map sub-dependencies of every vendor
Identify single points of failure
Flag anything with no backup as a Dark Node
```
Step 5 — Assess Volatility Coupling
Deliverable: Coupling classification (LOW / MEDIUM / HIGH) per axis.
```txt
Review last 3 external shocks
Trace transmission path into institution
Measure recovery time
Classify coupling level
```
Step 6 — Compute Final Index
Deliverable: Sovereignty Index score with adjusted penalty.
```txt
SI = (F + O + R + I) / 4
SI_adjusted = SI - (10 × HIGH-coupled axes)
Survival Horizon = minimum days across all axes
```
Step 7 — Report to Board
Deliverable: One-page sovereignty brief.
```txt
Overall SI score
Weakest axis
Binding constraint (shortest Survival Horizon)
Dark Nodes requiring immediate action
Recommended interventions ranked by cost and impact
```
4. Metrics & Measurement
```txt
Sovereignty Index (SI) — Composite 0–100
Adjusted SI — SI minus coupling penalties
Survival Horizon (days) — Per axis and composite minimum
Dark Node Count — Total hidden dependencies
Dependency Concentration Ratio — % of operations tied to top 3 dependencies
Coupling Score — Number of HIGH-coupled axes
Recovery Time Objective — Target days to absorb shock per axis
```
Measurement cadence:
```txt
Quarterly — Full SI recalculation
Monthly — Survival Horizon spot checks
Annually — Dark Node Simulation (full)
Event-triggered — Any major vendor/regulatory change
```
5. Board-Level Questions
```txt
What is our current Sovereignty Index?
Which axis is weakest and why?
How many days can we survive the loss of our largest dependency?
How many Dark Nodes exist that we have not mitigated?
Are we more or less sovereign than 12 months ago?
What is the cost to move from FRAGILE to STABLE on our weakest axis?
Which dependencies are tightly coupled to external volatility?
Do we have a standing plan if our binding constraint fails?
```
6. Failure Modes
```txt
DEPENDENCY_BLINDNESS
Cause: Leadership assumes diversification exists when it does not
Signal: SI score drops after first real audit
Fix: Mandatory dependency inventory with external validation
SURVIVAL_ILLUSION
Cause: Survival Horizon estimated by optimists, not operators
Signal: Actual shock recovery exceeds estimated horizon by 3x+
Fix: Stress test with operations team, not strategy team
DARK_NODE_DENIAL
Cause: Organisation refuses to map second-order dependencies
Signal: Surprise failure from unknown vendor or sub-process
Fix: Annual Dark Node Simulation mandated by board
COUPLING_COMPLACENCY
Cause: External stability assumed to be permanent
Signal: External shock transmits directly into core operations
Fix: Coupling assessment after every external disruption
SCORE_GAMING
Cause: Teams inflate axis scores to avoid scrutiny
Signal: SI score high but operational fragility visible
Fix: Independent scoring with evidence requirements
```
7. Case Application
Situation
Mid-market financial services firm.
Three regulatory jurisdictions. One core technology vendor.
Revenue concentrated in two client segments.
Problem
```txt
SI score: 31 (FRAGILE)
Weakest axis: Operational (single cloud vendor, no failover)
Survival Horizon: 4 days on operational axis
Dark Nodes: 7 identified (3 in sub-vendor chain)
Coupling: HIGH on financial and operational axes
```
Intervention
```txt
Phase 1 — Mapped all sub-vendor dependencies (Dark Node Simulation)
Phase 2 — Negotiated secondary cloud provider contract
Phase 3 — Diversified revenue across 4 client segments
Phase 4 — Created internal regulatory compliance capability
Phase 5 — Established 90-day cash reserve (financial decoupling)
```
Outcome
```txt
SI score: 62 (STABLE)
Survival Horizon: 47 days (operational), 90+ days (financial)
Dark Nodes reduced: 7 → 2
Coupling: HIGH axes reduced from 2 to 0
Board confidence: Measurably increased
```
8. Canon References
```txt
CX-20 — Institutional Sovereignty and External Exposure
Core principle: Autonomy is not declared, it is measured.
Application: The Sovereignty Index operationalises CX-20
by converting autonomy claims into auditable scores.
PD-31 — Pressure Dynamics and Structural Integrity
Core principle: Pressure reveals what structure conceals.
Application: The Survival Horizon and Volatility Coupling
components stress-test sovereignty under PD-31 conditions.
```
9. Product Integration
```txt
Sovereignty Index Dashboard → Executive Reporting
Dependency Inventory Tool → Risk Register
Dark Node Simulation Engine → Strategy Room
Survival Horizon Tracker → Board Pack (quarterly)
Coupling Assessment Module → Decision Exposure
Alert: SI below standard → Governance Escalation
```
10. Final Position
Sovereignty is not a feeling.
It is not a mission statement.
It is not an aspiration.
It is a number.
```txt
Measure it.
Stress test it.
Report it.
Improve it.
```
Institutions that cannot quantify their sovereignty
have already surrendered it.
The Sovereignty Index makes the invisible visible.
What is visible can be governed.
What is governed can survive.