Policy, sovereign compute, and standards ledger

As of: 2026-08-26 Issue: #9315 Authority: index.json

Result first

Regional infrastructure is not a uniform pool. Export controls, sovereign procurement, capacity-allocation rules, model regulation, and fabric standards change what hardware can be acquired, who can use it, where workloads may run, and which evidence a deployed service must retain.

This ledger separates proposal, rule, enforcement posture, tender, allocation, award, delivery, and operating capacity. It is not legal advice.

Operative advanced-computing replacement timeline

Effective date Jurisdiction / destination Operative state Deployment meaning Missing delivery evidence
2025-05-13 U.S. global AI export framework BIS withdrew enforcement of the January 2025 AI Diffusion Rule and promised a replacement The proposed tier framework was not the operative deployment matrix Replacement rules, licenses, shipments, installations, and runtime receipts
2026-01-13 China, approved customers H200, MI325X, and similar chips moved to case-by-case license review under supply, compliance, screening, and U.S. testing conditions A qualifying application can be reviewed; approval is not automatic Approved customers, quantities, licenses granted, shipments, installed clusters, useful goodput
2026-07-10 UAE Government and approved companies UAE moved from EAR D:3/D:4 to A:5; specified advanced-computing items, including AI chips and servers, became eligible for license-free treatment under the bilateral framework Destination/end-user eligibility differs materially from the rescinded global tier proposal Approved-company census, item quantities, shipments, facilities, healthy capacity, schedulable workloads

Version every regional hardware claim by effective date, destination, end user, item/ECCN, license or exception, conditions, quantity, shipment, installation, and engine/runtime receipt.

Dated ledger

Date / jurisdiction Instrument or program Current observed state Quantified boundary Operational implication
2025-05-13 / United States BIS AI Diffusion Rule rescission and chip guidance BIS said the January 15 rule would be rescinded before its May 15 compliance date, told enforcement not to enforce it, and issued PRC-chip/model/diversion guidance. Two rule dates; no capacity number. Bind hardware eligibility to effective/enforcement state, end user, end use, destination, and exact control text.
2025-01-31 / India IndiaAI Compute Capacity Multi-provider, subsidized sovereign compute marketplace announced and allocations published. >18,000 heterogeneous GPU compute units. Track provider, SKU, allocation, subsidy, project window, and start-by date; do not treat units as one cluster.
2026-07-30 / European Union EuroHPC AI Gigafactories call Tender call, not delivered sites. Up to 7 gigafactories; up to €10B public support; ≥€20B expected private investment; adjacent network of 19 AI Factories. Track tender → award → financing → site → installed/accepted capacity → access allocation.
2026-08-02 / European Union AI Act application/enforcement General application and enforcement began; GPAI obligations had applied since August 2, 2025. Dates, not compute capacity. Deployment receipts may need jurisdiction, provider/deployer role, model/system classification, documentation, transparency, and audit evidence.
2024-05-30 / Singapore Green Data Centre Roadmap Policy roadmap and later allocation calls condition growth on efficiency and green energy. ≥300 MW near-term additional capacity; potentially ≥200 MW more through green energy. Roadmap MW is not operating AI IT load; retain award, energy-source, efficiency, construction, and commissioning states.
2026-07-16 / global consortium Ultra Ethernet Specification 1.0.3 Current published version after 1.0, 1.0.1, and 1.0.2 corrections. Version/date lifecycle. Record deployed version and compliance evidence; a standard does not prove interoperability or goodput.

State machines

Export-control state

proposal -> published rule -> effective -> enforceable
         -> amended / stayed / rescinded / replaced
transaction = item + performance + destination + end user + end use + date + license

A country label alone is insufficient. A policy announcement alone is insufficient.

Sovereign-compute state

budget/announcement -> procurement/tender -> provider empanelment -> award
-> financed -> built/available -> allocated -> started -> healthy usage -> useful output

Public investment, procurement ceiling, GPU-unit count, and active allocation are not interchangeable.

Standard state

draft -> published specification -> correction/revision -> implementation
-> compliance test -> multi-vendor interoperability -> production deployment

IETF Internet-Drafts remain drafts. Consortium specifications remain distinct from certified deployed behavior.

Architecture consequences

  1. Regional scheduling: route only after checking data locality, hardware eligibility, provider/deployer obligations, and sovereign-access rules.
  2. Hardware receipts: include ownership, provider, SKU, physical location, export or license condition, and the policy version in force at acquisition/use time.
  3. Capacity accounting: keep public funding, tender value, allocated GPU units, roadmap MW, and useful goodput in separate fields.
  4. Network receipts: name fabric implementation, specification revision, congestion control, and observed compliance/interoperability.
  5. Change handling: policy and standards must be append-only events with effective dates; silent replacement destroys reproducibility.

Remaining gaps