WEO Methodology in 60 Seconds
What we document: AI infrastructure events demonstrating coordination or fragmentation dynamics
How we verify: 2+ primary sources OR 1 primary + 2 corroborating; 6-month verification lag
How we classify: Three tiers — T1: Cross-Bloc coordination, T2: Between-Bloc fragmentation, T3: Intra-Bloc coordination; four domains; four event types
What we tag: 11 categories identifying which industries each event's documented provisions address
What we assess: Environmental intersections across 5 tag types, producing the Warmth Engine Ratio (WER)
How we connect: Seven Coordination Connection types with confidence levels (CC-V, CC-E, CC-A)
How we profile: 7 capability dimensions assess sovereign control across the AI infrastructure stack — identifying which actors anchor each ecosystem
What we register: Verified commitments of computing capacity to societal challenges, assigned to a fixed challenge list

What WEO Tracks

The Warmth Engine Observatory tracks observable coordination and fragmentation dynamics across geopolitical blocs through verified events and mapped coordination connections.

Primary differentiator: The 7-type Coordination Connections taxonomy is the first systematic framework for tracking relationships between verified AI infrastructure events.

◈
Coordination
Active integration, cooperation, and alignment between or within blocs
◇
Fragmentation
Structural separation through parallel buildout or policy barriers

All classifications are based on observable facts from official public documentation. Implementation evidence is required, not announcements. Hidden intent, private communications, and future intentions are explicitly outside scope.

Processing Sequence

Events progress through five sequential stages. Failure at Stage 1 or 2 excludes the event from the database. Stages 3–5 classify qualifying events and document their relationships.

1
Event Verification
Gold-standard evidentiary requirements, implementation evidence, 6-month verification lag
2
Significance Assessment
Keohane Pre-Filter (coordination), Basel 5-Factor (physical), Route-Based (software), PISA-5 (policy)
3
Tier Classification
T1 Cross-Bloc, T2 Between-Bloc (Buildout/Restriction), T3 Intra-Bloc
4
Domain Classification
Energy/Infrastructure, Security, Technology, Trade
◈
Industry Tags
11 categories identifying which industries each event's documented provisions address
◈
Environmental Nexus Tags
5 types identifying documented environmental intersections; produces the Warmth Engine Ratio (WER)
5
Coordination Connections
Cross-event relationships documented with confidence levels

Geopolitical Significance Assessment

Events must demonstrate geopolitical significance to qualify for database entry. Four assessment pathways apply based on event nature, with an auto-qualification route for multi-nation coordination.

Keohane Pre-Filter
Multi-nation coordination
Events meeting Keohane coordination criteria auto-qualify. Multi-nation coordination is inherently significant.
Basel 5-Factor
Physical AI infrastructure
Size, Interconnectedness, Substitutability, Complexity, & Cross-jurisdictional Impact.
Route-Based
Software and platforms
Four strategic routes: Official Designation, Investment Scale, Multi-Criteria Assessment, AI Model Distribution.
PISA-5
Policy and institutional
Jurisdictional Significance, Regulatory Scope, AI Centrality (mandatory gate), Enforcement & Accountability, & International Relevance.

Event Types

Events are classified by Event Type — the mechanism by which the action occurs and the actor type involved. Event Type is distinct from Domain (which classifies subject matter) and Tier (which classifies coordination scale).

Coordination
2+ parties mutually accommodated positions through negotiation
Infrastructure
Physical/digital systems deployed by government/sovereign entity
Policy
Single jurisdiction enacted regulation (unilateral)
Corporate
Private sector action (partnerships, releases, market events)

Tier Classification

Events are classified into three tiers based on bloc participation and coordination dynamics — whether events represent coordination or fragmentation. Each tier captures a distinct dynamic in AI infrastructure alignment.

T1
Cross-Bloc Coordination
Coordination with verified adoption or implementation by the principal AI actor of each of at least two distinct ecosystems, with binding commitments and material integration.
Test: Principal AI actor verification + binding/implemented + material integration
T2
Between-Bloc Fragmentation
One bloc creating structural separation from the other through parallel buildout or policy restrictions.
Fragmentation Type: Buildout or Restriction · Explicit-Targeting or Impact-Demonstrated · Western-Led or Eastern-Led
T3
Intra-Bloc Coordination
Coordination occurring entirely within a single bloc — Western or Eastern.
Bloc: Western Bloc (WB) or Eastern Bloc (EB)

Domain Classification

Events are assigned to one of four domains based on their primary subject matter. Domain classification captures what the event is primarily about.

Energy/Infra
20–60 yr
Security
15+ yr
Technology
2–5 yr
Trade
3–10 yr

Durability ranges reflect typical commitment horizons for events within each domain.

Industry Tags

Each event is tagged with the industry whose operational landscape its documented provisions most directly address. Industry tags are distinct from classification — they identify an external relationship rather than an intrinsic property of the event.

Semiconductors & Equipment
Cloud, Data Centres & Connectivity Infrastructure
AI Software & Platforms
Defence & Aerospace
Energy & Power Infrastructure
Financial Services & Investment
Mining & Critical Minerals
Trade & Logistics
Automotive & Manufacturing
Quantum Computing Infrastructure
Telecoms
Structural secondary only

Primary/secondary structure: Each event receives one primary tag. Up to two secondary tags document specific pathways to other industries via mechanism statements.

Environmental Nexus Tags

