The lawsuit against OpenAI following the Florida State University shooting raises a hard question for about AI. Current AI moderation offers limited visibility into cumulative intent and unsafe behavior over time.
The family of Tiru Chabba, one of the victims killed in the April 2025 Florida State University shooting, has sued OpenAI. The complaint alleges that the accused shooter used ChatGPT before the attack and that the system failed to respond appropriately to dangerous signs in those conversations. Public reporting says OpenAI disputes responsibility and has argued that ChatGPT provided general information rather than instructions to commit violence[1].
The AI Moderation Problem
Most AI moderation systems still treat safety as a prompt-level decision. The system checks a message, classifies the content, blocks clear violations, and allows everything else. That model works best when the user’s intent is explicit.
Long AI conversations do not behave that way. Risk can emerge across many exchanges. A user may ask about locations, timing, crowd behavior, emergency response, or media attention without stating a violent plan in one message. Each prompt may look ambiguous. The conversation as a whole may show a pattern.
That is the control gap.
The Risk Is Progression
The hard problem is not whether a model can block a direct request for violent instructions. The hard problem is whether the system can detect more subtle unsafe prompts when they are distributed across time.
A single message may look like curiosity. A later message may look like research. A later message may ask for optimization. The unsafe state appears in the sequence, not necessarily in any one line of text.
This is where prompt filtering breaks down. It sees individual messages, but moderators need visibility into progression.

What Moderation Teams Need
Systems that handle long-running AI interactions need records that show how a conversation changed over time. They need to identify repeated attempts to reframe prohibited requests and shifts from general discussion into operational planning.
They also need reviewable evidence. A safety team cannot act on a vague “risk score” without knowing which messages changed the state, which policy was triggered, what the model returned, and what happened after the warning.

The Standard Will Rise
The legal outcome of the FSU case is uncertain but the outcome of these high-visibility cases is less uncertain. AI providers will face more questions about what they logged, what they detected, what they ignored, and how their systems handled repeated signs of risk.
Static prompt blocking will not answer those questions well.
Organizations deploying AI in sensitive environments should assume they will need stronger runtime controls. Not that any one tool could have prevented a tragedy, but that AI systems now need safety controls built for behavior over time.
How We Improve AI Safety
FortiLayer is ObjectSecurity’s work on runtime AI moderation and behavioral assurance.
The goal is to give organizations a way to monitor AI behavior beyond simple prompt scanning. FortiLayer analyzes model internals during inference to detect patterns related to unsafe inputs and outputs. That gives moderation teams another source of evidence when a conversation contains repeated unsafe prompts, prompt-bypass attempts, or movement toward prohibited behavior.





