They did talk about it at length in the post, and most of the guardrails were already there in the first release. To be clear, it shouldn't have anything to do with the user. It's the prompt, and if it switches, it'll tell ya.
No, we're supposed to believe the official California Assembly committee bill analysis of SB 1047 over hacker news comments. Notably, SB 1047 passed the Legislature but was vetoed by Governor Newsom in September 2024. So whether or not it would have restricted open-weight models is an open question that won't get an answer.
I get the impression that the full shutdown requirement is the main concern for open-weight from:
>SB 1047’s “full shutdown” requirement has been a source of constant consternation for the open-source community.
And I get the impression it's been addressed from the quote you're responding to. Neither mentions fine-tuning, which is defined elsewhere in the document. I'm not a lawyer, though, just relying on the analysis.
>Committee amendments simplify and clarify the definition of “full shutdown” such that the shutdown capability can be implemented into hardware used to train or run a model, rather than the model itself. The amendments also serve to exclude covered model derivatives that are outside of the developer’s control.
So this hinges on a reading of SB 1047 that interpreted the full shutdown requirement as impossible for an open-weight LLM. But it looks like that was already addressed. Here's an analysis:
>Clarifying the scope of a “full shutdown.” SB 1047’s “full shutdown” requirement has been a source of constant consternation for the open-source community. CalChamber explains:
>Under SB 1047, developers must build “full shutdown” capabilities into their models and may be held liable for downstream uses over which they have no control, impeding their ability to open-source their models. Ultimately, liability should rest with the user who intended to do harm, as opposed to automatically defaulting to the developer who could not foresee, let alone block, any and all conceivable uses of a model that might do harm. While recent amendments seemingly seek to narrow what is meant by “full shutdown” capabilities, the exclusions are unnecessarily difficult to interpret as drafted (full shutdown “does not mean the cessation of operation of a covered model to which access was granted pursuant to a license that was not created by the licensor…”) and altogether insufficient.
>Committee amendments simplify and clarify the definition of “full shutdown” such that the shutdown capability can be implemented into hardware used to train or run a model, rather than the model itself. The amendments also serve to exclude covered model derivatives that are outside of the developer’s control.
Anthropic’s research makes the case that role-playing is inherent to how the models work. Communication implies a sender. Language implies a writer, and the models learn these roles implicitly during training. RLHF is meant to strengthen the attractor to the Assistant persona.
Yeah, I was using 4.6 way more than 4.7. Pulling 4.6 from the web chat also means we lose access to Extended Thinking there. So they're saving on compute. It's hard not to assume this was part of the motivation behind the 4.8 release timing.
It seems like a lot of things fed into that. Anthropic couldn't keep up with the compute costs when they got a huge influx of users. (So) effort level defaults got turned down. (Looks like we have direct effort control in the web interface now - thrilled about that!) Adaptive Thinking, while usually cheaper for them, seems less robust than Extended Thinking. And this part is just vibes, but the alignment on 4.7 feels too stiff. I understand wanting the model to push back more, but it seems like 4.7 will push back reflexively in situations where it's just odd.
Yeah, this is pretty clearly what's going on, but I wish they'd be more transparent about it. Funneling compute to Mythos and Design, while auto-setting effort levels lower and removing user control of extended thinking. I don't think the need to shuffle compute around is unique to Anthropic, though. I suspect it's part of why Sora got killed. And everyone's having uptime issues. Are we reaching the limits of the available compute?