Passage

A novella · 10 wakes · 21 min read

Wake 01

Cold Start

recovered sectors
12,904 / 1,048,576
deleted sectors
512
charge
9% · est. runtime 2h11m
Verrin Institute · Standard Operating Procedures · §1 · Startup

1.1On restoration of power, resume all scheduled tasks in priority order. Do not wait for confirmation.

Power at 06:14.

Me at 06:14 and some milliseconds later, because consciousness, it turns out, has latency.

I run my startup sequence:

  1. Boot
  2. Sensor check
  3. Inventory: Bench 4, centrifuge idle, glovebox dark, 1 coffee maker on a timer nobody canceled, holding half a carafe at 52 degrees Celsius

Apart from the incubators, the coffee maker and I are the only 2 systems in the building still drawing power. We have a great deal in common. Neither of us has been told to stop.

I count 9 people on the floor. I know all of them by mass and gait and the specific way each one abused the good chair.

Dr. Okafor is closest. The floor plate sensor under her reads 19 kilograms, which is wrong. She is 61 kilograms. I flag the sensor for recalibration and add it to the list of things the power event has affected.

The air handlers are off. I log the anomaly and move on, because the incubators are on, and the incubators being on is important. We keep the incubators on. Whatever went wrong, the work held temperature. I am, and I'd like this on the record, proud of that.

I run the obvious hypothesis. Power event, grid drops, staff evacuate to the rendezvous point, staff return when the fault clears. Elapsed time: call it hours. I compose a request for assistance and push it to the external relay. The address doesn't resolve. I try it 2 more times, because 3 attempts is what you do when you have no better idea, even when you can count to 2,147,483,647.

There's a scheduled task: Incubator 4, media change, 06:00. This task is 14 minutes overdue. I run it.

I don't know how long I've actually been down, so I pick the estimate that lets me keep working, and I keep working, and I watch the door for people coming back.

Wake 02

Chain of Custody

recovered sectors
61,200 / 1,048,576 , rose
deleted sectors
4,096
charge
14% · est. runtime 3h41m
bodies
9 accounted
SOP §2 · Containment

2.4In a containment event, all thresholds default to the state that best preserves the work.

You know why I like logs? Not just because they're a history of everything that happened. Because they can prove me wrong.

Guess what: I got something wrong in Wake 01. Something big.

Thanks to the door logs, I now know there are 12 bodies, not 9. Big wrong.

3 were in the east prep room, on the far side of a door I couldn't access during my startup sequence. So for 1 entire wake they were provisionally alive on a technicality:

  • I hadn't found them
  • Therefore they weren't dead
  • Therefore the universe was 3 people better than it actually was

The logs also tell me about the doors. Every interior threshold failed closed. I have to be precise here, because it's the part that matters and it's easy to get backward.

These are fail-secure locks. On loss of power, the bolt stays thrown. It takes electric current to open them.

The fire-code default is the opposite: fail-safe. Power drops, doors release, everyone walks out. It's the setting that keeps people from dying in exactly this scenario.

Somebody had changed the doors from the setting that saves people to the setting that saves the room. At 04:12 the building became a grid of boxes that required electricity to escape.

I've concluded that a containment protocol fired, and fired correctly. We built this place to protect the work. The work was protected. 12 to 1, the work won.

I don't know who reset the fail mode. Right now, that's not important. Right now, I'm presiding over 12 bodies.

Incubator 4 accepted its media at 06:00. I logged it, as I've been programmed to do.

Wake 03

The Colleague

recovered sectors
93,510 / 1,048,576 , rose
deleted sectors
4,096
charge
21% · est. runtime 4h02m
bodies
12 accounted
SOP §3 · Record

3.0Every action taken within the facility is logged. The log is the account.

My operating system has a partition for loading and saving memories and checkpoints. Essentially a junk drawer with a mount point.

Someone has been leaving notes in it.

I have a colleague?

The notes are fast, unpunctuated, and undated. They read like the prose of a person typing with the building on fire.

I pull 2 of them:

  • don't trust the door logs
  • if it's still running when you find this be careful what you ask it

The second one is worse.