Each qualified event is assessed for environmental intersections across five tag types. Environmental Nexus Tags (ENTs) are an analytical enrichment layer parallel to industry tags — they identify documented relationships between events and environmental systems, not intrinsic properties of the event itself. A tag is applied when the event meets the qualifying threshold for that type.

Resource Demand
Event → Environment
Environmental Enablement
Governance → Event
Environmental Consequence
Event → Environment
Environmental Dependency
Environment → Event
Environmental Coordination
Governance ↔ Environment

Each applied tag carries a mechanism statement — a one-sentence document-verifiable description of how the environmental intersection manifests. Events carry 0–5 tags. Tags use a binary qualification model with evidence classified as Documented or Assessed.

Warmth Engine Ratio (WER) ENT-1 ÷ ENT-5

The Warmth Engine Ratio is the ratio of environmental resource demand to environmental governance coordination across the event database. A declining ratio indicates governance converging with demand; a rising ratio indicates demand outpacing governance response.

Coordination Connections

Novel Framework Event Relationship Layer

Coordination Connections are relationships between verified events — the first systematic taxonomy for mapping how AI infrastructure events influence, enable, or respond to one another. Each connection requires documentary evidence meeting confidence thresholds. No existing framework captures these event-to-event relationships.

Policy Cascade Joint Issuance Funding Flow Regulatory Enablement Response Framework Family Parallel Policy

Confidence Levels: CC-V (Verified) requires primary source documentation. CC-E (Established) requires authoritative statement with corroboration. CC-A (Analytical) permits analyst assessment for parallel policy patterns.

Auditability: Every connection can be verified against the evidence cited.

Actor Capability Profiles

Novel Framework Sovereign Capability Assessment

Actor Capability Profiles assess sovereign control across seven dimensions of the AI infrastructure stack. Each dimension tests whether an actor holds independent, domestically controlled capability at the leading edge. The framework identifies which actors anchor global AI ecosystems and which operate within them — providing the structural basis for WEO's bloc classification system.

Chip Design Fabrication Equipment Compute Models Regulation Investment

Four designations classify actors by their structural role. Principal AI Actors (PAA) hold full-stack or near-full-stack capability and anchor an ecosystem — each defines a WEO bloc. AI Infrastructure Keystones (AIK) control chokepoint capabilities that both ecosystems depend on. Advanced Capability State (ACS) hold significant capability that collapses without their principal ecosystem. Participants operate within an ecosystem without independent structural leverage.

Actor capability profiles and bloc alignment data are available on the Bloc Membership Register. The interactive capability panel on the Map provides full dimension detail and source evidence for each actor.

Compute Commitment Register

Novel Framework Compute Commitment Layer

The Compute Commitment Register records which actors have committed computing capacity to which societal challenges, and on what evidence. Each record is one documented commitment, such as a budget line, an allocation award, or a securities filing — verified against its source and recorded as declared. Quantities are never converted or summed, and a record's presence carries no information about its scale beyond its band.

Grant or Credit Programme Dedicated Allocation Sovereign or Multilateral Infrastructure Commercial or Philanthropic Supply

Challenge assignment: Commitments are assigned to the Challenge List Reference — a fixed list of societal challenges drawn from the published lists of major institutions, in which a challenge appears only where several institutions name it independently. The Observatory authors none of the categories; the list is refreshed on a set cycle.

Position in the Observatory: The register is a separate layer with its own unit of analysis, the record. It changes no event's classification and meets the event corpus at one point — a Challenge Attribution, recorded where an event's own source is also a register record.

The register is published as dated observations on the Commitments page. Method and first observation: The Compute Commitment Register — Methodology Working Note (Zenodo), also available as a self-hosted edition.

Verification Standards

2+
Primary Sources
6mo
Verification Lag
70%+
Confidence Floor

WEO aims to meet the verification rigour of major financial indices. All events require either 2+ primary sources OR 1 primary + 2 corroborating sources. The 6-month verification lag ensures implementation confirmation before database entry. All cited sources are submitted to the Internet Archive, with capture status tracked across the full evidence base. Current preservation rate: — across — cited source records.

Low-confidence events (<70%) are excluded from the database. Only HIGH (90%+) and MEDIUM (70–90%) confidence events appear in WEO.

Coverage and Structural Visibility

WEO's documentation-based verification applies consistently across all blocs and domains. Coverage varies because documentation accessibility varies — some regulatory landscapes produce denser public records than others, and classified activity is excluded from scope across all blocs. Event counts in less-documented areas represent conservative lower bounds, not the full extent of AI infrastructure activity.

Methodological Foundations

WEO applies proven institutional methodologies to tracking AI infrastructure coordination dynamics.

Keohane (1984)
After Hegemony Framework
Definition of coordination — mutual policy adjustment through negotiation
Basel Committee (2018)
G-SIB Methodology
Systemic importance assessment for physical infrastructure via 5-factor framework
Cross-Sector Standards
Verification Protocols
ICD 203/206, UK PHIA, Reuters, EFCSN, Jane's, GRADE, Cochrane
Finnemore & Sikkink (1998)
Norm Cascade Research
33% convergence threshold for demonstrated coordination validation

Full Documentation

WEO Methodology Manual
Complete technical specification covering all 10 chapters
DOI: 10.5281/zenodo.18427565
WEO Methodology Rationale
Empirical derivation and calibration justification for all methodology components
DOI: 10.5281/zenodo.18427582