FCPI Index
Finality Choke Point Index (FCPI): Measuring Platform Power and Strategic Dependency
A comparative method for identifying when control over a platform, infrastructure layer, or service becomes control over completion — the point at which dependency becomes leverage.
Finality Choke Point Index
A comparative method for identifying when a platform, infrastructure layer, or service occupies a point where outcomes become effective, binding, or hard to reverse. FCPI shifts analysis away from access alone and toward finality — the layer at which an action is actually settled, routed, executed, or made hard to reverse.
Choke Point
- ●Whether an organisation is building around a useful, important, or strategically decisive provider
- ●Cases where access looks available but completion remains externally controlled
- ●In procurement: architectures that place decisive layers outside meaningful control
- ●In risk assessment: kill-switch and continuity vulnerabilities
- ●In regulation: the difference between manageable dependency and non-substitutable dependence
- ●In design: sovereignty-by-design constraints before dependency hardens
- ●Not a reputation score — a benevolent provider can still occupy a dangerous choke point
- ●Not a moral judgment — a controversial provider can still remain replaceable
- ●Not a prediction that a provider will behave badly — FCPI measures structural position, not intent
- ●Not a substitute for antitrust, resilience, or sector-specific regulation
- ●Not a doctrine — scores depend on correct function definition, realistic time horizons, and evidence quality
- ●Not falsely precise — the framework is a diagnostic tool that requires explicit assumptions and stated confidence
Finality Choke Point Index (FCPI)
The Finality Choke Point Index (FCPI) is a framework for measuring when a platform, infrastructure layer, or system becomes a strategic dependency that others cannot realistically bypass.
It answers one core question:
When does a system stop being a supplier and become a control point?
A system scores high on FCPI when:
- critical functions depend on it
- alternatives are weak or slow
- switching is difficult under real conditions
- control of the system creates leverage over others
The FCPI Index is used to analyze:
- cloud platforms
- AI model providers
- satellite networks (e.g. Starlink)
- payment systems (e.g. SWIFT)
- digital identity infrastructure
In plain language
The FCPI Index measures how hard it is to operate without a system.
- Low FCPI → easy to replace
- Medium FCPI → costly to replace
- High FCPI → cannot be replaced in time
At high FCPI levels, the system becomes part of the governing environment, not just a tool.
Why the FCPI Index matters
Modern infrastructure is increasingly controlled by private platforms.
This creates a new problem:
- systems are critical
- but governance is not aligned with that criticality
The FCPI Index helps identify:
- hidden dependencies
- emerging choke points
- sovereignty risks
- coercive leverage inside infrastructure
FCPI vs other frameworks
| Framework | What it measures | Limitation |
|---|---|---|
| Market dominance | Size and market share | Misses dependency |
| Vendor risk | Supplier reliability | Misses systemic impact |
| Resilience analysis | System stability | Misses control and leverage |
| FCPI Index | Control over critical functions | Focused on structural dependency |
Examples of high FCPI systems
Starlink
- Provides mission-critical connectivity
- Hard to replace in conflict conditions
- Control affects military outcomes
See the full Starlink case study
Cloud providers (AWS, Azure)
- Host critical applications and data
- Migration is slow and costly
- Control affects business continuity
SWIFT
- Enables global financial messaging
- Exclusion removes access to global finance
- Control has geopolitical impact
Browse all scored examples in the case library.
How to use the FCPI Index
The FCPI Index is used to:
- Identify critical dependencies
- Assess substitution risk
- Evaluate governance exposure
- Design fallback strategies
It is most useful for:
- policymakers
- infrastructure operators
- investors
- security analysts
How FCPI is calculated
The FCPI score is based on six factors:
- Finality: does the system control execution or outcomes?
- Criticality: how important is the function?
- Reach: how many depend on it?
- Substitutability: are alternatives viable?
- Transition cost: how hard is switching?
- Governance leverage: how much control does it create?
Each factor is scored and combined into a 0–100 index. See how scores work.
The Finality Choke Point Index is a comparative method for identifying when a platform, infrastructure layer, or service occupies a point where outcomes become effective, binding, or hard to reverse.
It exists to answer a narrower question than size, market share, or popularity:
When does control over a system become control over completion?
That is the point at which dependency becomes leverage. The Starlink case is one of the clearest examples.
Why FCPI exists
Many contemporary claims of sovereignty rely on governance, orchestration, or contract rather than ownership. Sometimes that works. Often it does not.
FCPI is designed to distinguish those cases.
It shifts the analysis away from access alone and toward finality: the layer at which an action is actually settled, routed, executed, recognised, admitted, or made hard to reverse. The framework is meant to help policymakers, analysts, and system designers distinguish operational authority from illusory control.
Core intuition
A finality choke point appears when two conditions coincide:
- a process becomes effectively complete or irreversible;
- control over that point is concentrated enough to shape what others can do.
A system does not become strategically decisive only because it is large. It becomes strategically decisive when others can no longer operate around it in time.
Core concepts
Finality
Finality is the point after which an action is effectively completed and cannot be meaningfully re-routed, reversed, or re-governed without major cost.
Depending on the system, finality may mean:
- settlement of value;
- routing of communications;
- execution of a satellite command;
- admission to compute;
- model access or inference policy;
- identity assertion or compliance recognition.
The key issue is not the label. It is whether control at that layer determines whether others can complete the relevant activity.
Choke point
A choke point is a node or layer where:
- critical flows converge;
- substitutes are absent or non-equivalent;
- interruption or denial has system-wide consequences.
A finality choke point is therefore a layer where concentrated control over completion creates disproportionate leverage.
Formal definition
FCPI measures the degree to which control over points of finality is concentrated and externally governed within an infrastructure system, and therefore the structural limits of exercising sovereignty without ownership or direct control of the underlying decisive layer.
The five FCPI parameters
FCPI uses five scored parameters. Each is normalised between 0.0 and 1.0.
1. Concentration of Finality (CF)
How centralised is the decisive point of completion?
- 1.0 means finality is controlled by one actor or a tightly bounded set of actors.
- 0.0 means finality is widely distributed.
This parameter asks where completion actually happens and how concentrated that layer is.
2. Jurisdictional Control (JC)
Who governs the decisive layer in legal and political terms?
- 1.0 means finality lies fully outside the subject’s jurisdiction.
- 0.0 means finality lies fully inside it.
This parameter addresses whether the authority over finality is external even if access appears local.
3. Enforceability Asymmetry (EA)
Who can compel whom when conflict or disagreement emerges?
- 1.0 means the controller of finality holds overwhelming enforcement advantage.
- 0.0 means power is broadly symmetric.
This parameter captures whether the user of the system can meaningfully contest or override the decisive layer.
4. Substitutability of Finality (SF)
How hard is it to replace the decisive layer with a functionally equivalent alternative?
- 1.0 means substitution is effectively impossible within the relevant horizon.
- 0.0 means substitution is trivial.
This is not a question of theoretical alternatives. It is a question of realistic alternatives under actual time pressure.
5. Temporal Override Power (TOP)
How easily can an external actor interrupt, suspend, or alter finality in real time?
- 1.0 means override is immediate and external.
- 0.0 means override is absent or internalised.
This parameter captures kill-switch exposure, emergency revocation risk, and unilateral interruption capacity.
Formula
The underlying FCPI score is:
FCPI = (CF + JC + EA + SF + TOP) / 5
This produces a value between 0.0 and 1.0.
On this site, that underlying value can also be presented as a score out of 100 for readability. The public-facing score is a display layer. The method remains the same.
Interpretation
0.0–0.2 — Sovereignty achievable without ownership
Finality is distributed enough, or controlled closely enough, that governance and architecture can plausibly substitute for ownership.
0.2–0.4 — Conditional sovereignty
Control without ownership may hold under normal conditions, but remains exposed under stress.
0.4–0.6 — Phase-dependent sovereignty
Governance may work in some phases or horizons, but fail in others. Stress conditions are likely to reveal hard limits.
0.6–0.8 — Severely constrained sovereignty
The decisive layer remains structurally external. Governance helps, but does not remove the core dependency.
0.8–1.0 — Sovereignty impossible without ownership or direct control
Finality is so concentrated and externally governed that orchestration cannot substitute for control of the decisive layer.
How to apply FCPI
FCPI should never be assigned in the abstract. It must be anchored to a clearly defined function, unit, and horizon.
Step 1 — Define the primary function
State exactly what activity is being completed.
Examples:
- final settlement of cross-border value;
- beyond-line-of-sight connectivity for maritime control;
- hosted model access for reasoning and workflow execution.
Step 2 — Define the unit of analysis
Score the relevant layer, not the entire sector by default.
Examples:
- clearing layer rather than “finance” in general;
- network control and update authority rather than “space” in general;
- hosted inference layer rather than “AI” in general.
Step 3 — Set the assessment horizon
All FCPI claims are time-bound.
A system may be replaceable over three years and non-replaceable over thirty days. Horizon must therefore be explicit before any score is read as meaningful.
Step 4 — Identify the point of finality
Ask where completion actually occurs.
In finance, that may be clearing and settlement currency.
In LEO, it may be routing, cryptographic keys, firmware authority, or service disablement.
In AI, it may be compute admission, model weights, inference policy, or account-level revocation.
Step 5 — Score the five parameters
Assign CF, JC, EA, SF, and TOP using explicit evidence and stated assumptions.
FCPI should be treated as a disciplined hybrid method: structured judgment anchored in observable constraints.
Step 6 — Record confidence and rationale
A score without a function, horizon, confidence level, and short narrative should not be treated as a valid FCPI assessment.
The rationale matters more than false precision.
Cross-domain intuition
FCPI is designed for comparison across infrastructure types.
Finance
Financial infrastructure is a hard boundary case. If final settlement and settlement currency lie outside your jurisdiction, sovereignty is largely impossible regardless of messaging access or internal orchestration.
LEO connectivity
LEO systems are more variable. Finality is distributed more widely than in finance, so orchestration, redundancy, and architectural design can sometimes lower exposure. But sovereignty remains constrained where routing, keys, firmware, or disablement authority stay external.
AI cloud and model access
AI cloud infrastructure often resembles finance more than LEO. Compute admission, hosted inference, policy enforcement, and model withdrawal can create highly concentrated finality points with immediate override power.
What FCPI is not
FCPI is not:
- a reputation score;
- a moral judgment;
- a prediction that a provider will behave badly;
- a substitute for antitrust, resilience, or sector regulation.
A benevolent provider can still occupy a dangerous choke point. A controversial provider can still remain replaceable. FCPI measures structural position, not intent.
What FCPI helps reveal
FCPI is useful when organisations need to know whether they are building around:
- a useful provider;
- an important provider;
- or a strategic choke point.
It is especially useful where access looks available, but completion remains externally controlled.
Limits of the method
FCPI does not eliminate judgment.
Scores depend on:
- correct definition of function;
- appropriate choice of unit of analysis;
- realistic time horizons;
- evidence quality;
- explicit assumptions about substitutes and override power.
The framework should therefore be treated as a diagnostic tool, not a doctrine.
Design and policy relevance
FCPI can be used:
- in procurement, to flag architectures that place decisive layers outside meaningful control;
- in strategic risk assessment, to expose kill-switch and continuity vulnerabilities;
- in regulation, to distinguish manageable dependency from non-substitutable dependence;
- in system design, as a sovereignty-by-design constraint rather than a post hoc complaint.
FAQ
What is FCPI?
The Finality Choke Point Index measures when a system becomes a critical dependency that cannot be bypassed.
What is a choke point in infrastructure?
A choke point is a control layer that others must pass through to complete critical actions.
Is FCPI about monopoly power?
No. A system can have high FCPI without being a monopoly. It measures dependency, not market share.
Why is FCPI important?
Because modern power increasingly comes from controlling infrastructure, not just owning assets.
Bottom line
FCPI starts from a simple proposition:
Sovereignty collapses at points of finality under external control.
The purpose of the framework is not to abolish governance thinking. It is to identify where governance is enough, where it is conditional, and where it becomes an illusion.
Where to go next
- Platform Sovereignty
- Indispensability Threshold
- Starlink case
- Foundation models case
- Cloud providers case
- AI models case
- SWIFT case
Conclusion
The FCPI Index reframes power in digital systems.
The key question is no longer:
“Who owns the system?”
But:
“Who cannot operate without it?”