When the Evaluator Becomes the Evaluated: A Critical Analysis of the Claude Opus 4.6 System Card | by Yaniv Golan | Medium

Claude Opus 4.6 was released four days ago. I’ve been using it heavily — it’s a genuinely impressive model. Using it feels like working with a helpful and very competent partner more than ever. Out of curiosity, I sat down and read the full system card, the way I’d read any due diligence document: looking for the gap between what the narrative claims and what the evidence actually supports. What I found isn’t a story about a bad model or a reckless company. Anthropic is more transparent than any other frontier lab, and that transparency is what made this analysis possible. But the system card is candid enough to reveal the fault lines in its own safety framework — fault lines that, taken together, point to a structural problem the authors acknowledge in pieces but never confront as a whole. Structural and Methodological Gaps 1. Self-Evaluation Circularity Is Acknowledged but Not Resolved Section 1.2.4.4 makes a remarkable admission: Opus 4.6 was used via Claude Code to debug its own ev

Claude Opus 4.6 was released four days ago. I’ve been using it heavily — it’s a genuinely impressive model. Using it feels like working with a helpful and very competent partner more than ever. Out of curiosity, I sat down and read the full system card, the way I’d read any due diligence document: looking for the gap between what the narrative claims and what the evidence actually supports. What I found isn’t a story about a bad model or a reckless company. Anthropic is more transparent than any other frontier lab, and that transparency is what made this analysis possible. But the system card