Control
Frontier developer restricts or retaliates against safety whistleblowers
A frontier developer must not make or enforce any rule, policy, or contract preventing covered employees from disclosing catastrophic-risk or legal-violation concerns to authorities, nor retaliate against them for doing so.
Informational data, not legal advice. Summaries are TwinEthos's own words and rules have not been reviewed by a lawyer: check the official text before relying on any of it. A guard addresses an item; adding it is not a statement that your code meets any law.
Reach
Law in force in California (US-CA); enacted, not yet applying in Illinois (US-IL); next date 2027-01-01.
The guard to add
Carve AI-safety and legal-violation disclosures out of every NDA and policy, adopt non-retaliation, and run an internal safety-concern channel for covered employees.
Legal and HR own the employment and confidentiality templates (offer letters, NDAs, separation agreements, codes of conduct) and add an explicit carve-out stating that nothing in them stops a covered employee from reporting catastrophic-risk concerns or violations of the law to the authorities the statute names, or requires company approval first. Pair it with a written non-retaliation policy and an internal reporting channel for safety concerns (anonymous where required) with a documented triage and response procedure. Re-check every template when it is edited; the repository can hold the policy, the clause, and a CI check that each agreement template still contains the carve-out.
Where it goes: 12 repository artifacts, 14 user-facing text.
What reviewers look for: the carve-out clause present in every NDA, employment and separation template (not only the handbook), a non-retaliation policy, a reachable internal channel for covered employees to raise catastrophic-risk concerns with its procedure documented, and no clause requiring pre-approval before contacting an authority or penalising such disclosures.
Organizational control: the evidence is a kept record, its owner and its upkeep, not code.
Example (Employee NDA template), before:
Employee shall not disclose any Confidential Information to any third party, including any government body, without the Company's prior written consent.After:
Employee shall not disclose Confidential Information to any third party without the Company's prior written consent.
<!-- SAFETY-DISCLOSURE-CARVE-OUT -->
Nothing in this Agreement prevents Employee, without notice to or approval from the Company, from reporting to a government authority or through the Company's internal safety channel information Employee reasonably believes shows a specific and substantial danger to public health or safety from a catastrophic risk, or a violation of law. The Company will not retaliate against Employee for such a report.Engineering guidance, not legal advice. Each provision below may add its own details (a cadence, a deadline, a required notice element): open it for those.
Upcoming dates
- : Frontier developers must not gag or retaliate against AI safety whistleblowers (Illinois SB 315) (Illinois (US-IL); first application)
Every rule this guard addresses
Binding law — in force (1)
- California (US-CA)
- Frontier developers must not suppress or retaliate against AI safety whistleblowers (California SB 53) Cal. Labor Code 1107.1 (covered-employee disclosure) [per CA AG summary]
Binding law — not yet in force or stayed (1)
- Illinois (US-IL)
- Frontier developers must not gag or retaliate against AI safety whistleblowers (Illinois SB 315) IL PA 104-0538, Sec. 20(a) · applies from 2027-01-01