At four-fifteen, while Lily slept under observation, I asked my father how a company seeking a multimillion-dollar medical contract could submit documents containing signatures I had never written. He didn't offer the easy explanation I wanted. Instead, he laid the intellectual-property assignment beside the research authorization forms and said the transaction had been structured to appear legitimate to anyone checking it casually. The documents contained dates, addresses, administrative references, and enough supporting material to look ordinary until someone examined their origins.
I inspected the assignment again. It claimed that I had transferred software rights to LittleLight eleven months before, during the period when I was heavily pregnant and finishing a difficult consulting project. My name was correctly spelled. The address was accurate. The signature resembled mine at a glance, but the final letters curved in a way my handwriting never did. I turned the page over, half expecting to find some explanation on the back.
There was none. Dad explained that the Aster compliance team had received the assignment in response to questions about the source code. Until the legal review, the rights had been presented as settled. He showed me a payment acknowledgment connected to the transfer. According to the company's records, I had been compensated for allowing the technology to be incorporated into its platform.
“How much?”
“Seventy-five thousand dollars.”
I looked up at him. We had recently argued about replacing our aging dishwasher because Ethan said our finances couldn't support unnecessary purchases. I had postponed returning to work partly because he insisted the company needed another quarter to improve his compensation. Yet somewhere in LittleLight's accounting records, a substantial payment had supposedly been made to me for research I hadn't agreed to sell.
“Did the money come into any account I control?”
“That's one of the things counsel will need to establish,” Dad replied. “I won't pretend we know the destination yet.”
I appreciated that answer despite everything. There was a difference between a suspicion and a finding, and I wanted every conclusion about Ethan to withstand scrutiny. He had spent years using confident explanations to end disagreements. I would not allow that pattern to govern the investigation into his conduct.
I remembered the week identified on the assignment. It had been unusually hot for September, and my ankles had swollen so badly that I could barely tolerate shoes. Ethan had presented a packet of mortgage-related papers after dinner, telling me he needed signatures before the lender closed for the weekend. I insisted on reading them, though he complained about my caution. Later that night, he offered to put away my laptop and organize the papers on my desk while I took a bath. I had thanked him.
Now I wondered whether that had been the moment he copied documents, located old credentials, or found the external drive containing Blue Lantern. I could not know. But I remembered how comfortable he had seemed in my workspace and how often he had reminded me that marriage meant sharing everything. He had used the language of intimacy to make ordinary boundaries sound unreasonable.
Dad asked whether the original research documentation was still accessible. I explained that I had retained local archives and that Nora held copies of earlier versions. He encouraged me to contact her before anyone altered or deleted the files. Then he stepped into the hallway to speak privately with Aster's legal team, leaving me beside Lily's bed.
For several minutes I watched my daughter sleep. Her breathing was steadier, and the flushed color had begun to ease from her cheeks. A nurse came to check her temperature, recorded the result, and adjusted a line near the bed. When she left, I found myself looking automatically toward Lily's ankle. The band was gone. A faint indentation remained where its strap had rested against her skin.
The sight brought back Ethan's remark from the previous evening about Lily helping his career. He had spoken with the casual confidence of someone who regarded his daughter as an available resource. I had heard affection in the statement because I expected affection from her father. Now I could not stop wondering what else he had meant.
My phone vibrated on the chair. Ethan had sent a message asking how Lily was doing and whether Dad had calmed down. There was no apology for leaving us, no explanation of his company's paperwork, and no acknowledgment that the device had become the subject of serious concern. He added that the presentation would still proceed unless someone interfered. I read the message twice and left it unanswered.
Dad returned with an update from the compliance team. They had been examining records concerning LittleLight's clinical testing claims. Several participating institutions had yet to confirm the studies attributed to them. The gaps were troubling because a medical monitoring device required far more than a convincing demonstration to justify broad deployment. I understood the technical implications immediately. If the underlying performance evidence could not be trusted, a hospital might buy a system whose real limitations had never been properly identified.
That was precisely the problem Blue Lantern had been designed to address. Nora and I had spent years trying to prevent software from presenting unreliable data with unjustified certainty. The irony was almost unbearable: a company apparently using our work was marketing reassurance while failing to demonstrate that its own reassuring measurements were dependable.
Dad produced another copy of the technical memorandum. I examined the references to data quality and error handling, tracing the logic described in the diagrams. I recognized concepts that had emerged from long discussions with Nora. One particular decision concerned what the system should do when incoming measurements failed internal consistency checks. Our model was designed to communicate uncertainty explicitly rather than conceal it behind a normal status. LittleLight's material described a different user experience, one emphasizing an uninterrupted sense of reassurance.
I asked whether the reviewers had access to source-level technical logs from devices used in demonstrations. Dad said the team had secured some material as part of the diligence process and was requesting more. I told him I wanted any record associated with Lily's monitor examined, particularly the period after I first noticed her fever. He did not immediately promise what the logs would show. He said investigators needed to establish what information existed, who had access, and whether records had changed.
I looked toward the door and realized that our dispute had moved beyond the boundaries of a private marriage. If LittleLight's claims were false, other families might eventually rely on the same technology. Those families would never know that an infant in a Philadelphia emergency department had helped expose the problem. I was not willing to let my daughter become another reassuring entry in a flawed demonstration.
Dr. Patel returned shortly afterward and explained that Lily's preliminary findings pointed toward a urinary tract infection. The team would continue treatment and observation while confirming the diagnosis. I asked whether the device could have caused her fever. The doctor said there was no evidence at that point to support such a conclusion. That mattered. I wanted to hold Ethan accountable for what he had done, not accuse him of harms that the medical evidence did not establish.
After the doctor left, Dad suggested that I speak with an independent attorney as well as the lawyers advising Aster. He reminded me that the company's interests, his board responsibilities, and my personal rights were not necessarily identical. I agreed. I did not want anyone later claiming that I had used my father's position to settle a family grievance disguised as a corporate dispute.
The next time I heard from Ethan, he called rather than texting. I answered because I needed to know what he intended to say. He began by asking whether Dad was still with me. When I said yes, he complained that the situation was becoming unnecessarily complicated. He insisted that LittleLight had legitimate rights to its technology and that I should not allow my father to damage an important business relationship because of a domestic argument.
I asked him one question: had he submitted documents containing my signature to transfer Blue Lantern to LittleLight? He paused. Then he said there were several agreements involved and that I might not remember every administrative detail from the previous year. I told him I remembered enough to know that I had never assigned the project to his company.
Ethan sighed. I knew that sound. It usually came just before he explained why my concerns were exaggerated. This time he told me that the software had been sitting unused for years and that his team had invested significant effort turning academic ideas into something commercially valuable. He spoke as though the lack of current commercial activity meant my original work was available for anyone ambitious enough to take it.
“Did you sign my name?” I asked.
He ignored the question and said we could discuss the matter after the presentation. He was trying to maintain the ordinary rhythm of our marriage, in which his professional deadlines took priority and I was expected to postpone uncomfortable subjects until a convenient time that rarely arrived.
I looked at Lily, whose small hand rested open beside her face. “Our daughter is still in the hospital,” I said. “You do not get to put this conversation on hold because you have a meeting.”
He became angry then. He accused me of allowing Dad to interfere in our family and warned that jeopardizing LittleLight could cost us everything. I asked him what exactly we possessed that I didn't know about. He fell silent. Then he said I was being unreasonable and ended the call.
I placed the phone facedown on the chair. My hands shook, but I didn't cry. A few weeks earlier, the same conversation would have left me trying to identify which of my words had upset him. Now I was beginning to understand the pattern. Whenever I asked a precise question, Ethan transformed it into a dispute about my loyalty, memory, or emotional state.
Dad returned with fresh information from the review team. The materials suggested that LittleLight had been reporting favorable performance results while certain underlying records required closer examination. Aster's legal advisers were discussing preservation procedures so that relevant records could not quietly disappear. I asked whether Ethan knew about the inquiries. Dad said the company had already received requests for additional documentation, and that Ethan's presentation would need to address them.
I understood then why Sylvia had been so eager to remove him from the emergency department. She had spoken about his need for sleep, but the larger issue was his need to control what happened before the nine-o'clock meeting. Her financial interest meant that LittleLight's success was personal to her as well. The more I learned, the less believable her supposed concern about ordinary family inconvenience became.
At around five-thirty, I asked Dad whether I could see the original review notes concerning the software. He explained that some materials were subject to legal and confidentiality restrictions, but he would arrange for appropriate technical information to be examined by independent advisers. I agreed, although impatience made it difficult. There was a part of me that wanted to open every archive immediately and identify the exact files Ethan had taken.
I remembered Nora's habit of preserving development notes with the care of an archivist. Whenever I complained that she kept too many versions, she said mistakes were easier to understand when you could see how they had been made. She was right. The record of our work might now establish what belonged to us and what LittleLight had improperly claimed.
Dad asked whether I wanted to call her immediately. I checked the time and decided to wait until a reasonable hour. Nora lived in Boston with her husband and twin sons. We had remained close, though our conversations had become shorter since Lily's birth. I knew she would help if she could. More importantly, she would tell me when a technical conclusion wasn't supported, even if I desperately wanted it to be true.
The hospital corridor had grown busier. Morning staff were arriving, and the quiet nighttime rhythm gave way to the sounds of carts, voices, and ringing phones. Lily remained under observation, surrounded by people whose priorities seemed refreshingly clear. I watched a physician stop in the doorway to check on her before returning to another patient. No one in that room needed to be persuaded that her condition mattered.
Shortly before six, Dad received a call from Renée Lawson, an attorney advising him in relation to Aster's review. He stepped aside to speak with her. When he returned, his expression was more severe than before. He explained that the technical team had identified an important discrepancy in the demonstration system's records. He wanted us to discuss it with Renée before drawing conclusions.
I asked whether the discrepancy involved Lily's band. He said yes.
For a moment I couldn't speak. I remembered holding Lily beside Ethan's desk while he glanced at the application and told me the readings were normal. I remembered how quickly he had dismissed the thermometer and how angry he became when I insisted on going to the hospital. Until then, I had interpreted his behavior as selfishness and misplaced faith in his company's technology.
Now a more frightening possibility appeared. Ethan might not have been relying on the monitor because he trusted it. He might have known the monitor wasn't telling the truth.
I sat closer to Lily, waiting for Renée to arrive. I no longer wanted reassurance from anyone. I wanted the records, the timestamps, and the names of the people who had touched the system. Whatever those records revealed, I knew they would change the way I understood the man I had married.
