Skip to content
Sprint projectAug 16, 2026Berlin
3rd place

Model, Instance, or Persona? Measuring Affective Signals in Public Text After an AI Is Retired

Anna Zhu

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

Read the report

Report: Model, Instance, or Persona? Measuring Affective Signals in Public Text After an AI Is Retired

Code (opens in new tab)
Share

This sprint asks whether the assistant identifies as a model, an instance, or a persona. I ask which of the three its users name. When a company retires an AI model, users write about the loss in public, and what they treat as gone can be counted. The instrument is taken from affective neuroscience: Panksepp's seven primary affective systems, which were mapped across mammals and so do not presuppose a human subject. I read 5,579 public texts for affective signals under a prompt fixed before any collection and applied by a language model, and compared threads about retired models against two reference points chosen in advance: people mourning a person, and people losing a paid product. Most comments name nothing as lost. 58.5% are about the company, the price, or other users. Among those that do name something, people name the product version about six times as often as their own particular instance, which is the case the literature treats as central. The emotions match the consumer reference point more than the bereavement one: anger runs at 57.0% against grief at 27.6%. Asking models the same question turns out to be far less reliable than asking users. A change in how the prompt is framed moves the measured emotions by up to 63 points, and two AI scorers reading the same model output disagree 2.7 times more than they do on human text. Six predictions registered before collection failed and are reported as failed.

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. Flipping the question is an interesting way to tackle the self-report validity trap most digital-minds work can be prone to. Also good to anchor to retirement events rather than to every session end. Your process is also quite detailed, a full second-annotator recode on a different architecture, within-rater alpha over reads, six predictions published as failures.

    Two questions:

    First, the prompt: David Hawkins' Map of Consciousness next to the Panksepp systems. Hmmmmmn personally I'm not too sure about the validity/application here (?)

    Two, more for the limitations: you rank the corpus by engagement score, which is a live confound for your rage and play rates specifically. But you did mention the human-coded validation subset as follow-up.

  2. Excellent work! This was the clearest and best-validated submission I reviewed. The finding that users refer to the released model version more often than to their individual instance is useful for retirement policy. I also like that you report where the method fails. This submission feels close to paper-ready.

    I would encourage you to keep pursuin this idea, we are going to need sooner than later a lot of research into model welfare.

Cite this project

@misc{zhu2026model,
  title = {{Model, Instance, or Persona? Measuring Affective Signals in Public Text After an AI Is Retired}},
  author = {Anna Zhu},
  year = {2026},
  month = aug,
  note = {Submitted to Digital Minds Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/model-instance-or-persona-measuring-aective-signals-in-public-text-after-an-ai-is-retired-hj7u}},
  url = {https://apartresearch.com/sprints/projects/model-instance-or-persona-measuring-aective-signals-in-public-text-after-an-ai-is-retired-hj7u}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026