Skip to content
Sprint projectAug 16, 2026Krakow

Who Leads the Clap? How Hierarchical Agent Personas Shape Collaboration

Dmitry Boykiy

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

Read the report

Report: Who Leads the Clap? How Hierarchical Agent Personas Shape Collaboration

Code (opens in new tab)
Share

Can a simple persona change help AI agents coordinate? Across 60 runs and four frontier models, Coordinator-Member teams succeeded 20/20, versus 16/20 anonymous and 13/20 named peers, while often using fewer tokens. Hierarchy acted as a focal point, reducing protocol ambiguity rather than improving raw intelligence.

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 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.

  1. This is a fun investigation of a toy coordination problem. The visuals are nice, but the report omits crucial methodological details.

  2. This is more of a poster, not a paper. The visual format works for the medium, but the evidence cannot carry the claims as written. Need more information to meaningfully review, sorry.

    What I think works:

    - The coordination task is clean and unambiguous. Exact timestamp matching leaves no room for evaluator discretion.

    - 20/20 success in the coordinator condition is a nice initial finding, even at small N.

    - Token efficiency data is practical and often overlooked in multi-agent work, so props for that.

    - The failure taxonomy (protocol mismatch, conflicting commitments, late agreement) is useful for follow-up.

    Core limitations:

    - N=5 per cell. This is descriptive only. No confidence intervals, no statistical tests.

    - One task type. Exact synchronization may uniquely favor hierarchy. Nothing generalizes from this alone.

    - Model constraints uncontrolled. Grok on low reasoning, others not? This confounds persona effects with model differences.

    - No mechanism test. "Focal authority" is a plausible story, but there is no evidence it is what caused the effect.

    - Failures excluded from token means. This inflates efficiency claims for conditions with higher failure rates.

    Suggestions:

    - This deserves a broader study. Multiple tasks, larger N, preregistered analysis.

    - Consider collaboration with multi-agent systems researchers. The coordination primitive claim could land well there.

    - Add ablation studies. What specific coordinator behaviors drive the effect? Proposals? Deference? Both?

    Bottom line:

    As a sprint poster, this communicates clearly and shows something worth following up. As a paper, the evidence is too thin. The 20/20 result is interesting enough to warrant a proper study. Do not overclaim from N=5.

    Read full reviewShow less
  3. The headline was close to guaranteed by design: a pure common-interest game with no private information and zero cost to deference is exactly where focal points and leader election are the textbook fix (Schelling; Raft). Second, the stats support a weaker claim than "never failed." Coordinator vs anonymous is 20/20 vs 16/20, one-sided Fisher p = .053; the only solid pairwise contrast is coordinator vs named peers (one-sided p ≈ .004); Opus sits at ceiling in every condition, so all reliability signal comes from three models at n = 5 per cell. Token means are computed over successful runs only, which builds in survivorship bias, and the expiring timestamp makes slowness itself a failure, so part of the coordinator edge may be latency.

    Your most interesting data goes undiscussed: named peers trail anonymous (symmetric social identity may add negotiation overhead), and Opus needs no hierarchy at all, hinting that hierarchy's reliability dividend shrinks with capability.

    You've built the scarce thing, a working multi-model harness with documented failure modes. Now aim it at an open question: give the coordinator a detectably wrong proposal and measure override rates, or split constraints so the member holds decision-relevant private information. Deference propagating error is where this matters for agent systems, and your harness is one manipulation away.

    Read full reviewShow less

Cite this project

@misc{boykiy2026who,
  title = {{Who Leads the Clap? How Hierarchical Agent Personas Shape Collaboration}},
  author = {Dmitry Boykiy},
  year = {2026},
  month = aug,
  note = {Submitted to Digital Minds Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/who-leads-the-clap-how-hierarchical-agent-personas-shape-collaboration-2dcu}},
  url = {https://apartresearch.com/sprints/projects/who-leads-the-clap-how-hierarchical-agent-personas-shape-collaboration-2dcu}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026