Chapter 6 - Julian’s Phone Approved the Login
Julian denied it.
Immediately.
“I never approved Cassandra accessing lab controls.”
“The token came from your phone.”
“I approve twenty authentication requests a day.”
“That’s your defense?”
“No. I’m telling you what happened.”
His explanation was plausible.
Our security architecture was badly designed for convenience.
Executive authentication prompts often contained limited detail.
Approve access.
Device name.
Time.
If Julian was busy, he tapped yes.
I knew because I had complained about it.
Cassandra knew too.
The log showed her laptop requested elevated access at 11:43 p.m.
Julian approved twenty-two seconds later.
I asked where he was.
“Home.”
“With me?”
“No.”
That night I had slept at the lab.
Final stability cycle.
Julian had gone to a charity dinner.
Cassandra attended too.
“When did you leave?”
“Around eleven.”
“Together?”
He hesitated.
“Yes.”
There it was.
They went to Cassandra’s apartment.
At 11:43 p.m., her laptop requested elevated access.
Julian’s phone approved it.
“What were you doing?”
Silence.
I didn’t need details.
He wasn’t looking at the screen carefully.
Cassandra may have taken advantage of that.
Or he may have known.
I needed evidence.
Then the logs showed something else.
The safety interlock was re-enabled twelve minutes later.
That confused everyone.
If Cassandra intended to cause an explosion the next afternoon, why disable the system briefly and then restore it?
The answer came from our engineers.
She wasn’t necessarily sabotaging it yet.
She was testing whether she could control it remotely.
That was worse in one way.
More deliberate.
The actual explosion occurred seventeen hours later.
The interlock was disabled again.
This time no executive token request appeared.
Because Cassandra had created a persistent administrator session during the first access.
She no longer needed Julian’s approval.
The chain was clear.
Julian opened the door once.
Cassandra left it unlocked.
But intent remained unclear.
Our outside investigator asked the obvious question.
“Could she have disabled it for legitimate testing?”
Technically, yes.
Cassandra was not a scientist, but executives sometimes participated in security demonstrations.
No record showed one scheduled.
Then an email surfaced.
Cassandra to our operations director:
Do not run remote safety-maintenance testing this week. Elena is finishing the final cycle and cannot be disturbed.
Two days before she secretly accessed the system.
She had explicitly canceled legitimate testing.
Then performed her own.
That looked terrible.
But still:
Why?
Was she trying to kill me?
Or only create a lab failure dramatic enough to remove me from control?
The answer began to emerge from a private investor deck found on Cassandra’s cloud drive.
Slide title:
Founder Transition Scenario.
Under it:
Temporary incapacity creates cleanest governance path.
No death.
No murder.
Incapacity.
Cassandra had been planning for me to survive.
Just not remain powerful.
Then one bullet point:
Aurum delay after technical incident could justify emergency IP consolidation.
She intended an incident.
Not necessarily an explosion this large.
That distinction would become central.
Then another note appeared in the margin.
J says she always overrides alarms manually when she thinks they’re too sensitive.
J.
Julian.
I turned toward my husband.
May you like
He had told Cassandra exactly how I behaved during lab runs.
And she built her plan around it.
