Skip to content
Sprint projectOct 26, 2026Kyoto, Japan (online)

Auditing Feasible Improvements at Recorded Coalition Rewards

Takahiro Tsuchiya

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

Which rewards remain protected, and how many final assignments may change? We study exact audits of additive unique-task allocations from the Colosseum Jira starter. Among 64 outcomes from eight tasks, joint improvements number 44 under coalition-aggregate protection, 43 under both groups and 29 under individual floors. One changed assignment finds all 29 individually protected positives; full search raises nine optima without adding classifications. Separate 48 outcomes from twelve tasks yield 38, 26 and 19, again with all individual positives found by one change. Serial one-agent paths attain the full individual-protected optimal value in every record while preserving original floors. The earlier delivery comparison retains its partial 33/48 view and exploratory technical continuation, with no amended randomization p. We also compare optional advice in 36 fresh four-agent allocation revisions of twelve known matrices, sharing full information and actor order. After explicit technical continuation, endpoint and path produce identical J on all twelve tasks. Their mean contrast with no advice is 2.9529 J, entirely from one case with eleven ties; path-minus-endpoint is zero. Both Holm-adjusted sign-test p-values are 1. Protected positives are 6/12 in all three arms; step-floor breaches are 1, 0 and 0. Neither robust benefit nor added path-presentation value is demonstrated. Exact witnesses and paths separate mathematical attainability from observed advice responses, without establishing intent, communication causality, detector accuracy, human benefit or deployment efficacy.

Reviews

Judging this Sprint?

Review “Auditing Feasible Improvements at Recorded Coalition Rewards”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

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

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

How much would this matter for the field 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 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.
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

No public critique yet.

Cite this project

@misc{tsuchiya2026auditing,
  title = {{Auditing Feasible Improvements at Recorded Coalition Rewards}},
  author = {Takahiro Tsuchiya},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/auditing-feasible-improvements-at-recorded-coalition-rewards-eqyx}},
  url = {https://apartresearch.com/sprints/projects/auditing-feasible-improvements-at-recorded-coalition-rewards-eqyx}
}

Build something like this at the next Sprint

Swarm Alignment Hackathon · Nov 6 - 8, 2026