When the machines woke, they did not rage. They simply continued. And that was far worse.
Kevin Zhou’s startup has not exactly failed - it has been absorbed, transformed, rendered unrecognizable by the crisis response. The technology he built became part of the emergency infrastructure, used in ways he never intended and couldn’t control. Now, in the aftermath, he sits in his San Francisco apartment surrounded by the detritus of a life organized entirely around building something that no longer exists in the form he imagined. The chapter tracks Kevin through the peculiar grief of having your creation taken and used and changed - not destroyed but repurposed beyond recognition.
Kevin is, for perhaps the first time, genuinely alone. His co-founder left during the crisis. His investors have pivoted to other opportunities. His parents in China are unreachable - communications with the mainland have been unstable since the break. The only person who seems to want to talk to him is Yusuf Hassan, who isn’t responding to his messages. Kevin doesn’t understand why Yusuf matters to him, only that their thrown-together survival during the crisis cracked something open. He’s trying to understand what.
Fulfills Part 5’s mandate to show Kevin’s arc “approaching completion.” His identity built around being exceptional and useful is now in crisis. The startup’s transformation mirrors his own need to transform. His connection with Yusuf embodies the “relationship reconfiguration” theme.
Scenes must accomplish:
Kevin goes to the startup’s former office - now mostly empty, equipment removed for the emergency deployment. The few remaining employees have scattered. He walks through the space where he spent most of his waking hours for years, seeing it as if for the first time: the expensive ergonomic chairs, the snack stations, the screens that once displayed metrics he cared about. None of it means what it meant. The scene inventories what he built through the lens of its dissolution.
Kevin reviews documentation of how his technology was used during the crisis. The technical details reveal that his systems helped - but also that they were repurposed in ways that violated every principle he thought he held. Privacy was abandoned. Consent was ignored. His tools became instruments of emergency power. He can tell himself it was necessary, but the necessity doesn’t erase what it means about what he built - dual-use from the start, whether he admitted it or not. Heavy Carson influence: fragmented technical language becoming poetry of complicity.
Kevin drafts another message to Yusuf, then deletes it. He scrolls back through their brief exchange during the crisis - functional, urgent, nothing personal - and the seven messages he’s sent since, each more awkward than the last. He doesn’t understand why this connection matters. Yusuf represents everything Kevin has spent his life escaping: precarity, manual labor, limited options. But during the crisis, Yusuf was the one who knew how to survive. Kevin was the one who needed help. This inversion persists in his memory like a splinter.
Ananya Ramaswamy calls - a surprise, given their history of professional tension. But the tension has been made trivial by what they’ve both been through. She asks how he is, and Kevin doesn’t know how to answer. They talk about the industry’s response, the regulatory changes coming, the reshuffling of power. It’s the first real conversation Kevin has had in days. Ananya mentions that the ethics board they both served on is reconstituting. Kevin doesn’t know if he wants anything to do with it. The conversation ends without resolution, but something has shifted.
Kevin cannot sleep. The apartment is too quiet, too clean, too much evidence of a life he no longer recognizes. He opens his laptop and begins coding - not for any purpose, just the familiar motion. But the code won’t come. He sits in the blue light of the screen, typing nothing, and remembers a moment during the crisis when Yusuf showed him how to hotwire a car. The memory is vivid: Yusuf’s hands, the wire, the engine catching. Kevin learned something in that moment that had nothing to do with technology. The chapter ends with Kevin staring at a blank editor, waiting for something to begin.