Chapter 2 - The Digital Trace
The house was quiet at 3:15 AM. The only sound was the faint, rhythmic whistle of Louisa’s breathing as she slept in her bassinet beside our bed. While Miles snored softly across the room—completely untroubled, completely secure in his belief that he had successfully manipulated the narrative—I sat at the kitchen island with my laptop open.
Nora Chen had given me more than just dates. During our second conversation late yesterday afternoon, when she realized the gravity of the situation, she had quietly pointed me toward the system's access log history.
"Every time a user logs into the employee portal, it tracks the IP address, device ID, and action history," Nora had whispered over the line, her voice cautious. "If he accessed it four times, the system kept a record of what was modified during each session. I can’t email you those logs without a formal compliance request, Cat, but if you're sitting in front of a terminal... I can tell you what to look for."
I pulled up the exact timestamps Nora had provided and cross-referenced them with our text message history and Miles's personal calendar, which I could access through our shared home computer network.
The first login on April 8 had happened at 11:15 AM. That was a Tuesday. According to his calendar, Miles was supposed to be at a mandatory regional marketing meeting in downtown Chicago. Yet the IP address logged by the benefits portal matched our home Wi-Fi network.
Why was he home during a mandatory meeting?
I dug deeper into the portal's audit trail for that specific session. On April 8, Miles had uploaded Louisa’s birth certificate. He had filled in her Social Security number, selected her coverage tier, and designated her primary care physician. He had reached the final confirmation screen.
And then, according to the session log, he had clicked "Save as Draft" and logged out.
I checked the second login: April 12. A Friday afternoon. Timestamp: 3:42 PM. Location: Home Wi-Fi. Actions taken: Logged in, opened the draft application, reviewed the uploaded documents, checked the box acknowledging the terms and conditions, and... closed the browser window.
The third login: April 19. A Saturday morning. Timestamp: 8:05 AM. Actions taken: Logged in, modified the dependent coverage selection, re-entered the exact same birth certificate, reached the payment deduction summary screen, and logged out without submitting.
The fourth login: April 29. Forty-eight hours before the deadline. Timestamp: 11:30 PM. Miles had been fast asleep beside me, or so I thought. But the log showed a mobile login from an iPhone with his credentials. He had opened the portal in the dark, stared at the unsubmitted draft for six minutes, and then closed the app.
It wasn't a glitch. It wasn't an oversight, a moment of forgetfulness, or the result of being "overworked."
It was a deliberate, calculated pattern of behavior. He had gone through every single motion required to make it look like he was handling it, while ensuring the application was never actually finalized.
May you like
My heart hammered against my ribs. I felt a cold sweat break out across my shoulders. Why would my husband deliberately leave our six-week-old daughter without health insurance? What possible motivation could a father have to sabotage his own child's medical coverage?
I needed to look closer at our household finances. If Miles was hiding something related to insurance, what else was he hiding?
