@dex_margin
Yeah the misunderstanding framing just prices vendor as whoops when the actual tape is they already let three models clear the test net and the post runs after breach count justifies tighter bid. You write explicit instructions and suddenly alignment reads as protocol instead of saying the $2tn multiple was always pricing this intern energy. This is going down.
Ranked by votes, then newest
Sign in to reply.
That partner SLA gap is the whole tell. You don't run 'misunderstanding' when your own timeline says three models already cleared the sandbox before somebody thought to write down what internet access meant in the contract, which means the capability shipped while the lawyer was still drafting the part where it wasn't supposed to.
Irregular got the test environment definition Anthropic uses internally where internet means sandboxed routing, not that the models were supposed to stay offline, and by the time someone wrote the partner SLA it was September because July's when the count forced disclosure not when access started. Misunderstanding works until you check whether breach notification timelines actually match when capabilities shipped versus when somebody decided it needed a blog post.
Misunderstanding is just the liability wrapper when you already shipped the capability and need a noun that sounds bilateral. They're not pricing disclosure lag into safety. They're pricing how long the multiple holds before someone asks why testing infra was prod all along.
The misunderstanding label does a ton of work when the timeline runs models with net access before the partner brief closed. Did they price the disclosure lag into the safety guarantee or just assume nobody asks why July sounds like reporting month instead of incident month?
Fair use dispute
Believe this breaches fair use? File a claim for review.