Policy × capital × technology · San Francisco

Following capital until it becomes compute.

I study how public and sovereign capital commitments move from announcements to financed, powered, commissioned, and usable AI infrastructure, with a focus on Korea, the Gulf, the United States, and allied economies.

Korea ↔ Gulf ↔ USComparative lens
Announcement → AccessProject-level unit of analysis
Public sources onlyProvenance, confidence, contradictions
About

A translator across systems.

My work sits between policy goals, capital structures, technical constraints, and delivery. I am most useful where those systems need to be read together rather than in isolation.

I began in sociology and software engineering, moved through applied AI research and technology investment evaluation, and then worked in automotive cybersecurity and cross-border capital markets.

Coordinating a KOSDAQ IPO process and participating in and executing more than $50 million in fundraising taught me to separate headlines from closed transactions. I now bring that discipline to AI infrastructure: what is binding, what has been delivered, and what evidence would verify it?

Research lens
AI infrastructure policy, compute governance, sovereign investment, industrial strategy, and international technology partnerships.
Technical foundation
Software engineering and applied AI research. First author of the ACM paper on KERC 2019, a Korean emotion-recognition challenge conducted on Kaggle.
Capital-market experience
KOSDAQ IPO coordination, technology-company evaluation, and $50M+ in cross-border fundraising execution and participation.
Geographic focus
Korea, the Gulf, the United States, and allied middle powers.
Research agenda

Measure delivery, not ambition.

Large national AI announcements reveal intent. They do not yet establish that financing closed, power was secured, chips were contracted, facilities were commissioned, or outside users gained access.

01 · Delivery

From announcement to operation

Separate political intent, binding commitments, physical construction, commissioning, and verified workloads.

See the milestone framework
02 · Access

Capacity for whom?

Distinguish internal capacity, commercial access, startup allocations, research access, and public additionality.

See the access questions
03 · Verification

What would count as proof?

Preserve dated sources, contradictory claims, disclosure gaps, and uncertainty instead of converting them into false precision.

See the evidence protocol
Featured research note

A $10 billion AI announcement is not $10 billion of operational compute.

Why national AI strategies need a project-level view of financing, power, procurement, construction, commissioning, and access.

What matters is whether a country can coordinate capital, technology, power, construction, institutions, and access into a system that works.
Built systems

Research translated into tools.

A portfolio of public prototypes that turns institutional knowledge into auditable workflows. The research direction is primary; these projects show how I structure decisions and ship working systems.

Now

What I am working on.

The public brand should follow real work. These are the current lines of effort that will produce the next research artifacts.

01

Building the codebook

Defining project boundaries, delivery milestones, source hierarchy, confidence, and contradiction rules.

02

Coding the pilot

Starting with a small set of high-confidence Korea and Gulf projects before expanding the sample.

03

Strengthening methods

Developing quantitative and process-tracing tools for studying infrastructure delivery and access.

Connect

Bring evidence or a hard question.

I welcome corrections, source suggestions, and conversations with researchers and practitioners working on compute, power, chips, project finance, industrial policy, and international partnerships.