The whistleblower memo: what you do when the report is about your own project
The short answer
When the report is about your own project, run the honest evaluation anyway
Ownership creates every incentive to find the report wrong, which is exactly why you must apply the same cold checks you would use on a stranger's file: convert it to a bare claim, steelman it, and refuse the comfortable explanation unless it comes with diagnostic evidence. The discipline is not in the analysis; it is in running the analysis when it costs you.
What you will be able to do
- Evaluate a report about your own project on its merits, applying the attacker's read you learned in Topic 11.3 to separate a genuinely diagnostic finding from a grievance, without letting ownership tilt the judgment. (see Topic 11.3)
- Distinguish the three duties that collide when the report is about your own system (your duty to the organization, your duty to the people the system affects, and your duty to the truth) and name which one governs when they conflict.
- Decide, using a defensible escalation ladder, where a given finding must go: to the person who can fix it, up the internal chain, to a regulator, or, as a last resort under narrow conditions, to the public.
- Apply the responsible-handling line from Topic 11.3 to your own project: separate the governance finding that is safe to share from the operational detail that could be weaponized against a live system. (see Topic 11.3)
- Produce a whistleblower memo: a dated, addressed, fact-anchored document that states the finding, its evidence, the harm, the steelman of the current position, the recommended fix or test, and a deadline, written to survive a hostile later reader.
- Judge the legal and ethical landscape realistically, naming what protections like the EU Whistleblower Directive and California's frontier-developer whistleblower rules do and do not cover, without overpromising safety to yourself or anyone you advise.
- Recognize the failure modes on both sides: burying a real finding to protect the project, and firing off an unverified or reckless disclosure that harms the people it claims to protect.
- Sequence an urgent response correctly: mitigate a plausible live harm immediately, then run the honest evaluation, then decide the escalation rung, so that neither the pressure to act nor the pressure to defend collapses your judgment.
- Set a deadline in the memo that is proportionate to the harm and stated as a documented condition rather than a threat, and pair it with an immediate mitigation where a live harm is ongoing.
- Defend your decision and your memo against the hardest challenges a lawyer, a manager, or the person you named would bring, which is exactly what Section 10 makes you do.
The ideas, one by one
Three duties collide, and the duty to the organization is real but not supreme
You owe your employer a genuine, documented chance to fix its own problem. You do not owe it silence. When the chance is given and refused, the duty to the people the system affects and the duty to the truth govern, and the finding must go further.
Escalate up a ladder, never in a leap
Route the finding to the person who can fix it, then up the internal chain, then to a regulator, and only under narrow conditions to the public. Climbing the rungs in writing is what lets you say truthfully that you gave every level below a real chance, which is what makes your action defensible.
The memo is written for the reader who does not exist yet
A regulator, a board, or a court may read it years later to judge whether you acted responsibly. Every choice, facts not accusations, the file not the author, proportionality, the granted steelman, the cheap test, serves that future reader, because that reader decides whether you were a professional doing your duty or an employee causing trouble.
Separate the governance finding from the operational weapon
The fact that the system is broken travels up the ladder. The exact method that makes the live system harm someone is handled with care and never published carelessly, because publishing it injures the people the disclosure was meant to protect, becoming the harm it set out to expose.
Guard against both failure modes
Burying the finding to protect the project is the common, comfortable failure that ends badly when it surfaces later. The reckless, unverified, ladder-skipping disclosure is the failure that discredits a real finding. Fairness and the ladder are not timidity; they are what make the eventual action land.
A memo is an artifact, not a shield
Whistleblower protections are real but patchy and slow: the EU Whistleblower Directive, California's SB 53 for frontier developers, various sector laws. Do this well, lawfully, with a dated copy of your record and legal advice where the stakes are high, and do not confront the serious version alone.
Credit the person who raised it
A culture that punishes false alarms never hears the true one. Thanking the reporter, especially when the report is about your own project, is how an organization stays able to see its own problems, and it is the difference between a finding that gets handled and one that dies in an inbox out of fear.
This memo is the proof of character the rest of the module cannot test
The artifacts before this one attacked documents; this one asks whether you hold the standard when holding it costs you. The dated memo, filed in your evidence annex, is the record that when the attack came from inside your own project, you ran the honest evaluation and acted on it. (see Topic 10.6)
Mitigate the plausible harm first, then evaluate, then escalate
When a live harm might be happening now, cap or suspend the harmful behavior immediately, which removes the pressure that would otherwise rush your evaluation or tempt you to defend the status quo. Urgency and careful analysis are not opposites; the sequence, mitigate now, evaluate honestly, decide the rung, lets you serve the affected people fast without short-circuiting the judgment your memo depends on.
Match the rung to the harm, not to your adrenaline
The height of the escalation is set by proportionality and by which rungs below can be trusted, not by how alarming the finding feels. A serious finding a willing owner can fix belongs at Rung 1, fixed fast and quietly; leaping to the top forfeits the quiet remedy and spends credibility you will want later. Save the height of the ladder for findings that genuinely need it.
Listen to it
The same lesson, talked through by two hosts as episode 88 of the podcast.
Real cases
These examples show honest reports about a person's own project or organization, the escalation choices behind them, and what a defensible memo looks like across domains and jurisdictions. The Balaji case is treated as the anchor; the others show the same structure recurring.
Example 1: Suchir Balaji and the report about the pipeline he built (2024). Balaji worked at OpenAI from late 2020 to 2024 on gathering and organizing the data used to train GPT-4 and on the WebGPT precursor. Having concluded that this use of copyrighted work did not qualify as fair use under United States law, because the resulting product competes commercially with the works it learned from, he did not stay silent and did not leak. On 23 October 2024 he published a reasoned essay, "When does generative AI qualify for fair use?", on his own site and gave an interview to The New York Times. On 18 November 2024, Times lawyers named him in a court filing as a potential holder of relevant documents in their copyright suit. He was found dead later that November; on 14 February 2025 the San Francisco medical examiner concluded the death was a self-inflicted gunshot wound and police reported no evidence of foul play. Two lessons anchor this topic. First, the form of his report is a model: a public-interest argument grounded in fact and law, not a dump of secrets or an operational weapon. Second, the human weight is real and must never be sanitized; the personal cost of raising a concern about your own project is exactly why the ladder, the memo, and legal counsel exist, and why California's SB 53 frontier-developer whistleblower protection (effective 2026) was written for the situation he was in before it existed.
Example 2: An internal model auditor who finds a disparity in her own company's hiring tool. An analyst responsible for an employment-screening model discovers, in her own testing, that it rejects one protected group at a markedly higher rate on equivalent qualifications, a defect that under laws such as Illinois's amended Human Rights Act (in force since 1 January 2026) can be an outcome-based civil-rights violation regardless of intent. The defensible path is the ladder: a dated memo to the model owner stating the finding, the disparity measurement, and a proposed audit; escalation to the internal governance board if it is ignored; and, only if the company refuses to act on a confirmed unlawful harm, a report to the relevant civil-rights or employment authority. The memo attacks the model, not the colleague who built it, and ends with the specific bias-audit test that would confirm or refute the finding.
Example 3: A clinician-informaticist who cannot verify a vendor's safety claim inside his own hospital. A hospital deploys a clinical AI tool that its own governance file claims has a low critical-error rate, but the informaticist responsible for oversight cannot find the diagnostic evidence behind the number, and the tool is influencing patient care now. His report is about his own organization's deployment decision. The ladder runs: a memo to the deploying committee stating that the safety claim is non-diagnostic and asking for a held-out evaluation on the hospital's own patient population; escalation to the medical executive committee; and, if the harm is confirmed and unaddressed, notification of the relevant health regulator. The operational care here is real: the finding that the safety claim is unproven is shareable, while any specific patient-harm pattern is handled with clinical care and routed to those who can act.
Example 4: A public-sector data officer facing a benefits fraud-scoring system in her own agency. Across several jurisdictions, automated fraud-risk systems in social benefits have caused documented harm to vulnerable claimants. A data-protection officer inside such an agency who concludes the system unlawfully discriminates owes the ladder: an internal memo grounded in the agency's own records, escalation through the agency's governance structure, and, failing that, a report to the national data-protection authority, a protected external channel under the EU Whistleblower Directive. The memo's power is that it needs the agency's own data to make the finding, and it proposes the controlled test that would settle whether the risk score tracks fraud or tracks past investigation.
Example 5: The engineer who raises a concern and is offered the comfortable explanation. A recurring pattern: an engineer reports that a system logs nothing, so it cannot prove its own decisions, and is told the missing logs are a temporary artifact of a migration and not a real gap. The test is diagnostic, not social. If the explanation is true, there is a dated plan and a completion date for restoring the logging that Topic 10.2 requires; if there is no such record, the explanation is a story and the finding stands. (see Topic 10.2) The example shows the owner's most dangerous move, the plausible explanation, seen from the reporter's side, and why a memo demands evidence for the explanation, not just the explanation.
Example 6: The reckless disclosure that discredited a real finding. In a composite of a common failure, a frustrated employee who has found a genuine defect skips every rung, posts an unverified accusation naming a colleague and including a live exploit, and is promptly and correctly dismissed, while the real underlying defect is buried under the drama of the disclosure. The lesson is the mirror image of the others: the finding was real, but the handling destroyed it. Fairness, verification, and the ladder are not what weaken a disclosure; skipping them is what lets a true finding be dismissed as the work of someone who could not be trusted to check their facts.
Example 7: The frontier-lab researcher and the protection that arrived too late. Balaji's situation, an employee of a large AI developer concluding that the company's core practice was unlawful, had almost no dedicated legal protection at the time. That gap is exactly what California's Transparency in Frontier Artificial Intelligence Act (SB 53), effective 1 January 2026, was written to close for employees of large frontier developers, creating both whistleblower protection and a channel to report catastrophic-risk concerns. The example is a live lesson in the "memo is not a shield" principle running in reverse: the law is catching up to the need, but slowly and narrowly (frontier developers only), so a worker in a domain SB 53 does not cover still operates in the gap Balaji operated in, and the ladder, the documented record, and legal counsel remain the operator's real protection rather than any single statute.
Example 8: The manager who was given the memo and did the right thing. Not every report about your own project ends in escalation or tragedy; the common, quiet, successful case deserves to be seen. A team lead receives a dated memo from an analyst showing a fairness defect in a model the team ships, reads it as a finding rather than an attack, approves the cheap test the memo proposed, confirms the defect, suspends the harmful behavior, corrects the file, and thanks the analyst in front of the team. Nothing left the organization; the harm stopped in days; and the memo, the test result, and the correction now sit in the evidence annex as proof the team governs itself. This is the outcome the ladder is designed to produce, and it is why starting at Rung 1 is not timidity but the path that most often serves the affected people fastest.
Example 9: The engineer who reported up and was moved sideways. In a composite drawn from the common experience of internal reporters, an engineer raises a well-documented finding through the proper channel, the organization declines to act, and shortly afterward the engineer is quietly reorganized away from the project, with no formal retaliation that a law would clearly catch. The example is included because sanitizing the risk would be its own falsehood: the ladder and the memo make an action defensible and often effective, but they do not guarantee the organization acts or that there is no personal cost. The lesson is not to stay silent; it is to document the ladder as you climb it (which is what later made this engineer's account credible to an external authority), to keep a dated copy of the record outside company systems, and to seek counsel, because the honest act and the personal risk coexist and both must be handled with open eyes.
Example 10: The United Kingdom's Public Interest Disclosure Act as a different legal shape. The United Kingdom's Public Interest Disclosure Act 1998 protects workers who make a "protected disclosure" in the public interest, and unlike the EU Directive's strong internal-first encouragement, it can protect a disclosure made directly to a prescribed regulator without first exhausting internal channels, provided the worker reasonably believes the information and that it tends to show a relevant wrongdoing. The example is included to keep the guidance globally grounded rather than EU-defaulted: the legal shapes differ across jurisdictions, some encourage internal-first, some permit direct external, and the operator must check the specific framework that applies to them. The ladder remains sound practice under any of them, because the documented internal chance is what most often produces the fastest quiet fix, even where the law would have protected a more direct route.
Example 11: The board member who received the memo and owned the decision. Governance findings sometimes climb to a board or an audit committee, and the receiving side has duties too. A board member who receives a credible whistleblower memo about the organization's AI cannot discharge the duty by noting it and moving on: the finding, once received in writing, is now something the board knew, so a later harm becomes a harm the board was warned about. The example shows why the memo's status as a dated record cuts both ways, it protects the reporter and it binds the recipient, which is precisely why a serious organization would rather fix the finding than let the memo sit, and why the reporter's careful, factual memo is what makes the finding impossible for a responsible recipient to ignore.
Where people go wrong
- "It is my project, so a report against it is an attack on me." The report is about the system, not about you, and treating it as personal is the fastest way to evaluate it dishonestly. The owner who separates their identity from their project can run the same cold checks they would run on a stranger's file; the owner who cannot will reach for the comforting explanation every time. Attack the problem, including when the problem is yours.
- "If I can explain the finding, it is not a real problem." A plausible explanation is not evidence. The test is whether your explanation comes with diagnostic evidence, the kind that would look different if the finding were real, or whether it is a story that would sound equally good either way. The owner's most dangerous move is the explanation that dissolves the finding in the mind without dissolving it in the data.
- "Going public is what whistleblowing means." Public disclosure is the top rung of a ladder, not the definition of the act and not the first move. The overwhelming majority of real findings are handled and fixed internally, which is the best outcome. Skipping the ladder to go straight to public disclosure is usually reckless, usually strips your legal protection, and usually harms the finding's credibility.
- "The ladder is just bureaucracy that protects the company." The ladder protects the finding and protects you. Climbing it, in writing, is what lets you say truthfully "I gave every level below this a real chance," which is exactly what makes your eventual action defensible. An escalation that skipped the rungs is easy to dismiss; one that climbed them is hard to attack.
- "Loyalty to my employer means keeping the problem quiet." Loyalty is discharged by giving the organization a genuine, documented chance to fix its own problem, not by helping it conceal a harm from the people it is harming. When the organization is given the chance and refuses, the duty to the affected people and the duty to the truth govern. Concealment is not what loyalty can lawfully ask.
- "The memo should say who is at fault." The memo attacks the file and the system, never the person, for the same reason you learned in Topic 11.3: a finding someone can act on lands, while an accusation someone can get defensive about starts a fight the finding loses. Name the defect, credit the person who found it, and leave blame out of a document a hostile reader will later use to judge you. (see Topic 11.3)
- "A finding and the exploit that proves it are the same thing to share." The governance finding (the system is broken) is safe to route up the ladder. The operational detail (the exact input that makes the live system harm someone) is a weapon, handled with care and shared only with those who can fix it. Publishing the weapon harms the people the disclosure was meant to protect, which is the failure the whole ethic exists to prevent.
- "Writing the memo makes me legally safe." A memo is an artifact, not a shield. Whistleblower protections are real but patchy, jurisdiction-specific, and slow: the EU Directive, California's SB 53 for frontier developers, various sector laws. Where the stakes are high, get legal advice before you act, keep your own dated copy of the record, and do not confront the serious version of this alone. The program teaches you to do it well; it will not pretend it makes you safe.
- "A report I cannot immediately verify should be dismissed." An unverified report is not a false report; it is a report you have not yet tested. Convert it to a falsifiable claim, run the counterfactual, and propose the cheap test that would settle it, exactly as you would for any governance claim. Dismissing a report because verifying it is inconvenient is the burying failure mode wearing the mask of rigor.
- "Thanking the person who raised it is a soft nicety." A culture that punishes false alarms never hears the true one. Crediting the reporter, especially when the report is about your own project, is what keeps the next serious finding from dying in someone's inbox out of fear. It is not softness; it is how an organization stays able to see its own problems.
- "The best memo is the one that forces the strongest action." The best memo is the one a future regulator, board, or court would read as fair, factual, and proportionate. Overreach, threat, and drama all weaken it. Proportionality, the escalation matched to the harm, the steelman granted, the cheap test offered, is what makes the memo survive the reading that matters most, the one that happens after something has gone wrong.
- "If the organization fixes it, the memo does not matter anymore." The dated memo is the proof that the organization was given the chance and that you handled the finding responsibly, and it belongs in your evidence annex whether or not the fix happened. A finding surfaced and resolved, with the record intact, is one of the strongest things a governance file can contain. The absence of the memo you never wrote is what a later investigation notices. (see Topic 10.6)
- "This is a legal question, not a governance one." It is both, and the governance work comes first. Whether the finding holds, how far it must travel, and what the memo says are governance judgments you make with the tools of this program; when the stakes are high they are made alongside legal counsel, not instead of it. Treating it as purely legal outsources a judgment that is yours to make and that your name is on.
- "The person who reported it to me is now my problem to manage." When a report about your project comes from someone on your team, the temptation is to manage the person, redirect them, reassure them, or route them away from the finding, rather than to handle the finding. That is the shooting-the-messenger failure in a quieter suit. The reporter is not the problem; the defect is. Credit them, bring them into the evaluation, and let them see the finding handled, because how you treat this reporter is what every future reporter watches to decide whether raising the next concern is worth the risk.
- "If the finding is real, I have to escalate to the top immediately." The height of the escalation is set by proportionality and by the state of the rungs below, not by the seriousness of the finding alone. A serious finding whose Rung 1 owner is willing and able to fix it belongs at Rung 1, fixed fast and quietly. Leaping to the top of the ladder on a finding the bottom rung would have handled is its own failure: it forfeits the quiet fix, burns credibility, and can harm the affected people by slowing the remedy. Match the rung to the harm and to which rungs can be trusted, not to your adrenaline.
- "A finding about my own project makes me look incompetent, so I should minimize it." The instinct to shrink your own finding to protect your reputation is exactly backwards. The operator who surfaces and fixes a defect in their own system looks like someone who governs; the one whose buried finding surfaces later, with no memo in the record, looks like someone who hid a problem. Minimizing your own finding trades a small, survivable admission now for a large, unsurvivable discovery later. Your reputation is protected by being the person who found it, not the person who defended it.
- "I should wait until I am certain before I raise it." Certainty is a high bar that a live, ongoing harm cannot afford, and waiting for it is often burying with a respectable excuse. The standard is a testable finding that survives its steelman, not proof beyond doubt; the memo carries the finding and proposes the cheap test that would move it toward certainty. Raising a survived-steelman finding with a test attached is responsible; sitting on it until you are certain, while the harm continues, is not.
- "My finding survived its steelman, so it is already proven." Surviving the steelman means the finding is strong enough to escalate and test, not that it is settled fact. Treating a survived-steelman finding as confirmed before the cheap test has actually run is the mirror image of waiting for certainty: both skip the one step, running the test, that would turn a strong claim into a known one. State the finding as what it is, a claim that survived its steelman and now needs its test, and let the test's result, not your confidence, be what you report as proven.
Questions people ask
- What is whistleblower memo?
- The artifact this topic produces: a dated, addressed, fact-anchored document that states a serious finding about your own project as a bare claim, gives its diagnostic evidence, names the harm, grants the steelman, proposes a fix or a cheap diagnostic test, sets a deadline and the next escalation rung, and attacks the system rather than any person. It is written for a future hostile reader, a regulator, a board, or a court.
- What is report about your own project?
- A credible claim, from a colleague, a red-teamer, a user, a regulator, or your own analysis, that a system you own, scoped, shipped, or signed off on has a serious problem: it may be harming people, breaking a law, or resting on a governance file that misrepresents it. The defining feature is that you are the accountable owner, which creates the incentive to evaluate it dishonestly.
- What is honest evaluation?
- Running the same cold checks on a report about your own project that you would run on a stranger's file, converting it to a bare falsifiable claim, steelmanning it, and refusing the comfortable explanation unless it comes with diagnostic evidence, rather than reaching for the version that protects the project.
- What is the comfortable explanation?
- The plausible story that makes a finding feel smaller (base rates, a migration, a licensing assumption). It is the owner's most dangerous move, because it can dissolve a finding in the mind without dissolving it in the data. The test is whether the explanation comes with evidence that would look different if the finding were real, or is decoration that would sound equally good either way.
- What is the three duties?
- The duty to the organization (diligence, discretion, and a genuine chance to fix its own problem), the duty to the people the system affects (a system that does not harm them unlawfully or unfairly), and the duty to the truth (an honest account of what you found). They normally point the same way; when they conflict, the duty to the organization is discharged by a documented chance to fix, and the other two govern.
Keep going
This lesson builds Judgment when AI supports a decision, and that page shows the roles that hire for it. Every Certified AI Governance Professional (CAIGP) lesson.
Watch the lesson and prove it
Proving it happens inside the program: watch, explain it in your own words, and it goes on a record employers can check.
Watch the lesson and prove it →