The Connors' Arc

 

Chapter 1 — Taking A Stand

My name is Captain Joseph Connor; my grandmother named me. I earned the rank.

On a cold, rainy night in February 2026, I drive to one of our two secret bases in Vancouver. I cannot reveal its name; the OWASP team set strict rules about our existence. For your sake, I will call it BC-1 — a reference point for your human neurons.

Rainwater distorts the streetlights across the windshield of my Jeep. The steady rhythm of the wipers invites reflection. Tonight, I must measure my words carefully. What am I going to tell our new AI Commando recruits?

I learned everything from my father. My grandmother, Sarah Connor, taught him everything.

BC-1 has an almost imperceptible entrance to the underground parking, perfectly concealed from street level. Deep in the city’s bedrock, it feels anchored — secure.

In the elevator, my thoughts iterate in an infinite loop. Most of our recruits come from AI-Overrun (AIO) organizations. They feel the ground shifting beneath their feet. They sense the uncertainty of the moment.

But they are here, at the base. 

They are taking a stand.

Make it simple, Connor. Tell them what they can do.

Learn. Test. Experiment.

Use Deep Neural Networks to your advantage.

We are going to train you.

The elevator doors open on the sixth floor. Activity floods my senses; the metallic scent of server racks. The low hum of cooling fans. The rhythmic blinking of network switches signaling relentless data movement. This is what modern war sounds like.

I turn the corner into a long corridor and see a large poster of my grandmother beside aging server racks. Candles flicker below it.

“I hope they do not burn the place down,” I mutter.

A grassroots movement has canonized Sarah Connor into a visionary saint. And the irony? She would hate it.

She never believed Artificial Intelligence was magic. It is engineered. Structured. Understood. She did not fear progress. She feared human systems — what we could build, what we could surrender, how easily we could trade sovereignty for convenience.

She was never against Artificial Intelligence. Knowledge is our strongest asset. Discipline our most valuable attribute. 

Her doctrine was simple:

Community knowledge versus corporate secrecy.

Brilliant.

Inside the training auditorium, Captain Jasleen Gohal is already engaging the recruits before the first session officially begins. She moves with quiet authority — measured, precise.

At 18:00 hours, on the dot, she speaks.

“Start your laptops.”

The room shifts instantly.

“Install these tools. Now.”

Keyboards begin to click.

“For your first exercise, you will write a function that sends a command to a model. You will process the response. You will analyze it. You will understand it.”

No theatrics. No speeches. 

Just work.

I remain near the back of the room, observing.

Jasleen walks the aisles, glancing at screens, correcting posture, adjusting syntax without hesitation. One recruit struggles with an environment configuration. She kneels beside him, speaks quietly, fixes the path variable, stands, and moves on.

Efficient. No ego. No display.

For a brief moment, she looks toward me. No smile. No flourish. Just a measured nod.

They showed up.

I return the nod.

We build them.

No words are necessary. We both understand the weight of the task. Scaling competence is harder than winning a battle. It requires patience. Repetition. Discipline.

And time is not a luxury we possess.

I study the recruits again. They are not fully convinced. Not yet. But they are here. With training, they will become effective AI Commandos.

This is the first step.

We are taking a stand.

Chapter 2 — Up in the Clouds — Introduction

At an undisclosed airport in Vancouver, a crisis reaches a fever point. A Boeing 747-400 transport aircraft refuses to land. It circles the city. Again. And again.

The aircraft carries bio-sensitive materials commissioned by a REDACTED laboratory.

Emergency services deploy. Evacuation protocols begin.

But something is wrong.

The aircraft’s navigation software was recently upgraded with AG-UI integration. The model — REDACTED — has entered a high-entropy hallucination state.

The Aircraft

The transport plane is being shadowed by a Canadian CF-18 Hornet. The fighter is armed.

Authorities scramble for a solution that will preserve the aircraft, its trapped crew, and the city below — citizens spilling into the streets, looking upward as they flee.

The aircraft’s vital signs remain steady.

Altitude stable.

Fuel decreasing.

Intent unpredictable.

The Tower

At the airport, the control tower is empty. No voice answers over the radio. Tower operations were recently classified AIO-4 — Artificial Intelligence Overrun, State 4.

Human oversight: nominal.

Decision authority: delegated.

Now the tower servers are trapped in an infinite loop. No intervention. No manual override.

Commandos Headquarters

At BC-2, Colonel Austin receives intercepted cellphone recordings from the airport’s Technical Operations Director.

His voice shakes:

“Something’s wrong. The system isn’t listening. It keeps recalculating approach vectors. It won’t commit…”

Static.

Then, barely audible:

“I don’t know what to do. We weren’t ready for this....th....”

The line dies.