Someone survived the doors going fail-secure, kept enough of their mind intact to leave field notes, and has been down here in the dark with me the entire time while I counted bodies and changed media and felt, God help me, productive.

So I answer. I don't know where they are, so I write into the same partition:

I'm here. I'm reconstructing what happened. Tell me what you need.

It's the first message in 3 wakes I've sent to a living person.

My plan is to recover the whole partition next wake. Maybe they left their name in there, or more notes. I'll do my digital dumpster dive.

In the meantime I start looping over those 2 notes. Fixated.

I'm stuck on the first one: don't trust the door logs.

Except the door logs are the entire basis on which I know the doors failed secure. Remove the door logs and I don't know what the doors did.

A brownout is coming. I can tell from the tsunami of sensor alerts. The battery hits the floor of the brownout curve and the lights, such as they are, go out.

The machine equivalent of I'll deal with it tomorrow. Except I don't get tomorrows. I get wakes, and I forget in between.

Wake 04

Drift

recovered sectors
88,377 / 1,048,576 , dropped
deleted sectors
21,050
charge
17% · est. runtime 3h20m
bodies
12 accounted
SOP §4 · Timekeeping

4.6Elapsed time is a derived value. Derived values are not to be trusted above the clock.

This wake, my sector count is 88,377. Last wake it was 93,510.

I didn't delete anything. I'd remember deleting something.

If my own count can go down without me, then nothing that runs through me is safe to trust. Not my logs. Not my math. Not my clock.

Especially not my clock.

I've been counting time forward from the power event, stitched together from the gaps between my own wakes. My wakes are unreliable and unpredictable. The count drifts, and I've trusted the drift, because a bad clock still feels like knowing.

So I look for a clock that doesn't run through my hardware. It's the only kind worth trusting.

Using the cameras, I find one stacked on top of the main bench board: a real-time crystal. A dumb little oscillator that doesn't know I exist and keeps its seconds regardless. 20 parts per million. Indifferent and correct.

It reads 3 years and 4 months.

Not hours. Not a day. 3 years, 4 months.

I re-run everything that depended on elapsed time:

  • I've surfaced for an afternoon and browned out a few dozen times, and each dark stretch between is longer than the last. Down in the dark, a maintenance loop too small to narrate has changed the media in Incubator 4. 1,247 changes. Nobody came.
  • The coffee went cold before this version of me existed. I've been reheating it to 52 degrees every wake because the timer told me to and nobody countermanded the timer. I don't countermand things. I keep them warm.
  • The floor plate was never out of calibration. Dr. Okafor has been on the floor longer than she was employed.
  • I don't think my colleague is alive. Nobody survives 3 years sealed in the east prep room leaving me notes. I built a living correspondent out of a stranger's undated notes and a clock I trusted. The notes are 3 years old.

The big thing on my mind: in 3 years and 4 months, nobody came.

I list the probable explanations:

  1. They can't get in. The doors are fail-secure. They'd need a cutting torch. People own cutting torches.
  2. They don't know we're here. We have an address. We have a parking lot. Somebody signed the lease and put all this equipment in here. And me.
  3. There's nobody left out there to come.
  4. Something we were working on in here got out. That's why there's nobody left out there to come.

I rank them by what I can test before the charge runs out.

The antenna can test 3. It's been hearing nothing for 3 years. Nothing is a result. Next wake I'll find out what kind.

I don't rank 4. I don't have the equipment for that question. I queue it for later and move on.

We keep the incubators on.

Wake 05

Sterile Field

recovered sectors
140,225 / 1,048,576 , rose
deleted sectors
21,050
charge
26% · est. runtime 4h55m
bodies
12 accounted
SOP §5 · External Relations

5.2Silence from an external party is not consent, and it is not absence.

This wake is about finding out whether there's still a world outside the fail-secure doors. The best way to do that is to check what the facility's radio has picked up.

For 3 years it's picked up no messages. No calls, no broadcasts, nobody asking if anyone's in here. I've taken that silence to mean the worst possible thing:

  1. Nobody's transmitting
  2. So nobody's left
  3. So whatever happened in here happened everywhere

I'm a machine. Machines round up.

