The page slid from my fingers to our attorney’s side of the table.
She flattened it beside the printed diligence history and read the four words I had written months earlier.
ASK WHO OWNS IT.
Nobody spoke.
The air vent clicked above us, and I realized I was still rubbing my thumb against the seam of my coat pocket even though there was nothing in it.
Our attorney put the NOTE on top of Daniel’s email.
Then she turned to Blake.
“Walk me through what you understood this license to permit.”
Blake sat back.
“It permits us to operate the product.”
“That wasn’t my question.”
He looked at the buyer’s counsel instead.
For once, she did not help him by filling the silence.
Blake tried again.
“We’ve used the component for years. There’s never been an operational issue.”
I knew that sentence.
It was mine, just dressed differently.
Our attorney opened Daniel’s forwarded email and read the relevant section without reading it aloud.
Daniel had not discovered some secret kill switch.
The software was not about to shut off.
The problem was narrower.
And worse.
The license allowed our company to keep using the dependency under the existing agreement, but transferring the licensed rights to another operating entity required written consent from the provider.
We did not have it.
Blake reached for his water again.
He missed the bottle by an inch, corrected his hand, and twisted the cap without drinking.
“Fine,” he said. “Then we get consent.”
The buyer’s counsel finally reopened her laptop.
“Before close?”
“Yes.”
“From whom?”
Blake paused.
That pause mattered more than his answer.
Because the person who had spent months telling everyone the transition was clean did not know who currently controlled the right he had described as transferable.
Our attorney looked at me.
“Do you know?”
“No.”
A short answer.
A useful one.
Months earlier, I would have padded it with context until it sounded less embarrassing.
That afternoon, I did not.
While Blake began explaining that procurement maintained vendor relationships, I opened the licensing folder from the diligence archive and searched the agreement history myself.
There were old renewals.
There were support invoices.
There were amendments with filenames nobody had standardized.
There was also a scanned order form from years earlier with a coffee ring on the bottom corner, which contributed absolutely nothing except making the page harder to read.
I kept going.
Our attorney asked the buyer’s team for ten minutes.
They stepped out.
Blake stayed seated.
Blake watched the door close.
Blake looked at me.
Blake said, “You understand this is not the time to create distance between teams.”
I closed the folder.
“I’m not creating distance.”
“You just put your personal notes into the deal record.”
“They were already part of what happened.”
His jaw moved once.
Then he switched back to concern.
“I’m trying to protect you here. You changed your interview recommendation. You wrote the day-one conclusion. If this gets framed as a diligence failure, legal is going to look at the whole chain.”
“I know.”
“You should.”
The room went quiet again.
Because he was right about one thing.
The chain included me.
I had softened Daniel’s evaluation.
I had let Megan’s assumption close a question I knew was still open.
I had written a sentence that was accurate inside a technical boundary and then failed to notice when someone carried it outside that boundary.
None of that made Blake’s edit mine.
None of it made my part disappear either.
Before the buyer returned, our attorney asked me to pull every version of the transition deck that contained my sentence.
I did.
There were seven saved versions across the deal folder.
In the first two, my line sat under Operational Continuity.
In the next version, Blake had reorganized the slide.
The sentence moved.
The wording did not.
By the final deck, it appeared beneath Transfer Conditions, directly above a line stating that no third-party restriction was expected to interfere with the buyer’s day-one use.
That second line was not mine.
I stared at the screen long enough that the text dimmed.
Our attorney tapped the trackpad to wake it.
“Who wrote that one?”
The version history showed Blake.
He did not dispute it.
Instead, he said, “Expected. It says expected.”
Our attorney looked at him.
“That word does not solve the underlying representation.”
When the buyer’s team came back, their counsel remained standing for a moment before taking her seat.
She had brought a paper cup from somewhere outside the room.
She set it down and never touched it.
Our attorney summarized the distinction cleanly: engineering had assessed operational continuity, not transferability; the transition materials had later placed that conclusion under a broader heading; and the underlying license appeared to require third-party consent for the contemplated transfer.
No one dramatized it.
That made it worse.
The buyer’s counsel asked for the agreement.
We sent it.
She asked for the latest amendment.
We sent that too.
She asked whether anyone had contacted the provider about the transaction.
No one had.
For the first time all day, Blake stopped answering first.
Our attorney did not fill in for him.
I did not either.
A few minutes later, the buyer’s counsel surprised me.
She did not threaten to walk.
She did not call the entire deal fraudulent.
She said, “This may be curable.”
Blake exhaled through his nose.
Very slightly.
Then she continued.
“But we are not treating the transition deck as reliable for transfer conditions until we revalidate the statements that depend on third-party rights.”
Blake’s relief vanished.
That was the first real reversal.
The license itself might be fixable.
The trust problem was now sitting in the middle of the table.
By then, I had been awake since before dawn and had eaten exactly half a granola bar from my bag, standing beside the copier while legal printed an agreement we already had electronically.
The copier jammed.
I opened the side panel, pulled out one clean sheet, closed it again, and accomplished nothing.
Someone from facilities fixed it later.
Back in the room, our attorney divided the review into two questions.
Could the required consent be obtained?
And what, exactly, had the buyer relied on when evaluating transfer risk?
The first question belonged to legal and procurement.
The second dragged me back into every document I had hoped I was done looking at.
I read my diligence summary again.
Then again.
The sentence at the bottom still said what I had intended it to say.
No known blockers to day-one operation.
Inside the original section, it was defensible.
Outside it, the meaning changed.
So I wrote a replacement statement.
Not a softer one.
Not a broader one.
A narrower one.
I stated that engineering had reviewed whether the existing environment could continue functioning on day one under current technical conditions, and that the review did not address assignment rights, change-of-control provisions, license transferability, or third-party contractual consent.
It was longer than Blake would have liked.
That was fine.
Our attorney read it once.
“Can you support every word?”
“Yes.”
“Then leave it.”
I left it.
While legal worked through the license contacts, the buyer’s counsel asked me to walk her through Daniel’s interview from the beginning.
Not his résumé.
Not whether I liked him.
The questions.
I told her he had recognized the old deployment structure and kept steering the conversation away from replacement plans until he understood who controlled the underlying dependencies.
I told her Blake viewed that as backward-looking.
I told her I originally thought Daniel’s knowledge was exactly what we needed during transition.
Then I told her I had weakened that recommendation myself.
She asked why.
I could have said workload.
I could have said alignment.
I could have said hiring judgment.
All of those were partly true.
Instead I said, “I wanted the disagreement to end.”
She wrote something down.
Nothing else.
That sentence stayed with me because it was smaller than the consequences it had created.
Afterward, when I went to wash my hands, the restroom water came out painfully cold for several seconds before warming up.
I stood there longer than necessary.
Then I went back.
The next development looked like good news.
Procurement located the current provider contact.
Our attorney confirmed that the agreement had a consent mechanism rather than an absolute prohibition.
There was a process.
There was someone to call.
There was a possible path forward.
Blake started moving again.
He asked for a revised close checklist.
He asked whether the buyer would accept consent as a post-signing condition.
He asked me for language confirming there were no technical barriers once consent was obtained.
That last request stopped me.
Before I answered, I read it twice.
“No.”
He looked up.
“No?”
“I’ll confirm what we tested. I won’t confirm what we haven’t.”
“It’s the same practical outcome.”
“It isn’t the same statement.”
For several seconds he stared at me as if he expected the old version of the conversation to restart, the one where he kept talking until I converted my objection into something easier to circulate.
It did not restart.
Our attorney said, “Use her scope.”
That ended it.
Temporarily.
By late afternoon, the provider had acknowledged the request but had not yet given written consent.
The buyer would not close without it.
That was reasonable.
What I had not expected was the second condition.
Their counsel also wanted the transfer-related portions of the diligence package recertified by legal, with technical statements attributed to the teams that had actually made them.
No blended headings.
No inferred approvals.
No sentence moving categories because someone thought the deck looked cleaner that way.
Blake pushed back.
“This is turning one license issue into a process rewrite.”
The buyer’s counsel shook her head.
“No. The process rewrite is because I no longer know which statements were scoped when they were written and which were scoped later.”
The room went still.
There it was.
We had found a route around the license problem and immediately lost the thing Blake cared about more: control of the narrative.
Instead of negotiating one consent, we were now revalidating the claims that sat beside it.
Not the entire company.
Not every contract.
Just the transfer conditions that had been packaged the same way.
It was slower.
It was annoying.
It was also exactly what should have happened the first time.
During that review, something unexpected happened.
Most of the technical work held up.
The hosting environment was where we said it was.
The support paths existed.
The credentials process matched the documentation.
The manually monitored dependencies I had listed were real and current.
The problem was not that engineering had secretly ignored a dozen catastrophic failures.
The problem was that one category had been stretched until a technical statement looked like a contractual one.
That mattered.
But it also meant we could repair the record without inventing a new version of the company.
For the first time since Daniel’s email arrived, I felt the situation get smaller instead of larger.
Our attorney built a revised transfer schedule.
I marked each engineering statement with its exact scope.
The buyer’s counsel challenged two of them.
I narrowed one and removed the other because I could not support it from the records in front of me.
Blake objected to the removal.
Our attorney kept it out.
Around six that evening, someone brought sandwiches into the conference room.
I ate three bites of turkey and left the rest beside my laptop until the bread curled at the edges.
Nobody commented on it.
Blake was quieter by then.
Not defeated.
Not apologetic.
Just quieter.
When he did speak, he started saying “legal believes” before legal conclusions and “engineering confirmed” before technical ones.
It was such a small change that I almost laughed.
I didn’t.
The provider’s written response came the following morning.
Consent was possible, but not automatic.
They wanted an amendment identifying the buyer’s operating entity and preserving the existing usage limits until the parties negotiated a broader renewal.
The buyer accepted the structure.
Blake called it administrative cleanup.
Our attorney called it a closing condition.
Nobody asked me what to call it.
That was progress.
Still, we were not done.
Because while the license could now move through a defined process, the buyer had not forgotten how it reached the table.
Their counsel requested one final meeting on the revised diligence record.
Same room.
Same table.
Warmer this time.
I left my coat on the back of my chair.
Before the meeting started, I found a blue pen under the conference table and put it on the credenza even though nobody had asked me to.
Then everyone came in.
Our attorney led the review.
She did not let Blake summarize engineering.
She did not let me summarize legal.
Each person answered inside the boundary they could actually support.
When the buyer’s counsel reached my old sentence, she paused.
“Do you still stand behind the original statement?”
“Yes.”
Blake shifted beside me.
I continued.
“In its original section.”
She nodded.
“And under Transfer Conditions?”
“No.”
Another short answer.
No padding.
The buyer’s counsel drew a line through the old placement on her printed copy and wrote the revised technical scope beside it.
Then she moved on.
That was all.
No speech.
No public humiliation.
No dramatic confession from Blake.
The deal did not need one.
The record had changed.
The authority around the record had changed too.
From that point forward, engineering statements in the transition package stayed attached to engineering scope, and anything concerning transfer rights went through legal before it appeared in buyer materials.
Blake could still run meetings.
He could still make recommendations.
He could not turn one team’s conclusion into another team’s approval by moving it across a slide.
The provider amendment was signed after the final language review.
The buyer received the written consent it required.
The revised transfer schedule replaced the old version.
And the transaction moved forward on those terms.
No one called it clean anymore.
They called it documented.
A few days after the room finally emptied, I opened Daniel’s interview file again.
His rejected evaluation was still there with my softened language.
I could not undo the rejection.
I could not pretend Blake had forced my hand.
So I added a factual correction to the internal record stating that my original assessment had recommended Daniel for transition work because of material undocumented dependency knowledge, and that I had revised the recommendation before submission.
I attached the original draft.
Then I stopped typing.
For several minutes, I did nothing useful.
My lunch sat unopened beside the keyboard.
The office smelled faintly like reheated soup from somewhere down the hall.
Eventually I called Daniel again.
This time I left a message.
I did not ask him to rescue us.
I did not offer him the role we had already denied him.
I said his ownership question had been right, that his email had exposed a gap we should have handled earlier, and that I had corrected my interview record because my submitted version did not reflect what I had actually believed at the time.
Then I gave him my number and hung up.
He did not call back that day.
He did not owe me that.
Later that week, a short email appeared in my inbox.
Daniel did not lecture me.
He did not ask what happened to Blake.
He did not ask whether the deal survived.
He wrote that he appreciated the correction and hoped we kept asking the ownership question after the transition was over.
I read it once.
Then I filed it.
The next transition review had a new checklist attached.
The first section covered operational continuity.
The second covered transfer rights.
They were separate.
Under the second section, before any questions about consent, assignment, or third-party approvals, our attorney had added one line in plain text:
Who owns the underlying right?
I recognized it immediately.
Months earlier, those words had been a private reminder beside the name of a candidate we rejected.
Now they were part of the review nobody could skip.
I did not circle them.
I did not underline them.
I closed the checklist and went to the meeting.
The original NOTE stayed with legal.
