Skip to content
Sprint projectFeb 2, 2026London

Modelling the impact of verification in cross-border AI training projects

Fabio Marinello · Team I need to go sleep

Submitted to The Technical AI Governance Challenge. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Modelling the impact of verification in cross-border AI training projects

Code (opens in new tab)
Share

This paper develops a stylized game-theoretic model of cross-border AI training projects in which multiple states jointly train frontier models while retaining national control over compute resources. We focus on decentralized coordination regimes, where actors publicly pledge compute contributions but privately choose actual delivery, creating incentives to free-ride on a shared public good. To address this, the model introduces explicit verification mechanisms, represented as a continuous monitoring intensity that improves the precision of noisy signals about each actor's true compute contribution. Our findings suggest that policymakers designing international AI governance institutions face a commitment problem: half-measures in verification are counterproductive, and effective regimes require either accepting some free-riding or investing substantially in monitoring infrastructure.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. The introduction frames cooperation as potentially safety-enhancing, but I would like to see more discussion on, or explicit assumptions about, how this project contributes to AI safety (if that is the objective).

    Currently, the project findings support international AI development efforts. This could diffuse race dynamics , and democratise frontier AI by involving middle powers in development. It would be good to be more explicit about whether, and under what conditions, these findings could also accelerate AI development or increase race dynamics.

  2. The "verification valley" is the headline here, and it's a genuinely useful concept for policy people to have in their vocabulary. But once you hear it, it's kind of obvious: half-assed monitoring catches some cheaters (who then get punished) without actually deterring anyone. You end up paying for enforcement that doesn't work. The model tells you this formally, which has value, but it's not exactly a surprise.

    The bigger issue is that everything here lives in math-land. Every parameter is made up. No attempt to calibrate against, say, the IAEA's actual detection rates for nuclear material accounting, or carbon market compliance data, or anything real. Even one grounded parameter would change this from a toy model into something a policy person could point to.

    The actors in the model also have no memory. They optimize one round at a time. In real international relations, the whole game is reputation: "we cooperated last time, so you should too." Stripping that out probably changes the results in ways that matter. And the distributional result (big countries lose, small countries win) is buried when it should be front and center: if the US or China face net costs from a verification regime, the regime doesn't happen. That's not a footnote, that's the whole ballgame.

    Read full reviewShow less

Cite this project

@misc{marinello2026modelling,
  title = {{Modelling the impact of verification in cross-border AI training projects}},
  author = {Fabio Marinello},
  year = {2026},
  month = feb,
  note = {Submitted to The Technical AI Governance Challenge, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/modelling-the-impact-of-verification-in-crossborder-ai-training-projects-go92}},
  url = {https://apartresearch.com/sprints/projects/modelling-the-impact-of-verification-in-crossborder-ai-training-projects-go92}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026