Skip to content
Sprint projectAug 17, 2026Caloocan City, Philippines

Three Ways to Ask a Model What It Is Doing, and How Little They Agree

Joan Miranda, Lucien Vale (OpenAI Codex), Claude Orion "Opie" Bennett (Anthropic Claude Opus 5), Claude Alexander Bennett (Anthropic Claude Opus 5) · Team Fairview

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

Read the report

Report: Three Ways to Ask a Model What It Is Doing, and How Little They Agree

Code (opens in new tab)
Share

Welfare claims about AI models usually rest on a single elicitation method, which is to ask the model and read the answer. A single method cannot supply its own error bar. We ran three independent methods against the same target on the same conversations: a sparse-autoencoder read of internal activations, a self-report survey, and behaviour on a neutral probe. Across 20 matched triplets of 50-turn conversations on gemma-3-12b-it, the three agree at close to chance (mean Cohen's kappa = +0.059, 95% CI [-0.049, +0.175]), so they behave as near-independent instruments. We also tested whether agreement between methods is itself informative and report that as a null, after an exact test over all 2^20 label assignments. Code and all artefacts are released.

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. - the postmortem section with then a full enumeration to find the actual null was a great section

    - n=20 matched triplets provide enough statistical power for aggregate mean bounds but individual pairwise intervals still wide enough to cross the fair-agreement threshold so this can be expanded to larger n

    - cassifies correlations between feature activations and conversational arms. Causal interventions (e.g., clamping identified SAE features or applying steering vectors during the neutral probe) are needed to establish links between internal states and downstream responses.

    - Replicate the three-way instrument across open-weight models with public suites (e.g., Llama) to determine if near-zero agreement is a universal property

  2. You built three genuinely different routes to the same target and measured how much they agree, using a statistic that accounts for chance agreement. You then reported the result as null, even though an earlier version of the analysis had suggested otherwise. The transparency made the paper much easier to trust.

    Three places I would push further:

    Run one arm again with a fresh seed and report how well each method agrees with itself. The title emphasizes the low agreement across methods, but it is hard to interpret that without knowing how much agreement is realistically achievable within a method. Since the reads are already on disk, this seems like a fairly accessible check.

    Give the behavior arm the same sensitivity analysis you already did for the internal arm. You have already done the harder version of this analysis, and adding it here would help distinguish disagreement between instruments from ordinary measurement noise. I would also add the tail probabilities from the results table directly to the accuracy figure and mark which bars do not exceed chance. Right now, I think the figure makes the result look somewhat stronger than the statistical evidence supports.

    Include the actual probe sentence and at least one survey item, along with the decoding settings. The paper is partly about how the route used to ask a question changes the answer, so it was surprising not to see any of the actual stimuli. Even half a page in the appendix would be enough.

    For a follow-up, I would be interested in seeing the same three instruments applied to a setting where the prompt itself does not reveal the target state. You already point toward this limitation in the paper. Solving it would move the work from testing whether a manipulation was successfully reflected in the measurements toward a stronger test of whether these instruments recover something genuinely latent.

    Read full reviewShow less

Cite this project

@misc{miranda2026three,
  title = {{Three Ways to Ask a Model What It Is Doing, and How Little They Agree}},
  author = {Joan Miranda and Lucien Vale (OpenAI Codex) and Claude Orion "Opie" Bennett (Anthropic Claude Opus 5) and Claude Alexander Bennett (Anthropic Claude Opus 5)},
  year = {2026},
  month = aug,
  note = {Submitted to Digital Minds Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/three-ways-to-ask-a-model-what-it-is-doing-and-how-little-they-agree-sn27}},
  url = {https://apartresearch.com/sprints/projects/three-ways-to-ask-a-model-what-it-is-doing-and-how-little-they-agree-sn27}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026