Chapter 6
Felix texts me at midnight. A link to the spreadsheet with a new tab: ACCESS PROTOCOLS.
I open it in bed, screen brightness turned down, James snoring beside me. The tab is meticulous — Felix-meticulous, which means color-coded headers, merged cells for categories, and a notes column with full sentences.
| Location Type | Can non-account-holder add themselves? | Requires account-holder consent? | Method |
|---|---|---|---|
| Medical (HIPAA) | No — must be added by patient | Yes, verbal or written | In-person, portal, or phone with identity verification |
| Dental | Varies — some offices accept "on behalf of" calls | Weak verification | Phone call (name + DOB of patient often sufficient) |
| School | No — requires parent portal login | Yes, requires parent credentials | Online portal only |
| Gym/Fitness | Depends on gym — some accept phone updates | Often minimal verification | Portal, in-person, phone |
| Auto shop | Anyone can write on a paper form | Often no verification | Paper, in-person |
| Pharmacy (HIPAA) | No — patient must designate | Yes | In-person or portal |
| Insurance (beneficiary) | No — policy holder must sign | Yes, signature required | Paper or employer portal |
I scroll to the notes column. Felix has written:
DENTAL is the weak link. Many offices accept "I'm calling on behalf of [patient]" with nothing more than patient DOB and address.
Ruby could have done this at any dental office without James knowing.
The question isn't whether she COULD do it alone.
It's whether she DID it alone — at other places too.
Below that, in bold:
THEORY: What if it's not 4 James + 1 Ruby? What if Ruby did more of these herself than we think, and James just never checked?
I stare at that line. Then I close the laptop and lie in the dark thinking about systems.
* * *
Thursday. I tell James I need access to his employee portal.
"For what?" He's making coffee. Sophie is eating cereal at the counter, legs swinging, humming something from Encanto.
"Benefits review. I want to check our coverage before the gala season ramps up. Dental, vision, the life insurance details." I keep my voice breezy. Administrative. The voice I use with venue managers who want to charge extra for setup time.
"I can send you the benefits summary," he says.
"I need the actual portal. There's a beneficiary verification page I want to check. Make sure everything's current."
He pours his coffee. Doesn't look at me. "I'll pull it up for you tonight."
"Or just give me your login and I'll do it during the day. You'll be at work."
He shrugs. "Fine. It's the same password. Sophie's birthday plus—"
"Elm 42. I know."
"See? You know everything." He smiles. Kisses my forehead on his way past. Grabs his keys. "Back by six."
He leaves. Sophie finishes her cereal. I drive her to school. The drop-off line is twelve cars deep and I sit in it thinking about how easy that was. How he just gave me the keys to his entire employee benefits system because he doesn't think there's anything to find.
Or because he genuinely doesn't know what's in there.
* * *
9:47 AM. I'm at my desk. Felix is on a call with the LED wall vendor about Saturday's teardown logistics. Maya is organizing client packets. I have James's employer portal open on my screen.
Prudential Life Insurance. Policy #JM-4419-PRU. Coverage: $500,000. Policy holder: James Mercer.
Primary beneficiary: Calla Mercer (spouse) — 100%.
I exhale. Okay. That's intact.
But I scroll further. There's a section I didn't know existed: POLICY NOTIFICATIONS. "In the event of a claim, who should be contacted in addition to the beneficiary?"
Notification contact: Ruby Khoury. Relationship: Friend. Phone: 555-0147.
Not the beneficiary. The notification contact. The person who gets called when something happens. The person who would know before the money moves. Before I've even processed the news — Ruby would already have the call.
I sit back in my chair. My hands are on the keyboard but I'm not typing.
I'm staring at the screen — at that line, at Ruby's name in a field I didn't know existed until thirty seconds ago.
Policy notifications. A box most people skip.
A line that sits beneath the beneficiary designation like a footnote — easy to miss, easy to fill without thinking, easy to forget you filled.
But someone filled it. And that someone was James. And the person he put there was not his wife, not his mother, not his brother in Connecticut who he calls every other Sunday. He put Ruby.
I add to the timeline:
[Date unknown] — Prudential life insurance: notification contact (not beneficiary — but would be informed of any claim. Need to verify when added.)
Six.
I check the edit history. The portal shows: "Notification contact updated August 15, 2023." By whom? "Account holder: James Mercer."
August 2023. I check my calendar. My hands move automatically — swipe, tap, scroll.
August 15, 2023. I was in Portland. The Greenvale Foundation annual fundraiser.
Three-day event. I remember it because the ice sculpture melted two hours early and we had to pivot to a floral centerpiece at the last minute.
I remember calling the backup florist from the venue kitchen, surrounded by prep cooks who were trying not to listen.
I remember the satisfaction when we solved it — a centerpiece that actually looked better than the sculpture would have.
While I was solving an ice sculpture crisis in Portland, my husband was typing Ruby's name into his life insurance file.
He added her while I was dealing with a melting ice sculpture.
I keep scrolling. HR emergency contacts — a separate section from the insurance. "In case of workplace emergency, notify:"
Line 1: Calla Mercer (spouse). My number.
Line 2: Ruby Khoury (friend). Her number.
At least I'm first here. But she's second. She's in the system. If his office catches fire and they can't reach me — they call Ruby.
August 2023 (same date?) — HR emergency contact: secondary (James submitted via employer portal)
Seven.
Two more in one sitting. Both from the same portal session, probably. August 15, 2023. He sat down at his computer, logged into his benefits portal — maybe during lunch, maybe after hours — and added Ruby to his life insurance notifications AND his HR emergency contacts.
In one session. On the same day. While I was in Portland.
That's not carelessness. That's not "I just filled in the first name that came to mind." That's a man sitting down and systematically updating his files. Putting Ruby in the gaps. Making sure she'd know. Making sure she'd be called.
Felix appears at my desk. Sets down a coffee. Looks at my screen.
"How many?" he asks.
"Seven."
He pulls a chair over. Sits. Studies the spreadsheet. "August 2023 — two in one session. That's intentional."
"I know."
"And the pattern holds. You were traveling."
"Portland. The Greenvale fundraiser."
He leans back. Crosses his arms. "Okay. New theory.
Or — evolution of the theory. It's not just that he adds her when you're away.
It's that your being away is his TRIGGER.
You leave, and his brain goes: what if something happens?
Who's here? And the answer his brain gives him isn't 'I'll handle it. ' It's 'Ruby will handle it.'"
"He's outsourcing his own emergencies."
"He's outsourcing his own VULNERABILITY. He doesn't want to be the person who handles a crisis alone. He wants a woman available. And when his wife isn't available—"
"His wife's best friend is."
Felix nods slowly. Pulls his chair back and forth — a tiny rocking motion, thinking in motion. "Which is convenient for him. And it's also — and I'm sorry to say this — it's also something you trained him to expect."
I look at him. "What?"
"You run four-hundred-person events without breaking a sweat.
You handle every crisis for every client.
You are, professionally, the person everyone calls when something goes wrong.
I've watched you reroute an entire sound system in twenty minutes because the venue lied about their outputs.
I've watched you calm down a CEO mid-panic attack before his keynote.
I've watched you fire a caterer at 4 PM and have a replacement confirmed by 4:22.
" He holds up a hand before I can interrupt.
"I'm not blaming you. I'm saying — James married a woman who handles everything.
And when that woman is physically elsewhere?
He panics. Quietly. And he fills the gap with the closest available substitute. "
I don't say anything. Because he's right. And because it's the first time someone has said the thing I've been avoiding since Tuesday: I built this.
Not the forms. Not Ruby's name on the lines. But the expectation. The system where I am the contingency plan for everyone else's life — my clients, my vendors, my daughter, my husband. I made myself so essential to everyone that when I wasn't there, someone else had to take my place.
And Ruby volunteered.
"I need the rest of them," I say. "All thirty-two contact points. I need to know the full number."
Felix pulls out his phone. "I'll build a call script. For the places you can access — what to say, what to ask. We'll knock out as many as possible this week."
"This week" means before I decide what to do. Before I confront. Before I dismantle.
"Felix."
"Yeah."
"Am I the bad guy here?"
He looks at me for a long time. Long enough that I know the answer isn't simple. Long enough that the office air conditioning cycles off and the room goes quiet in that particular way that only happens when the white noise disappears and you realize how much silence was being covered up.
Then he says: "You're the person who built a system so good that when it ran without you, nobody noticed you were gone."
He stands. Takes his coffee back. Tucks a protein bar — oat and honey, his second choice for me after peanut butter chocolate — next to my keyboard without comment.
"That's not being the bad guy. That's being so good at your job that you made yourself invisible in your own life."
He walks back to his desk. I sit with the spreadsheet open. Seven entries. Four years. A map of every time I left and someone else took my place.
My phone buzzes. Ruby: Quick q — does Sophie need new ballet shoes? Her toes were at the edge last Tuesday. I can grab a pair at the dance shop on my way home if you want. No biggie!
She knows my daughter's shoe size is changing. Because she's at ballet. Because she's authorized for pickup. Because she sees Sophie's feet in the shoes every Tuesday while I'm at a late client meeting.
I type back: Oh you're right — she mentioned they were tight! Size 1 now. Thank you so much. I'll Venmo you. ??
Grateful. Normal. Complicit.
Felix's voice carries from across the office: "You're doing it again."
I lock the phone.
Seven entries. And Ruby is buying my daughter ballet shoes because she's closer to Sophie's feet than I am on Tuesdays.
I swipe the planning app. Green checkmarks. Everything on schedule. Saturday's gala will be perfect. Four hundred people will have the night of their quarter.
And somewhere in a file I haven't found yet — eight, nine, ten, eleven — Ruby's name sits on a line where mine should be.
I close the app. Open the spreadsheet. Start building the call script.
I plan events for a living. I deconstruct systems and rebuild them from scratch. I find the gaps, the overlaps, the single points of failure.
Time to audit my own life the way I'd audit a venue.
Every form. Every line. Every name.
Until I know the full number.