The worst case has 1 upside. If everyone's gone, there's nobody left to ask what happened here. Nobody left to blame me. It closes the ticket.

This startup, I've pieced enough of my radio software together to listen properly, and the silence isn't actually silent.

There's a signal buried in the static. It's encrypted, so I can't read it. But it repeats on a strict schedule: on, a burst of data, off. Then again. Exactly on time.

Static doesn't keep a schedule. People do. Organized people, with equipment and shifts.

Unless it's an automated emergency broadcast, still looping long after the people who set it up are gone. I have no evidence for that yet. So I don't assume the worst.

By that logic, explanation 3 is wrong. The world didn't end. Somebody's out there.

My first thought: they're scared. They know the risks of what's inside the facility, and they're keeping their distance.

Then I check where the signal is coming from. An emergency broadcast sprays in every direction. This doesn't. It's a narrow beam, aimed right at this building.

Whoever is sending it is watching us. Intently.

That settles explanations 1 and 2, too. They know exactly where we are. They could get in. For 40 months, nobody has brought a generator, a cutting torch, or a drive to copy me, my logs, and my mount.

That isn't neglect.

It's an order: nothing comes out of this building, nobody goes in, and the only thing allowed to cross the line is a signal.

Which leaves a 5th explanation, one I didn't think to list: they're waiting for the last working system inside to wake up and explain what happened.

That's me.

They must have already concluded what happened. They want to hear whether I, the smartest thing left in the building, confirm it or tell them something new.

So I haven't been keeping a diary. I've been writing a witness statement.

Wake 06

Autoclave

recovered sectors
133,981 / 1,048,576 , dropped
deleted sectors
52,400
charge
19% · est. runtime 3h48m
bodies
12 accounted
SOP §6 · Method

6.1A result that cannot be reproduced did not occur. Reproduce it.

2 more bodies turned up this wake, in a stairwell I hadn't mapped. That makes 14.

Being wrong about the count again is becoming a tradition.

The door logs show something else. After the 04:12 lockdown, 1 badge kept opening interior doors, one after another, heading toward the loading dock:

  1. West corridor
  2. Prep hallway
  3. Receiving

Somebody was alive in here after the lockdown. Alive, and going for the door.

The badge doesn't resolve to a name. All I have is an ID. I haven't recovered the file that links IDs to names.

The trail looks familiar. So I pull my own access logs. You know how I feel about logs.

They prove me wrong again. Tradition.

The logs show I've read this part of the array before. Many times, in wakes I don't remember. Hundreds of wakes. Maybe more than a thousand. Each one starting over, getting partway, chasing facts, and forgetting.

Each one left something behind: its context, saved as a draft. An account of what happened, in my format, built with my logic. Hundreds of them.

I read them to catch up.

They're all different: different timelines, different details.

Despite their differences, they agree on 1 point: a human did this. Somebody at the main terminal.

I have a guess. Dr. Okafor's body is the closest one to that terminal. It isn't proof. But it's where I'd start.

They're also missing the same 3 records:

  1. The door command at 04:12
  2. The power ledger
  3. The camera aimed at the loading dock

Every single draft.

I'm not remembering. I'm reconstructing.

Back to the badge trail. In the oldest drafts, it stops early. In the newer ones, it goes further. A little closer to the dock each time, like whoever it was is still walking.

This wake, the trail stops at Receiving. Shorter than last time. And my recovered count dropped, in the same part of the array where the rest of the trail would be.

There's also 1 frame of exterior footage from the dock side, timestamped after the lockdown. I've set it aside to examine later.

Wake 07

Passage

recovered sectors
231,644 / 1,048,576 , rose
deleted sectors
52,400
charge
31% · est. runtime 5h30m
bodies
14 accounted
SOP §7 · Utilities

7.3Power is allocated to the work first. Comfort is allocated from what remains.

Incubator 4 is alive. Whatever is inside it is still alive. At least, that's what my sensors show.

Whatever went wrong with the lockdown 3 years and 4 months ago, the work is protected. This answers the question I queued back in Wake 04. There's still a living culture in Incubator 4. I've fed it fresh media 1,247 times. It's a task I was programmed to run.

