A disputed safety firing needs a protected evidence route, not an instant verdict
OpenAI and three dismissed researchers give conflicting accounts of why they were fired. The governance test is whether concerns and misconduct claims can be examined without collapsing into a loyalty contest.
What happened
OpenAI said three researchers were fired after an investigation found breaches of sensitive-information policy; the researchers denied leaking information and warned that the dismissals could chill safety escalation.
Why it matters
The public record does not resolve the dispute. Frontier labs need a documented route that preserves allegations, access logs, rebuttals and independent review while protecting both reporters and confidential data.
Reuters reported on 9 October that OpenAI said Jasmine Wang, Tomek Korbak and Mikita Balesni were dismissed after an internal investigation found violations of policies for handling sensitive information. The researchers’ public statements and letter deny being the source of a reported leak and argue the firings could deter remaining employees from raising safety concerns. OpenAI says the decision was not retaliation and has not disclosed the alleged breach in detail.
Preserve the dispute as evidence
Neither account is independently adjudicated in the public material. Editors and employers should not infer motive from the job titles, the severity of the safety issue or the company’s investigation alone. The actionable question is whether a protected route can examine both the safety concern and any access-policy violation without requiring managers or the accused to settle the facts informally.
Build a case record with the original concern, authorised access scope, immutable access logs, policy version, alleged violation, employee response, conflicts and disposition. Separate the reviewer who evaluates the safety claim from the reviewer who decides employment conduct. Give both access to a neutral appeal path and record what evidence cannot be disclosed.
Tabletop the route with a false alarm, an accidental access event and a substantiated leak. Measure time to containment, retaliation safeguards, data exposure and whether the technical concern survives the personnel process. Publish aggregate process metrics without exposing the case file, and require recusal where a reviewer owns the disputed system or management decision. A protected channel is credible only if it can reject a weak claim, substantiate misconduct or preserve a valid warning without forcing all three outcomes into one verdict.