Inha Seo

Research · Capital to Compute

I trace what announced capital becomes.

A public-source research notebook on the chain between AI infrastructure announcements and compute that is financed, powered, commissioned, and actually usable.

Read the agendaSee the work behind it
Public sourceauditable records first
Korea · Gulfinitial comparison lens
Draft codebookpilot in development
No rankingunknown stays unknown

01 / The project

Sovereign Compute Delivery Observatory

National AI strategies often put targets, partnerships, facilities, chips, and investment in one sentence. The observatory separates those claims and follows one project at a time.

The working artifact is deliberately modest: a draft codebook, a source and confidence protocol, and a small Korea–Gulf pilot. There is no completed dataset, ranking, or country score to report yet.

QuestionWhen does public or sovereign capital become real, usable AI compute—and where does that conversion stall?

02 / Three ledgers

Every project gets read against three records.

This keeps political intent, corporate delivery, and closed money from being counted as the same thing.

01

The state's target

A dated national strategy, ministry plan, budget, or capacity goal. This is intent.

02

The corporate pipeline

A named campus, partnership, vendor commitment, or capacity figure. This is a delivery claim.

03

Money that closed

An approved budget, signed financing, completed transaction, or binding procurement. An MOU is not this ledger.

03 / Delivery stages

Eight stages keep a ceremony and a running cluster in different cells.

Each milestone gets a date, a source, and a confidence note. The stages describe delivery; access is assessed separately.

  1. 01AnnouncementA project is named.
  2. 02Formal structureAn approved vehicle or agreement exists.
  3. 03Binding financingCapital is committed through a binding mechanism.
  4. 04Power and siteLand and a credible utility path are in place.
  5. 05Binding procurementCritical hardware, EPC, or systems work is contracted.
  6. 06ConstructionPhysical delivery is observable and dated.
  7. 07CommissioningThe facility is powered, tested, and accepted.
  8. 08Verified operationThe system is serving intended workloads.

04 / Access and evidence

Delivery is not the same as public capability.

A project may operate while remaining closed to local startups and researchers. Another may offer public access while depending on foreign vendors. I record who can apply or buy, how capacity is allocated, and whether public support created additional capability.

Sources closest to the event come first: government decisions, permits, utility records, regulatory filings, and binding procurement, vendor, engineering, or construction disclosures. Company announcements and strong reporting are useful; databases are leads.

05 / Current outputs

AgendaCapital to ComputeWhy announcements need project-level evidence ↗ Career bridgeCapital, diligence, deliveryCompany-side work behind the research ↗ Open notebookSource corrections welcomeSend a document or contradiction ↗
Limits are part of the method. I will not publish confidential deal or government information, security-sensitive facility details, or causal findings a small pilot cannot support. When the public record does not establish a milestone, the value is unknown—not zero, delay, or failure.