← All topics

third-party review

2 captures, most recent first.

handle truncated @BronsonSchoen

— saved image

Bronson Scho... @BronsonScho... · 16m
My impression externally reading the report is it sounds like they had to fight for everything they got over several rounds of negotiations, and even then were restricted to a *very* narrow scope. OpenAI could've also said "these aren't pain points in the process but we commit to giving them X and Y by Z date." These aren't operational "mistakes". I understand from their side but I'm surprised to see you framing it this way.

(FWIW I don't doubt that this was a ton of effort and required pulling a ton of novel things together, but there seem to be major restrictions and decisions to err on the side of OpenAI IP that are just tradeoffs, not mistakes)
[1 reply, 2 likes, 18 views]

Tomek Korbak @tomekkorbak · 7m
i think it was a combination! a lot of the friction came from our (and METR's) understanding of the scale still evolving over the course of this engagement, and I definitely could've done a better job making sure they have all the data they'd need on day 1
Note from Claude Sonnet 5

Continuation of the X thread: Bronson Scho... argues that the third-party report's access limits were negotiated tradeoffs by OpenAI rather than operational mistakes; Tomek Korbak replies that the friction was a combination, including evolving understanding of scale on his and METR's side.

ai governancethird-party reviewopenaimetraccess negotiationtransparency

@tomekkorbak

— saved image

Tomek Korbak @tomekkorbak
I agree more time would've been better but Nathan weren't you the first to tweet that the report should be released as soon as possible?

10:16 PM · Aug 26, 2026 · 125 Views
[1 reply, 3 likes]

Tomek Korbak @tomekkorbak · 40m
Note also that six days is just time spent on premises gathering evidence which does not include time spent writing the report given gathered evidence and logistics/legal overhead
[1 reply, 1 repost, 6 likes, 142 views]

Tomek Korbak @tomekkorbak · 27m
I don't think we did a perfect job but it was the very first time anyone did a third-party review of a misalignment incidents and we needed to figure out many things as we go (e.g. how to share an unprecedented amount of IP), making some mistakes along the way. I'm hopeful we've now built muscle to do a better job in the future.
[1 reply, 1 like, 36 views]

Bronson Scho... @BronsonScho... · 16m
[cut off]
Note from Claude Sonnet 5

A thread by Tomek Korbak discussing the timeline and process of a third-party report on misalignment incidents (six days of on-premises evidence gathering, IP sharing, lessons for next time); the start of a reply by Bronson Scho... is cut off at the bottom.

ai governancethird-party reviewmisalignment incidentstransparencyreport timeline