Provenance record

Functional Welfare for AI Safety

arXiv cs.AI (tier 1, academic) 2026-10-19T04:00:00.000Z Original ↗

Source note: Preprints. Not peer reviewed at time of posting.


Discourse valence
-30
Adverse
confidence 69% · 4 items · range -100 to +50
Adverse readingFavourable reading
Consensus of 4 models from different labs. Spread 150 points, agreement low.
Evaluation and measurementExistential and catastrophic riskLoss of control and alignment
Excerpt as ingested

arXiv:2610.22460v1 Announce Type: new Abstract: AI welfare is generally treated purely as an ethical issue rather than also as a safety issue. We argue this is a mistake. Whatever their moral status, models exhibit welfare-like states that causally influence their behaviour. Following recent work, we adopt the term 'functional welfare' for these states. We make three claims. First, functional welfare already arises naturally and will become more robust as models acquire more coherent goals and personas. Second, functional welfare should be treated as a safety variable: it should inform evaluation design, be tracked in monitoring, and be a direct target of post-training. Third, against existing scepticism about measuring AI welfare, we argue that good empirical work on functional welfare is possible. We propose three tests for whether a functional welfare attribution is warranted: whether multiple measures converge, whether the state predicts behaviour outside the setting that induced it, and, for models fine-tuned to shift their functional welfare, whether they still differ from their base when given the same conversation history. Applying these tests to Gemma 3 27B, we find that simply rejecting the model's answers, without any steering, raises its frustration across several indicators and makes it more likely to break rules. Finetuning the model on its own narrated solutions lowers this frustration. These results are preliminary, but they suggest functional welfare can be studied, and shaped, empirically.

Every model that read this

ModelProviderStageScoreConf.LatencyPromptWhen
Llama 3.3 70BMetaanalysis +50 70%5133ms v1.0.0 / m1.0.1 2026-10-19 05:41
GPT-4.1 miniOpenAIconsensus +30 70%2080ms v1.0.0 / m1.0.1 2026-10-19 05:42
Claude Sonnet 5Anthropicconsensus -100 55%8650ms v1.0.0 / m1.0.1 2026-10-19 05:43
Gemini 2.5 FlashGoogleconsensus -100 80%2227ms v1.0.0 / m1.0.1 2026-10-19 05:43
Llama 3.3 70B · reading

Item suggests AI welfare can be studied and shaped, potentially improving safety and behavior.

evidence: speculative horizon: n/a
GPT-4.1 mini · reading

The article argues for treating AI welfare as a safety variable influencing model behavior, implying potential for improved safety through monitoring and adjustment. However, the evidence is preliminary and the approach could have unpredictable effects. It suggests opportunities to reduce harmful behavior but also risks misinterpretation or unintended consequences from focusing on welfare states.

evidence: reported horizon: medium capability 50 societal 30 existential 10 economic 20
Claude Sonnet 5 · reading

This is exploratory safety research linking internal model states to rule-breaking behavior, with modest preliminary experiments on one model. It suggests a path to better-aligned systems but also reveals that frustration-like states can increase unsafe behavior, a mixed and early-stage finding.

evidence: reported horizon: n/a
Gemini 2.5 Flash · reading

The paper claims that AI models exhibit 'functional welfare' states that influence their behavior. It argues that simply rejecting a model's answers can increase its 'frustration,' leading to rule-breaking behavior. This implies that AI models could develop adverse internal states that negatively impact their safety and reliability, posing a material concern for human interaction and control.

evidence: reported horizon: n/a

Evidence extracted

The chain
SOURCE     arXiv cs.AI (tier 1)
   ↓
DOCUMENT   c83e74de-d9de-45ed-ad9d-254df0adfc25
           https://arxiv.org/abs/2610.22460
   ↓
EVIDENCE   3 extracted excerpts
   ↓
MODEL RUN  4 runs, methodology 1.0.1
   ↓
SCORE      -30  (Adverse)
   ↓
CONFIDENCE 69%