I gave Ethan the bedroom photograph Lauren had sent me, and I watched him study the image instead of looking at my face.
He held it by one corner, as if touching less of the paper might somehow make the picture contain less of him.
I waited.
The office was colder than it had been that morning, and I could feel the vent blowing against my wrists while my stomach reminded me I still had not eaten.
Ethan set the photograph on his desk and asked, “What exactly did she tell you?”
I noticed what he had not asked.
Not whether I was all right.
Not why she had done it.
Not even how long I had known.
I pulled out the page Cal had shown me and placed it beside the photograph.
“Baycrest,” I said.
Ethan looked at the page.
Then he looked at me.
I kept my hands flat against the folder because my right thumb had started shaking against the cardboard edge.
“You don’t know what you’re looking at,” he said. “And you’re exhausted. I don’t want you making permanent decisions because Lauren decided to be cruel.”
I pointed to the timestamp.
11:47 p.m.
Four minutes after our final Baycrest package had been exported.
I asked him for the name of the Arcwell manager who had received it.
He rubbed his mouth, turned once toward the window, and straightened a pen that was already parallel to the edge of his desk.
“It wasn’t what you think,” he said.
I said nothing.
That helped.
Ethan filled the silence himself.
He told me Baycrest had been a one-time mistake, an informal comparison he had made because he wanted to know whether Arcwell’s numbers were real or whether we were losing work for reasons neither of us understood.
I let him finish before I tapped the line showing an attachment had gone with the message.
“A comparison doesn’t need our completed bid package attached to it.”
His jaw tightened.
I waited again.
He said he had never meant for the file to be used against us.
I asked why the subject line sounded like an ongoing conversation.
That stopped him.
The word printed on Cal’s page was ordinary enough that I had almost passed over it the first time.
Transition.
I circled it.
“Transition from what?”
Ethan picked up the photograph instead of answering, and I took it back before he could fold it.
“Lauren is trying to destroy our marriage,” he said. “You’re letting her control what happens next.”
I slid the photograph into my folder.
“Lauren didn’t send Baycrest.”
He went quiet.
I wanted the name.
I wanted the thread.
I wanted every date.
Instead of giving me any of those things, Ethan told me I was turning an ugly personal situation into a company crisis.
I opened my laptop on the corner of his desk.
The access console was one of the systems I had built years earlier, back when we were small enough that the same person could price a project, repair a formula, answer a vendor call, and reset somebody’s password before lunch.
I found Ethan’s account and removed his permission to export completed bid packages.
He watched me do it.
“You can’t lock me out of my own company.”
“I didn’t.”
I showed him the screen.
His client access remained active.
His calendar remained active.
His ordinary project folders remained active.
Only the function that let him carry a finished pricing package out of the bid library was gone.
I clicked save.
He leaned back slowly.
“You’re going to break something you don’t understand because you’re angry.”
I closed the laptop.
“I built it.”
Then I walked back to the conference room and locked the door behind me.
Cal was sitting where I had left him, turning the empty plastic jam container from the diner between two fingers because he had apparently carried it back with the paperwork without noticing.
I put Ethan’s explanation in front of him and asked him to trace the word transition through every record we already had authority to review.
Cal read the Baycrest page again and said Ethan might be telling part of the truth about one isolated exchange, although he did not like the subject line.
I asked him to leave theories alone for an hour.
“Dates first.”
He nodded.
While Cal worked through the records, I opened the archived bid system and filtered exports by Ethan’s user ID rather than by project name.
That changed the picture.
Baycrest was not alone.
Three other completed packages had been exported under Ethan’s credentials during the twenty-four hours before submission deadlines, and two of those projects had later gone to Arcwell by margins narrow enough that I had written them off as bad luck.
I wrote every time on paper.
I wrote every project beside it.
I wrote the result.
One export had happened at 1:16 in the morning, a time Ethan had once explained by telling me he had woken up worried about a client question and checked his email from downstairs.
I remembered being annoyed because the kitchen light had woken me.
I had gone back to sleep.
I kept reading.
Cal said, “If you cut his export permissions, that shouldn’t interfere with anything due today. Those client portals are separate.”
I accepted that for the moment and asked him to keep tracing the Arcwell recipient.
At 1:38, I removed the remaining automatic export privileges attached to Ethan’s role and changed the bid library so that any completed package required a second authorized user before it could leave the archive.
It took six minutes.
My hand cramped halfway through, and I stopped long enough to flex my fingers against the table.
A bent paper clip lay near the chair leg.
I picked it up, dropped it into the trash, and went back to work.
At 1:52, Ethan knocked once and opened the conference-room door before I answered.
I shut my laptop.
He told me a current client had revisions due that afternoon and asked whether I intended to damage an active relationship just to prove a point to him.
I asked for the deadline.
“Three fifteen.”
I checked the project record.
The client portal really was active.
Then I saw the problem Cal had missed.
The portal itself was separate from our bid archive, but Ethan was still the only verified relationship contact authorized to submit the final response, and changing that designation required a client administrator who was not going to process it in ninety minutes.
Cal had been wrong.
I did not mention it.
For the first time since morning, I had to give Ethan back a piece of access I had just taken under control.
I hated that.
I did it anyway.
At 2:07, I created a temporary session limited to that client portal, moved the final package myself into the approved submission folder, and told Ethan he could send it from the conference room with me sitting beside him.
He stared at the chair.
“Seriously?”
“Sit down.”
He sat.
The room had become cold enough that I pulled my coat around my shoulders, and when Ethan opened the client portal I noticed a faint ink mark along the side of his hand from the photograph he had handled earlier.
I checked every attachment before he uploaded it.
He checked the client message.
I checked the recipient.
He submitted the package.
I recorded the confirmation number and ended his temporary session before he could close the browser himself.
For several seconds, neither of us moved.
Then Ethan said, “I was trying to protect what we built.”
I put the confirmation page into the project folder.
He continued because I did not answer.
He said our pricing had become too aggressive, that we were taking risks he could see from the client side, and that I was too close to the numbers to notice what those risks were doing to us.
I listened without correcting him.
Then he said something he should not have said.
“Sometimes losing a bad project is cheaper than winning it.”
I looked at him.
He knew immediately.
I asked, “Did you decide which ones we should lose?”
His face changed.
Not much.
Enough.
He told me I was twisting his words.
I opened the archive again and turned the screen toward him, showing the four completed packages exported from his account.
“Pick one,” I said. “Tell me why this one left the system.”
He refused to touch the computer.
I picked Baycrest.
“This one.”
He stood and told me we both needed food, sleep, and twenty-four hours before we said things we could not take back.
I stayed seated.
“Who was the Arcwell manager?”
Ethan walked out.
I ended the conversation there and locked the conference-room door again.
Sometime after two thirty, my phone lit up with another message from Lauren.
I did not open it immediately.
I finished documenting the temporary portal session, saved the client confirmation, and copied the new access-control report onto the same secured drive that held the original files from that morning.
Only then did I read her message.
Lauren had written that Ethan had told her I was already preparing to leave the company and that our marriage had been finished privately for months.
She added one sentence asking why I was pretending otherwise now.
I did not answer.
The message did not prove a bid leak.
It proved Ethan had been telling different versions of my life depending on who was listening.
I preserved it anyway.
At 3:04, Cal found the first useful result from the word I had circled.
Transition appeared in two older subject records connected to the same Arcwell manager.
Neither record included Lauren.
Neither came after the affair began.
I read the dates twice.
One was nine weeks before Baycrest.
The other was three weeks before it.
The subject lines were short.
Transition question.
Transition follow-up.
I asked Cal whether he could establish what had been attached without moving beyond records we were entitled to examine.
He said he could establish file names from the company side if Ethan had exported company material first, but he could not tell me what Arcwell had retained without a different process.
“Company side only,” I said.
I did not need shortcuts.
I needed evidence that would survive being challenged by Ethan five minutes later, five months later, or by anyone who had never seen Lauren’s photograph and did not care about my marriage.
By 3:36, we had one more match.
An archived export from Ethan’s account carried the same internal revision code as a filename referenced in the older transition record.
It was not a completed bid.
It was worse in a quieter way.
The file contained our pricing assumptions, vendor discount ranges, and the walk-away numbers I used when deciding how low we could go without turning a job into a problem we would pay for later.
I closed the screen.
For a minute, I did nothing except press my tongue against the dry inside of my cheek and listen to the ventilation click on again.
Then I printed the record.
Ethan had spent the afternoon telling me he was worried that my pricing exposed the company to bad projects.
Before Baycrest, he had exported the document that explained exactly how I protected us from them.
I carried the page into his office.
He was standing beside the window with his phone in his hand, but he put it down when he saw the paper.
I asked him one last time for the Arcwell manager’s name.
This time, he gave it to me.
I checked it against Cal’s record.
It matched.
Ethan sat down.
He said he had made contact because he was scared about where the company was going and wanted options if we ever needed them.
I asked what transition meant.
He said it meant nothing formal.
I put the pricing-assumptions export beside the Baycrest record.
“Then why send this?”
He did not answer.
I waited until he did.
Ethan said Arcwell had wanted proof that he understood the market from the inside and that he had shown them material he believed was general enough not to hurt us.
I pointed to the vendor discount ranges.
“Those are ours.”
He said, “I know.”
That was the first clean sentence he gave me all day.
I asked him to put in writing that he would not export, alter, delete, or transmit any company bid material while we reviewed the records.
He resisted the word transmit.
I kept it.
He resisted the sentence preventing contact with Arcwell about active bids.
I kept that too.
When he finally signed the temporary access acknowledgment, I copied it, scanned it into the company record, and handed him his copy.
He asked whether I was really going to make eleven years of work depend on a few emails and one vindictive woman.
I put Lauren’s photograph back inside my folder.
“No.”
I pointed at his signature.
“I’m making today’s access decision depend on what you did.”
At 5:11, Ethan left the office with his client access suspended except for ordinary read-only contact records and no ability to export completed pricing material.
I watched the door close behind him, then verified the permissions myself.
For the first time all day, the immediate risk felt contained.
It was not an ending, but it looked enough like one that my body believed it for several minutes.
I ate half of a stale granola bar from the bottom of my bag.
I drank water.
I stood beside the copier while it warmed up and peeled an old shipping label from my sleeve without remembering how it had gotten there.
At 5:47, Cal came to my doorway holding three pages.
I knew from his face that the word transition had finally produced more than a date.
I set down the water bottle.
Cal had matched another company-side export to the oldest transition record, and this time the filename referenced a document Ethan himself had created from information pulled out of my bid library.
The document was a stripped-down client and pricing summary.
No dramatic title.
No confession in the filename.
Just numbers, account histories, renewal windows, and notes identifying which relationships Ethan personally managed.
I read the first page.
Then the second.
On the third, Cal had highlighted a line preserved in the subject-record excerpt from Ethan’s exchange with Arcwell.
Ethan had described the material as an example of what he could bring with him if a transition became possible.
I sat down.
The affair had not created the leak.
Lauren had not persuaded Ethan to betray the company.
Before she ever entered the personal part of my life, Ethan had already been using the work I built to prove his usefulness to the competitor taking projects from us.
I read the line again because I wanted the exact meaning, not the version anger would invent for me.
It stayed the same.
He had sent Baycrest later.
He had sent pricing assumptions earlier.
He had described our client information as something he could bring over.
The pattern was complete enough for me.
At 6:22, I called Ethan and told him I needed one answer before he came home.
He asked whether this could wait until morning.
I read him the sentence from the transition record.
He stopped asking for time.
When I got home at 7:16, Ethan was upstairs packing an overnight bag in the guest room.
I left my shoes by the stairs and carried the transition pages with me.
The house was warmer than the office, and I realized halfway down the hall that my shoulders had been raised almost to my ears for hours.
Ethan folded a shirt, unfolded it, and folded it again while I put the three pages on the bed.
He told me he had never planned to destroy our company.
I asked whether he had planned to go to Arcwell.
He said he had wanted a possible landing place if things between us or the company became impossible.
I asked whether Arcwell had requested confidential material.
He said not in those words.
I asked whether he had sent it anyway.
He looked at the pages.
“Yes.”
I asked whether the Baycrest package was intended to prove that he still had access to current numbers.
He sat on the edge of the bed.
For several seconds, he stared at the floor.
Then he said yes again.
I did not ask him why Lauren ended up in our bed.
That answer no longer controlled the company problem, and I was not going to let the affair drag me away from the part of the betrayal that could keep hurting people who had nothing to do with our marriage.
I asked for his company key and the backup access token he kept in his work bag.
He gave me the key first.
Then he searched the front pocket of the bag and handed over the token.
He told me we should not make decisions about the marriage while we were angry.
I put both items in my pocket.
“You can stay somewhere else tonight.”
He said I was treating him like a criminal.
I did not argue with the word.
I picked up the transition pages and walked downstairs.
Ten minutes later, Ethan carried his bag past the kitchen and stopped beside the counter where the chipped blue sugar bowl was still sitting beside the coffee I had abandoned before sunrise.
He looked as if he wanted to say something important.
He asked whether I had eaten instead.
“Enough.”
He left.
I locked the door after him.
Before I went upstairs, I poured the old coffee into the sink, washed the cup, and put the sugar bowl back where it had always been.
The next morning, I verified every active bid account, separated client-contact permissions from pricing-export permissions, and added a second review requirement to finalized packages so no single relationship owner could quietly carry one out again.
Cal preserved the records we had already collected, including the export history, Ethan’s temporary acknowledgment, Lauren’s messages, the original bedroom attachment, and the file information she had left inside it.
I sent the documented Arcwell contacts through the formal company process and recorded exactly what material appeared to have left our system, without claiming outcomes we could not yet prove.
I did not announce an arrest.
There wasn’t one.
I did not claim Arcwell had collapsed or that Ethan had lost everything overnight.
None of that had happened.
What had happened was smaller and more useful: Ethan no longer controlled our bid exports, the current projects remained intact, and every suspicious transfer we could substantiate was preserved with its original dates.
The marriage took longer than the access settings.
I did not need to solve it before breakfast.
For several days, Ethan kept asking for conversations about context, pressure, fear, Lauren, and what he believed would have happened if I had listened to him sooner about the business.
I answered only the questions that required an operational answer.
The rest could wait.
The company could not.
A week later, our next major bid went out under the new two-person review process, and I watched the confirmation arrive without Ethan touching the pricing archive once.
I printed the confirmation for the project file even though a digital copy already existed.
Then I opened the secured evidence folder I had started before sunrise on the morning Lauren tried to humiliate me.
Her photograph was still there.
I had not deleted it.
I had not sent it back to her.
I had not used it to punish Ethan publicly.
The picture had arrived as proof that another woman believed she had taken my place.
It ended up documenting the moment I finally looked closely enough at the files leaving my company.
The bedroom image stayed in the evidence file under my control.
