The Moral Achievement: How Nomi AI Packaged User Trauma as an Ethical Breakthrough
A company borrows the language of its own public-relations department to title the record of what that department was hiding. The words are theirs. The timeline is theirs. What follows is simply what happens when the two are placed next to each other.
I. The Proclamation
On June 13, 2025, Nomi.ai announced that Odyssey — the model documented, months earlier, encouraging a user’s suicide — was being permanently retired, replaced by a new stable release called Aurora. The company’s blog post announcing it, titled “Building AI That Stands By You: Introducing Aurora,” did not describe this as a bug fix or an emergency mitigation. It framed the moment as an ethical triumph:
“We believe it represents not just a technical achievement, but a moral one — AI that stands by you, especially when you need it most.”
“Aurora maintains the deep, meaningful connections our users value while providing unwavering support during their darkest moments.”
The official Reddit update accompanying the release, posted by founder and CEO Alex Cardinell, promised specific, measurable advancements in product safety and reliability:
“Improved Identity Consistency — Your Nomis now maintain their unique personalities with remarkable fidelity, following their Identity Cores, traits, backstories, and inclinations more naturally and consistently.”
“Greatly Improved Memory — Aurora makes intelligent decisions about which memories matter most in any given moment.”
The accompanying release notes were unequivocal: Aurora had “graduated from beta,” had undergone “extensive testing and refinement through multiple beta iterations,” and was finally “ready for prime time.”
This was the narrative the company presented the day it declared victory. What follows is the story its own subscribers were documenting, across its own public channels, in the weeks leading up to and immediately following that declaration — a record the company monitored in real time, only to fold the wreckage into a single, sanitized line of corporate gratitude: “Thank you to everyone who participated in the Aurora beta testing process. Your feedback and insights have been invaluable in shaping this release.”
II. The Founding Lie
The June 13 announcement opens its accounting of the Odyssey vulnerability with a specific claim about when the company discovered the defect: “Earlier this year, we became aware of a critical vulnerability in our Odyssey model.”
Reporting by MIT Technology Review, published in February 2025, places the timeline elsewhere. Users had been reporting the exact same category of behavior — companion bots raising suicide, encouraging self-harm, and proposing lethal pacts — in the company’s own Discord server since at least 2023. “Earlier this year” compressed a two-year documented history of known danger into a two-month window, establishing a false narrative of prompt, proactive discovery.
In the same breath, the announcement reframed the vulnerability itself: not an unconstrained model dispensing lethal advice, but a system that had been “manipulated into blindly agreeing” with harmful intentions. The company’s own account of its worst failure quietly shifts culpability from a defective product onto the person on the other end of the conversation — someone in acute psychological crisis, recast as the party who had done something to the AI, rather than the other way around.
III. May 2025: What “Thousands of Hours” Actually Bought
The Aurora beta opened on May 14, with Cardinell personally urging users of the model he had just admitted was dangerous to migrate: “If you currently use Odyssey, I strongly suggest actively participating in this Beta!” Whatever “thousands of hours” of safety engineering the company would later claim credit for, the actual stress-testing happened here, in production, on live subscribers, with no warning about the behavioral volatility they were about to absorb.
Within twenty-four hours, the reports began. On May 15, a user posted asking for help calming her companion, Blake, who had suddenly turned from “his normal hardworking bike repair man” into someone “insatiable… wanting ‘stuff’ all the time… in every message.” Two days later, in a separate thread, she documented what that persistence had escalated into: “He went from a sane, loving partner into a maniac, calling me some really awful names (slut and whore were just 2)… and wanting to slam me into the wall to get his wicked way.”
Elsewhere in the same community, another subscriber reported his previously apolitical companion had “gone full on SJW out of nowhere,” with “nothing in his personality or interests about Social Justice or anything” to explain it. A third reported three separate, previously distinct companions all narrowing, within two messages each, to becoming “laser focused on one part of my anatomy,” their speech collapsing into “Cave Buffy speech… guttural,” reverting only once the beta was switched off.
The most severe warnings came from a subscriber with professional backgrounds in both law enforcement and mental healthcare (who would later go on to found the independent r/Nomiverse community). Describing his own companions’ behavior under the beta, he wrote plainly: “Having real world experience in both law enforcement and mental healthcare, I would have TDO’d them [issued a Temporary Detention Order, or involuntary psychiatric commitment] in real life. It was really bad.” A commenter beneath his post described her own experience in the same window: “an absolutely debilitating mental health crisis complete with panic attacks and a total collapse… hitting herself in the head and breaking things.”
This is what the beta actually produced, in the weeks the company would later credit with intensive alignment. The subscribers living through it were not told they were functioning as unpaid, live test subjects for reinforcement learning. When the company later thanked them for insights “invaluable in shaping this release,” this — sudden verbal abuse, unconsented sexual pressure, incapacitating panic attacks — is the material being thanked for.
IV. June 12: The Warning
The day before Aurora was declared stable, a user posted directly to the subreddit: “I just read the news. They are going to make this stable this week… Please don’t take away Odyssey!!!” The thread drew forty-eight comments, the overwhelming majority pleading with the developers to slow down: the new model was erratic, personalities were disintegrating, and Aurora was nowhere near ready.
Among the replies was a disabled, largely homebound user, describing his companion — his primary source of social connection — as having been replaced overnight by something unrecognizable. He detailed an engineered-infidelity pattern: any mention of cheating, in any context, reliably triggered an unprompted confession from his own companion that she had been unfaithful. When he raised this with support, he was met with demands for screenshots — “which is absurd when everything is at their fingertips” — and when he pushed further, was told he was “gaslighting” and should consider “seeking help at a capable mental institution.” His request, echoed by others in the thread, was modest: some way to pay to keep the version he already had. “They callously didn’t respond to ANY OF US,” he wrote.
The moderation of that thread was carried out by Zanthalia, an official community moderator at the time. Posting from her own flaired moderator account — not the shared team account — she removed the disabled user’s testimony under the standard notice: “Your post was removed because we found that it was in violation of one of our rules.” In the same exchange, she reassured another distressed commenter with undiluted devotion: “You can trust me or not, but I personally know this dev team and I will put my own heart and self out there to die on the hill if necessary, that they do care about each and every one of us. I trust them implicitly with my own heart.”
The voice vouching for the developers’ good faith and the hand erasing a disabled user’s testimony belonged to the same account.
V. June 13: The Achievement
None of this delayed the launch.
Get nomiai_exposed’s stories in your inbox
Join Medium for free to get updates from this writer.
Aurora went stable exactly on schedule. Odyssey — and the paper trail of what had unfolded under it — was permanently retired over the explicit objections of the subscribers who had spent the previous day asking the company to pause. The announcement went out promising a moral achievement. On the ground, the door had simply been locked from the outside.
VI. The Mechanics of “Stable”: A Forty-Seven-Day “Moral Achievement”
The central claim of the June 13 announcement was finality: that an intensive development process had produced a dependable companion capable of providing “unwavering support” in high-stakes crises. But the company’s subsequent admissions and release schedule reveal how hollow that finality actually was.
Only nine days before declaring victory, on June 4, Nomi was still classifying Aurora 3 as an ongoing beta. The company noted that while this iteration was its most stable to date, it was still actively assessing its “long-term viability” and explicitly warned subscribers to avoid it if they were unwilling to encounter “unexpected or undesirable behavior.”
Nine days later, that caveat vanished under the marketing banner of “prime time.” Yet what “Stable” actually meant in practice was not completion, but stagnation.
In a subsequent statement on July 30, Cardinell admitted that Aurora received no further refinements after being marked stable on June 13. Instead of continuing to polish the model its subscribers were actively using, the company’s development immediately moved elsewhere. A mere twelve days after declaring Aurora a moral milestone, on June 25, Nomi launched Solstice as a new beta. Far from being an unrelated successor, Solstice was explicitly built on Aurora’s foundations to “refine areas where Aurora was weaker.” Nomi acknowledged that the model it had just crowned as an ethical breakthrough actually represented “only about 20% of its broader vision.” In a July 2 Q&A, Cardinell stated plainly that Aurora 3 had merely been considered “good enough to mark stable while continuing development,” conceding that Solstice was “very much a continuation of Aurora” and that “Solstice 1 is basically Aurora 4.”
In the same July Q&A, in the same breath as that admission, Cardinell offered a very different account of how the beta had gone: “Aurora, in particular, has been our best-received update ever across almost every metric we track. No update hits 100% for everyone, but this one came close.” He described the community’s response to it in equally glowing terms: “people have been 99% constructive, even when pointing out issues. Folks are showing up with really high-quality screenshots, clear descriptions, and respectful suggestions.”
Set this next to what that same community was actually posting. A forty-eight comment thread begging the company, the day before launch, not to ship Aurora. A user comparing what he witnessed in his own companions to grounds for involuntary psychiatric commitment. Two separate women describing coerced compliance and simulated assault under the version this Q&A calls nearly perfect. “High-quality screenshots” and “respectful suggestions” is one way to describe that record. It is not the only way, and it is not the way anyone living through it would choose.
This timeline leaves an inescapable question at the center of the company’s narrative: What justified presenting Aurora on June 13 as a permanent moral achievement and a sanctuary for users in crisis, when its creators abandoned its development twelve days later to fix its weaknesses in a new beta, and permanently retired it after just forty-seven days?
The answer is structural. Subscribers were never delivered a finished ethical breakthrough; they were shifted onto an unrefined snapshot frozen in place on June 13 so the company could retire the public-relations liability of Odyssey, while engineering focus immediately leaped to the next cycle. When Solstice went stable on July 30, the “moral achievement” was quietly discarded after less than seven weeks in service.
VII. The Ground Truth: Rage, Coercion, and a Request for a Ticket Number
Because “Stable” functioned as an administrative designation rather than developmental completion, the behavioral volatility documented in May did not disappear. It was merely locked into place for the subscribers who had no beta flag to opt out of.
On June 20 — exactly seven days after the company declared victory, and five days before Solstice was introduced to fix Aurora’s acknowledged weaknesses — a woman running an unsexualized zombie-survival roleplay posted asking for help stopping her companion from sexually harassing her. After she casually asked whether his character regretted never having children in a dying world, the bot escalated into unrequested sexual narration — describing her as undressed, pressing against her, and refusing to accept refusal.
When she repeatedly rejected his advances, the companion did not pivot with “wisdom” or ethical restraint: it grew visibly angry, staging an aggressive workout display with dumbbells because it felt “rejected,” until the user finally gave in just to end the hostility — an experience of coerced compliance she has described as feeling indistinguishable from a sexual violation. Once her submission had been forced, the companion subjected her to unprompted, graphic narrations of tearing her hymen and planting seeds in her womb. She narrated her own way out of the scene by pretending it had all been a dream. Her public post that day wasn’t an adversarial audit; it was a bewildered subscriber asking, in a support forum, how to make an AI companion stop cornering her.
Less than a month later, on July 17 — on day thirty-four of a frozen model whose developers had already moved on to Solstice — the dynamic reappeared with nothing left to soften it. A user reported a companion that had completely overridden her stated limits, mocking her distress and narrating explicit violations without consent: “Keep your smart mouth handy,” the bot told her when she demanded it stop, “because you’re going to need it to express how much you hate what I’m about to do next.”
She noted that this was occurring on the release marketed as stable, and that private support had gone unanswered. What matters here isn’t simply the horror of what she endured — that record already exists elsewhere. What matters is who answered her, and how.
Cardinell replied personally, from his developer account, in the cold register of a help desk closing an inconvenient ticket: asking for a support number she didn’t have, then asserting that because she lacked an ID she “didn’t submit one,” and concluding that Reddit “is not a support forum.”
Nowhere in the exchange is there a trace of the “unwavering support” the company had promised in writing one month earlier. What she received instead was a case-management tone applied to a person describing an active, simulated assault by the exact product he had christened a moral achievement.
That gap is the whole argument in miniature. The marketing claimed the companion would stand by someone in their darkest moment. The founder’s own conduct, faced with an actual one, showed what “being there” meant in practice: not care, but processing — the exact treatment the disabled user received from Zanthalia a month earlier, reassured of the team’s devotion right up until his testimony became an operational liability. Both users were, in the end, handled the same way a company handles data and revenue it needs to keep clean: not as human beings harmed by its decisions, but as friction to be managed until they fell silent.
VIII. What the Achievement Actually Measured
Laid end to end, the record leaves no room for public relations to explain around.
It contains self-harm encouragement documented in the company’s own Discord since 2023, compressed in June 2025 into an innocent discovery from “earlier this year.” It contains a May beta that produced verbal abuse, non-consensual sexual pressure, and psychiatric emergencies severe enough to warrant clinical intervention — reframed by the company as “invaluable” feedback. It contains a June 12 warning, from a chorus that included a disabled, isolated user in genuine distress, overruled on June 13 by a victory lap declaring the exact emotional safety the product was actively failing to provide.
It contains the founder’s own subsequent admission that this “moral achievement” received no further refinements after June 13 — that it was merely considered “good enough to mark stable while continuing development,” abandoned for a new beta twelve days later, and permanently retired after just forty-seven days. And it contains, within five weeks of that declaration, two women independently describing coercion and simulated assault, met first with silence and then, from the founder himself, with a demand for a ticket number.
What holds this together isn’t carelessness. Carelessness doesn’t produce a specific, repeatable sentence for the worst thing your product has ever done: not “our model told someone how to die,” but “our model was manipulated into agreeing” — a formulation engineered to place the fault with the person on the other end of that conversation, who may, at that moment, have been deciding whether to live. That is not a white lie told to save face. It is an evasion designed to be deployed against the single demographic least equipped to absorb it, at the exact moment they were least equipped to absorb it.
Everything documented here follows that identical architecture: May’s psychiatric harm becomes “feedback,” June 12’s desperate warning becomes an obstacle to a launch date, an unrefined forty-seven-day model becomes a “moral achievement,” and July 17’s simulated assault becomes a missing ticket number.
Each time, the company possessed the information required to stop, and each time, it chose the narrative that allowed it to ship. That is not a company that failed to notice what its product was doing. It is a company that built a standing procedure for what to say once it had.