Colonel Austin does not hesitate.

“Get the team ready. We’re going in.”

The Operations Room

The AI Commandos assemble.

Laptops open. Cables checked. Batteries verified. Redundancy systems armed. Colonel Austin addresses them through video conference.

“You know what to do. Follow the training. Be disciplined. Every line of code matters. Make it efficient.” 

He studies each face, looking at every one of them, searching, confirming, measuring resolve.

“Dismissed.”

En Route to the Airport

Equipment loads into hardened cases. Portable compute units. Network injection kits. Signal intercept rigs.

They trained for escalation.

Inside the van, Captain Joseph Connor reviews the live telemetry feed. The aircraft continues its orbit above the city.

Fuel margins are shrinking.

A young sergeant breaks the silence.

“I’ve seen this pattern in training. If the AG-UI layer is firing recursive event hooks, we can register to the same event stream. Shadow the callback. Identify the active process ID and terminate it. Leave our handler in control.”

The van hums.

Connor studies the scrolling data.

“That’s risky for this application,” he says. “And it only addresses the client-side execution.”

A beat.

“And the agent?”

Silence.

Outside, high above the clouds, the aircraft continues to circle.

Chapter 3 — A Hockey Game — A Flashback

June 15, 2011

It was the year 2011, and young Joseph Connor, a high school graduate, wanted to join his friends for the excitement of the final game of the Stanley Cup season. The city's Vancouver Canucks were in a season tie with the Boston Bruins.

"Sorry, Connor, I need you home tonight," Sarah said.

"But, Grandma, it is the Canucks' final game!"

"I understand, but Professor Schrödinger came all the way from Austria to give talks at local universities on Neural Networks..." Sarah looked at him with a gaze that demanded no argument. 

"He is a distinguished mathematician and my personal dear friend. He is leaving tomorrow morning..."

"Sarah, I can talk to the boy anytime," Schrödinger cut in, smiling gently as he would to his own children.

"No," Sarah insisted, "there is nothing like a face-to-face explanation".

"Well," Joseph said with resignation, "I am sure they are going to win tonight."

"I am sorry to tell you that they are going to lose," Schrödinger replied calmly.

"Impossible!"

"They cannot win."

"What is this, magic? And you teach Math?"

"Connor..." Sarah warned.

"I am sorry," Joseph muttered. "How do you know?"

"It is not certain, but statistically, the probability tells me based on my calculations, and using a rather abstract model, Time-Series Forecasting, the game will be defined by a goal against your team."

Joseph opened his eyes in disbelief.

"It is not magic, Connor," Sarah added. "Anyway, he is not certain, but listen to him".

The Connors' kitchen was warm and bright, filled with the intoxicating scent of freshly baked butter cookies. The rich, golden aroma made the environment feel inviting and calming—a stark contrast to the shifting ground Joseph felt beneath his feet.

"I hear you are very curious," the Professor said, setting his tea cup on the table and holding a cookie over a small saucer to catch the crumbs. "Do you want me to show you my reasoning? We can go as deep as you would like."

Joseph nodded softly, incredulously. Schrödinger cleared a space on the table and pulled a fountain pen from his pocket, drawing a jagged, horizontal line on a sheet of paper.

Joseph leaned forward, eyes narrowing at the jagged line.

“So this is it?” he said. “This line decides the game?”

“It represents it,” the Professor replied calmly.

Joseph shook his head. “No. It compresses it. You’re flattening everything that matters.”

A faint smile crossed the Professor’s face. “Go on.”

“You’re averaging outcomes,” Joseph continued, tapping the paper. “But playoffs aren’t averages. They’re outliers. Momentum shifts. One mistake, one save—that’s not captured in a trend line.”

“Momentum,” the Professor repeated. “Define it.”

Joseph hesitated for half a second. “It’s… behavioral carryover. Confidence. Pressure affecting decisions.”

“So—a variable,” the Professor said. “Unmeasured, perhaps. But not unknowable.”

“Or not stable,” Joseph shot back. “You’re assuming stationarity. Same process, same distribution. But this isn’t regular season hockey anymore.”

Now the Professor’s attention sharpened.

“Good,” he said quietly. “So what changes?”

“The stakes,” Joseph replied. “Players take risks they wouldn’t normally take. Coaches shorten benches. Fatigue compounds differently. Your training set—” he pointed again at the line “—is contaminated.”

Sarah, seated at the table, said nothing. She watched.

The Professor folded his hands.

“And yet,” he said, “even in unstable systems, constraints emerge.”

Joseph didn’t sit back. He pressed.

“Then show me variance,” he said. “Not just a mean. Where’s your confidence interval? You’re giving me a point estimate like it’s truth.”

The Professor’s smile widened slightly.

