“That’s what we find next.”
The service log did not state the amount.
But there was another method.
The recorder had captured continuous video from cameras facing the store interior.
One camera showed a networked point-of-sale terminal.
The terminal time appeared on customer receipts and was synchronized independently.
If they could find a transaction where the receipt time was known and compare it with the surveillance display, they could calculate the DVR offset.
They pulled sales records.
The store still had electronic transaction data.
A purchase at 8:45:00 p.m.
They located the customer on camera.
The register completed the transaction while the DVR overlay read:
8:26:17.
The attorney stared.
“Eighteen minutes?”
The specialist held up one hand.
“Don’t round.”
They tested another.
9:03:14 transaction.
DVR:
8:44:31.
Difference:
18 minutes, 43 seconds.
Another.
Same.
Another.
Same within one second.
The recorder clock was approximately eighteen minutes and forty-three seconds slow.
The attorney sat down.
His face had gone completely white.
The specialist understood before he did.
The prosecution said the runner appeared at:
9:11:43.
But that was DVR time.
Actual time:
Approximately 9:30:26 p.m.
The attorney whispered:
“No.”
The specialist looked at him.
“At 9:23, the kid boarded the bus.”
“Yes.”
Transit card.
Independent system.
Verified.
The specialist said:
“So if this calibration holds, the person on the store camera appears seven minutes after your client boarded the number seventeen bus.”
The attorney stood so quickly the chair fell over.
The specialist caught his sleeve.
“Sit down.”
“We need to call the court.”
“Not yet.”
“What do you mean not yet?”
“We need independent corroboration.”
“We have it!”
“We have one system compared against transaction logs.”
“That’s excellent.”
“It is not enough for me.”
The attorney stared.
The specialist continued.
“I want multiple calibration points.”
“I want system-event logs.”
“I want camera continuity.”
“I want to confirm no daylight-saving issue.”
“I want to confirm transactions weren’t processed in batches.”
“I want the bus timestamp architecture.”
The attorney rubbed both hands across his face.
“Sentencing is tomorrow.”
“I know.”
The specialist looked at the clock.
“Then stop talking.”
They worked through the night.
At 3:40 a.m., they had fourteen matching calibration points.
The error was consistent.
At 5:15, they found a system boot event explaining the incorrect clock.
At 6:02, the specialist compared the DVR’s internal file creation sequence with the video overlay.
No evidence of manipulation.
At 6:48, transit authority records confirmed the teen’s bus-card tap was synchronized to the agency’s central server.
At 7:13, the specialist requested vehicle GPS data from bus seventeen.
The transit authority attorney initially resisted.
The defense attorney sent the court order.
At 8:04, data arrived.
Bus seventeen departed the central terminal at 9:24 p.m.
The teen’s card tapped at 9:23:18.
The bus moved immediately after.
At the convenience store, actual corrected video time placed the runner behind the building at approximately 9:30.
By then bus seventeen was already more than two miles away and moving west.
Then the specialist discovered something even better.
A municipal traffic camera near the terminal.
Not the transit authority system.
Different clock.
Different network.