Skip to content

About

A research publisher for AI power, not a generic AI site.

Compute Statecraft tracks how AI capability, advanced chips, capital flows, and state coalitions reshape power. The site is designed so readers and machines can audit scope, method, source quality, and revision history.

Object

Maps

Canonical story pages with confirmed claims, competing narratives, source stacks, and update history.

Object

Dossiers

Evergreen actor, organization, and country files with receipts, positions, networks, and timelines.

Object

Brief

A noindex daily scan that routes readers toward the canonical Maps and Dossiers instead of creating duplicate story URLs.

Who

Publisher identity

Compute Statecraft publishes under a single organizational standard instead of anonymous pages with shifting rules.

How

Visible method

Claims are constrained by provenance labels, source hierarchy, evidence drawers, and changelogs.

Why

Decision use

The goal is not maximal coverage. It is faster orientation on the power structure behind AI capability and policy disputes.

What makes the work auditable

  • Provenance labels: claims are marked SOURCED, INFERRED, or SPECULATIVE.
  • Primary-source preference: official records, policy text, filings, transcripts, and direct statements are prioritized.
  • Visible update history: Maps carry changelogs instead of silently rewriting assessments.
  • Structured disagreement: narratives can support, contradict, or contextualize a claim without pretending all evidence is equal.

What this site covers

  • AI capability and model competition when compute, chips, or state action materially shape the outcome.
  • Advanced semiconductors, packaging, interconnects, foundry leverage, and export controls.
  • Capital allocation, procurement, subsidies, enforcement coalitions, and standards alignment.

If a topic is disconnected from those power levers, it is usually out of scope. The detailed boundary lives on the coverage page.

Read coverage priorities

Coverage

What is in scope

The questions, sectors, and policy levers this site is built to track.

Method

How Maps are built

The claim pipeline, narrative deck, source triage, and correction loop.

Standards

How sources are treated

Primary, secondary, and social source roles, plus evidence limits.

What this site does not do

  • No broad “AI news” coverage when the story lacks a compute, chip, capital, coalition, or statecraft angle.
  • No truth scores, ideology meters, or automated actor ranking.
  • No thin topic pages made only for search traffic.
  • No claim is upgraded from inference to fact without direct source support.