Chapter 14 - The Rest Script
Sloan Logistics did not design the entire electronic logging system.
They built an integration tool.
Purpose:
Synchronize dispatch schedules with driver duty records.
Legitimate.
Then someone added a feature internally called:
REST PROJECTOR.
It estimated when a driver would become legal based on scheduled rest.
Nothing wrong with prediction.
Problem:
Arrow Ridge dispatch interface sometimes displayed projected eligibility as if it were current status.
Red became green before rest completed.
Drivers could still see actual ELD data.
Supervisors saw simplified dashboard.
Did this violate law by itself?
Not necessarily.
But if dispatch relied on projected status, fatigued drivers could be assigned early.
Then manual override turned projection into active route clearance.
Travis’s Sunday status:
Actual rest: four hours.
Projected by departure: eight hours.
He left before eight.
Dashboard showed green because Kenneth overrode.
That explained system confusion.
Who approved REST PROJECTOR?
Brandon Sloan.
As product manager at Sloan Logistics.
He insisted it was never intended as legal certification.
Emails supported him.
Brandon to Kenneth:
Do not use projected status for dispatch clearance. It is planning only.
Kenneth:
Then why show green?
Brandon:
Because green means projected available, not legal now.
Kenneth:
Drivers understand.
They did not.
Then Brandon later proposed changing colors.
Kenneth delayed.
Why?
Operations liked quick planning.
Again.
Design ambiguity plus pressure.
Did Brandon knowingly cause Travis’s route?
He viewed it Sunday.
Saw red alert.
Texted Dad.
His father told him fixed.
He did not intervene.
Responsibility.
But not conspiracy.
Then the foundation’s technical consultant found something worse.
Travis’s dashboard screenshot preserved at 5:30 Monday.
Green.
Label:
AVAILABLE.
Actual ELD:
NOT LEGAL UNTIL 9:58.
Crash 8:22.
The interface had hidden the truth from dispatcher’s main screen.
Arrow Ridge still had raw data.
Bennett audit still had raw data.
Everyone had enough information somewhere.
No one forced the systems to agree.
Then Melissa’s role in Sloan Logistics release agreement.
The family release included them because Brandon feared software liability.
Was Melissa trying to protect fiancé more than Dad?
Both.
Then her engagement collapsed.
Not because I told her to leave.
Brandon postponed wedding after investigations.
Melissa blamed me initially.
Then she read his product emails and realized he had warned his father.
That changed her view.
“You think he is innocent?”
I said:
“I think he did some things right and some things wrong.”
She hated that answer.
Then:
“Do you still love him?”
“Yes.”
“Then decide based on truth, not whether I approve.”
She stared.
“Why are you helping me?”
“I’m not.”
Good.
Then Kenneth Sloan finally agreed to sworn deposition in preserved third party claims.
He admitted manual override under his admin credentials.
Claimed assistant actually clicked.
Who?
Night operations manager Kelly Monroe.
Kelly denied.
System authentication used Kenneth’s phone approval token at 10:12.
His phone.
Face ID.
Could assistant use?
Hard.
He stopped denying personal override.
Why?
“Because Reed had a customer critical load.”
“Did you know his rest was incomplete?”
“I believed it would be complete before departure.”
“Did you check?”
“No.”
“Did Richard warn you?”
“Yes.”
“Why ignore?”
“Because his firm had already certified us.”
That sentence brought everything full circle.
Dad’s clean report became shield against Dad’s own later warning.
Then:
“Did Diane’s call matter?”
“It reassured dispatch.”
“Was she qualified?”
“No.”
“Why ask anyone at Bennett?”
“I needed confirmation.”
“You needed cover.”
Kenneth’s lawyer objected.
Fair.
Then Mara asked:
“Did you know Ethan Miller was examining Arrow Ridge?”
“Yes.”
“When?”
“Before crash.”
“Did that affect Travis’s assignment?”
“No.”
“Any evidence Ethan was targeted?”
“No.”
“Did you know he would be on Interstate 95?”
“No.”
That mattered.
No murder plot.
No engineered collision.
Just risk.
Then:
“Why meet Richard at Melissa’s birthday during funeral?”
Kenneth looked ashamed for the first time.
“Because Charles Voss told us we needed a joint preservation plan.”
“Could you not meet after funeral?”
“Yes.”
“Why didn’t you?”
No answer.
Then:
“Did you tell Richard not to attend funeral?”
“No.”
Dad chose that.
My father owned that cruelty alone.
Then Andrew received a new preservation package from Arrow Ridge’s former IT director.
A server image from Sunday night.
REST PROJECTOR source code.
One hidden admin feature:
FORCE AVAILABLE.
Developer initials:
BS.
Brandon Sloan.
He had told us the system could only project.
May you like
He personally coded a force function.
Continue to the next part: Brandon claimed his software could only predict driver availability, but recovered source code shows he personally created a hidden “FORCE AVAILABLE” command used inside Arrow Ridge’s dispatch system.
