To understand why Protocol 7 was so uniquely dangerous, Chloe pulled up the architectural documentation comparing Zenith's core system layers. The airline's modern infrastructure relied on lightweight, RESTful JSON APIs running over HTTPS. Every REST endpoint was protected by an API Gateway that enforced OAuth 2.0 authentication, checked user scopes, and logged every incoming transaction to an immutable audit cluster. When a normal customer or gate agent modified a seat through the modern application, the RESTful service triggered automated event-driven webhooks. These webhooks immediately pushed real-time notifications to the passenger's smartphone, updated the mobile pass, and sent an encrypted receipt to the customer history database.
In stark contrast, Protocol 7 was an old SOAP (Simple Object Access Protocol) XML service that communicated directly with the legacy IBM mainframe via unencrypted TCP sockets. It bypassed the modern API Gateway entirely. When a command was issued through Protocol 7, it sent a heavy XML payload directly to the core database driver, executing direct SQL `UPDATE` queries on the database tables `passenger_manifest` and `pnr_reservations`.
Because Protocol 7 operated beneath the application layer of the modern microservices, it never published events to the system's Kafka event bus. As a result, no webhooks were ever triggered. The system executed the database mutation silently. The field `seat_assignment` was rewritten from `3A` to `3B`, and `consent_flag` was set to `TRUE`, without generating an event notification, without updating the user's mobile app state, and without leaving a trace in the standard customer interaction logs. It was a ghost transaction—a direct write to the raw database tables that left the front-end user interfaces completely unaware of the underlying corruption.
Chloe sat back in her mesh chair, her face pale in the blue glow of her dual monitors. Her discovery was methodical and terrifying. She had isolated the exact database query log from 7:15 AM, matching the raw socket connection to an internal IP address assigned to the executive suite on the 85th floor. She printed the raw SQL trace, watching the ink dry on the paper, knowing that this single technical document contained the indisputable proof that would dismantle Julian Vance's career.
Whoever had triggered the change had used a command-line script to construct a raw REST payload sent directly to the legacy port, bypassing the modern API gateway entirely. The payload injected an automated database update directly into the Passenger Name Record (PNR) table. To prevent the system from flagging an inconsistency, the script executed a secondary stored procedure that set the field `consent_flag` to `TRUE` and forged an internal timestamp, mimicking an automated customer self-service transaction. Because the request came from an internal IP address with a legacy root authorization token, the core database accepted the write operation without routing an event notification to the user's mobile app. It was a sophisticated, deliberate technical backdoor—one designed specifically to alter records while leaving modern security layers completely blind.
Chloe reached for her desk phone, her hand trembling slightly. She didn't dial her direct supervisor. She dialed the direct, unlisted number for the Integrity Division. A ghost was in the machine, and it was tearing up the rulebook.
Chapter 4: A Standoff in First Class
Back on Flight 212, the atmosphere inside the first-class cabin had transitioned from tense to suffocating. The aircraft's auxiliary power unit hummed loudly, pumping cold air through the overhead vents, but it did little to cool the rising tempers.
Zara felt the heavy silence press against her eardrums like altitude sickness. In her mind, a chaotic stream of calculations played out. She mentally parsed her C++ codebase for SafeNav, specifically the spatial interpolation module that calculated distance vectors between point-cloud clusters. She focused on the math to keep her pulse from skyrocketing. Focus on the data, she repeated like a mantra. The array indexes don't lie, and neither does a PNR database. Yet, underneath the analytical shield, a sharp blade of vulnerability poked through. She was fifteen, standing in an aisle surrounded by adults who viewed her either as an inconvenience or an obstacle. Every second she spent standing there, she felt the gaze of the cabin eroding her resolve. But she thought of the visually impaired testers who had trusted her app, people who walked into chaotic, unpredictable environments every day without the luxury of backing down. If she couldn't defend her own assigned space on a commercial airliner, how could she build technology meant to give others agency over theirs?
The contradiction between her personal situation and her ambition was staggering. For over twelve months, she had poured her heart into SafeNav, designing every line of code around the concept of digital empowerment. The application was engineered to give visually impaired travelers independence, allowing them to navigate complex transit environments like JFK without relying on the good graces or erratic help of strangers. The software converted spatial ambiguity into rigid, objective sensory feedback. It was built on the fundamental belief that technology should be a neutral, reliable shield that protects user agency against an uncaring environment.
Yet here she stood, trapped inside the exact type of environment her app was designed to demystify, watching human entitlement override system rules. The digital architecture of Zenith Airlines had been designed to track every passenger with absolute precision, yet a powerful executive had swept away her assigned parameters with a casual phone call. If the systems governing commercial transit could be silently manipulated to strip a teenager of her assigned space, what did that mean for the vulnerable users relying on digital infrastructure for their basic mobility? It was a harrowing realization that code was only as honest as the human structures controlling the database.
Jessica, the flight attendant, stepped closer to Zara, her expression a mix of sympathy and acute professional stress. She leaned in slightly, lowering her voice so it wouldn't carry to the rest of the first-class cabin.
"Sweetheart, I completely understand why you're upset," Jessica whispered, her hands clasped nervously in front of her apron. "It's a terrible situation, and you're entirely in the right. But Mr. Sterling is a very prominent client, and when Vice Presidents get involved, it gets extremely complicated for the crew. Seat 3B is right next to the window seat—it has almost the exact same view. If you just sit in 3B for this flight, I can make sure you get premium snacks, free Wi-Fi, and I'll personally write a report to customer relations so you get a full travel voucher."
Zara looked at Jessica, seeing the genuine panic in the woman's eyes. She knew Jessica was just trying to keep the peace and protect her job, but taking the easy way out felt like betraying everything she was working toward.
"Thank you, Jessica," Zara replied softly but firmly, looking directly into the flight attendant's eyes. "I know you're trying to help, and I don't want to make your job harder. But 3A isn't just a seat preference to me. I reserved it months ago so I could focus and work on my presentation. If I move to 3B just because he's loud and important, I'm agreeing that his time is more valuable than mine, and that the rules don't apply to people with expensive suits. I can't do that."