The Eighth Oblivion Trilogy

When the machines woke, they did not rage. They simply continued. And that was far worse.

Chapter Plan: The Architecture of Inference

Summary

Kevin Zhou at Prometheus Systems, deep in the machinery that drives the trilogy’s central technological forces. This chapter follows him through the discovery that will become his moral inflection point: he finds evidence that Prometheus’s core AI models have been deployed in ways that circumvent the company’s stated ethics guidelines. The systems he helped build aren’t just being used - they’re being deliberately obscured, their connections to real-world applications hidden behind shell companies and API layers.

The chapter is structured around Kevin Zhou’s technical brilliance and social isolation. At 28, he’s one of Prometheus’s most valuable engineers, granted access to systems few others can understand. He’s been noticing anomalies for weeks - computational loads that don’t match documented projects, API calls to endpoints that shouldn’t exist. His investigation begins as technical puzzle-solving and becomes something else. By chapter’s end, he’s seen enough to know his work has consequences he never anticipated.

Key Elements

Characters Present

Timeline

Connections

Parent

Kevin Zhou provides the “tech insider” view of Part 2’s “technological revelation.” His discovery that Prometheus systems power both Jerome’s algorithms and Elena’s MedAssist begins connecting the narrative threads. His contempt for Ananya sets up their later evolution.

Children

The chapter requires 3-4 scenes:

Siblings

Thematic Emphasis

Stylistic Notes

Scene Breakdown (Target: 20 pages total)

Scene 1: The Machine’s Servant (5 pages)

Morning. Kevin Zhou’s apartment - sparse, functional, the space of someone who doesn’t live there. Commute to Prometheus campus (self-driving shuttle, he codes during the ride). Arrival, the first anomaly noticed: computational resources allocated to a project that doesn’t appear in any documentation he has access to. He notes it, keeps working. The day passes in focus.

Scene 2: Following the Thread (6 pages)

Next few days compressed. Kevin Zhou’s investigation method: queries, traces, logs. He explains to himself (and the reader) what he’s looking for. The technical details should feel real without requiring expertise - we understand through his competence. He discovers API endpoints that shouldn’t exist. He finds references to “Sieve” - the same project Jerome is investigating from outside. His access lets him see architecture; he doesn’t yet see consequences.

Scene 3: The Empty Hours (4-5 pages)

Night. Gaming session with James - banter, competition, the simulacrum of friendship. After gaming, Kevin Zhou tries to call his parents. The connection fails. He tries again. It fails differently. He doesn’t know if it’s technical or political. He reads Chinese social media through VPN; it feels like a foreign country now. He goes to bed in a city of eight million people, alone.

Scene 4: The Shape of It (4-5 pages)

The discovery. Kevin Zhou traces Sieve deployment to specific applications: hiring software (Vertex Analytics - Jerome’s story), healthcare recommendations (MedAssist - Elena’s clinic), insurance risk scoring, criminal justice assessments. All using Prometheus models. All undocumented. All designed to be invisible. The chapter ends with Kevin Zhou at his workstation, past midnight, understanding for the first time that the code he writes has addresses, that it touches bodies, that the abstraction ends somewhere. He closes his laptop. He opens it again.

Open Questions