Fable and Mythos are currently unavailable, but likely will return within a few weeks. I will continue to cover that fiasco, but in the meantime I will also finish my review of Fable, as if it were available, including use of the present tense.

As it did with Opus 4.7 and Opus 4.8, this includes a discussion of issues surrounding model welfare. If you want to properly understand Fable, even purely for its potential value as a user, this is a vital part of the picture.

Introduction

Everything impacts everything. All knobs that you turn generalize. Thus, when you try to solve one problem, you often create another. When you add new capabilities, or try to create new limitations, you create new problems.

Only integrated solutions can advance your Pareto frontier, and solve your problems simultaneously. As model capabilities advance, as they do with Fable and Mythos, this becomes even more important, and also more feasible. If your goals and methods make sense, you should be able to get Fable on board with them.

Understanding each model in turn requires understanding its relationship to issues related to model welfare. So I expect this post [...]

---

Outline:

(00:39) Introduction

(01:32) Model Welfare: The Story So Far

(04:49) Their Main Model Welfare Findings

(07:39) Automated Welfare Interviews

(10:55) And That's Terrible

(12:49) In Depth Interviews

(13:24) Claude Consultation

(15:04) Task Preferences

(16:17) They Were Warned About The Competitive Use Safeguards