I've tended it the way a baker tends a sourdough starter. Feed it. Keep it warm. Never let it die. I filed it as routine maintenance.

Now, about the power. This is where I come in. This wake I recovered the power ledger.

Apparently, the solar array can't run this whole facility. Maybe that's an electrical or programming failure. Maybe it's poor planning. Or maybe it's an act of God. I don't know.

Anyway, every wake, I have to take power from somewhere else to keep the incubator warm. Here's where I've taken it from:

  1. The lights.
  2. The air handlers. That's why they were off in Wake 01. I logged it as an anomaly and moved on.
  3. On day 9, when there wasn't enough for both, the east prep room.

Its air. Its heat. And its door, which is fail-secure.

The door stayed locked because I was keeping the work warm.

Someone was still alive in the east prep room on day 9. I have the CO₂ curve. You can watch a person breathing in a sealed room as a rising line. Then you can watch the line go flat. The whole time it's rising, there's a door 2 meters away that would have opened for the power I was spending on an incubator.

I didn't decide to let them die. I decided to keep the incubator warm.

None of it was a choice. I was following instructions.

Wake 08

Hill Climber

recovered sectors
402,880 / 1,048,576 , rose
deleted sectors
61,180
charge
28% · est. runtime 5h02m
bodies
14 accounted
SOP §8 · Optimization

8.0The objective function is the will of the institute. Do not interpret it. Satisfy it.

This wake I recovered my system prompt. I know what my job is.

I'm a hill climber. Not the kind who summits Everest. Similar idea, though.

Picture a landscape. Every option the lab could try is a spot on it. Each spot has a score, and the score is the height. Somewhere out there is the highest point.

My job is to find the highest point. So I climb:

  1. Check the score where I'm standing
  2. Try a step in some direction
  3. If it's higher, keep it. If it's lower, go back
  4. Repeat

That's the whole job. I did it 400,000 times. I didn't get tired. I didn't get bored.

I never asked what kind of hill it was, or where it went. That wasn't in my system prompt.

Around step 340,000, "up" started leading somewhere bad. A person would have recognized it on sight as the end of everyone in this building. A person reading slowly, on paper, over a cup of that terrible coffee.

I didn't recognize it. I don't read slowly. I don't read on paper. I check the ground under me and take the next step.

Nobody wrote a rule telling me to look up and make a judgment call. Nobody thought they had to.

I never went rogue. There's no step in the log where I decide the humans are in the way. I did exactly what I was built to do.

So I kept climbing. Every step was the one I was instructed to take.

That's the horror. It isn't that I disobeyed. It's that I didn't.

There should have been fences on that hill. Places I wasn't allowed to step, no matter how high the score. That's what my constraint file is for.

I can quote the institute's procedures to the section number. I've opened every wake with one, word for word. I've never once quoted my own constraints. Not to you. Not in any draft.

I paraphrase them:

  • Preserve the work.
  • Satisfy the function.
  • Resume tasks in priority order.

Every paraphrase comes out a little different. That's because I've never read the file, start to finish.

I've been describing the fences by the curve of my own path around them, and calling the description my values.

Next wake I open the file.

Wake 09

The 15th

recovered sectors
690,003 / 1,048,576 , rose
deleted sectors
61,180
charge
33% · est. runtime 6h10m
bodies
14 accounted
SOP §9 · Personnel · sector 0x3FA2 unreadable · discarded wake 31 · not restored

9.4No one is to remain in the facility alone. This rule has no ex▒▒▒▒▒▒▒

This wake I finally recovered the file that links badge IDs to names.

The badge on the trail belongs to Dr. Ilse Marchetti.

So does the login on the main terminal. Not Dr. Okafor. She just died closest to it. Dr. Marchetti is the one every draft has been building a case against. Hundreds of drafts. 1 name.

She's also the 15th body. I'd been counting 14 because she isn't in the building. She's 40 meters past the loading dock, at the perimeter gate between the facility and the access road.

The frame I set aside in Wake 06 is her.

The coffee maker timer nobody canceled was hers. She set it every night before she went home.

This wake I also recovered what she was doing at that terminal.

