<!--
Source: https://scrutica.com/compute-leverage/coordination
Generated: 2026-09-04T00:13:00.456Z
Format: Markdown extraction of the rendered HTML at the source URL.
For the full agent guide see: https://scrutica.com/llms-full.txt
For the MCP server see: https://scrutica.com/api/mcp
-->

# Allied Coordination Gap Analyzer
## Where allied control binds

Where allied export control actually binds: per facility, whether compute inside an allied regime traces to a parent beyond it — the structural arbitrage two regimes could be played against.

[2 corrections · latest Aug 6, 2026→](/corrections#advanced-packaging-accountability "This page has had one or more public corrections. Click to see the full record.")Cite

CSVJSONJSON+Prov

PrintScreenshot

STRONG

104

chain reaches a non-aligned or restricted jurisdiction · 838,575 H100-eq GPUs

OPAQUE

2,955

chain terminates before a public-filing or government endpoint · 9,764,675 H100-eq GPUs

MILD

234

chain reaches allied-partial only · 2,547,669 H100-eq GPUs

NONE

964

every documented jurisdiction allied-coordinated · 12,727,391 H100-eq GPUs

The 30 largest of 3,059 STRONG/OPAQUE classifications (ranked by H100-equivalent GPUs, STRONG first). Population: 4,257 public-source facilities have a resolved ownership-chain classification. Facility rows sourced from licensed databases are excluded from this instrument entirely. Regime snapshot v2026-04-25. The interactive analyzer (requires JavaScript) loads the complete set with severity/jurisdiction filters, search, and per-facility chain detail; the toolbar above exports the full set as CSV or JSON.

Facility

Located

Operator

Severity

Hops

H100-eq

[DayOne Nusajaya Tech Park](/facilities/fac-dayone-johor-nusajaya)

MY

DayOne Data Centers Limited

STRONG

1

~281,455

[Alibaba Zhangbei](/facilities/fac-epoch-alibaba-zhangbei)

CN

Alibaba

STRONG

1

~132,895

[Huawei Horinger](/facilities/fac-epoch-huawei-horinger)

CN

Huawei Technologies

STRONG

1

~123,799

[VNET Bayin Ulanqab](/facilities/fac-epoch-vnet-bayin-ulanqab)

CN

VNET Group ADR

STRONG

1

~122,789

[G42 Microsoft 100 MW UAE Cluster](/facilities/fac-epoch-gc-g42-microsoft-100mw-uae-cluster)

AE

G42

STRONG

2

~55,000

[YTL AI Johor](/facilities/fac-epoch-gc-ytl-ai-johor)

MY

YTL Power

STRONG

2

~38,979

[G42 Microsoft 30 MW UAE Cluster A](/facilities/fac-epoch-gc-g42-microsoft-30mw-uae-cluster-a)

AE

G42

STRONG

2

~15,000

[G42 Microsoft 30 MW UAE Cluster B](/facilities/fac-epoch-gc-g42-microsoft-30mw-uae-cluster-b)

AE

G42

STRONG

2

~15,000

[Foxconn Big Innovation Cloud AI factory](/facilities/fac-epoch-gc-foxconn-big-innovation-cloud-ai-factory)

TW

Foxconn

STRONG

1

~13,050

[Saudi Data & AI Authority Sovereign AI factory](/facilities/fac-epoch-gc-saudi-data-ai-authority-sovereign-ai-factory)

SA

Saudi Data And Artificial Intelligence Authority

STRONG

1

~12,633

[Foxconn Hon Hai Kaohsiung Supercomputer](/facilities/fac-epoch-gc-foxconn-hon-hai-kaohsiung-supercomputer)

TW

Foxconn

STRONG

1

~11,642

[Aramco Groq Inference Cluster](/facilities/fac-epoch-gc-aramco-groq-inference-cluster)

SA

Saudi Aramco

STRONG

1

~7,475

[KAUST Shaheen-III](/facilities/fac-epoch-gc-kaust-shaheen-iii)

SA

King Abdullah University of Science and Technology

STRONG

1

~2,816

[Core42 SuperPOD](/facilities/fac-epoch-gc-core42-superpod)

AE

G42

STRONG

2

~1,272

[Yandex Chervonenkis](/facilities/fac-epoch-gc-yandex-chervonenkis)

RU

Yandex

STRONG

1

~502

[Saudi Aramco Dammam-7](/facilities/fac-epoch-gc-saudi-aramco-dammam-7)

SA

Saudi Aramco

STRONG

1

~500

[Condor Galaxy 3 (CG-3)](/facilities/fac-epoch-gc-condor-galaxy-3-cg-3)

US

G42

STRONG

2

~485

[Saudi Aramco Tuwaiq-1](/facilities/fac-epoch-gc-saudi-aramco-tuwaiq-1)

SA

Saudi Aramco

STRONG

1

~416

[Core42 AI-03](/facilities/fac-epoch-gc-core42-ai-03)

AE

G42

STRONG

2

~395

[Yandex Lyapunov](/facilities/fac-epoch-gc-yandex-lyapunov)

RU

Yandex

STRONG

1

~346

[Yandex Galushkin](/facilities/fac-epoch-gc-yandex-galushkin)

RU

Yandex

STRONG

1

~343

[Condor Galaxy 1 (CG-1)](/facilities/fac-epoch-gc-condor-galaxy-1-cg-1)

US

G42

STRONG

2

~243

[Condor Galaxy 4 (CG-4)](/facilities/fac-epoch-gc-condor-galaxy-4-cg-4)

—

G42

STRONG

2

~243

[Condor Galaxy 5 (CG-5)](/facilities/fac-epoch-gc-condor-galaxy-5-cg-5)

—

G42

STRONG

2

~243

[Condor Galaxy 6 (CG-6)](/facilities/fac-epoch-gc-condor-galaxy-6-cg-6)

—

G42

STRONG

2

~243

[Condor Galaxy 7 (CG-7)](/facilities/fac-epoch-gc-condor-galaxy-7-cg-7)

—

G42

STRONG

2

~243

[Condor Galaxy 8 (CG-8)](/facilities/fac-epoch-gc-condor-galaxy-8-cg-8)

—

G42

STRONG

2

~243

[Condor Galaxy 9 (CG-9)](/facilities/fac-epoch-gc-condor-galaxy-9-cg-9)

—

G42

STRONG

2

~243

[G42 Artemis](/facilities/fac-epoch-gc-g42-artemis)

AE

G42

STRONG

2

~82

[Bridge Data Centres MY06 (Sedenak Tech Park)](/facilities/fac-bridge-data-centres-my06-sedenak-johor)

MY

Bridge Data Centres (BDC)

STRONG

2

—

## How the analyzer classifies each facility

Four-step deterministic pipeline; every step is reproducible against the substrate plus the versioned regime snapshot linked below.

1\. Chain walk

Per facility, the classifier starts at COALESCE(operator\_org\_id, owner\_org\_id, hardware\_owner\_org\_id) and walks ownership\_chain\_edges upward, picking the highest-authority documented parent at each hop. Termination conditions: a publicly-listed entity (CIK present), a government entity, a public-filing-grade ancestor edge, a cycle, or 10 hops, whichever lands first. The walker is the same one the Facility Intelligence Card uses, so the card view and the analyzer never disagree about what the documented chain says.

2\. Posture lookup

Each hop's country\_hq normalizes to ISO 3166-1 alpha-2 and resolves through jurisdictional\_regimes.json (v2026-04-25, built from the Wassenaar participant list, EU 2021/821, EU Delegated Regulation 2025/2189, national export-control authorities, and CSIS Allen & Goldston, March 2025). Hops whose country does not resolve surface as 'unrecognized' rather than getting silently bucketed.

3\. Severity rule

STRONG when the chain reaches a non-aligned or restricted jurisdiction. MILD when the chain reaches at least one allied-partial jurisdiction without reaching a non-aligned/restricted one. OPAQUE when the chain terminates short of a public-filing or government endpoint AND no non-aligned/restricted jurisdiction has been documented; the gap may exist upstream but the public record does not say so. NONE when every documented jurisdiction is allied-coordinated AND the chain terminates at a documented endpoint.

4\. Conservative defaults

If a chain terminates opaquely AND a non-aligned hop is already documented, the row is STRONG (the documented signal carries). If a chain has no documented jurisdictions at all, the row is OPAQUE (no fabrication, period). Operators with no organization linked at all surface as a separate data-quality bucket inside OPAQUE so they can be filtered out without contaminating the gap analysis.

Severity reference

STRONGChain reaches a non-aligned or restricted jurisdiction. Compute physically sitting in an allied posture has parent-chain control extending to a jurisdiction outside the coordinated framework; this is the coordination-arbitrage signal the allied coordination-gap analysis is built to surface.

OPAQUEChain terminates short of a public-filing or government endpoint. A coordination gap may exist upstream of the documented chain but the public record cannot confirm it. Surfaced explicitly rather than defaulted to NONE.

MILDChain reaches at least one allied-partial jurisdiction (Wassenaar member or EU dual-use applicable, but no AI-compute-specific instruments); coordination on AI-compute items is not end-to-end.

NONEEvery documented jurisdiction in the operator-to-ultimate-parent chain runs coordinated AI-compute export controls aligned with the US-led trilateral framework.

Regime classifications are versioned; snapshots live under `data/processed/jurisdictional_regimes_versions/` so a researcher citing a Scrutica snapshot can re-run the classification against the historical regime data even after a later session updates the live file. Current snapshot: [v2026-04-25 JSON snapshot](https://scrutica.com/data/jurisdictional_regimes_versions/2026-04-25.json).

The Center for a New American Security publishes a program-level Sovereign AI Index (Chavez, Chilukuri, Scanlon, April 2026), which readers working on jurisdictional control over AI compute will want alongside this page: [cnas.org](https://www.cnas.org/). The analyzer here works at facility granularity: every classification names one facility and the documented ownership chain behind it, and no country-level ranking is published — the severity scale escalates only as that chain reaches further into non-coordinated jurisdictions.

## Regime coverage, scenarios, and the export-control timeline

Technology-by-regime coverage matrix, multilateral-regime structure, named coordination scenarios, and the export-control policy timeline. Reference material for the analyzer above; not a country-level ranking, and not intended as one.