Skip to content
Sprint projectFeb 2, 2026

Maxwell

Patrick Duffy, Emlyn Graham, Josh Tuffy · Team Compute Permit Markets Simulator

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

Maxwell: A Mechanism for Compute Permitting under Imperfect Monitoring

Traditional command-and-control governance fails when monitoring is imperfect or expensive. We introduce 'Sovereign Subsidies', a novel cryptoeconomic mechanism (ERC-20 + Slashing) that aligns private profit with public safety.

Using a multi-agent simulation (Rust/Solara) and a conversational interface (ElevenLabs), we demonstrated that a $0.84 subsidy is sufficient to deter defection even with <5% audit frequency. This effectively solves the "Imperfect Monitoring" problem in compute governance.

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. There's a problem with the headline number that the paper doesn't address. The "phase transition at 50% compliance" sounds dramatic, but 50% is also what you get mechanically when you hand out 10 permits to 20 agents. Half the firms have permits and are compliant by default. So how much of that transition is deterrence and how much is just... math? Running the same sweep with different agent-to-permit ratios (say, 20 agents / 5 permits, or 20 agents / 15 permits) would answer this pretty quickly, and the fact that it wasn't done is a miss.

    The model is also really small: 20 agents, 10 time steps. That's barely enough to see anything interesting happen. You can't get reputation effects, coalition formation, or escalation dynamics in 10 rounds. The authors clearly know this because their future work section reads like a better version of the paper (dollar-denominated fines, dynamic reputation, compute thresholds). That's a bit of a red flag when the to-do list is more compelling than the results.

    Credit where it's due: the heatmap is clear, the code is open-source, and the security considerations section honestly grapples with the dual-use problem. The bones of a good project are here; it just needed more time in the oven.

    Read full reviewShow less
  2. The tradeoff presented is excellent and the results are intriguing. The central result-- that penalty size doesn't really seem to matter relative to p(getting caught)-- is a bit confusing and makes me want to ask the authors more details about how their model works.

    To be very simple about it, there is definitely a penalty that is large enough such that the difference between a 10% and 30% chance of getting caught would meaningfully change behavior. There are other simple "gut checks"//"sanity checks" like this that call into question some of the modeling assumptions.

    Nonetheless, it's an interesting challenge/tradeoff and the authors deserve credit for attempting to model it quantitatively in such a short timeframe.

Cite this project

@misc{duffy2026maxwell,
  title = {{Maxwell}},
  author = {Patrick Duffy and Emlyn Graham and Josh Tuffy},
  year = {2026},
  month = feb,
  note = {Submitted to The Technical AI Governance Challenge, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/maxwell-xqox}},
  url = {https://apartresearch.com/sprints/projects/maxwell-xqox}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026