Or were they attempting to create a dangerous incident that would justify emergency control over the reservoir?
The sheriff had no intention of treating speculation as fact.
But she also knew that the city could not afford to ignore the possibility that the operation involved critical infrastructure.
She instructed the utility to review all recent contractor access, preserve monitoring records, and secure the facilities under its control.
Then she made another call.
This one was to the county prosecutor.
"We need an emergency legal review of the Northstar contract, the access orders, and the missing engineer's allegations."
The prosecutor answered with a tired voice.
"I've been reviewing the documents for the past hour. The contract contains several unusual provisions, including a clause allowing Northstar to assume temporary control of certain facilities under a declared emergency."
"Who approved it?"
"The mayor signed the order. The council authorized the underlying contract, but the emergency provision was added later through an administrative amendment."
"Was the amendment properly reviewed?"
"That's what we're trying to determine."
The sheriff looked at the photograph of Maria.
"Someone is moving witnesses while we search buildings. I need the legal process to move as quickly as it can without compromising the case."
"I understand. I'm contacting the state attorney general's office."
The sheriff ended the call.
Outside the operations center, rain began falling.
It was a thin, cold rain that made the streets shine beneath the lights.
The city seemed ordinary.
Cars passed.
Traffic signals changed.
A late-night delivery truck turned toward the commercial district.
Thousands of residents slept in their homes, unaware that people inside the municipal administration might have approved an arrangement that could transfer control of critical infrastructure during an emergency.
If Project Lantern was what Hargrove claimed, the city had been preparing to surrender control of its own systems to the very company whose records were under suspicion.
The question was no longer whether the scandal could damage the mayor's reputation.
It was whether the city had been placed in danger to protect a contract.
At 1:17 a.m., Riker received a call from Moose.
"We've got a problem."
Riker stood from the desk.
"What happened?"
"Somebody is circulating a new video."
"Of what?"
"The motorcycles."
Riker opened the link Moose sent.
The video showed a long line of motorcycles moving along a highway in darkness.
The camera followed them from a car traveling behind the group. The riders' headlights stretched into the distance, creating the impression of a massive procession heading toward the city.
A voice-over claimed that hundreds of members of the Steel Saw organization were assembling for a coordinated attack on municipal infrastructure.
The footage was real.
The caption was false.
The motorcycles had been traveling toward a charity gathering earlier that year, long before the current events. The video had been edited to remove the original context and combined with footage of emergency vehicles near the reservoir.
The result looked convincing enough to frighten anyone who did not know the truth.
Riker watched it twice.
"Who posted it?"
"An account that was created this afternoon. The first shares came from people connected to a local political discussion group."
"Can we establish who runs the account?"
"Not yet."
"Then don't guess."
Moose sighed.
"You're going to say that every time I call you tonight, aren't you?"
"Probably."
Moose lowered his voice.
"People are angry. A few riders want to head toward the reservoir just to prove we aren't afraid."
"Tell them that proving you're not afraid by doing exactly what the other side wants is not courage."
"I've already told them."
"Tell them again."
Moose paused.
"There's another issue. Some members have family working at the municipal utility. They're worried that something is actually happening at the pumping station."
"That's a legitimate concern. They can contact their family members directly, but nobody should enter restricted areas or interfere with the utility's work."
"Understood."
Riker looked at the video again.
The editing was sophisticated enough to suggest someone had spent time preparing the material. The creator had selected footage that would produce the strongest emotional response and removed the context that would weaken the accusation.
It was a manufactured threat.
And it was spreading while law enforcement was still trying to establish what had happened.
Riker called Sheriff Brooks and informed her about the video.
She responded with restrained anger.
"We're documenting it. Our communications office will issue a factual statement once we can confirm the relevant details."
"Do you want me to make a statement?"
"Not yet. If you post something while the investigation is active, it may be used to suggest that the club is coordinating a response."
"What do you recommend?"
"Keep your members away from the restricted areas. Preserve the video and its original link. Do not contact the account owner. Let us investigate."
Riker agreed.
When the call ended, he walked into the main room.
Nearly fifty riders were still present.
Some sat at tables, talking quietly. Others stood near the windows, watching the rain.
Riker raised his voice.
"The video circulating online is old footage presented out of context. The sheriff has been informed. We are not going to respond with our own spectacle, and nobody is going to the reservoir."
A rider near the doorway spoke up.
"What if people believe the video?"
"Some will."
"Then shouldn't we defend ourselves?"
"We defend ourselves by preserving the truth, not by giving them new footage to misrepresent."
The rider looked dissatisfied.
Riker continued.
"If the authorities ask for evidence, we provide it. If they ask for a statement, we cooperate. If someone threatens us, we report it. We do not turn an investigation into a street confrontation because an anonymous account wants us to lose our discipline."
He looked around the room.
"Anybody who cannot follow that instruction should leave the property and stay away from the situation."
No one moved.
Walter Briggs stood beside a table.
"You heard him. We're not going anywhere."
The others nodded.
The club had reached a decision.
They would not be baited into creating the image their enemies wanted.
But Riker knew that the night was not over.
The people behind Project Lantern had already demonstrated that they could manipulate public opinion, interfere with monitoring systems, and move witnesses before investigators arrived.
If they were prepared to sacrifice their own cover to provoke a confrontation, they might be willing to do something far more dangerous.
At 1:43 a.m., the digital forensics unit reported that the device recovered from Leo's shoe contained encrypted data.
The initial examination revealed a small amount of readable metadata, including a date, a device identifier, and a reference to an archive stored on an external server.
The data did not immediately reveal the contents of the archive.
The specialist cautioned that the device might be an authentication token rather than a conventional storage drive. Its purpose could not be established conclusively without further examination.
But one item stood out.
The metadata included the initials D.H.
Daniel Hargrove.
A second field contained the phrase:
LANTERN / ROOT CERTIFICATE.
The technician explained that a root certificate could be used to establish trust between systems, but the exact meaning depended on the architecture of the archive.
The device might authenticate records created by Hargrove's engineering office.
It might verify the integrity of a collection of files.
Or it might serve as one component in a larger security system.
The investigators could not yet say.
Sheriff Brooks sent the preliminary findings to the prosecutor and asked the utility to identify the archive's technical structure.
At 1:56 a.m., the utility located a reference to an external repository in a maintenance record from two years earlier.
The repository had been established to preserve engineering documentation during a municipal software migration.
It contained inspection reports, design specifications, contractor invoices, equipment serial numbers, and signed approvals.