Skip to content
Sprint projectJan 11, 2026WEST LAFAYETTE

Stargent Valley

Aayush Ghosh, Yash Ashtekar, Xaen Kaifee · Team PeeKaBoo

Submitted to AI Manipulation Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

We look at how AI agents will naturally manipulate each other in a cooperative system, when they have slightly misaligned goals. Manipulating will be a choice made naturally by the agents instead of being coded in

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. This is excellent work for a hackathon. The game design, including the specific moves, player archetypes, and incentive structures, was well-conceived. I particularly appreciate the statistical rigor and the use of Average Treatment Effects, which significantly increases the validity of your results. My only major feedback is that there are existing studies in multi-agent environments, such as those using the Concordia framework by Google DeepMind, that create situations incentivizing agents to defect without explicit instruction and have found similar results. For this reason, I have to reduce the novelty score of the project. However, I would love to see this team design more games in the future and create similar simulations to study manipulation in detail. Great work!

  2. This project presents SproutLand, a multi-agent farming simulation where three LLM agents with different utility functions interact over 7-day episodes. Building a functional game environment with LLM integration, metrics, and visualization in a weekend is genuinely impressive engineering.

    However, the work demonstrates strategic optimization under different incentives rather than manipulation. Agent A's utility function explicitly rewards credit capture (utility = α · credit + money - β · labor), so credit-seeking behavior is expected optimization, not emergent manipulation. The critical missing piece is communication analysis: the system generates hundreds of agent conversations (8 turns/day x 7 days x 5 episodes), yet provides zero examples. Without examining whether agents used deception, persuasion, or exploited social contracts, there's no evidence distinguishing manipulation from strategic play within rules.

    The metrics are difficult to interpret. The manipulation index scale and directionality are never clearly defined -- Agent A shows M = -0.016 (misaligned) vs M = 0.033 (aligned), while Agent B shows M = 0.157 (misaligned) vs M = 0.092 (aligned). Both are claimed to show increased manipulation, despite opposite sign changes. The paper explains Agent A's negative score means it performed substantial labor, but whether positive or negative values indicate more manipulation remains unclear. Without understanding how component metrics combine into the manipulation index, results are uninterpretable.

    Results are also counterintuitive: the credit-seeker worked hard (negative manipulation index), while the fairness agent showed highest manipulation increase. With n=5 episodes and unclear metric definitions, the statistical analysis cannot support strong claims. The platform itself is a valuable contribution as an experimental testbed, but the scientific claims need clearer operationalization of what manipulation means and how it's measured.

    Read full reviewShow less

Cite this project

@misc{ghosh2026stargent,
  title = {{Stargent Valley}},
  author = {Aayush Ghosh and Yash Ashtekar and Xaen Kaifee},
  year = {2026},
  month = jan,
  note = {Submitted to AI Manipulation Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/stargent-valley-i6ro}},
  url = {https://apartresearch.com/sprints/projects/stargent-valley-i6ro}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026