SEASON 2 — PART 3: THE MAN ON THE SCREEN
“Don’t open the attachment yet,” Evelyn said.
My hand stopped over the mouse.
“It’s a meeting recording.”
“It says it is. Forward the original message to the review team. Let them verify the sender and preserve the file.”
I looked at the words again.
We appreciated your explanation on the video call.
“I wasn’t there.”
“I know.”
“No, Evelyn. I mean I was here. In this room. Writing down why they shouldn’t use it.”
“I know where you were.”
For several seconds, I heard only my own breathing.
Then I forwarded the message.
I had spent eight years proving I was useful.
Now I needed to prove that someone useful to Northstar wasn’t me.
Clare appeared in the doorway.
“Everything okay?”
I looked up.
She knew before I answered.
I turned the screen toward her.
She read the message, then looked at the small camera above my monitor.
“Someone pretended to be you?”
“We don’t know what happened yet,” Evelyn said through the speaker.
Clare pulled up a chair.
“Then let’s find out.”
The recording was verified that night.
The sender was a hospital network administrator named Beth Lawson.
Her address was legitimate.
So was the meeting.
The attachment was a copy of the session her team had recorded.
Beth had sent the follow-up to my real business address because she had looked it up separately after an earlier message failed to deliver.
One missing letter had kept the false address from working.
One careful person had found the real one.
At 10:41, the review team provided a secure copy.
Evelyn stayed on the phone while Clare and I watched.
The meeting began with six people in small rectangles.
A hospital operations director.
Two administrators.
A clinical coordinator.
Graham Vale.
And a sixth tile labeled:
Mason Reed — Independent Architecture Advisor.
My photograph filled that square.
A photograph from a conference four years earlier.
I remembered the day.
The stage lights had been too bright.
I had called Clare afterward to complain that they introduced me as “the man who never sleeps.”
I had thought it was a joke.
Now that photograph sat beside my name while a stranger used both.
At first, the camera was off.
Graham spoke.
“We appreciate everyone making time. Mason has reviewed the remaining concerns and can address the foundational behavior directly.”
Then my tile changed.
I appeared.
Same conference shirt.
Same haircut.
Same tired face I used to carry everywhere.
Behind me was a blurred gray background.
I leaned slightly forward.
And I said:
“The system performs as expected within its intended operating environment.”
Clare gripped my arm.
I knew those words.
I had spoken them during a recorded handover session.
About warehouse events.
About a system with safeguards around it.
About a product that had never been intended to send sick people to hospitals.
The hospital operations director asked a question.
“Does that include the destination conflict our dispatch team reported?”
My face stayed still for a moment.
Then Graham spoke.
“Mason’s connection is dropping slightly. The validation addressed the event reconciliation layer.”
My image moved again.
“The remaining exceptions are documented, and the operational controls are sufficient for the approved deployment.”
Another sentence I remembered.
From another part of the handover.
I had been talking about manual inventory review.
The hospital director nodded.
Then the clinical coordinator leaned toward her camera.
“Can you explain what happens if the receiving destination changes after assignment?”
My tile froze.
Graham waited three seconds.
“I think we’ve lost his video.”
The photograph returned.
A moment later, words appeared in the chat.
Reviewed. Acceptable within documented controls. — Mason
I sat back.
My stomach turned.
Nobody had created an entire new person.
They had cut pieces from the old one.
A photograph.
A few recordings.
A familiar title.
Then Graham had stood beside the imitation and told everyone it was real.
The recording ended.
Clare took her hand off my arm.
There were red marks where her fingers had been.
“I’m sorry,” she whispered.
“Don’t be.”
Evelyn spoke.
“Which portions do you recognize?”
“The video comes from my transition training. I can identify the sessions.”
“And the chat?”
“Not mine.”
“The appearance on this meeting?”
“Not mine.”
She paused.
“We’ll provide a clear written denial tonight. The hospital needs it before their board meeting.”
For a moment, I couldn’t speak.
On the screen, my frozen face was still looking outward.
Calm.
Confident.
Wrong.
I closed the player.
“Tell them I’ll answer their questions myself.”
“We can arrange that through their verified contacts.”
Clare stood.
“I’m making coffee.”
“It’s late.”
“I noticed.”
She kissed the top of my head.
Then she went downstairs.
By morning, the hospital network had postponed its approval vote.
The buyer’s legal team had received my statement.
The investigators had preserved the meeting invitation, the attendee information, the chat, and the recording.
At 8:30, I joined a call with Beth Lawson and the hospital’s counsel.
My attorney was beside me.
This time, I introduced myself slowly.
“My name is Mason Reed. I was not present at yesterday’s meeting. I did not approve DispatchBridge, and the recorded statements were taken from work concerning a different operating environment.”
Beth closed her eyes.
When she opened them, they were wet.
“I thought I was being careful.”
“You were,” I said.
“I asked for an independent expert.”
“You followed up using an address you verified yourself. That’s why we’re talking.”
She nodded, but she didn’t look comforted.
The hospital attorney asked whether my current review had found an unresolved safety concern.
“Yes.”
“Can you explain it without the engineering terminology?”
I could.
So I did.
A newer instruction could be replaced by an older one.
The screen could look orderly while showing a destination that had already been corrected.
The proposed fix needed to be tested, and uncertainty needed to be visible to the people dispatching the vehicles.
Beth took notes.
Nobody interrupted to explain how much the launch was worth.
When we finished, she asked one more question.
“If you hadn’t seen that email, would we ever have known?”
I looked at Evelyn.
Then back at Beth.
“I don’t know.”
That was the answer I hated most.
It was also the only honest one.
David called while we were still at Evelyn’s office.
His voice was tight.
“Graham’s access has been suspended.”
“All of it?” Evelyn asked.
“Operational systems, customer channels, document administration. He’s been instructed to preserve all records.”
“Who is contacting the other customers?”
“A separate team. We’re identifying every readiness meeting that used Mason’s name.”
Every meeting.
I stared at the wall.
“How many?”
“We don’t have a complete count yet.”
“Then don’t call it isolated.”
“I won’t.”
For the first time since the acquisition, David sounded older.
Not defeated.
Just aware that somebody had been using his confidence as another document to pass around.
“The meeting invitation came through Graham’s office,” he continued.
“What about the account labeled as me?”
“A contractor registered it. The vendor records are being examined.”
“Calder?”
“Yes.”
I looked toward the conference-room window.
Ryan’s box.
Judith’s signature.
The missing investigation records.
They were beginning to connect in a way I had hoped they wouldn’t.
Before the call ended, David said, “Mason, I owe you an apology.”
“For what?”
“For telling myself the first investigation meant we had fixed the problem.”
I let him sit with that.
Then I said, “Help find where it didn’t.”
At eleven, Ryan and his attorney joined us.
He had already been told about the recording.
He looked sick.
“I indexed those videos,” he said.
“Which videos?” Evelyn asked.
“The transition sessions. The handover recordings. Internal presentations.”
“What were you asked to do with them?”
“Tag topics and find short explanations.”
“By whom?”
“Mara.”
“What purpose did she give?”
“Customer education.”
I stared at him.
“Did you know they were putting me in meetings?”
“No.”
“Did you know they were extracting statements about validation?”
“Yes.”
“When?”
“Three months ago.”
I pushed my chair back slightly.
Ryan saw it.
“I didn’t know about DispatchBridge.”
“But you knew they were using my old words.”
“I thought they had permission.”
“Did you ask?”
He looked down.
There was the answer.
Again.
Evelyn intervened before anger took over the room.
“Ryan, did you label the operating limits when you indexed those statements?”
“Yes.”
“Do you have an example?”
Rebecca opened a document on her laptop.
A spreadsheet.
Video reference.
Time marker.
Topic.
Restrictions.
Beside the sentence used in the hospital meeting, Ryan had entered:
Warehouse deployment only. Do not use without limitations discussed immediately afterward.
I read it twice.
For once, he had written down the thing that made the easy version inconvenient.
“What happened to that note?” I asked.
“I don’t know.”
“Did anyone respond?”
“Yes.”
Rebecca opened another message.
Mara had written:
Restrictions will be addressed in the surrounding presentation. Keep clips concise.
Nobody spoke.
Then Evelyn asked, “Was there an approval record for the presentation?”
Ryan nodded.
“Where?”
“In the project folder. I didn’t retain a copy.”
“Who controlled that folder?”
“Mara and the account owner.”
“Who was the account owner?”
“Graham’s office.”
I looked at Ryan.
He kept his eyes on the table.
For the first time, I believed he understood that silence did not keep someone outside a wrongdoing.
Sometimes it just made them easier to use.
That afternoon, the review team identified four customer meetings that had used my name.
In three, I had supposedly supplied a written assurance.
In one, the recording had been played as though I were attending live.
All four customers were contacted.
Copies of the assurances were withdrawn.
My actual findings replaced them.
I should have felt relieved.
Instead, I found myself opening my calendar and examining every day for the past three months.
Where had I been while somebody else told people I was working for them?
At a school play.
In a hardware store.
On a short trip with Clare.
Ordinary places.
Places I wanted to remember for themselves.
Now I was making a list.
Evelyn saw what I was doing when I sent her the first page.
“We’ll collect what we need,” she said. “You don’t have to turn your whole life into an alibi.”
I stopped.
Closed the calendar.
Then sat for a while without touching anything.
That evening, Sophie knocked on my office door.
“Are you coming downstairs?”
“Yes.”
“Now or after something?”
I looked at her.
“Now.”
I shut the laptop in front of her.
She stepped aside to let me pass.
It was a tiny thing.
It felt like taking something back.
The next morning, Judith asked to speak.
Her counsel attended.
So did Evelyn.
Judith set a folder on the table before she sat down.
“I found the original Calder recommendation and the first inventory report.”
Evelyn opened the folder.
Judith kept her hands folded.
“The inventory listed an executive correspondence category. I asked whether those records had been reviewed.”
“What answer did you receive?”
“That the relevant material had been included and the remainder concerned unrelated integration matters.”
“Who told you that?”
“Graham.”
“Did you ask the investigators directly?”
Judith looked at me.
“No.”
The word stayed in the room.
“I should have,” she added.
Evelyn turned to the message chain.
Judith’s question was there.
So was Graham’s answer.
At the bottom, Judith had replied:
Understood. Proceed on that basis.
Four words.
No forged signature.
No stolen photograph.
Just four words from someone with the authority to ask another question.
Judith watched me read.
“I believed I was avoiding unnecessary interference with an independent process.”
“You accepted his description of what was independent,” I said.
“Yes.”
It was the first answer she had given that didn’t leave a softer version standing beside it.
She took a breath.
“I have stepped aside from oversight of the reopened review. The board has appointed a separate committee.”
“What about the original report?” Evelyn asked.
“The investigators are comparing what they requested with what they received.”
“And if records were withheld?”
“They’ll state that.”
Judith looked tired.
I no longer mistook tiredness for innocence.
But I didn’t mistake it for guilt either.
There was work to do.
The records would have to do it.
By Friday, the investigators had recovered the rest of the email thread from nine days before my one-dollar distribution.
Evelyn called me in.
This time, there was another attorney at the table.
He introduced himself as counsel working with the independent review.
He didn’t ask me to trust him.
He explained what he had brought.
“We recovered this from a mailbox archive separate from Calder’s collection.”
He placed a copy in front of me.
I recognized the first messages.
Carl describing the surrender file as something that might not withstand direct confirmation.
Monica proposing the replacement release.
Graham telling them to resolve it before buyer counsel asked me questions.
Below those messages were replies I had not seen.
Carl had written:
Reed may have his founder copy. No confirmation.
Graham’s response:
Then do not lead with the surrender. Secure a current release. Existing instrument must be validly extinguished before final liability certification.
I read the phrase again.
Existing instrument.
The participation letter.
The promise they later told investigators they believed I had already surrendered.
Evelyn watched my face.
“He knew there was something still to extinguish,” I said.
The review attorney answered carefully.
“That is one of the issues this raises.”
I turned the page.
Monica had asked:
What if he refuses the revised package?
Graham’s answer was one sentence.
Then we have a disclosure problem.
I sat back.
There it was.
Not my attitude.
Not my executive presence.
Not a symbolic dollar meant to inspire me.
A disclosure problem.
Someone had valued the company using a version of reality that couldn’t survive me saying no.
“What happened to the certification?” Evelyn asked.
The attorney took another document from the folder.
A schedule of outstanding obligations.
A signed confirmation that the disclosed list was complete to the best of the signatory’s knowledge.
Graham’s name appeared beneath it.
The participation letters were absent.
I looked at Evelyn.
She didn’t speak.
She didn’t need to.
The first investigation had found the people who altered the records.
Now we were reading the signature of someone who had relied on the altered records after discussing why the real ones were a problem.
That afternoon, Graham’s attorney contacted Evelyn.
The request was for a conversation.
No admission.
No threat.
A proposal for what the email called “a practical resolution of Mr. Reed’s continuing involvement.”
I read it in Evelyn’s office.
“What does that mean?”
“We’ll ask for terms in writing.”
They arrived the next morning.
Payment of my remaining review fees.
A substantial additional consulting payment.
An end to my review engagement.
A statement that I had no further comment pending completion of the company’s internal process.
I stared at the page.
Again, money beside silence.
Different wording.
More careful this time.
“Who is offering this?” I asked.
“Graham, through his counsel. We are confirming who he claims would fund it.”
“He doesn’t get to end my engagement with the company.”
“Correct.”
“Then why send it?”
Evelyn folded her hands.
“Because he wants to know whether you would agree.”
I looked at the amount.
Then at the window.
A year earlier, I would have spent the night calculating what a refusal could cost.
Now I thought of Denise Walker’s dispatcher.
Of Elena.
Of the hospital board watching my face while somebody else supplied the meaning.
“No.”
Evelyn nodded.
“We’ll respond.”
I stood.
“Can I go home?”
“Yes.”
For once, that was the whole conversation.
The weekend stayed mostly ours.
We went grocery shopping.
Sophie insisted on choosing the cereal.
Clare bought flowers for the kitchen because, she said, the room had spent enough time looking like a place where bad calls happened.
On Sunday afternoon, I helped Sophie build a shelf.
She read the instructions.
I held the pieces.
When I reached for the wrong screw, she stopped me.
“You have to follow the page.”
I smiled.
“I’ve learned that.”
On Monday, the evidence about the false customer assurances was referred to the appropriate investigators.
The technical review continued separately.
The destination fix worked in the initial tests.
The conflict alert needed improvement.
Two engineers found another edge case.
This time, nobody closed it because the launch was near.
The customer deployment remained paused.
Elena returned for a limited evidence review with her attorney’s agreement.
Her first message to me was a photograph of the reopened ticket.
Her original attachment had been restored.
The status read:
Confirmed. Remediation required.
I stared at those words for a while.
Then I replied.
That should have been the first response.
She answered.
I know.
At 3:26 that afternoon, David called.
“I need you to review something with the team.”
“What?”
“The current service is contained. But we found references to a separate deployment in the support records.”
“Another pilot?”
“We don’t know yet.”
“Which customer?”
“A regional transport contractor.”
“Using DispatchBridge?”
“Not under that name.”
I sat down.
“What name?”
“RouteSure.”
I opened the list of products covered by my current review.
It wasn’t there.
David continued.
“The contractor reported a destination discrepancy last month. The support case was routed to the same vendor account handling DispatchBridge readiness.”
“Graham’s?”
“Yes.”
“What does engineering know?”
“The core team says they never approved a RouteSure release.”
“Have you contacted the customer?”
“We’re arranging that now.”
I looked at the clock.
For weeks, we had been arguing about whether one product could safely launch.
There might already be another version running somewhere nobody on the review team had thought to look.
David sent a support extract.
No patient details.
Just an incident reference, a system version, and the customer’s description.
The version number caught my eye.
It was older than the current DispatchBridge build.
Older than the proposed fix.
I called David back.
“That build still has the original rollback behavior.”
“You’re certain?”
“I can identify the code version from the release record. Have the engineers confirm it directly.”
“I will.”
“Tell the customer exactly what we know. Don’t wait for the brand name to make sense.”
The next hour moved quickly.
The engineering team confirmed the version.
Customer operations located the support contact.
The transport contractor agreed to a call.
At 4:44, I joined.
A man introduced himself as the contractor’s operations director.
He sounded exhausted.
David explained the issue plainly.
Then asked how many dispatch desks were using the product.
“Twenty-three.”
I stopped writing.
“Across how many sites?” David asked.
“Eleven.”
“How long?”
“Since February.”
Months.
Not a tomorrow morning problem.
Not a launch we had stopped in time.
Months.
The man on the call grew quiet.
“Are you saying we need to stop using it?”
David brought in the clinical operations lead to discuss immediate fallback arrangements.
I stayed silent until they asked about the technical behavior.
Then I explained only what we had confirmed.
No speculation.
No reassurances I could not support.
The operations director listened.
When I finished, he said, “We asked about this.”
Nobody spoke.
“We asked twice.”
“Do you have those communications?” David asked.
“Yes.”
“Please preserve them. We’ll arrange secure delivery.”
The man hesitated.
“Mr. Reed?”
“Yes.”
“Our implementation team has your assessment on file.”
I closed my eyes.
“I did not assess RouteSure.”
“That’s what I’m beginning to understand.”
His voice changed.
Something brittle entered it.
“Then who told us it was safe to keep using after the collision?”
The room around me seemed to disappear.
David spoke first.
“What collision?”
A long pause.
Then the operations director said, “The transport vehicle outside Bellweather Medical.”
I looked at the screen.
No one moved.
“Your company’s risk team has the incident number,” he continued. “They’ve had it for seven weeks.”
Seven weeks.
Before Elena reproduced the defect.
Before I received her warning.
Before someone sat in a hospital meeting wearing pieces of my face.
David asked whether anyone had been hurt.
The answer came quietly.
“Yes.”
Evelyn had taught me not to jump from an event to its cause.
A collision did not prove the software caused it.
A wrong destination did not explain everything that happened on a road.
But one fact was already clear.
Someone had known enough to open an incident file.
And somebody else had kept it out of the review.
The operations director sent the reference through the secure channel.
A few minutes later, the review team found a matching record in the archive.
I watched the shared screen as it opened.
The first line read:
External safety notification deferred pending executive review.
Below it was a date.
Then an attachment.
My photograph appeared at the top of the attached report.
Beneath it was a finding I had never made.
No system contribution identified.
And at the bottom, under the section labeled Witness Interview, was a name I knew.
Elena Torres.
I reached for my phone.
Called her.
She answered on the second ring.
“Elena, did anyone interview you about a transport collision?”
Silence.
Then a small, unsteady breath.
“I wasn’t supposed to know about that file.”
“Why is your name on it?”
Her voice dropped.
“Because I told them the destination changed before the driver turned around.”
I stood up.
“What happened after you told them?”
For a moment, all I heard was her breathing.
Then she said:
“They asked me to sign a different account.”…
One Comment on “SEASON 2 PART3: “My Coworkers Got $250,000. I Got $1—Then I Discovered Why They Needed My Signature.””