# Chapter 12 — No Check-In
On Friday morning, Michael’s name appeared in Emma’s inbox again.
Not inside an old message.
Not in a search result.
At the very top.
Unread.
Emma stopped moving.
The pointer remained over the INBOX folder. Beside her ThinkPad T480, Michael’s blue hoodie hung over the back of the second kitchen chair. Behind her, Byte rustled in his large cage and dragged strips of paper beneath his shelter.
From the kitchen came the soft click of the coffee machine.
Sarah said something.
Emma did not hear the words.
On the screen was:
From: RoboDad <robodad@michamailgate.com>
Subject: Grissom
Date: Fri, Aug 7, 2026She read the line again.
Seven days since Michael had been supposed to collect her from Chloe’s house at 3:05.
Seven days since he had not come.
Emma placed two fingers on the touchpad and opened the message.
Sarah entered with her mug.
“Do you want toast?”
Emma did not answer.
Sarah stopped.
“Em?”
The message was short.
Morning, Em.
Please give Grissom one algae wafer when you check the aquarium.
If he still looks hungry after ten minutes, you can give him a second one.
The filter should be fine until tonight.
DadSarah set her mug down so carefully that the spoon inside barely touched the ceramic.
“What is that?”
Emma read the message again.
Not faster.
Slower.
Every word.
“It’s from Dad.”
Sarah stepped behind her.
When she saw Michael’s name, one hand closed around the back of the chair.
“When did it arrive?”
Emma looked at the clock in the corner of the screen.
8:07 AM
“Just now.”
Sarah reached for her phone.
“Don’t reply.”
“I’m not replying.”
“Don’t touch anything.”
“I’m not touching anything.”
Sarah already had Daniels’s number open, but she had not called yet.
“Can you tell whether it really came from his address?”
“It says his address.”
“Someone can fake that.”
Emma nodded.
She knew.
Michael had taught her that a display name was not an identity and a visible address was not proof.
But that was not the problem.
“It’s wrong,” Emma said.
Sarah looked at the screen.
“What is?”
“The message.”
“Maybe someone has his account.”
“No.”
“Emma, we don’t know—”
“Dad would never write that.”
Sarah read the lines again.
“The filter?”
“No.”
Emma pointed to the middle paragraph.
If he still looks hungry after ten minutes,
you can give him a second one.“That.”
Sarah looked at her.
“Why?”
Emma turned halfway around in the chair.
“Because Grissom always looks hungry.”
“Maybe your father only meant—”
“No.”
Her voice rose.
Not angry.
Certain.
“Dad says bristlenose catfish are professional liars when food is involved.”
Sarah fell silent.
Emma looked at the message again.
“He says Grissom could eat an entire bucket and ten minutes later still act like nobody had fed him in three years.”
The memory did not return as a picture.
It returned as Michael’s voice.
Michael standing in front of the aquarium with an algae wafer between his thumb and forefinger.
One. Not two.
Emma asking how he could know Grissom was not truly hungry.
Because fish have no concept of responsible portion control.
Then several minutes about water quality and digestion, until Emma asked whether he still remembered her original question.
Michael had claimed that was beside the point.
“He would never tell me to give him a second one,” Emma said.
Sarah still held the phone.
“Maybe whoever wrote it didn’t know that.”
Emma stared at the message.
“Then they would have just written that I should feed him.”
“What do you mean?”
“If someone wanted to pretend to be Dad, why would they add something that was wrong?”
Sarah looked at the email again.
“Maybe it was a mistake.”
“Dad doesn’t make mistakes about Grissom.”
“Everyone makes mistakes.”
“Not that one.”
Emma placed both hands flat beside the touchpad.
“And he wouldn’t say the filter should be fine until tonight.”
“Why not?”
“Because a filter isn’t just fine until tonight.”
Sarah frowned.
“I thought it was running.”
“It is.”
“Then I don’t understand.”
“Dad would tell me to check the flow. Or whether there was air in the hose. Or whether it sounded different.”
Emma pointed at the sentence.
The filter should be fine until tonight.“That isn’t something he says.”
Sarah sat in the chair beside her.
“What would he say?”
Emma did not need to think.
“He would say, ‘Don’t trust the light. Check the water.’”
Sarah looked at her.
“Did he say that often?”
“Always.”
Emma looked back at the message.
The sender name, the harmless subject, the short sentences, the simple Dad at the end—almost everything looked like Michael.
Enough that someone else might not notice.
But Michael had not written it for someone else.
“It’s for me,” Emma said.
Sarah placed the phone on the table without ending the call screen. Daniels’s number was still there.
“Of course it is.”
“No.”
Emma shook her head.
“I mean it’s really for me.”
Sarah said nothing.
“Not just sent to my address.”
Emma pointed again at the incorrect feeding instruction.
“He knew I would notice.”
“You think your father wrote something wrong on purpose.”
“Yes.”
“Why?”
Emma studied the message.
No warning.
No location.
No explanation.
Not even the sentence she had wanted to hear for seven days.
I’m okay.
“So I would know it wasn’t normal.”
Sarah picked up the phone and called.
Daniels answered.
“Daniels.”
Sarah did not speak at once.
Emma looked at the message time.
8:07 AM
Seven days after Michael disappeared.
The exact minute might never have mattered.
Somewhere, a small system had only been waiting—not for Emma, but for Michael.
Sarah cleared her throat.
“Officer Daniels, Emma just received an email from Michael.”
There was a short silence at the other end.
“Do not reply to it,” Daniels said.
“We haven’t.”
“Do not close the device. Do not disconnect it from the network. Do not open any attachments or follow any links.”
“There aren’t any.”
“I’m coming to you. Until then, don’t touch anything.”
Emma looked at the wrong sentences.
“Officer Daniels?”
“Yes, Emma?”
“The email really is from Dad.”
Sarah looked at her.
Daniels answered carefully.
“We don’t know that yet.”
“Yes, we do.”
“How?”
Emma read the line one final time.
If he still looks hungry after ten minutes,
you can give him a second one.“Because he wrote it wrong on purpose.”
Daniels was silent.
Emma pulled Michael’s hoodie from the chair and held it against herself.
“Dad wasn’t trying to tell me how to feed Grissom.”
Her voice grew quieter.
“He wanted to know whether I would notice that he hadn’t checked in.”
Daniels arrived twenty-six minutes later.
He did not come alone.
The woman beside him wore no uniform and no police equipment. Only dark trousers, a gray shirt, and a flat black case, which she placed on the kitchen table with both hands.
“Specialist Navarro,” Daniels said. “Digital forensics.”
Emma was still seated in front of the ThinkPad.
She had not touched the screen.
The message remained open.
Sarah stood at the window holding a second cup of coffee, though she had barely drunk the first.
Navarro pulled out a chair but did not sit.
First she photographed the entire table.
The T480.
The charger.
The open message.
The time in the panel.
The network status.
Then she asked Emma to place her hands visibly in her lap.
“Not because you did anything wrong,” Navarro said. “I only need to know exactly who touches what from this point forward.”
Emma nodded.
“I only opened the email.”
“Nothing else?”
“No.”
“No attachment?”
“There isn’t one.”
“You didn’t reply?”
“No.”
“You didn’t open another message afterward?”
“No.”
Navarro looked at the screen.
“Was the mail client already open?”
Emma thought about it.
“Yes. It starts automatically.”
“Were you already in the inbox?”
“I had just checked.”
“And then the message appeared?”
“It was suddenly at the top.”
“Did it make a sound?”
“Only the normal one.”
“A notification?”
“Yes.”
Navarro photographed the visible header again.
From: RoboDad <robodad@michamailgate.com>
Subject: Grissom
Date: Fri, Aug 7, 2026“Your father configured this laptop?”
“Yes.”
“The operating system too?”
“Debian 13 with XFCE.”
Navarro glanced at Daniels.
“Like his.”
“Not exactly,” Emma said. “He doesn’t use XFCE on the work machine.”
Navarro looked back at her.
“Do you know the password for your account?”
“Yes.”
“Later I’ll ask you to enter it yourself. Do not tell it to me.”
Daniels remained at the end of the table.
“Can you determine where the message came from without changing anything?”
“Not completely on a live system.”
Navarro opened her case.
“First we preserve the current state. Then we create a forensic copy. The laptop stays here until we understand what we’re dealing with.”
“There’s nothing dangerous on it,” Emma said.
“I hope not.”
Navarro documented the running processes, network connections, and signed-in users without closing the email. Emma entered her own password while Navarro looked away. Every action was explained and recorded.
Daniels looked at the message again.
“What would you check first?”
“The transport path.”
“The mail server.”
“If there was one.”
Daniels turned toward her.
“What does that mean?”
Navarro pointed to the visible sender.
“That is only what the mail client displays. A message can appear there without arriving from the internet today.”
“How?”
“Imported. Copied locally. Written into the mail folder by another program. Restored from a backup.”
Emma looked from the screen to Navarro.
“Or by a script.”
Navarro paused.
“Why did you say that?”
Emma shrugged one shoulder.
“Dad wrote scripts for everything.”
“Do you know one related to email?”
“Not directly.”
“To your laptop?”
“Probably twenty.”
Sarah looked at her.
“Twenty?”
“Small things.”
“What small things?”
“Backups. Updates. Battery warnings. Sorting Byte pictures.”
Daniels raised his eyebrows.
“A script sorts hamster pictures?”
“By date and whether they’re blurry.”
“Of course it does.”
For the first time that morning, Daniels sounded tired enough to be human.
Navarro exported the full headers and read them on her own device.
After several seconds, she frowned.
“There is no normal delivery path. No chain of external mail servers, no incoming SMTP transport, and no receiving server ID from this morning.”
“Forged?” Daniels asked.
“Not necessarily. It may never have traveled through a mail server.”
The message existed as a complete local file in Emma’s inbox. Its file entry had been created shortly after 8:07.
“It was placed there this morning,” Navarro said. “But not from outside.”
Emma looked at the timestamp.
8:07 AM
“Then it was already on the laptop.”
Navarro looked at her.
“Maybe.”
“Where else would it be?”
“Encrypted. Archived. Stored in another local directory. Or assembled by a program from separate parts.”
Emma thought of Michael’s small programs with names always slightly too silly for what they did.
“Search for robo,” she said. “That’s what he names things.”
Navarro noted the term and checked the user services that had run automatically that morning.
One entry started every day at 8:07.
Not through the system-wide scheduler.
Under Emma’s user account.
Its name was:
roboping.timerEmma leaned forward.
“That’s Dad.”
Daniels looked at the line.
“You know it?”
“I know the name.”
“What does it do?”
“He said it checks whether RoboDad is still on this planet.”
Sarah slowly turned toward her daughter.
“When did he say that?”
“When he set up the laptop.”
“And you never asked what it meant?”
“I did.”
“What did he say?”
Emma tried to remember.
Michael had been sitting on the floor beside her desk. The T480 had still been open. Byte had been trying to pull an entire sheet of paper through the bars of his transport cage.
“He said computers sometimes need to check whether other computers are still there.”
Navarro opened the related service definition from the forensic copy.
Description=RoboDad heartbeat checkBelow it was:
ExecStart=/home/emma/.local/lib/robodad/roboping.shDaniels looked at Emma.
“Robo Ping.”
“I told you. He names everything.”
Navarro examined the metadata.
The script had not been created today.
Not that week.
It had been on the laptop for months and had been modified only once.
The final modification date was July 18, 2026.
Less than two weeks before Day Zero.
“Open it,” Daniels said.
“From the copy only.”
Navarro loaded the file into a read-only text view.
The script was short: no malware, no remote-control function, and nothing that monitored Emma. Once each day, it retrieved a signed timestamp from Michael’s private server.
“The server provides a heartbeat,” Navarro said.
“From Michael?” Sarah asked.
“From a key this script trusts as Michael’s.”
Daniels pointed at the code.
“Could someone else generate the value?”
“With the corresponding private key.”
“Is that key on Emma’s laptop?”
“No.”
“On Michael’s workstation?”
“We’ll have to check.”
Emma saw the line Navarro had highlighted.
MAX_AGE=604800“What does that number mean?”
“Seconds,” Navarro said.
“How many?”
“Seven days.”
Nobody spoke.
She scrolled to the next section.
The script compared the current time with the last valid signed check-in.
If the age was less than seven days, it exited without displaying anything.
If it was greater, it called a second local file.
/home/emma/.local/share/robodad/queued/grissom.eml.ageSarah took one step closer.
“Grissom.”
Navarro nodded.
“An encrypted email file.”
“How long has it been there?”
Navarro checked the metadata.
“Since July eighteenth as well.”
Emma looked at the message again.
Michael had not written it during the night.
Not from an unknown room.
Not from a stolen phone.
It had been waiting on her laptop for eighteen days.
Invisible.
Encrypted.
And every morning, roboping.sh had asked whether Michael had checked in.
Until today, the answer had always been yes.
Navarro opened that morning’s execution log.
Aug 07 08:07:01 emma-t480 roboping.sh[4817]:
Last valid heartbeat age: 604847 seconds
Aug 07 08:07:01 emma-t480 roboping.sh[4817]:
Threshold exceeded
Aug 07 08:07:01 emma-t480 roboping.sh[4817]:
Delivering queued message: grissom.emlBelow it was one final line.
Aug 07 08:07:02 emma-t480 roboping.sh[4817]:
No check-in.Sarah sat down.
Not slowly.
As though her legs had stopped waiting for her.
“He expected this.”
Daniels continued to look at the log.
“He expected the possibility.”
“That he would disappear.”
“That he would be unable to provide a valid check-in for seven days.”
“That’s the same thing.”
“Not necessarily.”
Sarah looked at him.
Daniels continued in the same steady voice.
“He could have been thinking about illness. An accident. A server failure. Any circumstance in which Emma should receive a message.”
Emma shook her head.
“Then he wouldn’t have written the wrong thing about Grissom.”
Daniels looked at her.
“No.”
Navarro examined the script again.
“The email was not the only file delivered.”
Every head turned toward her.
“What else?” Daniels asked.
Navarro pointed at a second path in the log.
No attachment.
Nothing visible inside the message.
Only a small text file copied into Emma’s local documents directory at the same time.
Its name was:
check_the_other_machine.txtEmma stopped breathing.
Navarro opened the file from the forensic copy.
It contained one sentence.
A computer can forget. Two machines have to agree.Henry was not in the room.
Frank was not there.
No one from Chesapeake.
But Daniels had seen the two entries.
The last outbound value in the old controller.
The paper strip at C.M.T.A.
Both machines.
The same number.
00417.
Daniels looked at the message about Grissom.
Then at Michael’s sentence.
“He knew what the printout would do.”
Emma held the hoodie against her chest.
“Dad didn’t contact C.M.T.A. by accident.”
Daniels did not answer at once.
The evidentiary limits remained.
They still did not know who had connected the dongle.
They still did not know which process had opened the serial interface.
They still did not know what Michael had seen or understood at the workstation.
But the file had been prepared on July eighteenth.
The sentence was older than Day Zero.
Michael had already decided then that one computer would not be enough.
Daniels looked again at the final log line.
No check-in.“No,” he said.
“He made sure there would be two witnesses.”
The serial number appeared on Henry’s screen at 10:34.
Not in Michael’s forensic image.
Not in the old controller.
In an ordinary inventory report.
Henry had opened the central hardware records only to see whether the dongle had ever been registered elsewhere inside Chesapeake.
The system had not been built for investigations. It tracked assets and warned employees about unknown hardware. Frank had expanded it two years earlier after several incidents—one involving Steve.
Henry entered the individual serial number again.
The result did not change.
DEVICE SERIAL MATCH FOUND
FIRST SEEN:
THU JUL 30 2026 — 04:18:43 PM
HOST:
S.HARPER-WORKSTATION
INTERFACES:
USB MASS STORAGE
VENDOR-SPECIFIC SERIALDaniels stood behind him.
“Read the host name.”
Henry did not need to.
“Steve Harper.”
“Thursday.”
“Yes.”
“One day before Michael.”
“Yes.”
Henry opened the full record.
The dongle had been connected to Steve’s workstation for six minutes and thirty-four seconds.
The system had registered both interfaces.
Mass storage.
Serial.
A local process had accessed the storage volume. Seconds later, a Linux executable had been launched directly from the dongle.
The file name was:
TagStudio-x86_64.AppImageDaniels pointed at it.
“What is TagStudio?”
“Unknown so far.”
Henry scrolled.
The program had not come from Chesapeake’s approved software repository. It had been executed directly from the removable device.
Steve’s graphical desktop had paused the launch.
UNAPPROVED REMOVABLE DEVICE
UNVERIFIED EXECUTABLE SOURCE
DESKTOP SECURITY WARNING DISPLAYED“He was warned,” Daniels said.
“Yes. But his demonstration permissions allowed him to continue.”
“Who granted those?”
“I did,” Henry said. “For customer demos. Not this.”
The next entry showed that Steve had confirmed the warning.
Not closed it accidentally.
Not missed it.
Confirmed it.
USER ACTION:
RUN ANYWAYHenry leaned back.
“Damn it.”
Daniels ignored the word.
“What happened next?”
Henry opened the process activity.
The AppImage had started in Steve’s graphical user session, created a local configuration directory, and attempted to open the dongle’s serial interface.
The operation had failed.
Not because of the security software.
Because the expected external device was not connected.
TAG READER NOT DETECTED
PAIRING FAILEDSteve had then selected three audio files from a personal directory.
The central log did not preserve their full file names. Only the directory access.
“He tried to transfer music,” Henry said.
Daniels looked again at the program name.
“A tag programmer.”
“Possibly.”
“RFID?”
“Or NFC. Some kind of children’s audio box.”
Daniels took out his phone.
“Where is Harper?”
“Upstairs. He was supposed to be working on customer records.”
“Bring him down.”
Henry was already standing.
Steve entered the room four minutes later.
He wore a pale blue shirt and carried a notepad. When he saw Daniels, his pace slowed.
Then he noticed the report on the screen.
Only some of the color left his face.
“Sit down,” Daniels said.
Steve pulled out the chair.
“Did something happen?”
Henry turned the screen toward him.
“Do you know this device?”
Steve looked at the serial number.
Too long.
“Not from the number.”
“Then from the interfaces.”
“Mass storage and serial could be a lot of things.”
Henry opened the next entry.
HOST:
S.HARPER-WORKSTATIONSteve placed the notepad on the table.
“Okay.”
Daniels sat opposite him.
“What does okay mean?”
“That apparently I connected a device with that number.”
“Apparently?”
Steve glanced at Henry.
“I test a lot of things.”
“Not anymore,” Henry said.
Steve pressed his lips together.
Daniels pushed the printed report toward him.
“You connected this exact device on Thursday at 4:18 PM. Your desktop warned you that the executable source was not verified. You clicked ‘Run Anyway.’”
Steve looked at the paper.
“It wasn’t a company project. It was an audio box.”
“For whom?”
Steve looked at Henry.
“For Emma. A birthday gift Michael could give her.”
Daniels did not move the report.
“Where did you get it?”
“From a supplier.”
“Name.”
Steve was silent.
“Company.”
“I don’t remember.”
Henry stared at him.
“You took an unknown USB device from a supplier with no company and attached it to your workstation?”
“He looked like a supplier.”
“What does that mean?”
“Polo shirt. Badge lanyard. Box.”
“That is not a company.”
Steve looked back at Daniels.
“He approached me in the parking lot.”
The room stilled.
“When?” Daniels asked.
“Thursday. Just before four.”
“After you left the building?”
“I only went outside to get something from my car.”
“What did he want?”
“He asked whether Michael Weber was still inside.”
“And?”
“I said probably.”
“Why didn’t he take the package to reception?”
Steve swallowed.
“He said it was a surprise.”
Henry closed his eyes briefly.
“For Emma,” Daniels said.
“Yes.”
“How did he know Emma?”
“He said Michael had asked about a box like that.”
“Did Michael ever tell you he intended to buy one?”
“Not directly.”
“But you accepted the package.”
“It sounded believable.”
“Why?”
Steve lifted one shoulder.
“Michael buys technical things for Emma.”
“That was your entire verification.”
“The man knew her name.”
“That should have made you more suspicious.”
Steve looked down.
“He said the reader still needed to be programmed. That Michael hadn’t had time.”
“And you wanted to help,” Daniels said.
Steve did not answer.
Henry answered for him.
“He wanted to prove he could do it.”
Steve looked up.
“I only wanted to load a few songs.”
“Which ones?” Daniels asked.
“Three. Space stuff. Things I thought Michael would appreciate. For Emma and the Major Tom project.”
“Did it work?”
“No. The reader saw the tags, but the assignments were wrong. The dongle was supposed to pair them again.”
“According to the man?”
“Yes. The instructions were on the dongle.”
“And although you had already been reprimanded for downloading unverified software and connecting hardware of unknown origin, you did it again.”
Steve did not look at him.
“Frank overreacted last time.”
“Frank told you not to attach unknown hardware to company computers.”
“I thought it was a product adapter.”
“You didn’t think. You wanted to be the one who made it work.”
Steve remained silent.
Daniels allowed Henry’s anger to remain in the room before continuing.
“What happened to the box and the dongle?”
“I gave the box to Michael on Friday morning.”
“What time?”
“Shortly after nine.”
“What did you tell him?”
“That someone had left it for him. For Emma.”
“Did you tell him the supplier had given no name or company?”
Steve did not answer.
“Mr. Harper.”
“No.”
“Did you tell him the software had triggered a security warning?”
“No.”
“Did you tell him the device presented a serial interface in addition to storage?”
“I didn’t understand what that meant.”
“Did you give Michael the dongle as well?”
Steve nodded.
“It was in the box.”
Daniels looked at the working timeline.
“What did Michael do with it?”
“He looked over everything. Asked where it came from.”
“And what did you say?”
“A supplier.”
“Not an unknown man in the parking lot.”
Steve looked at his hands.
“No.”
Henry stood by the window, shoulders rigid.
“Why did Michael later go to his car?”
Steve looked up.
“Probably because of the box.”
Daniels said nothing.
Steve explained.
“He didn’t want Emma to see it if she came into the office that afternoon. So he put it in his car.”
Brenda’s footage immediately entered the room between them.
Michael walking to the car at 1:30.
Michael returning a few minutes later with a small object in one hand.
“Did Michael speak to you again about the device?” Daniels asked.
“Yes.”
“When?”
“Just before he connected it.”
“What did he say?”
Steve looked at the report.
“He asked whether that was really everything the man had given me.”
“And?”
“I said yes.”
“Was that true?”
Steve hesitated.
Daniels did not lean forward.
He did not need to.
“Mr. Harper.”
Steve exhaled.
“The man said something else.”
“What?”
“He said Michael would recognize the connection.”
Henry turned from the window.
Daniels kept his eyes on Steve.
“His exact words.”
Steve closed his eyes for a moment.
“Tell him it’s the connection he was looking for.”
No one moved.
“Did you tell Michael that?” Daniels asked.
“No.”
“Why not?”
Steve’s voice dropped.
“Because then it didn’t sound like a gift anymore.”
Daniels pulled the device report back toward himself.
“What did you do instead?”
Steve looked at the serial number.
“I gave him the dongle.”
For the first time since Michael disappeared, Steve did not merely know what he had seen.
He knew where it had come from.
And Michael had not connected the object to his workstation by chance.
Someone had used Steve to place it there.
Daniels had Steve describe the man three times.
The first time, Steve told the story.
The second time, he had to separate what he had actually observed from what he had inferred.
The third time, he was allowed to state only details he considered certain.
The man had probably been between forty and fifty, perhaps older. About Michael’s height, maybe slightly taller. Average build. Short hair. Dark polo shirt, dark trousers, black shoes, and a badge lanyard around his neck.
“What color?” Daniels asked.
“Blue.”
“The lanyard or the badge?”
Steve thought.
“The lanyard.”
“What was printed on the badge?”
“I couldn’t read it.”
“Did you try?”
“No.”
Daniels wrote something.
“Logo on the shirt?”
“Maybe.”
“That isn’t an answer.”
“I remember something light on the left side.”
“A company logo?”
“Could have been.”
“Or a fold.”
Steve looked at him.
“Yes.”
“Hat?”
“No.”
“Glasses?”
“No sunglasses. I don’t remember whether he wore regular glasses.”
“Facial hair?”
“Maybe stubble.”
Henry stood near the window and no longer interrupted.
His anger was still there, but it had changed.
It was no longer only anger at Steve’s carelessness.
Now it was the realization that someone had known about that carelessness—or had judged it correctly.
“The box,” Daniels said.
Steve indicated its size with his hands.
“Larger than a shoe box.”
“Markings?”
“A shipping label.”
“Name?”
“Michael’s name.”
“Address?”
“The company address.”
“Sender?”
Steve shook his head.
“Not that I noticed.”
“Courier logo?”
“No major logo.”
“Sealed?”
“Clear tape.”
“New or already opened?”
Steve thought longer.
“Maybe opened before.”
“Why?”
“One side had two layers of tape.”
Daniels wrote that down too.
“Other packages? Scanner? Clipboard?”
“No.”
“Anything that actually identified him as a delivery driver?”
“The badge.”
“That you couldn’t read.”
Steve looked down. “No.”
Daniels did not close his notebook.
“Where exactly was he?”
Henry opened the site plan and pushed it toward Steve.
Steve marked the western edge of the employee parking lot.
Not at the main entrance.
Not near the loading area.
Between two rows of parked vehicles, near the route Steve usually took when he went to his own car.
“Was he there before you left the building?”
“I only saw him when I was between the cars.”
“Did he approach you?”
“Yes.”
“Did he use your name first?”
Steve paused.
“I don’t think so.”
“Think or know?”
“He said, ‘You’re Steve, right?’”
Henry looked at him.
“You didn’t mention that before.”
“I didn’t remember.”
“He knew your name.”
“Maybe he had seen me before.”
Daniels did not look away.
“Or he knew whom he wanted.”
Steve rubbed his thumb.
“He could have heard my name inside.”
“Outside in the parking lot.”
“Or from someone.”
“Who?”
Steve had no answer.
“How long did the conversation last?”
“Maybe two minutes.”
“Did he touch you?”
“No.”
“Did he try to enter the building?”
“No.”
“Did he ask you to deliver the package to reception?”
“No.”
“Did he ask you to get Michael?”
“No.”
“He handed it directly to you.”
“Yes.”
“Although Michael was supposedly inside.”
Steve looked at the map.
“He said it had to remain a surprise.”
“And therefore Michael could not see him.”
Steve lifted his head.
Daniels allowed the sentence to remain.
“What did he do after you took the package?”
“He walked away.”
“Where?”
“Toward the rear of the parking lot.”
“To a vehicle?”
“I didn’t see one.”
“Did you see him get in?”
“No.”
“Did you hear an engine?”
“Not consciously.”
“A white SUV?”
“No.”
Daniels waited until Steve looked back at him.
“No GMC Yukon.”
“No.”
“No white vehicle that caught your attention.”
“No.”
Henry folded his arms.
“If a Yukon had been parked there, you would have noticed.”
“Maybe not behind the other cars.”
“But you didn’t see one.”
“No.”
Daniels nodded.
“Then that is what the report will say.”
He called Brenda.
The parking footage was not usually retained for long. Since Michael’s disappearance, however, all available video from the relevant week had been preserved.
Not only Friday.
The days before it too.
The Thursday recording existed.
An hour later, Daniels, Henry, and Steve sat before the wall display.
The camera covered the main entrance and most of the employee parking lot.
Steve’s car stood near the western row.
At 3:56 PM, Steve left the building.
He did not go directly to the car.
He stopped, looked at his phone, and continued.
The man did not come from the main entrance.
He emerged from the left edge of the image between two parked vehicles.
Not suddenly.
As though he had been waiting there.
“Stop,” Daniels said.
The image froze.
The man was visible only partly from the front. His face lay in the shadow between vehicles and was too small for reliable identification.
The blue lanyard was visible.
The badge itself was turned around.
Its blank back faced the camera.
Henry stepped closer.
“Deliberately?”
“Or movement,” Daniels said.
“It is lying completely flat.”
“That does not prove intent.”
They continued the footage.
The man spoke to Steve.
Steve stopped.
The box changed hands.
The man pointed briefly at the top. Perhaps at Michael’s name. Perhaps at a label.
Steve said something.
The man answered.
Then Steve continued to his car.
The stranger remained still for four seconds.
He did not look toward Steve.
He looked toward the building.
Then he disappeared between the vehicles and left the frame through the same edge from which he had entered.
No delivery van drove away.
No car moved immediately afterward.
No white Yukon was visible.
Daniels had them review the next ten minutes.
Nothing.
The man did not return.
“He could have parked beyond the last row,” Henry said.
“Outside the camera coverage,” Daniels replied.
“Or arrived on foot.”
“Yes.”
“Through the rear access road.”
“Possible.”
Steve sat farther back in the room.
“Can you enlarge his face?”
“You can enlarge the pixels,” Daniels said. “That does not create a better face.”
Forensics stabilized several frames. They gained approximate height, posture, dark clothing, the blue lanyard, and the way he carried the box.
No readable badge.
No distinguishing mark.
No license plate.
No vehicle.
Daniels also ordered a comparison with the known Yukon footage.
The driver remained obscured by glass, reflections, and the vehicle frame.
Height and build could be estimated only broadly.
The man in the parking lot was not inconsistent with those limited features.
But he could not be identified as the same person.
The report would not identify him as the Yukon’s driver.
It would state:
A match can neither be confirmed nor excluded from the available imagery.
Steve looked at the frozen frame.
“He looked more normal.”
“Than who?” Daniels asked.
Steve did not answer at once.
“Than someone you should be afraid of.”
Daniels left the image on the screen.
“That was probably the point.”
Henry looked at the place where the man had waited.
“Why Steve?”
Daniels looked at the timestamp.
Then at the path from the building to Steve’s car.
“Because Mr. Harper would not take the package to reception.”
Steve lowered his eyes.
“He would open it himself,” Henry said.
“He would try the software,” Daniels said.
“He would try to prepare it better than Michael could.”
Steve said nothing.
The man had not approached Michael directly.
He had not requested entry to the building.
He had not carried anything through a controlled door.
He had only needed someone curious enough to connect a stranger’s device to a company computer.
Daniels kept the frame paused at the moment the box hung between them.
“He did not choose a random employee.”
Steve looked up.
“He chose you.”
Daniels left the parking image frozen and took out his phone.
“The vehicle file,” he said.
Henry looked over.
“Michael’s car?”
“The full record from the later search.”
Steve lifted his head.
“The box is still there?”
Daniels looked at him.
“What box?”
Steve was silent.
Only for a moment.
Long enough to show again that he knew more than he had admitted.
“The gift,” he said. “I thought Michael might have taken it.”
“Michael left his car.”
“I know.”
“And you knew he placed the box inside.”
Steve looked at his hands.
“Yes.”
Daniels requested the digital vehicle file, every overview and detail photograph, and the inventory of secured contents.
Henry stayed near the wall display.
“The car was searched.”
“After the footage confirmed that Michael had left without it,” Daniels said. “Fully documented. Everything inside was photographed and classified.”
“Then we already saw the box.”
Daniels ended the call.
“We did.”
The file arrived minutes later.
The first images showed Michael’s locked car and its interior after controlled entry.
No signs of a struggle.
No keys.
No wallet.
In photograph forty-three, a medium cardboard shipping box sat behind the passenger seat.
Daniels enlarged it.
The package had already been opened. Two layers of clear tape crossed one side. The shipping label carried Michael’s name and Chesapeake’s address.
No readable sender.
Steve stepped closer.
“That’s it.”
Daniels did not look at him.
“Certain?”
“Yes.”
“How?”
“The tape. And the sticker at the top right.”
A small dark-blue star was attached to the cardboard.
Not a manufacturer’s logo.
Only a decorative sticker.
“Was that already there?” Daniels asked.
“Yes.”
Henry opened the inventory.
VEHICLE ITEM 07
Opened cardboard retail package.
Children’s electronic audio player.
Four programmable character tags.
USB charging cable.
Printed quick-start guide.
Decorative space-themed sticker sheet.
No immediate evidentiary significance.
Photographed in place and secured with vehicle contents.Daniels read the final line.
“No immediate evidentiary significance.”
“Why would it have been?” Henry said.
He did not sound defensive.
Only tired.
“Michael had a twelve-year-old daughter. Her birthday is in September. Technical gifts were normal for him.”
“Sarah knew nothing about it.”
“That would also be normal for a surprise.”
Steve pointed at the next photograph.
“There.”
The box had been opened on a clean evidence surface.
Inside lay a small cube-shaped audio player with rounded edges. Beside it were four flat character cards, a charging cable, and a folded guide.
The packaging contained several fitted recesses.
One for the player.
One for the cable.
Four narrow spaces for the cards.
And one small rectangular recess near the upper edge.
Empty.
Daniels enlarged it.
“What was there?”
“The dongle,” Steve said immediately.
“Certain?”
“Yes.”
“Was it secured?”
“In a small foam sleeve.”
“Which is also missing.”
“Yes.”
Henry looked at the inventory.
“No one could have known anything belonged there.”
The recess could have held any accessory.
An adapter.
Another cable.
A power plug.
Or packaging material that had never been supplied.
Daniels opened the detail photographs.
“Was the player powered on?”
“Not during the initial vehicle processing,” Henry said. “Electronic devices were documented externally first.”
A later controlled examination found no microphone, camera, cellular modem, or configured Wi-Fi. The four character cards contained simple programmable NFC tags. Three had been written; the fourth was blank.
Daniels opened the list of local assignments.
No complete audio files had been preserved in the report. Only labels, mappings, and modification times.
TAG 01 — SPACE ROCK
Modified: Thu Jul 30 2026 — 04:23 PM
TAG 02 — SYNTH ORBIT
Modified: Thu Jul 30 2026 — 04:25 PM
TAG 03 — ROBOT SONG
Modified: Thu Jul 30 2026 — 04:27 PM
TAG 04 — UNASSIGNEDSteve looked at them.
“Those are mine.”
“Your songs?” Daniels asked.
“My labels.”
“Why those three?”
Steve rubbed the back of his neck.
“Michael liked the first kind. The synth one would have made him laugh. And the robot song was silly enough for RoboDad.”
Henry looked at him.
For the first time since the interview began, his expression was not only anger.
Steve had not invented everything.
He had truly intended to prepare the gift.
He had actually thought about Emma.
And that was why someone had been able to use him.
Daniels opened the tag examination report.
The mappings existed, but two cards contained unusually long values the player could not match to music. They had originally been classified as damaged or incomplete programming.
“That was the problem,” Steve said. “The cards were recognized, but not connected properly.”
Henry read the identifiers.
“These are not normal audio-tag values.”
“Then what are they?”
“I don’t know yet.”
“Could they belong to the old protocol?” Daniels asked.
Henry shook his head.
“Not enough information. They could be corrupted tags or deliberately malformed values.”
“But the dongle was supposed to correct them.”
“Yes.”
Daniels looked again at the empty recess.
“And after Mr. Harper failed, he gave everything to Michael.”
Steve nodded.
“Friday morning.”
“Michael later took the box to his car.”
“Yes.”
“Then at approximately 1:30, he returned to the car.”
“That must have been it.”
Daniels looked at him.
“We still do not know why.”
“For the dongle.”
“Likely. Not confirmed.”
Steve lowered his eyes.
Henry reopened Brenda’s footage.
Michael left the building.
Empty-handed.
A few minutes later, he returned.
A small object was in one hand.
The image quality was insufficient for identification.
But the size fit.
“The box stayed in the car,” Henry said.
Daniels arranged the vehicle photograph, the packaging image, and Brenda’s footage side by side.
“And the dongle came back inside.”
Steve studied the three images.
“He must have known something was wrong with it.”
“Maybe,” Daniels said.
“Why else would he take only the adapter?”
Henry answered.
“Because the box was not the problem.”
In the first photograph, the package looked ordinary.
A gift for a child.
In the second, only a small recess was empty.
In the third, Michael carried something back toward his workstation that no one could identify.
Police had possessed the gift for days.
They had photographed it.
Inventoried it.
Secured it.
The box had never been hidden.
Only the relationship.
Daniels pointed at the empty recess.
“The man in the parking lot did not need to smuggle something suspicious into the building.”
He pointed at Steve.
“He gave you a birthday present.”
At Michael in the footage.
“You gave it to Michael.”
Then at the missing space in the packaging.
“And Michael brought back only the part no one would mistake for a gift.”
The final attribution arrived early that afternoon.
Daniels had not released Steve.
He sat in another conference room, his phone temporarily secured, while investigators completed his statement and tried to follow the parking-lot man through additional cameras.
Henry remained in front of the forensic image of Michael’s workstation.
On the second screen was the file recovered from Emma’s ThinkPad.
A computer can forget. Two machines have to agree.Navarro joined by secure connection. Beside her was the analyst who had confirmed the dongle’s second interface.
“Start with the connection,” Daniels said.
The normalized sequence appeared on Henry’s screen.
LOCAL LOGIN — 13:41:26
USB DEVICE CONNECTED
MASS STORAGE INTERFACE REGISTERED
VENDOR-SPECIFIC SERIAL INTERFACE REGISTERED“Up to this point, everything could have happened automatically,” Daniels said.
“Yes,” the analyst replied. “Then the serial interface remained unused for eleven seconds. The dongle did not open the Chesapeake path on insertion.”
The analyst continued the timeline.
SERIAL DEVICE CREATED
11-SECOND IDLE PERIOD
LOCAL PROCESS STARTED FROM TTY1 SESSIONHenry read the last line twice.
“From the console. Not udev, not an autostart service.”
“Correct.”
“Then someone had to do something,” Daniels said.
“Can we say who?”
Henry did not answer at once.
“We can say the process was started from the same local session opened at 1:41:26 under m.weber.”
“Not which person used the keyboard.”
“Correct.”
Steve’s statement continued to make Michael overwhelmingly likely.
But overwhelmingly likely was not identical to technically proven.
Daniels nodded.
“What was launched?”
A path from the dongle’s storage volume appeared.
/media/mweber/TAG_SERVICE/tools/linkdiagHenry frowned.
“linkdiag.”
“A small Linux binary,” the analyst said. “No graphical interface. No installation. Executed directly from the device.”
“Signed?”
“No.”
“Reliable manufacturer metadata?”
“None.”
“What did it do?”
“The first invocation only enumerated local devices.”
The reconstructed command appeared.
linkdiag --listDaniels looked at Henry.
“He asked it to show what was connected.”
“Yes.”
“That could still be a normal inspection of a supposed gift adapter.”
“Yes.”
A second process followed nine seconds later.
linkdiag --inspect /dev/ttyUSB0The output was not fully preserved.
Parts of it were recovered from memory and temporary terminal artifacts.
INTERFACE TYPE: LEGACY SERIAL BRIDGE
REMOTE PROFILE: CM
LOCAL LINE PRESENT
CONTROLLER RESPONSE DETECTEDThe room went silent.
Henry pointed at the second line.
“Remote profile CM.”
“Yes.”
“That would have reminded him of C.M.T.A.”
Daniels corrected him immediately.
“Or something else with the same initials.”
“Together with a legacy serial line inside this building?”
“C.M.T.A. is highly likely,” Daniels said. “Not more than that.”
Henry nodded.
The next action had not been generated automatically.
Twenty-seven seconds passed between the inspection and the following command.
Time to read the output.
Time to think.
Time to stop.
Then linkdiag was launched a third time.
With additional arguments.
linkdiag --probe /dev/ttyUSB0 --profile CM-047 --no-actionDaniels leaned forward.
“No action.”
“A connection-only probe,” Henry said.
“What does that mean?”
“The command requested no switching operation, no configuration change, and no data transfer beyond the handshake.”
“He only wanted to know whether the other end answered.”
“Yes.”
The analyst paused.
“There is more.”
The reconstructed invocation contained an additional parameter that had initially been treated as a short hexadecimal value.
--note 54574FDaniels looked at Henry.
“Meaning?”
“Hexadecimal.”
Henry wrote the three byte pairs on a sheet and converted them.
54 57 4F
T W ODaniels looked at the word.
“Two.”
Henry turned to the second display.
Two machines have to agree.No one spoke.
The laptop file and the workstation parameter had been created two weeks apart.
The same word.
“Was that parameter technically necessary?” Daniels asked.
“No,” the analyst said.
“Did it affect the probe?”
“Not according to the recovered function. It was accepted as a short optional note in the local diagnostic transaction.”
“Was it transmitted to C.M.T.A.?”
“We cannot confirm that.”
Henry slowly shook his head.
“It didn’t need to be.”
Daniels looked at him.
Henry pointed at the command.
“Michael only needed us to recognize later that he had initiated the event deliberately.”
“If we found the file on Emma’s laptop.”
“And reconstructed the process.”
Daniels looked again at the timeline.
“That is a great deal of trust in a later investigation.”
“No.”
Henry indicated Michael’s sentence.
“It is distrust of any single piece of evidence.”
Navarro spoke from Sarah’s apartment.
“That fits roboping.sh.”
“How?” Daniels asked.
“The message itself contains no location and no technical proof. It only ensures Emma has the laptop examined.”
“And the file tells us what to look for.”
“Not specifically,” Navarro said. “But it tells us there must be a second system that confirms the same event.”
Henry looked between Emma’s T480, Michael’s workstation, and the paper recorder many miles west.
Three machines.
Only two had to witness the same transaction.
The analyst placed the final portion of the reconstruction on screen.
PROBE INITIATED
LOCAL CONTROLLER SESSION OPENED
OUTBOUND TRANSACTION CREATED
SEQUENCE ASSIGNED: 00417
SERIAL SESSION CLOSEDDaniels pointed at the last line.
“Controlled close. No crash or interruption.”
“Correct. The storage volume was unmounted and the device disconnected seconds later.”
“He safely ejected it,” Henry said.
“A person who had accidentally triggered an unknown system probably would not begin by cleanly unmounting the storage volume.”
“That is an interpretation,” Daniels said.
“A strong one.”
Daniels did not disagree.
The local session started no second probe.
Requested no configuration.
Retrieved no data list.
Triggered no door function.
Created no further sequence.
Only one connection record.
00417The Chesapeake controller had retained it as the last outbound number.
The C.M.T.A. recorder had printed it on paper.
And the local invocation included TWO.
Daniels went to the board and wrote beneath the confirmed chain:
INTENTIONAL PROBE
NO ACTION REQUESTEDBelow that:
NOTE: TWOHenry studied the words.
“He knew by that point that the dongle connected to the old system.”
“Yes.”
“And he wanted someone to prove it later.”
“Very likely.”
“That is all you’ll give me?”
“Not while we still cannot prove Michael himself was at the keyboard.”
Henry looked at the time.
Steve had seen Michael at the workstation.
Michael had retrieved the dongle from the car.
Michael had said:
Just checking something quickly.
Minutes later, he had walked toward the archive area.
“Then let’s say it correctly,” Henry said.
Daniels waited.
“The person at Michael’s console recognized the legacy connection, deliberately performed a no-action probe, requested nothing further, and left the word TWO.”
“Yes.”
“And before Day Zero, Michael had prepared a message on Emma’s laptop explaining why two machines mattered.”
Daniels placed the marker down.
“Yes.”
Henry looked toward the door.
“That was Michael.”
This time Daniels did not answer with a limitation.
He wrote only:
MICHAEL WEBER — STRONGLY SUPPORTEDNot proven beyond doubt.
But no longer an unsupported assumption.
Daniels called Navarro again.
“Is Emma still with you?”
“Yes.”
“I don’t want her hearing every technical detail before we speak to Sarah.”
From the background, Emma said:
“I can hear you.”
Navarro said nothing.
Daniels closed his eyes for a moment.
“Of course you can.”
“Did Dad make the printout?”
Daniels looked at Henry.
Then at the matching sequence numbers.
“We believe your father deliberately tested a connection.”
“So the number would be printed.”
“Very likely.”
“And TWO?”
“Someone entered that into the command.”
“Dad.”
Daniels answered carefully.
“Everything now points that way.”
Emma was quiet for several seconds.
When she spoke again, she did not sound relieved.
Only more certain.
“Then he knew someone could delete things.”
Henry stepped closer to the phone.
“Yes.”
“But not paper.”
“Not as easily.”
Emma exhaled.
“That’s why Grissom.”
“What do you mean?” Daniels asked.
“Dad left something wrong on my laptop so I would find it.”
She paused.
“And something right on the other machine so you could prove it.”
No one corrected her.
Daniels ended the call only after promising Sarah he would come by again that evening.
Afterward, Henry remained alone with him in the conference room.
On the first screen was the process invocation.
--probe
--profile CM-047
--no-action
--note 54574FOn the second was Michael’s sentence.
A computer can forget. Two machines have to agree.Henry thought about the eleven seconds after the device connected.
The twenty-seven seconds before the final command.
Michael had not panicked.
He had examined the device.
Recognized the connection.
Made a decision.
And generated one transaction that would remain in two places.
Then he had removed the dongle and walked toward the archive room.
What he searched for there, what the man in the Yukon later said, and whether Michael knew someone was coming all remained unknown.
But 00417 was no longer an accident.
Michael had not sent a message to C.M.T.A.
He had left one there.