November 2013 — Ann Arbor, Michigan
On a cold Tuesday in November, Ethan Reyes hires his first employee.
Her name is Amara Osei. She is twenty-nine, Nigerian-American, the daughter of a Detroit autoworker and a public school librarian, and she has a master's degree in computer science from Carnegie Mellon and four years of experience as a network security analyst at a firm in Pittsburgh that didn't deserve her. Ethan finds her through a referral from Christine Mao at Google — Christine's one-line email reads simply: She's the smartest person in any room she's been in except the ones where I was also in the room. Hire her before someone else does.
The interview is three hours long. Ethan asks her no standard questions. He gives her a network traffic capture log and asks her to tell him what happened. She spends forty minutes on it, asks for a whiteboard, and then spends another thirty minutes mapping a sequence of events in the traffic that Ethan himself had identified but that she has extended — found two additional steps in the anomaly chain that his analysis had stopped short of.
He offers her the job that afternoon. She asks for twenty-four hours.
She calls back in twelve.
"One condition," she says.
"What."
"I want to know what the tool is. Not the code, not the specifics. Just the philosophy. Because what you're doing doesn't match anything I know about how security software works, and if I'm going to build something with you, I need to understand the foundation."
Ethan is quiet for a moment. He has thought about this. He has thought about how much to say, and to whom, and in what order.
"The philosophy," he says carefully, "is that systems reveal their nature if you ask the right questions. Most tools ask questions from a list. This one reasons. It asks questions the list doesn't have yet."
A pause.
"That's not a technical answer," Amara says.
"No."
"But it's an honest one."
"Yes."
"Okay," she says. "I'll take the job."
Apex Systems opens a proper office in December — not a large one, a suite on the third floor of a building in Ann Arbor's downtown that has exposed brick and good natural light and a coffee machine that Amara selects with the focused attention she brings to all technical decisions. There is a server room the size of a walk-in closet, which Ethan and Amara spend a Saturday afternoon setting up together, which involves more cable management than either of them expected and a disagreement about labeling conventions that they resolve by letting Amara win, because she is right.
The office has two desks. Ethan is thinking about four.
He has interviews scheduled.
He is also, during this period, working with a quiet intensity on two parallel tracks that he has not discussed with Amara yet — not because he doesn't trust her, but because the pieces aren't assembled enough to explain.
The first track: Protocol Zero.
He has acquired, in November, a fourth tool from the catalog.
SECURE COMMUNICATIONS ARCHITECTURE SUITE
End-to-End Cryptographic Infrastructure Design System
The SCAS is not a product. It is a blueprint — or more accurately, the knowledge necessary to construct a product. What SCAS gives Ethan is a comprehensive understanding of cryptographic protocol design at the implementation level: not just how to use existing encryption standards but how to reason about the design of communication systems from first principles, how to identify the points where mathematical soundness meets implementation reality and where that gap creates exploitable weakness. It includes a deep understanding of the post-quantum cryptographic approaches that are, in 2013, almost entirely theoretical in the academic literature.
COST: 1,600 CREDITS
The integration takes twenty-seven minutes and leaves Ethan sitting in the dark of his Ann Arbor office for nearly an hour, not moving. When he comes back to himself, he is acutely, almost painfully aware of how most of the world's communications work — not as a paranoid observation but as a technical fact. The gaps are everywhere. The walls are thin.
He begins building what will eventually become the core cryptographic layer of everything Apex Systems does.
The second track is less technical. More human.
He has been thinking about his mother.
Diane Reyes lives in a two-bedroom house in Southwest Detroit that she has owned for twenty-two years and that has needed a new roof for the last four. She works part-time at a medical billing office and full-time at the business of not worrying about Ethan, which is a business that has never turned a profit. She knows he is doing well. She knows it in the vague but certain way that mothers know things — from the quality of his voice on the phone, from the fact that he stopped asking about freelance leads, from the way he changes the subject when she asks about money.
Ethan drives to Detroit on a Sunday in late November. He takes her to the restaurant she likes, a Haitian place on the east side that has been there since before he was born. He orders the griot. She orders soup joumou and watches him across the table with the expression she has worn since he was small — a particular combination of love and assessment that he has never been able to fully read.
"You going to tell me?" she says, eventually.
"Tell you what?"
She gives him a look.
He puts his fork down. He tells her as much as he can, within the bounds of the NDAs. He tells her about the company, about Ann Arbor, about the kind of work he's doing. He doesn't tell her the numbers — not the full ones — but she's good at arithmetic and she watches his face and she doesn't need the full picture to understand the scale.
She is quiet for a long time when he finishes.
"You're being careful," she says. It is not a question.
"Yes."
"Who knows about what you're doing?"
"The clients. My lawyer. My financial advisor."
"That's not what I mean." She looks at him steadily. "Who knows about how you're doing it?"
He holds her gaze. "Nobody."
She nods slowly. She picks up her spoon. She looks at the soup.
"Keep it that way," she says. "For as long as you can."