Skip to content
Sprint projectJun 21, 2026Chennai

FlukeBench

Shalini Arthirajan

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

FlukeBench, a research tool for measuring the consistency among responses across iterative generations and capturing abnormal outputs using the analysis of their semantic similarities.

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. Good job! I see you test Qwen2.5-1.5B at temp 1.0, 100 max tokens, n=10. You should increase n and max tokens to have statistically significant results!

  2. air point: one answer isn't enough to judge a model, so measuring how much answers vary is useful, and the tool works. But the test is tiny — one small model, one question, three personas, ten answers each. Comparing answers by meaning alone also can't tell a real change (yes vs. no) from just different wording. Next: measure a safety action like refusing, use more questions, and drop real public figures as personas.

  3. Innovation and Impact for AI Safety: 2/5

    The instinct here is genuinely good, and noticing that single-sample evaluations can be misleading is exactly the kind of critical thinking AI safety needs more of. The reason this scores lower on innovation is that the field has already developed this concern into a body of work worth reading into: self-consistency methods, variance-aware benchmarking, and tools like EvalPlus and BenchAgent all grapple with the same problem from different angles. That context is not a reason to abandon this direction at all, it is actually an invitation to go deeper. If the author looked at how existing eval frameworks handle sampling variance and then asked what they get wrong or miss, FlukeBench could become a meaningful contribution rather than a parallel rediscovery.

    Methodology and Execution Quality: 2/5

    The implementation is clean and the logic is sound for a first version. The main limitation to understand here, not as a criticism but as a learning opportunity, is that 10 samples per condition is not enough to distinguish a real pattern from random noise in a probabilistic system. If you reran this experiment tomorrow, the similarity scores might shift noticeably. The other thing worth knowing is that cosine similarity on sentence embeddings measures whether two texts talk about the same topic, not whether they take the same stance or reach the same conclusion, so two responses that disagree completely about AI regulation could still score very similar if they use the same vocabulary. Presentation and Clarity: 3/5

    The writing is clear and honest, the motivation is well stated, and the limitations section shows real intellectual integrity. The section numbering jumps from 3 to 4.1 without a 4.0, and the connection between the tool's promise for alignment-faking or scheming evaluations and the actual persona experiment is never made explicit, but for a hackathon project this is a genuinely solid foundation to build on.

    Read full reviewShow less

Cite this project

@misc{arthirajan2026flukebench,
  title = {{FlukeBench}},
  author = {Shalini Arthirajan},
  year = {2026},
  month = jun,
  note = {Submitted to Global South AI Safety Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/flukebench-ozlv}},
  url = {https://apartresearch.com/sprints/projects/flukebench-ozlv}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026