April – May 2013
The wire transfer clears on April 19th.
Ethan is sitting at his kitchen table when the bank notification arrives on his phone. He has already retained a lawyer — a woman named Patricia Holt, who works at a small firm in Ann Arbor and who specializes in technology contracts and who spent twenty minutes, during their first call, failing to conceal her astonishment at the terms she was reviewing. She had negotiated three clarifications and one material change to the remediation clause. Google had accepted all four. The final signed figure is $85 million, held in escrow through a third-party financial services firm until the initial remediation verification is complete.
The wire hits his account at 9:14 AM on a Friday.
He makes coffee. He drinks it standing at the kitchen counter, looking out the window at the alley behind the apartment building, where someone has left a broken office chair.
Then he opens Protocol Zero.
The system interface loads. His credit balance has changed.
> CREDIT BALANCE: 4,250
He stares at that number for a long moment. The first acquisition cost 500. He now has 4,250. He opens the catalog and simply reads it — not purchasing, not comparing, just reading. He has done this before, in the days after the Google scan, but now it lands differently. Now it is not a fantasy. It is a menu.
The Cybersecurity category alone has eleven items beyond Sentinel-Prime. One of them — Network Architecture Intelligence Suite — costs 1,800 credits and is described as a system for mapping the internal logical structure of complex networks from the outside, identifying segmentation weaknesses, and modeling lateral movement paths. Another — Cryptographic Analysis Framework — costs 2,400 credits and describes a quantum-adjacent approach to identifying weaknesses in implementation-level cryptographic deployments.
He doesn't buy either. Not yet.
He closes the catalog. Opens a spreadsheet. He has never had money before — real money, not paychecks but capital — and he is aware, with a clarity he finds both sobering and useful, that he does not know what to do with it. He is also aware that not knowing is not a permanent condition. He makes three columns: Legal/Structure, Living/Stability, Operational.
Under Operational, he writes one line: Company.
The money is not secret but it is not public. Ethan has signed an NDA that covers the specific details of the Google engagement — the vulnerabilities, the findings, the exact compensation figure. What he can say, to anyone who asks, is that he completed a significant security consulting engagement for a major technology firm. He cannot say which firm. He cannot say what he found.
He does not post about it. He does not tell people. He calls Patricia Holt and asks her to begin the paperwork for incorporating a private LLC in Delaware. He calls a financial advisor whose name Patricia has given him, a man named Vincent Darrow, who works out of Chicago and who manages the portfolios of several mid-sized technology executives, and who receives Ethan's situation with professional equanimity that Ethan suspects is a performance of equanimity but is grateful for anyway.
"You're twenty-four," Vincent says, on their first real call.
"Yes."
"And this is from a single engagement."
"Yes."
A pause. "Ethan, I'm going to ask you something directly, and I want you to understand it's a professional question, not a personal one."
"Okay."
"Is there any legal exposure on this income? Anything I should know about the nature of the engagement?"
"No. Fully authorized, fully documented, fully disclosed. I have the signed authorization agreement, the engagement terms, and the wire records."
"Good." Vincent pauses again, and when he speaks next his voice has shifted — slightly warmer, the way a man's voice shifts when he decides he's actually interested. "Then let's talk about what you want to build."
There is a man in Washington D.C. named Conrad Ellis.
He is 61, a senior analyst at the NSA's Tailored Access Operations division, and he has been in the business of knowing things that are not publicly known for long enough that he has developed a physical sensitivity to the absence of information — a kind of allergic reaction to gaps in his intelligence picture. He has consultants, algorithms, automated monitoring systems. He reads seventeen daily intelligence digests before noon.
On April 22nd, one of his automated monitors — a system that tracks anomalous financial activity cross-referenced against security-industry keywords — flags a wire transfer. $85 million from a corporate escrow account traceable, through two shell layers, to a Google-adjacent legal entity, to a personal account held by one Ethan Marcus Reyes, DOB 1988, Detroit, Michigan, currently unemployed, no prior security clearances, no known affiliations.
Ellis reads the flag. He reads it again. He makes a note on a legal pad — he still uses legal pads, has for thirty years, considers the habit a feature rather than a flaw.
The note reads: Who is Ethan Reyes?
He sets the pad aside. He has other things to do today. The North Korea situation. The congressional briefing. The thing with the German subcontractors.
But the pad stays on his desk. Conrad Ellis does not throw away legal pad notes.
Ethan moves out of the Detroit apartment on May 1st.
He does not move far — he rents a house in Ann Arbor, a plain two-bedroom with a good internet connection and a backyard where someone has optimistically planted a garden that has since been reclaimed by weeds. He buys a proper desk. He buys a workstation — not an ostentatious one, but a proper machine, custom-built, the kind you spec for serious computational work. He buys a mattress that costs more than his old monthly rent and spends the first night in it staring at the ceiling, feeling the profound strangeness of not hearing his neighbor's television through the wall.
He registers the LLC as Apex Systems LLC. It is not a real company yet — no employees, no office, no products. Just a legal structure holding a bank account. A placeholder for intention.
He opens Protocol Zero on the new workstation.
He acquires the Network Architecture Intelligence Suite.
The integration takes nineteen minutes this time, longer than Sentinel-Prime. It is also more complex — not just a new set of tools but a new way of thinking about networks, a spatial intuition for topology that he doesn't have a prior framework for. When it settles, he can close his eyes and think about a network the way an architect thinks about a building — not as a list of components but as a space, with load-bearing walls and corridors and rooms that connect in ways that weren't intended and therefore are not protected.
He opens a code editor.
He begins to build.