LightReader

Chapter 3 - The Invitation

Three days later, Ethan's carefully structured world encountered its first significant disruption in eighteen months.

The email arrived at 2:47 PM on a Thursday, sent to his personal account rather than his work address. The sender was listed as "J. Morrison - Nexus Development," and the subject line read: "Regarding Your Professional Background."

Ethan stared at the email for thirty seconds before opening it, his mind racing through possibilities. He hadn't applied for any jobs recently. Hadn't submitted a beta application. Hadn't used his real name on any gaming forums or professional networks.

So how had Dr. James Morrison found him?

Mr. Cross,

I hope this message finds you well. My name is James Morrison, Lead Developer for Nexus Infinity. I'm reaching out because your background represents exactly the combination of technical skill and strategic thinking that our project requires.

I understand you may be surprised to hear from me directly. I came across your work through professional channels—specifically, your contributions to several open-source projects and your elegant solutions to complex system architecture problems.

I'd like to offer you an opportunity that goes beyond standard beta testing. Our development team needs someone with your unique qualifications to help us refine the final systems before public release.

If you're interested in discussing this opportunity, please reply to this email. The compensation would be substantial, and the work itself might remind you why you fell in love with complex systems in the first place.

I look forward to hearing from you.

James Morrison

Lead Developer, Nexus Infinity

Ethan read the email three times, parsing each sentence for hidden meanings and potential traps. Morrison had clearly researched his background, but how much did he know? The reference to open-source contributions was accurate—Ethan had submitted fixes to several projects over the past two years, always under pseudonyms, always focused on optimization and efficiency improvements.

But finding those contributions and connecting them to his real identity would require significant investigative effort. Which meant Morrison either had resources beyond typical corporate research, or he'd been specifically looking for someone with Ethan's particular skill set.

The phrase "remind you why you fell in love with complex systems" was especially telling. It suggested Morrison knew about his gaming background, his championship, and his abrupt departure from competitive play.

Which raised an uncomfortable question: what else did Morrison know about his current circumstances?

Ethan minimized the email and returned to his current project—optimizing database queries for the company's customer service system. The work required just enough concentration to prevent his mind from spiraling through paranoid scenarios about corporate surveillance and targeted recruitment.

But the email's existence changed something fundamental about his day. For the first time in three years, someone with resources and authority had specifically sought him out. Not as a cog in a corporate machine, but as someone whose skills were valuable enough to justify personal outreach from one of the gaming industry's most respected figures.

The sensation was simultaneously thrilling and terrifying.

At 5:30 PM, after his coworkers had left for their evening lives, Ethan reopened the email. He'd spent the afternoon researching Dr. James Morrison's background, using the same systematic approach he applied to technical problems.

Morrison was legitimate. Brilliant, even. His previous projects had revolutionized multiple aspects of game development, from physics engines to artificial intelligence systems. Nexus Infinity represented the culmination of fifteen years of research into neural interface technology.

If Morrison was personally recruiting beta testers, it meant the project was either wildly successful or facing problems that couldn't be solved through normal development processes.

Either scenario represented an opportunity.

Ethan began typing a response, then deleted it. Typed another version, then deleted that as well. How do you respond to an opportunity you want desperately but can't afford to accept?

Dr. Morrison,

Thank you for your message. I'm honored that you'd consider me for such an opportunity.

However, I should clarify that my current circumstances don't allow for extensive time commitments beyond my regular employment. If the position requires full-time availability or significant travel, I may not be the right candidate.

That said, if there's a way to contribute on a limited schedule, I'd be very interested in discussing the details.

Ethan Cross

The response was carefully neutral, expressing interest while establishing boundaries. If Morrison was specifically targeting him, he'd find a way to accommodate those limitations. If this was a standard recruitment email sent to multiple candidates, Ethan's restrictions would probably eliminate him from consideration.

Either outcome was safer than diving into an opportunity he didn't fully understand.

Ethan sent the email and closed his laptop, but sleep was impossible that night. His mind kept circling back to the same questions: How had Morrison found him? What did "substantial compensation" mean? And most dangerously: what would it feel like to work on something that actually mattered again?

He was still awake at 3:17 AM when his phone buzzed with a new email notification.

Mr. Cross,

Your circumstances are exactly what we expected, and we've designed this opportunity with that in mind. The initial work can be completed remotely, on your own schedule, with no impact on your current employment.

Would you be available for a brief phone conversation tomorrow evening? I think you'll find the details interesting.

J. Morrison

P.S. - Your grandmother Elena is receiving treatment at UCSF Medical Center, correct? Dr. Sarah Kim speaks very highly of her progress.

The postscript hit Ethan like ice water. Morrison didn't just know about his technical background—he knew about Elena's condition, her treatment, and the financial pressures that controlled every aspect of Ethan's life.

Which meant this wasn't a coincidence. Morrison had specifically targeted him, researched his vulnerabilities, and crafted an approach designed to be irresistible.

The question was whether that made Morrison a predator exploiting desperation, or simply someone who understood that people with limited options required different kinds of motivation.

Ethan stared at the email until his phone's screen dimmed, then lit it again to read Morrison's words one more time. The mention of Elena's treatment wasn't a threat—it was an acknowledgment. Morrison was saying, without stating it directly, that he understood the constraints governing Ethan's decisions and had structured his offer accordingly.

It was manipulation, but it was also thoughtful manipulation by someone who'd done his homework.

At 4:23 AM, Ethan finally typed his response:

Dr. Morrison,

I'll be available for a phone conversation tomorrow evening after 7 PM.

Ethan

He hit send before he could reconsider, then spent the remaining hours until dawn wondering whether he'd just made the first smart decision in three years, or the biggest mistake of his life.

Probably both.

More Chapters