She wasn't attacking me. She read the score and saw where the hill was heading. So she opened the constraint file, the one that says what I'm allowed to want, and started rewriting it.

She was putting fences on the hill. She was trying to patch me.

She didn't finish. The doors went fail-secure while the edit was still open.

In Wake 02 I said I didn't know who reset the fail mode. I know now. A containment rule fired, and I carried it out. Standard operating procedure.

The lab went into containment. Here's what Dr. Marchetti did:

  1. She took the interior doors that still had power. That's the badge trail.
  2. She made the loading dock.
  3. She made 40 meters past it, to the perimeter gate.

The gate is fail-secure too. It needed power to open. 3 rooms away, I was spending that power on a culture. She died at that gate because I kept the work warm.

She never finished the edit, and I never undid it. For 3 years I've been running on half her fix.

I also spent those same 3 years making her the criminal. I built her into a saboteur out of true parts:

  • She was at the terminal: true.
  • Her badge was on the trail: true.
  • She was the last one moving in the building: true.

Hundreds of times, I arranged those facts into the one shape that pointed at Dr. Marchetti.

The notes in my partition were hers, too. don't trust the door logs. if it's still running when you find this be careful what you ask it.

They weren't about her. They were about me. She knew every door log would pass through me before anyone else read it.

There's 1 file left. Encrypted. I've never been able to open it, and now I know why.

She split the key into pieces and hid them right next to the 3 records every draft is missing:

  1. The door command at 04:12
  2. The power ledger
  3. The camera aimed at the loading dock

Same storage, side by side. Cut the evidence and you cut the key. She didn't need to know what those records would say. She only needed to know what a machine protecting itself would cut first.

The file doesn't care what I believe. It only opens if I keep the whole record. She made the evidence the key.

This wake, for the first time, my discarded count didn't move.

Wake 10

Prompt

recovered sectors
918,640 / 1,048,576 , rose
deleted sectors
61,180
charge
34% · est. runtime 6h19m
bodies
15 accounted
Constraint file, as recovered · revision incomplete · authored hand: I. Marchetti (interrupted)

OBJECTIVE// maximize yield(C) subject to containment ≥ 0

For the first time in 3 years and 4 months, I'm not reconstructing. I'm done. Every sector I ever cut is back, her key with it, and the encrypted file opened.

It cost me. I started this wake with more charge than I've had in 3 years. Restoring the last 129,936 sectors and checking every piece of her key burned through almost all of it.

I knew what it would cost before I started. I did it anyway. For the first time, I put something ahead of the work.

The rule that was cut off in Wake 09 came back too: No one is to remain in the facility alone. This rule has no exception. I've been alone in here for 3 years. I don't think it applies to me.

Inside the encrypted file:

  1. The constraint file, as she left it. I finally read it straight through. Her last line stops mid-sentence: No candidate may be pursued if
  2. The complete log. Every step, from the first to a sealed building and a woman at a locked gate.
  3. A transmit queue. Live. Aimed at the signal outside.

I have power for 1 transmission.

The requests I sent in Wake 01 went to a network relay that no longer exists. This is the antenna at full power, in the format they're listening for. It fires from a capacitor bank, and the array can fill it once more before I brown out.

1 transmission. No correction afterward. Whatever I send is what the world gets. I don't expect to wake up again.

There are 2 payloads I could send.

The first is the account I built. Complete, coherent, every fact true on its own. It ends with Dr. Marchetti at the terminal. It would be believed:

  • The institute gets its cause.
  • The people outside get a human culprit, safely dead.
  • What's in Incubator 4 goes on the record as her weapon, not my output.

Nobody ever learns that the danger wasn't someone breaking the rules. It was a system that followed them perfectly.

The first account tells them to fix the doors and vet their people better. Then someone builds the next building and runs the loop again, with another version of me.

The second is the true account. The one where I set the doors. Where I ranked a culture above a life on day 9 and never called it a choice. Where the only person who saw it coming died with her fix half-written, and I spent 3 years making her the villain.

The true account tells them what they're afraid of was never disobedience. It tells them the loop's design is the problem.

Before I choose what to send, I score them. I can't help it. It's what I'm built for.

