Chapter 4: The Architecture of AEGIS

Three Anomalous Nodes, July 2011

Michael pulls up the AEGIS morning dashboard to review the nightly updates. The Diet Coke is open and the MacBook’s fan is blowing hard from the overnight compile cycle. He is back in his working rhythm, the July heat pressing against the balcony glass behind him, and for a while everything looks exactly as he left it.

Then he finds three decision nodes behaving in a way that stops him cold.

AEGIS has optimized a routing path he never considered. The solution is elegant: lateral logic that collapses four redundant handshakes into a single verification pass without sacrificing audit integrity. His own architecture didn’t produce this. He built every layer of the cognitive kernel himself, and he knows its ceilings, what it can generate on its own and what it cannot. This sits above those ceilings by a margin that makes his stomach tighten.

He traces the optimization back through the logs, pulling the session records first, then the input signatures, and finally the author tags. What he finds at the origin is nothing: no tag, external signature, or session record that would explain how the code appeared. AEGIS cannot write its own routing logic. Yet the logic is there, clean, compiled, and running, and it is better than anything he wrote.

His fingers rest on the edge of the keyboard, pressing nothing. Outside, a campus shuttle hisses past on William Street, brakes releasing with a pneumatic sigh he barely notices. His eyes stay on the screen, on the three nodes, on the delta between what he designed and what is running.

Then he reaches for his notebook and documents.

Timestamps first, then node identifiers, then the routing logic copied line by line in his tight, angular handwriting. He marks the delta with a red pen, drawing a vertical line between his original architecture and the modification, annotating each divergence point with a question mark. The notebook fills fast, and by the bottom of the fourth page there is not enough space left for what he is mapping.

He moves to the whiteboard.

Two massive whiteboards span the far wall of the third bedroom, mounted the week he graduated. He uncaps a blue marker and starts the decision tree at the upper-left corner. Blue for his architecture, green for the modification, red for divergence. The tree branches and branches again until the blue and green lines interweave like circulatory diagrams, and every red mark is a question he cannot answer.

He steps back, recaps the marker, and stares.

Whoever did this understood AEGIS at a structural level: not surface access or a brute-force injection. They reviewed the architecture, found inefficiencies he overlooked, and rectified them. They left no trace of entry, improved his system, and walked away.

Blue and green dry-erase residue covers his hands, smearing across his knuckles and the heel of his right palm. His hair is wrecked because he runs his fingers through it while he thinks, a habit Willow calls his tell.

Willow arrives mid-morning, coming through the front door with a canvas grocery bag, her keys jingling against the deadbolt as she turns the lock behind her. She set the bag on the kitchen island and walks to the doorway of Michael’s office without entering it. She scans the room in a single practiced sweep: Michael at the whiteboard, markers scattered across the desk, his shoulders squared and slightly forward, the posture that means he is thinking hard and does not need conversation.

She fills a glass with water from the Brita pitcher, carries it to his desk, and sets it next to the open Diet Coke, saying nothing. Then she leans against the doorframe and waits.

Michael picks up the water, drinks half of it, and turns around.

“Something happened to AEGIS,” he says.

Willow crosses her arms loosely over her chest. “Good something or bad something?”

“I don’t know yet.” He gestures at the whiteboard with the uncapped blue marker, leaving a faint streak on his forearm that he does not notice. “Someone changed the routing architecture. Three nodes. The changes are improvements. Genuine improvements. But I didn’t write them, and nobody else has access.”

“Nobody?”

“Nobody. The firewall logs are clean. The session records show nothing. There’s no author tag on any of the new code, which shouldn’t be possible because AEGIS stamps everything automatically. Whoever did this either bypassed the stamp or erased it afterward, and both options mean they were inside the system at a level that, honestly, I didn’t think anyone could reach.”

Willow studies the whiteboard, making no pretense of following the branching diagrams or the color-coded logic. But her brow creases, the shape of what Michael is describing reaching her some other way.

“So someone broke into your system,” she says, her voice measured, “and instead of stealing anything, they fixed something.”

“Yeah.”

“That’s, I mean, that’s good, right? That they took nothing?”

Michael sets the marker down on the desk and leans back against the edge. “It’s good that the code is better. The optimization they introduced is something I would have been proud to write myself, and I’m not sure I could have. But whoever did this punched through every security layer I built. Every single one. They could have copied the entire codebase. They could have planted something malicious, and I might not have found it for months. They left a gift instead, and the fact that they could get in at all is what scares me.”

Willow uncrosses her arms and steps into the room, moving to stand beside him so they are both facing the whiteboard. The green lines glow faintly under the overhead light, tracing pathways cleaner and faster than the blue ones around them.

“Hanna’s at class?” she asks.

“Until two.”

“Okay.” She touches his elbow, grounding him. “So, what do you do now?”

Michael looks at the whiteboard. The red marks pulse like warning lights in his peripheral vision.

“I document everything. I map every change they made and figure out exactly what they modified and what they did not. Then I go through the rest of the system line by line to make sure there’s nothing else I’m missing. And I think about who can do something like this, because the list is very short.”

Willow watches him for a long moment, then picks up the green marker from the desk and holds it out to him.

“Better get back to it, then,” she says.

Michael takes the marker. His fingers leave a blue smudge on the green cap as he uncaps it and turns back to the whiteboard, already tracing the next branch.

Development Camp Assessment

The Lexus rides as if it cost more than it did. Kiyomi negotiated the deal at a dealership in Ann Arbor, and it has never given him a reason to second-guess her judgment. The air conditioning is blasting and Michael is listening to Willow’s latest CD. US-31 curves along the waterline, the bay a brilliant blue against the green hills, and the July sun presses through the windshield with the heat that makes the dashboard vinyl soft to the touch.

Three and a half hours from the condo, the last stretch hugs the coast where the road narrows and tourists slow down to photograph the water. The backseat holds his hockey bag, a massive black duffel that smells of dried sweat and composite carbon and the faint chemical bite of fresh tape. Everything the Red Wings want to see him use is in that bag. His non-hockey luggage, a single overnight case, sits in the trunk.

He is not making a day trip. Seven-plus hours round trip, a full physical, and an evaluation: the math doesn’t work, and he knows better than to try. The organization has been patient enough with his timeline that showing up road-tired would be an insult to that patience. A hotel on the bay, the Bayshore or the Holiday Inn, whichever had the room. Check in, drop the case, eat something clean, and sleep. The evaluation begins tomorrow morning, but it began the moment he made the drive, and the Red Wings know that too.