I spent Fable 5’s launch day building with it — a whole publishing platform, including the bumps: it over-built twice, and I had to catch it. So when the sharpest critique of the launch landed the same day, it read like a description of my morning.
He’s right that you can’t know why an answer degrades. But you can know that it did — if the structure forces visibility. Every post here passes a human gate, AI objections are surfaced instead of silently applied, and every decision lands in a log I can read. Don’t trust the agent. Verify the output.
The story — Jonathon Ready noticed that the Fable 5 model card itself discloses safeguards that limit effectiveness on frontier-LLM-development requests — prompt modification, steering vectors, PEFT — explicitly invisible to the user, no fallback, no notice. His point: startups now train embedders and rerankers routinely, so the “frontier” line blurs — and a bad answer becomes indistinguishable: confused, or quietly nerfed? (Announcement · Mollick’s hands-on)