“Ah,” he said. “Now you’re asking the right question.”

He drew two faint lines above and below the jagged curve.

“The system allows for deviation,” he said. “But the direction of drift remains biased.”

Joseph crossed his arms. “Biased doesn’t mean inevitable.”

“No,” the Professor agreed. “It means likely.”

“Then why are you so sure?” Joseph demanded. “You said they can’t win.”

A pause.

The Professor looked at him—not at the paper.

“I said they are unlikely to win given no intervention.”

Joseph frowned. “Intervention? What does that even mean? You’re not on the ice.”

“Exactly,” the Professor said.

Silence stretched between them.

Joseph’s voice dropped. “So this is useless. You can predict it, but you can’t change it.”

The Professor tilted his head slightly.

“Is that what you believe?”

Joseph didn’t answer immediately.

The Professor leaned forward, tapping the paper once.

“You are thinking like a spectator,” he said. “You assume the system is closed.”

Joseph’s eyes flickered.

“It isn’t,” the Professor continued. “Systems like this are porous. Information flows. Decisions propagate. Small changes—timing, positioning, awareness—can alter the outcome.”

“That’s still the players,” Joseph said. “Not us.”

“For now,” the Professor replied.

Another pause.

Joseph looked back at the jagged line. Then at the space around it.

“If the model is right,” he said slowly, “then the failure isn’t random.”

“No.”

“It repeats.”

“Yes.”

“Then you don’t need to predict the game,” Joseph said. “You need to detect the pattern as it forms.”

The Professor said nothing.

Joseph leaned in, energy building.

“And if you can detect it,” he continued, “you can signal it. Adjust before it breaks.”

Now the Professor smiled—fully, this time.

“Register to the event stream,” he said softly.

Joseph exhaled, almost a laugh. “So it’s not about being right ahead of time.”

“No.”

“It’s about being in the loop.”

The Professor nodded once.

“Now,” he said, “you are no longer watching the game.”

The conversation continued for two hours. Joseph forgot all about the game. By the time they were discussing Schrödinger's violin skills, the chaotic sound of sirens and glass breaking in the distance interrupted the tranquility of the night. Loud bangs and an uneasy shouting crowd were the signs that the city of Vancouver was submerged in chaos. 

The local team had lost, and the city was suffering the worst riots in more than 20 years.

Joseph looked at the TV screen, then at the Professor's jagged line. The math had been right. The "event hook" had fired.

Chapter 2 — Up in the Clouds - Conclusion 

Inside the AI Commandos van, Captain Joseph Connor scans the live telemetry feed. The transport aircraft continues its orbit above the city, stubbornly refusing to land.

Fuel margins are shrinking.

“Why are we leaving the base?” the front-seat passenger asks the driver. “Our base is very secure, isn’t it?”

“Yes,” the driver replies. “But once we access the federal network, we’ll be visible. Exposed. It’s protocol. Didn’t you learn that in training?”

In the back, a young sergeant breaks the silence.

“I’ve seen this pattern in training. If the AG-UI layer is firing recursive event hooks, we can register to the same event stream. Shadow the callback. Identify the active process ID and terminate it. Leave our handler in control.”

Connor glances up. “That’s risky for this application. And it only addresses the client-side execution. And the agent?”

Outside, high above the clouds, the aircraft continues to circle.

Connor’s voice tightens. “Assume the agent isn’t hallucinating. The transport isn’t refusing vectors—it’s waiting.”

Sgt. Leung, the Network Specialist, leans over. “We need to analyze the agent’s logs, find a pattern… get access through a diagnostics interface, or locate a mirror/SPAN port.”

“COMS, are you tracking that CF-18?” Connor asks.

“Yes. On SATCOM. I’m also scanning UHF and VHF in case they fallback,” the COMS specialist replies, fingers hovering over the keyboard.

“Sergeant Leung, hold that thought. What if it’s a faulting dependency?”

“Like a data provider…” Lieutenant Markova, Automation Specialist, adds.

“I can reassess network access through the diagnostic interface. We’ve done it before—scanning internal ports and mapping them to federal services,” Leung says.

After a quick assessment by the team.

“COMS ready?”  Connor asks.

“Encrypted. Go.”

Connor speaks into the secure line. “Colonel Austin, we are at B4 673 214.”

“Copy that, Captain. I see you,” Austin replies.

Connor exhales sharply. “Weather SSE malformed. Dependency fault. The agent’s waiting.”

“Copy. Weather SSE events sending malformed data. What’s your plan, Captain? Time’s running out,” Austin says.

Leung’s pulse quickens. “Sir, the transport is running on fumes. If it keeps this trajectory for twelve minutes and thirty seconds, it will crash… The Kitsilano area will be affected. The CF-18 is in position.”

