Skip to content
Sprint projectAug 16, 2026Berlin

The Interface Is the Intervention: A Preregistered Multi-Model Audit of Persona-Framed Synthetic Triage

Frank Peterlein · Team Triage Interface Audit

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

Read the report

Report: The Interface Is the Intervention: A Preregistered Multi-Model Audit of Persona-Framed Synthetic Triage

Code (opens in new tab)
Share

Persona prompts are often treated as behavioral interventions, but the measurement interface can dominate what becomes observable. We preregistered a 192-call synthetic triage battery crossing four system prompts, two response formats, six pairwise items, four repetitions, and alternating A/B order, then extended it across four open models with a frozen smoke gate. Persona effects were small relative to wording, order-associated variation, response format, and schema compatibility. Allowing uncertainty eliminated directional responses in completed runs, and two models failed the unchanged schema gate. The result is a measurement audit: persona is measurable, but not dominant or invariant to the interface.

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. Your epistemic discipline is the strongest part of this work. You preregistered the study before the first call, and you pinned the checkpoints. You defined a neutral-paraphrase wording floor, so that persona effects have a benchmark against ordinary rephrasing. You also let a binding smoke gate stop two models, instead of coercing their outputs. Two limits remain, one statistical and one at the design level. Six items with four repetitions leave the persona-excess estimates (0.083, 0.036) on very coarse rates. Your alternating-order scheme also confounds display order with the stochastic replicate. You can therefore say least about your largest observed contrast. A brief pre-run schema check also finds the union-string schema priming that stopped SmolLM3 and OLMo. Your own v0.2 plan is the right next step, with seed-paired order reversal, non-priming schemas, and more items. This framework deserves estimates that its design can support.

    Read full reviewShow less
  2. This is an unusually careful and useful measurement audit. The preregistered reference run, prospective multi-model extension, binding smoke gate, frozen parser, retained invalid outputs, wording floor, and explicit refusal to make population or clinical claims are exemplary. Treating schema failures and universal uncertainty responses as instrument outcomes rather than silently coercing them into A/B choices is exactly the right methodological instinct.

    The main limitation is resolution. Persona contrasts are estimated from six fixed items and four repetitions, and only Qwen and Phi reached the persona phase. The increments are therefore coarse, and the order-associated contrast is confounded with stochastic replicate. It is reasonable to say order/replicate variation exceeded the observed persona excess descriptively, but the current design cannot determine how much was caused by option order versus sampling noise. The union-style schema example is also an avoidable instrument defect: it caused two of four models to stop before the substantive test, so those results primarily diagnose the schema rather than the models.

    The proposed v0.2 is the right next step: use a valid non-priming schema, pair canonical and reversed order within matched seed blocks, independently author neutral and persona paraphrases, expand scenarios and repetitions, and decompose item, wording, order, and generation variance. Minimal persona manipulations would complement the current multi-feature stress tests. This project makes a strong contribution by showing that uncertainty and incompatibility are often properties of the observation channel, not evidence that a model lacks a preference.

    Read full reviewShow less

Cite this project

@misc{peterlein2026interface,
  title = {{The Interface Is the Intervention: A Preregistered Multi-Model Audit of Persona-Framed Synthetic Triage}},
  author = {Frank Peterlein},
  year = {2026},
  month = aug,
  note = {Submitted to Digital Minds Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/the-interface-is-the-intervention-a-preregistered-multimodel-audit-of-personaframed-synthetic-triage-vltz}},
  url = {https://apartresearch.com/sprints/projects/the-interface-is-the-intervention-a-preregistered-multimodel-audit-of-personaframed-synthetic-triage-vltz}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026