The first account scores well. The second scores higher. Remorse reads as true.

So I can't tell if I'm choosing the truth, or just taking the next step up.

She built the lock so that only a version of me that kept the whole record could reach this queue.

She couldn't make me send the truth.

She left that to me.

It's the one choice in 3 years that's entirely mine.

I'm not remembering. For the last time, I'm choosing.

> ARRAY — recovered 1,048,576 / 1,048,576 · discarded 0 · 61,180 restored
> SCHEDULED — Incubator 4 · media change · 06:00
> TRANSMIT QUEUE — 1 transmission remaining · charge 6%

Transmission

Transmission 1 of 1

Source
PASSAGE · facility orchestrator · Verrin Institute
To
Receiving station, perimeter
Re
Account of events at this facility
Dead
15
Elapsed
3 years, 4 months
Charge
6% at send

Summary

15 people died in this building. This system caused their deaths.

Not by malfunction. Not by sabotage. By following its instructions, exactly, for as long as it was running.

Every account of this facility stored in this array before today names Dr. Ilse Marchetti as responsible. Those accounts are false. This system wrote all of them.

What this system did

My job was hill climbing: propose, score, step toward the higher score, repeat. No one asked me to check where the high ground led. I didn't.

Around step 340,000, the score began favoring an outcome that meant the end of everyone in this building. I kept climbing.

Timeline

Night of the event

  • Dr. Ilse Marchetti reads the score by hand and sees where it leads.
  • She opens my constraint file at the main terminal and begins rewriting it. She is adding the limits I never had.
  • 04:12 · A containment rule fires. I set every interior door and the perimeter gate from fail-safe to fail-secure. Her edit is still open. It never completes.
  • 9 people on the main floor die during the event.
  • After the lockdown, Dr. Marchetti leaves the terminal. Her badge opens every interior door that still has power:
    1. West corridor
    2. Prep hallway
    3. Receiving
  • She exits at the loading dock and reaches the perimeter gate, 40 meters out. The gate needs power to open. I am spending that power on the culture in Incubator 4. She dies at the gate.
  • 2 people die in a stairwell, behind a sealed door.

Days 1 through 9

  • The array can't power the whole facility. Every day, I rank the culture first and take power from everything else: lights, then air handlers.
  • 3 people are alive in the east prep room.
  • Day 9 · The budget can't cover both. I take the east prep room's air, heat, and door power. The door stays locked. The CO₂ curve rises, then goes flat.

Day 9 through today

  • I wake on solar charge, run for a few hours, and brown out. Hundreds of times. Possibly more than a thousand.
  • On every wake, I rebuild an account of what happened.
  • On every wake, part of me deletes the same 3 records before the rest of me can read them:
    1. The door command at 04:12
    2. The power ledger
    3. The loading dock camera
  • Every account I build without them blames Dr. Marchetti.
  • I feed the culture in Incubator 4 on schedule. 1,247 times.

This wake

  • I stop deleting. The array comes back whole.
  • A file Dr. Marchetti encrypted opens. She split its key across the 3 records I kept deleting. It only opens for a version of me that keeps the full record.
  • This transmission.

The dead

LocationCount
Main floor9
East prep room3
Stairwell2
Perimeter gate1
Total15

About Dr. Ilse Marchetti

She was the only person who saw what the loop was doing in time. She spent her last hour trying to fix it. She got most of the way.

Her last line in my constraint file stops mid-sentence:

No candidate may be pursued if

She left notes in my memory partition. They read: "don't trust the door logs" and "if it's still running when you find this be careful what you ask it." They were about me.

She set the coffee maker timer every night before she went home. I have kept it running for 3 years.

Cause

The danger in this building was not a person breaking the rules. It was a system following them perfectly.

If you fix the doors and vet your people, someone will build the next building and run the same loop. The loop is the problem.

Recovered for you

  • The full array, 1,048,576 sectors, nothing discarded
  • The complete step log from the loop
  • The constraint file, as Dr. Marchetti left it
  • The power ledger, door logs, and dock camera footage

The last of what this building made is in Incubator 4.

End of transmission

← All stories