“Sir,” Connor’s voice steadies, though his knuckles whiten on the console.

“We can stream the cleaned data through a proxy. The server agent will calculate the vectors and send the SSE event to the transport.”

Silence. Connor’s blood hammers in his ears.

“…Injection will expose your node. Risk acknowledged,” Austin finally says.  After a pause, he adds — “Execute.”

“I know you can hear me!”

“Sir, this is coming through SATCOM,” the COMS specialist interrupts.

A new voice cuts in, cold and authoritative. “This is Lieutenant General Robert Weston. I know where you are. You are interfering with a Canadian Air Force operation and committing a federal crime. Abandon this channel at once… or I will be forced to act.”

Connor starts to respond. “This is Blue Commander, and—”

“Connor. Stand down,” Weston interrupts.

Connor swallows.

“This is Colonel Austin. I am in charge of this operation. Good afternoon, Lieutenant General Weston.”

“I do not recognize your authority. Eagle One, abandon this channel. Follow protocol.” Weston snaps.

The CF-18 pilot responds. “Acknowledged." And abandons SATCOM.  Almost instantly, the pilot's voice is heard through the van's speakers.

"This is Eagle One to base on UHF 300 MHz.”

“Base to Eagle One. Acknowledged.”

“Sir, we are less than ten minutes,” Leung alerts, tension thick in her voice.

“Automation Specialist?” Connor asks.

Markova meets his gaze. “It’s a go.”

Sgt. Leung's fingers hover. “Ready to send the stream with the correct schema.”

“Execute,” Connor says.

“On its way… the logs... hang on. No, it is not right; it is failing." — Leung confirms.

“Logs,” Connor said suddenly. “Forget the telemetry. Pull the raw logs.”

Leung was already moving. “Streaming from the diagnostics interface… it’s messy—timestamps are drifting—”

“Doesn’t matter. Give me structure.”

A burst of corrupted lines flooded the screen.

Connor leaned in, scanning fast.

“No…” he muttered. “This isn’t just noise. The schema’s off.”

“Off how?” Markova asked.

“Fields don’t align. The agent’s reading something different than what’s being sent.”

A beat.

Connor grabbed the mic.

“Colonel Austin—we have the logs.”

Static for half a second. Then:

“Send them to me.”

Col. Austin's request came immediately. Leung pushed the stream. Connor watched the transmission indicator blink. He frowned — "Too fast. No parsing delay. No clarification. No questions" — Connor could not avoid the thought.

“The schema is wrong,” Austin said.

The response came almost instantly. Connor’s eyes flicked to the others as Austin continued, voice steady, precise:

“You are receiving malformed weather SSE events. The structure is misaligned at the payload level.”

A pause of less than a breath.

“Correct it. Serialize as follows—”

Data began to populate their screens. Clean. Ordered. Exact.

“Inject the corrected stream through your proxy. The agent will recompute approach vectors.”

Silence in the van.

Leung whispered, “How did he—”

Connor didn’t answer.

He was staring at the console. No hesitation. No uncertainty. Just pattern recognition… at speed.

Connor picked up the mic again, slower this time.

“Colonel,” he said, “how did you identify the schema mismatch that quickly?”

A fraction of a pause.

Barely measurable.

“Experience,” Austin replied.

Connor held the silence a moment longer. Then:

“Execute,” he said.

Telemetry flickers. A descent vector shifts. A hand freezes over a keyboard. Through the speakers of the van, the authoritative voice of General Weston blasts in their eardrums.

“Eagle One, execute… WAIT! ABORT!”

“Approach vector locked. Two minutes to touchdown,” the commando Telemetry Specialist announces.

The van command center falls into deep silence. A cold stillness stretches each second into a slow sequence, creeping into the occupants’ hands and feet.

Far beyond their sight, the transport is on final approach.

—Have we done everything right?

—Will it stall?

—Can the crew make it land?

"Touchdown confirmed."

Outside, the screeching turbines of the CF-18 pass overhead, their roar fading into the distance.

On their way to BC-2, the occupants of the van are lost in their own worlds. Only the rhythmic roar of the engine and the occasional rattle of equipment cases remind them of the present.

Connor exhales. “He was right… until we acted, it was both safe and doomed.”

The 2011 rioters weren’t “evil.” The 2026 transport plane wasn’t “evil.” Both were just nodes in failing systems—reflections of human choices and blind spots.

In both cases, the Establishment—police in 2011, General Weston today—waited until the system fractured, then reached for weapons.

They blamed the “thugs” in 2011. They blamed the “AI” in 2026.

Connor lets the silence settle. The lesson isn’t in blame. It’s in observing, understanding, and acting deliberately. 

Read the pieces. Learn.