Events Database

Each event meets WEO's verification standards for substantive AI infrastructure connection — whether through direct AI designation, dedicated AI provisions in policy frameworks, or documented AI-enabling capacity. The database maps relationships between events through seven Coordination Connection types, wherever supported by sufficient documentary evidence.

Questions this database addresses:
  • Where is AI infrastructure capacity being built—and by whom?
  • Where have restrictions triggered documented infrastructure responses?
  • Which critical materials and supply chains show cross-bloc dependencies?
Connection Types
Confidence Levels
Connections identify documented relationships between events. CC-V and CC-E require documentary evidence; CC-A reflects analyst assessment of policy similarity.
WB
EB
XB
n
TechnologyTech
HIGH
MED
HIGH
—
Energy / InfrastructureEnergy / Infra
HIGH
MED
—
—
SecuritySecurity
MED
LOW
—
—
TradeTrade
LOW
LOW
—
—
WEO's documentation-based verification standard applies consistently across all blocs. Coverage distribution reflects how AI infrastructure coordination is documented across different jurisdictions and institutional cultures: multilateral frameworks, regulatory disclosure conventions, and infrastructure deployment practices generate varying levels of publicly discoverable documentation. Cross-language verification workflows extend source reach beyond English-language documentation, but event counts in any bloc or domain represent conservative lower bounds on AI infrastructure coordination activity, bounded by documentation accessibility rather than event occurrence. The Security domain is additionally constrained by national security classification across all blocs — military and intelligence AI cooperation occurs at levels that public documentation does not reflect, making observable event counts in this domain a particularly conservative lower bound.
Coverage confidence reflects WEO's assessment of documentation accessibility per domain and bloc, based on methodology analysis and observed discovery patterns. Event counts update with the database; confidence designations are reviewed at methodology milestones. Why does coverage vary?
Data Currency and Corrections

Event data is verified against primary and corroborating sources at the time of entry and during periodic corpus-wide audits. Source authorities may revise published figures after initial release, and operational metrics — capacity, participation, investment — evolve after implementation. Where corrections are identified through internal audit, source revision, or external reporting, events are updated with documented correction histories.

Database records are assessed against a versioned methodology. Where a new version tightens qualification criteria, existing records are re-derived against the edition in force — reclassified, or removed from the live corpus and preserved archivally. A removed event identifier is never reused; any later re-qualification enters as a new record. A removed connection is eligible for fresh assessment under the methodology then in force. Methodology corrections are recorded as errata and corrigenda at warmthengine.com/research/methodology/errata/.

Users identifying potential inaccuracies are invited to contact [email protected] with the event ID and supporting evidence.

Tier
Bloc
Type
Domain
Industry
ENT
Sample events with full analysis
‹‹‹
›››
ID Event TypeEvent Type: Coordination, Infrastructure, Policy, or Corporate — HOW the action occurred Date TierCoordination Tier: T1 Cross-Bloc, T2 Between-Bloc, T3 Intra-Bloc BlocBloc Attribution: Western, Eastern, Cross-Bloc, or Western/Eastern-Led DomainSubject Matter: Energy/Infrastructure, Security, Technology, or Trade IndustryIndustry tag: which industry's operational landscape is most directly addressed ENTEnvironmental Nexus Tags: where AI infrastructure coordination intersects with environmental systems CCCoordination Connections — relationships between verified events VerifVerification Checkpoints: AI Connection, Threshold, Implementation, Currency ConfConfidence Tier: A (High 90%+), B (Medium 70-90%) SrcSource Count: Cumulative Primary + Corroborating across all versions

Event IDs are permanent identifiers. Gaps in numbering reflect events removed during verification or due to subsequent resolution.

Subscriber Access
Invalid access token.
Not a subscriber? Subscribe here