AITAH for threatening to divorce my wife if she doesn’t change our infant daughter’s name to one we agreed on?
A 31-year-old dad is facing a complete relationship breakdown just weeks after his daughter’s premature birth. His wife unilaterally named their baby Vriska—a direct reference to a controversial Homestuck character—despite their clear agreement to stick to subtler names from a pre-approved list.
The betrayal escalated quickly: custom baby gifts revealed the secret plan at the shower, an explosive fight turned physical, and she cut him off completely during labor. Now she’s named the child anyway, and he’s told her to change it or face divorce. Family sides against him, but he’s wondering if he’ll ever trust her again.
‘AITAH for threatening to divorce my wife if she doesn’t change our infant daughter’s name to one we agreed on?’
The couple met at an anime convention and built their relationship around shared geeky interests. When they started trying for a baby after buying a house, naming became a fun project with ground rules:
After finding out they were having a girl, his wife fixated on one specific name he’d rejected multiple times:
Late in pregnancy, her mom threw an excited baby shower. Gifts from her immediate family made the secret plan obvious:
He waited until they got home to confront her calmly, but she erupted immediately:
The fight spiraled—she called her family, refused contact, and stayed with her mom until induction at 33 weeks:
When she later tried coming home with the baby, he learned she’d gone through with the name anyway and set his boundary:
Most family members call him unreasonable and suggest just using the middle name instead:
Naming a child is one of the first major irreversible decisions new parents make together. When one partner overrides a clear mutual agreement—especially after involving extended family behind the scenes—it shatters trust at the exact moment the couple needs it most.
The sudden intensity here goes beyond a simple disagreement. Physical aggression, complete communication blackout during labor, and excluding a partner from birth are serious escalations that suggest something deeper might be at play, whether extreme stress, hormonal shifts, or underlying issues that surfaced under pregnancy pressure.
Clinical psychologist Dr. Alexandra Solomon, author of “Loving Bravely,” often highlights how major life transitions expose partnership weaknesses. She explains that true intimacy requires both people to feel safe bringing up needs without fear of retaliation or unilateral action—something clearly missing in this showdown.
Realistically, changing a name after birth certificate signing gets complicated quickly and varies by location, often requiring court involvement once time limits pass. The healthier long-term focus might be rebuilding (or assessing) the relationship foundation: individual therapy for both, medical evaluation for possible perinatal mood issues, and only then joint counseling—if trust can even be salvaged after such a breach.
Take a look at the comments from fellow users:
Pretty much everyone online landed solidly on the husband’s side, stunned by the level of deception and escalation:
Many couldn’t get past naming a real child after Vriska—a deeply unpopular and manipulative character—and predicted a lifetime of awkward explanations:
Several urged consulting lawyers immediately, stressing baby names need two enthusiastic yeses:
A handful raised concerns about mental health, wondering if the extreme behavior signals postpartum or prenatal issues:
One voice pushed therapy but warned of ongoing control patterns:
Almost everyone online sees this as a massive betrayal of partnership at the worst possible time. Going rogue on a child’s name—after coordinating secretly with family—strikes most as a boundary violation too big to ignore.
Could mental health struggles explain some of the explosion without excusing it? Would you fight to change the name, or see this as proof the relationship can’t recover? Drop your own experiences in the comments.
