Daemon, Chapter 2: Chapter 2:// Rogue Process

Chapter 2 of *Daemon* is titled "Rogue Process," and the trick is that for most of its length you don't know who the rogue process is. Sebeck and Mantz investigate what looks like a motocross accident — a wire strung across a remote Thousand Oaks canyon road that nearly decapitates a CyberStorm Entertainment developer named Joseph Pavlos. The chapter reads like straight procedural: sanitized suburbs, forensic detail, a partner who cracks jokes. But the title is doing double work. In computing, a rogue process is one that escapes its expected bounds and consumes resources uncontrollably — and here the rogue process isn't the Daemon (which hasn't yet revealed itself) but the dead man, a senior developer who presumably wandered outside the boundaries Sobol set for him. The murder method — a physical wire, not a hack — is the chapter's real tell. It announces that the Daemon operates in meatspace, not just cyberspace, and that its violence will be mechanical, literal, almost primitive. Suarez is building a techno-thriller where the most sophisticated AI in the plot kills its first target with technology older than Rome.