Chapter 10
Thursday. James sends me screenshots throughout the day. His HR portal — emergency contact changed to Calla Mercer. His Prudential portal — notification contact removed. His gym — updated. Each screenshot arrives with no text. Just the image. Proof of correction.
I save each one. Add them to a folder on my phone labeled ADMIN. Then I go back to work.
But there's one thing James can't change from a portal. One thing that requires paperwork. And it's the one that keeps pulling at me like a tablecloth caught under a centerpiece — if I tug too hard, everything on top comes down.
The life insurance beneficiary.
Ruby isn't the beneficiary. I confirmed that. I'm the beneficiary — 100%. But the notification contact is different from the beneficiary designation form itself. And I keep thinking about what Felix said: "Can the beneficiary be changed without spousal notification?"
So I look it up during lunch. The answer, in most states: yes. A policy holder can change beneficiaries at any time. No spousal consent required unless it's a community property state. We're not in one.
James could change the beneficiary to anyone. Tomorrow. Without telling me. Without my signature.
He hasn't. But he could.
And if someone is already the notification contact — the person who gets called when a claim is made — and the beneficiary were to change... that person would know about the money before anyone else.
I'm not saying Ruby is after the money. I don't believe she is. But I'm saying the architecture allows for it. The system, as built, would make it possible.
I close the browser tab. Open the planning app. Swipe. Green. Green. Green. Thursday presentation went well. Friday venue scout confirmed. Sophie's recital next week.
Close it. Open a different browser tab. Type: "Ruby Khoury divorce records [county]."
* * *
Public records are searchable online. It takes eleven minutes.
Ruby Khoury, née Atwell. Married David Khoury, April 2016. Divorced final, March 2020. Filed by David Khoury. Grounds: irretrievable breakdown.
I knew this. I knew the broad strokes. David left. It was sudden. It was devastating.
But I didn't know the details of the filing. I didn't know what was in the public record.
I read the docket. The entries are dry — court dates, motions, responses. But one line catches me:
Respondent (Ruby Khoury) filed Motion to Compel Discovery re: financial accounts. Petitioner (David Khoury) alleged to have removed respondent from joint accounts, insurance policies, and emergency contacts prior to filing without respondent's knowledge.
He removed her. Before he left. He went through their shared life — bank accounts, insurance, emergency contacts — and erased her from all of it. Systematically. Before she even knew he was leaving.
I read the motion twice. Three times. The language is legal and cold — "respondent alleges," "petitioner failed to disclose" — but underneath it I can hear Ruby.
The Ruby who told me about it over wine four years ago.
The Ruby who said: "I went to use the credit card and it was closed.
I called the bank and they said I wasn't on the account anymore.
I called the insurance company and they said David had removed me as a covered dependent two weeks before he left.
Two WEEKS, Cal. He was planning it. He was erasing me while we were still eating dinner together every night. "
She came home one day and she was already gone from everything. The forms said she didn't exist in his life anymore. And then he left.
I sit at my desk. Staring at the screen. At a line in a court document from six years ago. The office is quiet — Felix is at a venue walkthrough, Maya is on lunch. I'm alone with this.
David Khoury did to Ruby what Ruby is doing to me. Except in reverse.
He removed her from everything. She's adding herself to everything.
He made her disappear from a life she was still living in. She's making herself impossible to disappear from a life she doesn't live in.
It's the same wound. Just inverted. A woman who was erased is now making herself inerasable. A woman who was removed without warning is making herself impossible to remove.
I think about Ruby at brunch. The gold band she still wears on her right hand.
The spin class three times a week. The discipline.
The control. The way she volunteers for everything — every pickup, every form, every small administrative task that no one else wants to do.
The way she shows up early and stays late.
The way she knows Sophie's shoe size and James's dentist schedule and the code to our alarm system.
She's not building a fortress around James.
She's building a fortress around herself.
INSIDE someone else's family. Because the last time she was inside a family, someone demolished it overnight and she woke up in the rubble.
She found out she was erased not from a conversation — from a declined credit card at a gas station.
From an insurance call that said she wasn't a covered person anymore.
From a phone number that had been removed from an emergency form she didn't know existed until she needed it.
I close the court records tab. Open the planning app out of pure reflex — the muscle memory of control. Swipe. Green checkmarks for the Hargrove follow-up. Green for tomorrow's venue scout. Green for Friday's client lunch.
Green means safe. Green means running. Green means no surprises.
I close it. Nothing about today is green.
My phone buzzes. Felix: How's the James situation? He complying?
I type back: He's changing everything. Screenshots as proof.
Good. And Ruby?
I look at the court document on my screen. At the motion to compel. At the word "removed" used three times in one paragraph.
I found her divorce records.
And?
Her husband removed her from everything before he left. Accounts, insurance, contacts. All of it. Without telling her. She didn't know until he was already gone.
A long pause. Then Felix: So she's inoculating.
What?
It's a medical term. You expose yourself to a controlled version of the thing you're afraid of. She's afraid of being erased. So she's inserting herself into another family so deeply that erasure becomes structurally impossible. She's inoculating herself against abandonment.
I read his text three times.
That's exactly what she's doing.
Does it change anything?
I think about it. Does understanding why someone does a thing change what the thing is? If I know that Ruby's wound is real — that her fear is earned, that her behavior comes from a place of genuine trauma — does that make the behavior okay?
It makes it sadder, I type. But no. It doesn't change what she did.
So what now?
Now I have to decide if I show her what I know. Or if I just quietly remove her and let the friendship die without a confrontation.
Which one are you leaning toward?
I look at the timeline in my notes. Ten entries. Three years. A woman building herself into a position she can never be removed from — because the last time she was IN a position, she was removed without ceremony.
The quiet option is easier. Change the forms. Distance slowly. Let Ruby figure it out over months — the calls stop coming, the pickups get reassigned, the invitations thin out. Death by administrative correction.
But that's what David did. He removed her quietly. Without explanation. Without giving her the dignity of knowing why.
I won't do that to her. Even if she did it to me.
I'm going to tell her, I type. But not yet. I need the full number first.
How many more do you think there are?
James is checking the rest today and tomorrow. His barber, his car insurance, anything else with a form. He's cooperating.
And when you have the total?
Then I show Ruby. All of them. At once. So she sees the pattern the way I saw it — not one at a time, where each one seems small. All together. Where the accumulation speaks for itself.
Felix sends one last text: That's an event planner answer. Build the show. Control the reveal. Make the audience see what you need them to see.
He's right. That's exactly what this is.
I'm planning one last event. Guest list: three. Venue: my dining room. The program: every form I can find, on a table.
And the keynote is me.
* * *
Friday. James comes home with a list. Handwritten on a legal pad.
He slides it across the kitchen counter like a man submitting evidence.
His tie is loosened. His sleeves are rolled.
He looks like he spent the day doing something other than his actual job — and he did.
He spent it calling every place he could think of, verifying, correcting.
"Everything I could think of," he says. "And everything I checked today."
I pick it up. Read. His handwriting is the same cramped scrawl it's always been — the handwriting of a man who never slowed down enough to form his letters properly.
I've read this handwriting on anniversary cards and grocery lists and Post-its stuck to the bathroom mirror.
Now I'm reading it on a list of places he put another woman's name where mine should have been.
His barber — Ruby listed. Date unknown.
His car insurance — Ruby listed. January 2023.
His passport application — me (correct).
His golf club emergency card — Ruby listed. Date unknown.
His therapist — emergency contact is me (correct).
His work parking garage emergency card — Ruby listed. 2022.
Six more entries. Four with Ruby. Two with me.
I add the Ruby ones to the timeline. Fourteen total now. Fourteen systems where Ruby Khoury exists as emergency contact, authorized person, or notification recipient for my husband or daughter.
"There might be more," James says. "Places I can't remember. Anything I filled out on paper and never thought about again."
"Fourteen is enough."
He nods. Doesn't meet my eyes. "What are you going to do?"
"I'm going to remove her from all of them. You already started. I'll finish."
"And Ruby?"
"I'm going to talk to her."
"When?"
I set the legal pad down. Look at my husband.
The man who typed another woman's name into fourteen blank spaces over three years because it was easier than waiting for me.
Because I was in another city building someone else's perfect night.
Because Ruby was ten minutes away and I was a flight delay and a timezone and a missed call.
"Soon," I say. "After I've corrected every single one."
"Do you want me there?"
"No."
"Cal—"
"This is between me and her. You already told me what I needed to know. You were careless. You were lazy. You said yes because it was easy. I believe you."
"I'm sorry."
"I know."
"I love you."
"I know that too." I pick up the legal pad.
Fold it. Put it in my bag next to the protein bar Felix restocked this morning.
"But James — love isn't a form you fill out once.
It's every time you type a name on a line.
Every time you choose who gets called. Every time you decide who matters enough to be the first person to know. "
He doesn't say anything. He looks at the counter. At his hands. At the space between us that used to feel like routine and now feels like measurement.
"You chose easy," I say. "For three years. And easy was someone else."
I go upstairs. Pull out the timeline. Fourteen entries now. I organize them chronologically. I print the spreadsheet Felix and I built — every entry with its date, location, contact type, who submitted, method, and status.
The full picture. The run-of-show for my own erasure.
Now I just need to decide how to present it.