Page 49 of Hollow Code
Zadie's fingers moved. On the wall, he watched the credential package slide into the permission architecture—native formatting, legacy timestamps, buried three layers deep in a dormant section.
"Two minutes forty," Zadie said. "Package is seated. Running integration check."
Gideon kept feeding the AI. His smashed-window script generated massive response traffic. The system was throwing everything it had at the perceived extraction attempt. Shadow servers multiplied across his monitor—like cells, dividing. Data reroutes cascaded in chains. The AI was fully committed.
Then something shifted.
His left monitor stuttered. It wasn’t a lag. More like a redirection. The AI's behavioral tracking had changed pattern mid-cycle. Instead of following his latest probe, it doubled back. Scanned the previous attack vector, returned to the current one, and doubled back again.
That wasn't how the AI worked. The AI chased the loudest threat. It didn't second-guess.
"Something's going on," Gideon said.
"What do mean?" Zadie asked.
"The tracking pattern. She's oscillating. Checking my old vectors against my new ones." His fingers flew across the keyboard, pulling up the AI's response logs in real time. "That's not automated behavior. The AI commits. She doesn't waffle."
"You think someone's steering her?"
He watched the pattern repeat. Like the AI was being asked to verify something. Like someone was sitting on the other end, watching the same data Gideon was watching, and telling the system to take a second look.
"Someone’s inside the system watching me."
"Who?" Coulter asked.
Gideon didn't answer. He adjusted his attack pattern. A subtle variation, a slight shift in timing that wouldn't register as different to the AI's algorithms but would be obvious to a human analyst watching the feed. A test. If the response adapted to the variation in a way that followed logic rather than code, it wasn't the AI making the call.
The AI's containment protocol shifted to match his new timing. Someone had overridden the automated response and manually adjusted the tracking parameters.
Gideon's blood chilled. "How much longer do you need?"
"Thirty seconds. Integration is running."
Gideon went loud. Every remaining script he had, he launched simultaneously. His monitors turned into a wall of scrolling data—red flags, containment responses, shadow server deployments, honeypot redirects.
And whoever was on the other end had to deal with all of it.
"Fifteen seconds," Zadie said.
Gideon's fingers ached. His shoulders burned. Sweat beaded at his hairline.
"Ten."
The AI's tracking oscillation stopped. Whoever was assisting had been forced to focus on the barrage. The automated systems took over, and the behavioral pattern normalized.
"It’s done." Zadie wiggled her fingers. "Credentials planted. Integration complete. I'm out."
Gideon killed his scripts in sequence. One by one, the attack vectors went dark. The AI's containment protocols wound down. Shadow servers collapsed. The system settled back to baseline like a lake after a stone had been thrown.
"Does that mean it worked?" Coulter asked.
"It should." Zadie looked at Gideon. "Unless someone goes looking for them specifically."
Gideon stared at his monitors. The AI's response logs were still scrolling. It was all standard post-engagement behavior. Nothing unusual.
Except.
He leaned forward. One of the containment logs had a formatting anomaly. A string of code buried in the AI's threat assessment output that didn't match the surrounding syntax. The AI didn’t generate it. Someone had inserted it manually. Embedded it in the response data like a note tucked inside a book.
