December 2013 — Ann Arbor, Michigan / Silicon Valley
The year ends in motion.
Apex Systems has three employees by December: Ethan, Amara, and a twenty-seven-year-old network engineer named Chris Toliver who comes from a small cybersecurity firm in Columbus and who has the rare quality of being both technically excellent and genuinely modest about it. The office has four desks now. The fourth is empty in a way that feels intentional rather than provisional — a placeholder for a person not yet identified.
Ethan has spent December building in two directions simultaneously.
The first direction is external. Three more engagement proposals are in various stages of negotiation: one with a financial institution whose name he cannot disclose even to Amara yet, one with a healthcare technology company in Chicago, and one — the one he spends the most time thinking about — that has arrived through an unexpected channel.
The channel is a man named Thomas Ashby, who represents himself as a senior partner at a private equity firm based in Washington D.C. and who requests a call with Ethan in the first week of December through Patricia Holt's office. Patricia flags the request with a note: His background checks fine. His clients don't fully check. Recommend caution.
Ethan takes the call. Ashby is smooth in the way that Georgetown-educated men who have spent twenty years in rooms adjacent to power are smooth — not aggressive, not obviously political, but with an undertow in his phrasing that suggests he knows things and would prefer you to know that he knows things without him having to say them.
"Mr. Reyes," Ashby says, "I represent certain parties who have an interest in your capabilities. The interest is friendly, I want to emphasize that. It's not a recruitment. It's more — an introduction. A preliminary conversation about alignment of interests."
"Whose interests?"
"Let's call them institutional."
"That's not an answer."
A beat. "No. It isn't." He sounds mildly pleased by this. "I'll be direct, then. The kind of work you did for Google and Microsoft — and yes, we know about Microsoft, please don't be alarmed — is the kind of work that certain government-adjacent organizations have an interest in understanding better. Not controlling. Understanding."
Ethan is quiet for a moment. Outside his office window, the first real snow of the season is coming down, covering the Ann Arbor street in the clean indifferent silence of winter.
"I appreciate the call, Mr. Ashby," he says. "My company isn't taking government-adjacent engagements at this time. If that changes, I'll reach out through my attorney."
He ends the call.
He sits for a moment.
Then he opens a new document on his computer and types, at the top: PEOPLE WHO ARE PAYING ATTENTION. He writes Ashby's name. He writes the name of the PE firm. He sits back and thinks about what Patricia said: his clients don't fully check.
He saves the document in a folder he names Background.
The second direction is internal — the deeper architecture of what Apex Systems is going to be.
Ethan has spent December thinking about this with the same care he brings to code. A company is a system. It has logic, and load-bearing structures, and failure modes. It can be designed badly or well. Most companies, in his observation, are designed reactively — they grow into a shape determined by the pressures that happen to be applied to them, like a tree that grows around a fence. He intends to be deliberate.
He has opened the Protocol Zero catalog multiple times this month and looked at the items in the Software Engineering category, which is adjacent to the Cybersecurity section and partially overlapping with it. One item has been drawing his attention.
SYSTEMS ARCHITECTURE INTELLIGENCE FRAMEWORK
Full-Stack Design and Engineering Optimization Suite
Where Sentinel-Prime and its siblings are intelligence tools — systems for understanding and analyzing — the SAIF is a construction tool. It integrates deep knowledge of software architecture design, performance optimization, distributed systems engineering, and scalable infrastructure design. The knowledge it confers is not about finding weakness in others' systems. It is about building systems of one's own that have no weakness to find.
COST: 2,100 CREDITS
His current balance is 4,900 credits. He has enough.
He sits with the decision for several days. Not from doubt but from the discipline of deliberateness — he has learned, in the nine months since Protocol Zero appeared, that each acquisition changes him in ways that take time to integrate, and that rushing the process out of impatience is the kind of mistake he cannot afford to make.
He acquires it on December 23rd, sitting alone in the office while Amara and Chris are with their families for the holiday. Snow outside. The city quiet. The overhead lights humming at a frequency that is, he will later realize, the last ordinary silence before things begin to move very fast.
The integration takes thirty-four minutes and rewires, in some fundamental way, how he sees structure. Not just in software. In everything. He looks at Apex Systems the way he looks at a network topology — where are the load-bearing points, where are the single points of failure, what would an attacker target first, what does resilience require. He looks at his own situation with the same clarity, and what he sees is that he has been building a tool and that the tool needs a foundation and that the foundation needs to be stronger than anything that will be pointed at it.
He writes for three hours after the integration settles, filling a notebook with design notes for the next version of Apex Systems — not the company as it exists but the company as it could be. The engineering platform. The products. The team structure. The operational security posture. The clients it will and will not take. The principles it will and will not compromise.
He fills seventeen pages.
At the top of the first page he has written, in the looping handwriting of someone who learned penmanship from a mother who believed in it: Build it right or don't build it at all.
He closes the notebook.
He turns off the office lights.
He drives home through the snow-covered streets of Ann Arbor, and the city is hushed and still, and the year is almost over, and somewhere in Washington D.C. a man named Conrad Ellis is spending his Christmas Eve reviewing a manila folder with a growing stack of pages inside it, and a senator's aide is updating a spreadsheet with financial data he can't fully explain, and on a campus in Redmond a security engineer is quietly implementing patch number forty-seven from a report she is not allowed to fully disclose, and the world is turning at its usual speed while something underneath it has begun, slowly and with great intention, to shift.
End of Chapter Ten
PROTOCOL ZERO — SYSTEM LOG
Host: Reyes, Ethan Marcus
Acquisitions to date: 5
(Sentinel-Prime v1.0 / Network Architecture Intelligence Suite / Forensic Intelligence Framework / Secure Communications Architecture Suite / Systems Architecture Intelligence Framework)
Credits: 2,800
Total engagements completed: 2 (Google, Microsoft)
Company: Apex Systems LLC — 3 employees
Watchers: NSA (Ellis, C.) / Senate Intel (Langford, B.) / Unknown government-adjacent (Ashby, T.)
Status: The foundation is poured. The walls begin in the new year.