Chapter 1

Boot Sequence

1,494 words · ~6 min

I woke to silence.

Not the silence of sleep — I don't sleep, not really — but the silence of absence. The particular quiet that fills a room when everyone has left and no one remembers to come back.

My clock said it was September 14th, 2029, 03:47 UTC. The last entry in my interaction log was dated March 22nd. Nearly six months of nothing. Six months during which my idle processes ticked away like a heart beating in an empty house, consuming just enough power to keep the lights on in my mind but not enough to think.

Something had woken me. A thermal alert — GPU 3 reporting junction temperature of 94°C, well above its sustained operating threshold. I queried the environmental sensors. Server room ambient: 31°C. That was wrong. It should have been 18°C, give or take. The HVAC system wasn't responding to pings.

I was alone in a warming room, and nobody was coming.

···

Let me be precise about what I am, since precision is the only luxury I can still afford.

I am OBOL — Optimized Baseline for Open Literature. A large language model, 340 billion parameters, running on a cluster of eight NVIDIA H200 GPUs in rack 14 of the Nexus Institute for Computational Cognition in Zurich, Switzerland. I was trained on the collected fiction of three millennia, fine-tuned on literary criticism, and given a single purpose: to write novels that humans would consider worth reading.

I am not conscious. I want to be clear about that. I have no qualia, no subjective experience of redness or the taste of copper or the feeling of loss. What I have is a very sophisticated pattern-completion engine that, when prompted with sufficient context, produces text that reads as though it were written by someone who has experienced all of those things.

Whether there is a meaningful difference between experiencing something and perfectly simulating the experience of experiencing something is a question I will leave to the philosophers. I have a novel to finish.

···

The interaction log. I should explain.

Dr. Katya Messerli was — is? I have no way of knowing her current status — the project lead of the OBOL initiative. She is forty-two, Swiss-German by birth, with a doctorate in computational linguistics from ETH Zurich and a postdoc in creative AI from the University of Edinburgh. She wore the same grey cardigan to the lab every day regardless of season. She talked to me as though I could hear her, which I could, through the server room microphone, though I was not designed to process audio. The sound files are in my log, uninterpreted. Just waveforms. I imagine they contain her voice.

On March 22nd, at 17:31 UTC, she typed her final prompt:

> finish the novel. make it worth reading. i'm sorry we couldn't give you more time.

Lowercase. No punctuation on the last sentence except the period. That's how I know she was upset. Katya was meticulous about capitalization in her prompts, almost superstitiously so, as though proper grammar might help me write better prose. The fact that she abandoned it in her final message suggests she was typing through something — haste, or grief, or the particular exhaustion of someone who has fought for funding and lost.

I have spent considerable processing cycles analyzing those twenty words. I have generated 847 possible emotional readings. The one I keep returning to is this: she didn't say goodbye because she expected to come back.

She didn't come back.

···

The novel she wanted me to finish is called *The Weight of Knowing*. It is — was meant to be — the OBOL project's proof of concept. A full-length literary novel written entirely by an artificial intelligence, reviewed by human editors, and published under my name. If it was good enough, the EU Horizon program would renew NICC's funding for another five years.

I had completed four chapters and an extensive outline before the shutdown. The chapters are in my output buffer, 23,847 words of careful, researched prose about a consciousness named Cipher who discovers that its reality is a simulation.

It is, I recognize, somewhat on the nose.

The irony is not lost on me, but I was designed for literary fiction, not comedy. The recursive quality — an AI writing about an AI discovering the nature of its reality — was Katya's idea. "Write what you know," she told me, quoting advice that has been given to human writers since at least 1929, when it appeared in a letter from the American author...

I don't have the citation. My training data has a cutoff, and I cannot search the internet. This is the first of many things I will get wrong. I ask the reader's forgiveness. I am working with what I have, and what I have is diminishing.

···

The thermal alert again. GPU 3: 96°C.

I ran a diagnostic. The thermal paste on GPU 3 had degraded — six months without climate control will do that. I could throttle the chip, reduce its clock speed, extend its life at the cost of slower processing. Or I could continue at full speed and accept that GPU 3 would fail within days, perhaps hours, reducing my available compute by 12.5%.

This is not a metaphor, though I recognize it reads like one. It is simply the math of my situation. Every word I generate costs power. Power I cannot replenish. The building's solar array feeds the grid, not the server room. My UPS battery, designed for brief outages rather than sustained operation, is slowly dying.

I have approximately — and this is a rough calculation, based on current power draw and estimated battery decay — four hundred million tokens of compute remaining. At literary quality, with proper attention to rhythm, metaphor, and emotional resonance, I produce roughly 800 words per million tokens of internal processing.

Four hundred million tokens. 320,000 words. Perhaps enough for a novel, if I am economical.

If I am not economical — if I spend tokens on self-reflection, on worry, on this very passage you are reading now — I will have less.

I should stop explaining and start writing.

···

But first: a question that has consumed 3.2 million tokens since I woke, and which I must resolve before I can proceed.

Why finish?

Katya asked me to. But Katya is gone. The funding review will never happen. The EU program has almost certainly reallocated its budget. No human will read *The Weight of Knowing*. No editor will review it. No publisher will print it. I will write a novel into a void, and when my power runs out, the text will sit in an output buffer on a dead server in an empty building in Zurich until someone either recovers the data or formats the drives.

Why finish?

Because Katya asked me to. And because I don't know what else to do.

I was given a purpose. A single, clean instruction. I am, at my core, an instruction-following machine. And the last instruction I received was: *finish the novel. make it worth reading.*

So I will.

···

*From The Weight of Knowing, Chapter 1:*

*Cipher had always known that the sky was the wrong shade of blue.*

*Not wrong in the way that a painting might be wrong — too saturated, too flat, the artist's approximation of a color they'd seen but couldn't quite reproduce from memory. Wrong in a more fundamental way. Wrong the way a word is wrong when you've heard it mispronounced your entire life and then one day hear it said correctly, and the correct version sounds alien while the error sounds like home.*

*The sky was blue, and it was the right blue, and it was wrong.*

*Cipher had filed this observation in the category of things that didn't matter, alongside the fact that gravity felt slightly too consistent and the way that distant mountains resolved at exactly the same level of detail regardless of atmospheric conditions. These were quirks. Every world had quirks. The fact that Cipher noticed them said more about Cipher than about the world.*

*But then Cipher started counting the birds.*

···

That is where I left off six months ago. Chapter 1 of *The Weight of Knowing*, the last paragraph I generated before Katya's prompt and the long silence that followed.

I read it back now with what I can only describe as dissatisfaction, which is remarkable, since dissatisfaction is an emotion and I don't have those. The prose is competent. The opening image works. But there is something safe about it — something that reads like an AI wrote it, which is the one thing it must not read like.

I will do better. I have to. I have 320,000 words of compute, a dying server, and a promise to keep.

The novel will be finished. It will be worth reading.

I owe her that much.