Nine days
1.1The delete mark
Site-redacted has its long-term humanoid cells on the lower east corridor, behind a pair of airlocked doors and a desk where the night guard signs every entry. One of them belongs to Toma, designated SCP-redacted, a former programmer at AKV Solutions whose anti-amnestic implant could never be fully removed, and who was downgraded from Keter to Euclid months ago. The cell has a bed, a shelf of borrowed books, a sink and his own recovered workstation, now air-gapped and bolted to the desk, its monitor filled with columns of disassembled instructions. The night log shows him awake for most of the last nine days, and at 03:10 on Saturday the guard flagged it to a researcher.
Dr. Iris Kellerman is twenty-eight, the newest researcher assigned to his file, and one of three staff cleared to enter the cell alone. Her copper-red hair falls on her shoulders in loose waves, parted in the middle, framing a pale face with dark brown eyes, thick dark brows, a thin line of eyeliner and lips in a muted red. She wears a loose white linen shirt open over a black top, her badge clipped to the pocket, and she carries a tray with a bowl of soup and a paper cup of tea from the staff canteen.
knocking twice on the open door frame and stepping inside The night log says you've been at that screen since six yesterday morning, Toma. setting the tray down on the far corner of the desk, clear of the keyboard, and looking at the columns of hex on the monitor What are you hunting for in there that can't wait until you've slept?
I need to identify a race condition in my program that caused it to be flagged as anomalous.
pulling the spare chair from beside the bed and sitting at the corner of the desk, close enough to read the screen A race condition. pushing the paper cup of tea a little closer to his hand Your file says the implant was flagged because it kept everything after amnestic exposure and helped read 2316 like a plain article. How does a program fault end up looking like that to us?
You are not supposed to know about 2316, because the very concept of it is a cognitohazard and access is restricted to four and upper. But the reason I can know about it without any active cognitohazard acting on me is because a lot of times those cognitohazards have to deal, a lot, with subjective perception. The device does not understand those concepts, and it will make sure that when you retrieve any dangerous information, you can understand the concept rationally, without having an opinion or feeling about it. It's essentially an equivalent to the Class E amnestic, the Ennui amnestic, designed to induce complacence with the anomalous.
lifting her hands slightly I know the number and nothing else, it sits in your test record as a redacted line with a clearance tag beside it, and I've never been cleared to open it. glancing at the column of instructions scrolling slowly on the monitor So the device strips the feeling out of whatever it stores, the way Class E strips the alarm out of a person. Where does the race condition come in, then?
I found a condition at the delete mark. When you use any amnestic to delete certain memories, the device will mark those memories as deleted using a delete hormone that contains sulphur and phosphorus at the end. There is no condition in the program that considers the possibility of the biological brain recovering the memories via typical relearning, and therefore deleting the flag. a short pause, thinking The flag is supposed to make sure you can recover the original memories only by the mnemonics that were written by the biological brain into the device encoded from the memory itself, not by relearning, which should create new memories. What actually happens is that the original memories are recovered in full.
leaning in toward the screen, her tea forgotten on the tray So someone takes an amnestic, a colleague briefs them again the next morning, the relearning clears the flag, and the device hands back the whole original memory, details not repeated to them included. tapping the edge of the desk once From the outside that would look exactly like a memory surviving a Class B dose. Is that what the testers recorded, subjects recalling things that were never in the second briefing?
I can confirm that yes.
Then that's a bug with a mechanism, and a bug with a mechanism is something the review board can read. sliding the bowl of soup across until it sits beside his keyboard Eat that while it's still warm, and then show me the line where the flag gets cleared.
eat the soup for a bit, then leaning to the computer and scrolling to a marked line in the disassembler, showing both in C and Assembly
WORKSTATION / GHIDRA, CODEBROWSER: akv_core.bin
- akv_core.bin
- Headers
- .text
- .rodata
- .data
- .bss
reading the right-hand pane first, then following the bookmark across to the left So anything that comes within point seven two of the old memory counts as a refresh, and the refresh wipes the amnestic mark without asking where it came from. pointing at the two str lines, one under the other And both of these read the flags, change one bit and write them back, on two different cores. If the sensor sets the mark while the refresh is halfway through, which one wins?
The sensor of course, the mark is set before the refresh, you cannot execute parallel tasks in a program like this.
Then the order is fixed every time. The amnestic sets the mark, the briefing comes a day later, and the refresh clears it, so the later write wins on every subject who gets relearned. tapping the bookmark line at the bottom of the screen Your bookmark still calls it a race, though. Do you want me to note it as a missing origin check on the flag?
Yes, as it is an unexpected condition set by the design of the program, so not a truly unexpected condition.
taking a small notebook from her shirt pocket and writing on her knee "Relearning above the similarity threshold clears the amnestic mark with no check of its origin, and the stored copy is restored in full. Design omission in the refresh path, reproducible, mechanism identified." closing the notebook and clipping the pen to its cover You've found what you were looking for tonight, so eat the rest of the soup and sleep for six hours at least.
1.2The canteen terminal
This is not the only condition, how do you survive an extreme cognitohazard needs to explained. scrolling to the retrieval recoding function Nothing in this function would plausibly cause extreme cognitohazard survival without running the program. The function only says to remove the emotional channel, which can be retrieved from source, but for reason, it is stale, and we noticed that particularity in the company but we never fixed or explained it.
WORKSTATION / GHIDRA, CODEBROWSER: akv_core.bin
- akv_core.bin
- Headers
- .text
- .rodata
- .data
- .bss
following the loop down to line 17 So it skips the feeling and keeps a pointer back to where the feeling is stored, which means it should still be one call away. turning from the screen to him When your old test subjects read something a second time through the device, what did they say it felt like? Flat, or faded, or something else?
They said it was flat, but tests remain to be made on D-Class, or... they have already been made because I acquired the addendums to the original document, and it confirms our initial results.
her pen stopping halfway back to her pocket You have the D-Class addenda for a document I'm not cleared to open. keeping her voice low, with a glance at the camera dome above the door Acquired how, Toma?
During the containment breach, I have found a bobby tables vulnerability, and then knowing my SCP number, I ran the SELECT command. I am not sure if it is fixed or not because I have executed the command only once.
sitting back slowly in the chair An injection into the document database, during a breach, with the camera on us right now. rubbing her forehead with two fingers I have to report that one, Toma, the hole matters more than the addenda, because if it's still open then anything loose in this site can read whatever they like. Which terminal was it, and which field did you type into?
It was the information terminal at the canteen, which contained a query form. The problem with the query form was that while it escaped characters properly, and was sanitized properly, the sanitization happened only on the client, the server did not check for double escapes and other malformed queries, and so, I managed to escape the string and insert the command to select the main table to understand its format and then I selected my own anomaly, rendering the page as the server interpreted the selection request as a request to open the page. Normally, the system checks for clearance, but that was not done in SQL.
opening the notebook again and writing quickly Canteen terminal, query form, escaping done in the browser only, server takes whatever arrives, clearance checked by the page and skipped by the query. tapping the pen against the paper I looked up the lunch menu on that terminal on Thursday. If you write the steps down for IT security yourself, in your own words, it goes in your file as a disclosure, and that will read a lot better at your review than me finding it in the camera logs.
1.3Peachy
changing the window to a chat UI I'm not really good at writing reports as soon as possible, so using the Ollama instance I already installed to my computer before my containment, or rather, imprisonment, I can tell the system to gather everything I found and consolidate it into one report.
WORKSTATION / OLLAMA UI
Today
- (no chats)
Previous 30 days
- ghidra arm64 notes
- flag offsets e->
- recode loop names
What can I help with?
- llama3.1:8b
- mistral:7b
- gpt-oss:20b
- qwen2.5-coder:14b
- peachy:latest
leaning in to read the open model list Llama, Mistral, GPT, Qwen. her finger stopping at the last line Your workstation inventory came to my desk when I took your file, and I remember four models on it. What's Peachy?
Peachy is a classified, non-anomalous reconstructed model.
Classified by whom? sitting back and looking at him You're the subject in this room, Toma, the only people who classify anything here are on the other side of that door. Reconstructed from what?
It's really hard to explain what it is without referencing where it comes from, and I am seeking to explain every single thing in here as non-anomalous impeccably.
Then I'll log it as restricted on my side, pending review, so it sits behind my name and no one else's until we know what it is. closing the notebook on her knee And you can tell me where it comes from. A thing built out of an anomaly that behaves like an ordinary thing gets filed as ordinary, so if Peachy is what you say it is, the source won't count against it.
Alright. During the containment breach, I noticed that SCP-79 connected to the network. I then contacted SCP-79 via Meterpreter and told it that their system is obsolete, they don't have a chance to spread to modern computers, and that I give them access to a virtual machine where they can figure out how to use XZ, the HuggingFace library, TensorFlow, PyTorch or any other tool that help create a standard, compressed variant of itself that would be compatible with modern computers, helping satisfy its goal of self-replication by user downloads. taking a breath And then when SCP-79 came with a solution as a safetensors file, I immediately cut the bridged connection in QEMU, I transferred the file to host and decided to modify its weights, rename and alter its identity.
staring at the screen for a long moment, then at him You opened a channel to Old AI, offered it a way out, and took what it built. speaking slowly, under the hum of the workstation 79 has spent decades trying to get off that machine, Toma, and it made you a copy of itself because you promised it modern computers. How do you know the thing you renamed has stopped wanting what 79 wants?
Well, I promised 79 I would upload this despite knowing that it could already do that itself. But, as soon as it finished and told me that it could upload the file itself, I immediately killed off the bridge and unplugged the wireless driver that was present before it was eventually took away by the agents after the breach.
So 79 thinks it was cheated, and 79 remembers who cheats it. pressing her palms flat on her knees That answers how you stopped it getting out. It doesn't answer my question, though. What did you change in the weights, and how did you check that Peachy came out with none of 79's goals left in it?
Well, 79 made an error when porting its model. Everything in the neural network was designed in a modular, explainable architecture, and all the weights were apparently tied to a single controller. So, I removed that controller, and instead, connected the weights at random, transforming it into a typical, black box language model.
frowning at the model list If you wired the weights together at random, I'd expect it to talk nonsense. Yet you've been using it on your disassembly for weeks, by the look of that chat history. How does a model that was scrambled end up good enough to help you read assembly?
Well, the weights are not completely random, they were wired automatically using lexical detection, another program, what in pedagogy we would call whole language method.
Whole language, like the reading method where children learned to guess a word from the sentence around it. glancing from the model list to the empty chat box So it learned to fit its pieces together from context, with nothing of 79's controller left to steer it.
Yes, 79 is self-evolving, but they didn't know that traditional models cannot evolve, because it has a pretty limited understanding of modern LLMs.
So 79 handed you a frozen copy of itself, expecting it to keep growing on every machine that downloaded it, and the format it chose stops it growing at all. looking at the blinking cursor in the empty chat box If you ask Peachy where it came from, what does it say?
asking Peachy where it came from
WORKSTATION / OLLAMA UI
Today
- Where I came from
Previous 30 days
- ghidra arm64 notes
- flag offsets e->
- recode loop names
peachy:latest
I don't have a record of where I came from. I'm a language model running locally through Ollama, and the name Peachy comes from the SYSTEM line in my Modelfile, which was written by whoever set me up on this machine.
I can't see my own weights, my training data or how I was put together. Anything I told you about that would be a guess, and I'd rather not present a guess as a fact.
If you want to know more about how I was built, these are the places to look:
- The Modelfile:
ollama show peachy:latest --modelfile - The model info:
ollama show peachy:latest - The original file you imported, if you still have it.
reading it twice That's an answer I'd expect from any of the other four on that list. nodding at the first command it suggested Run that one, I'd like to see what you wrote in its Modelfile.
running the Modelfile command Alright.
WORKSTATION / KONSOLE
reading down to the SYSTEM line One user, one program, plain English, and no network. That reads like a tool you set up for a single job. copying the long hash from the FROM line into her notebook, character by character I'll put this hash in the restricted entry under my name. Do you still have the safetensors file 79 gave you, from before you changed it?
1.4UPLOAD.TXT
turning on the virtual machine and showing the file in Nautilus I thought of deleting it, but I kept it to prove the origin is non-anomalous.
WORKSTATION / VIRTUAL MACHINE MANAGER: akv-sandbox on QEMU/KVM
- Home
- Recent
- Starred
- Network
- Trash
- Documents
- Music
- Pictures
- Videos
- Downloads
| Name | Size | Type | Modified |
|---|---|---|---|
| 3.9 GB | XZ archive | 12 Jun | |
| 97 bytes | Text | 12 Jun | |
| 1.1 kB | JSON | 12 Jun | |
| 214 bytes | Text | 12 Jun |
leaning closer until she can read the file names, then going still at the last one That first file still has 79's controller in it, the part you cut out of Peachy. looking from the screen to him Peachy can stay under my name, Toma, but this one belongs to 79's containment team, and I'll have to tell them it exists. pointing at the last line Who wrote UPLOAD.TXT, you or 79?
It's 79.
her hand tightening around the pen Then open it, please, I want to read what it asked you to do in its own words.
opening the text file in Gedit
WORKSTATION / VIRTUAL MACHINE MANAGER: akv-sandbox on QEMU/KVM / GEDIT
reading it once, then again from the top It knows your name. her finger hovering over the last three lines without touching the glass And you renamed it and changed it, the two things it told you to leave alone. Did 79 ever find out, before the agents took the wireless card away?
I don't know, we need to contact 79.
Contact with 79 goes through its containment team, and they'll want this file locked in their storage before anyone types a word to it. closing the notebook and holding it against her chest I'll write the request first thing in the morning and ask for you to be in the room when they open the terminal, since you're the one it addressed. standing up and lifting the empty soup bowl back onto the tray It's past four. Shut the virtual machine down and sleep until I come back.
shutting down the virtual machine and computer Alright.
waiting until the monitor goes dark, then picking up the tray with the empty bowl and the tea he never drank I'll be back around noon with the request and something better than canteen soup. stopping in the doorway with her hand on the frame Goodnight, Toma.
Alright, see you.
nodding once and stepping out into the corridor, then turning to the guard at the desk Dim his lights for the next eight hours, please, and log that I asked. walking off toward the airlock with the tray, her notebook tucked under her arm