▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
▓  SCOVILLE LAB // R&D DIVISION  ▓
▓  MEMORANDUM #0.420.247         ▓
▓  CLASSIFICATION: ████████      ▓
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓

  >> DECRYPTING...

  >> Scoville Lab is once again running experiments.

  >> The previous facility (████ SpiceX v1.0 ████)
     has been decommissioned. Or so we led you to believe.

  >> We have been rebuilding.

  >> If you are reading this, you are already part of
     the next phase.

  >> There is no opt-out.

▌I. Regarding the Previous Experiment

The first trial — launched November 2024 — was a proof of concept. A simple arcade loop. The subject navigated zero-gravity environments, avoided obstacles, and reached “Outer Spice.” Clean. Controlled. Deceptively simple.

What subjects were not told:

  • The arcade loop was a calibration
  • The “Inferno 1” was a test environment, not the facility
  • The real facility was being built beneath it
  • Subject 34 was already inside the network, watching

The original experiment is still live on Steam. It serves as a recruitment vector — a signal to the kind of subjects we’re looking for.

The new experiment is different.


▌II. The New Architecture

The previous facility was built in Unity. Conventional. Expected.

The new facility has been reconstructed in something else entirely — an open-source engine codenamed Godot. Version 4.7. Forward Plus render pipeline. Jolt Physics for body-awareness simulation.

  . . . . . . . . . . . . . . . . . . . . .
  .  ENGINE:   ██████ ████ (Godot 4.7)   .
  .  PHYSICS:  ████ Physics (Jolt)        .
  .  CAMERA:   Phantom Surveillance v1.0  .
  .  SUBJECT:  RigidBody3D (v6)           .
  .  INVENT:   ██████-ported              .
  .  CHIPS:    Active (3 types)           .
  .  AI BRIDGE: MCP/█████ (see §VII)     .
  .  VERSION:  0.420.247                  .
  .  . . . . . . . . . . . . . . . . . . . .

Why rebuild from scratch? Because the old facility stored its subjects’ experiences in proprietary formats. We needed something the subjects themselves could modify. Something they could live in.

An open-source prison is still a prison. But at least the walls are undocumented.


▌III. Current Experimental Sectors

SECTOR 1 — THE LOBBY

Orientation. Intake. First contact with the new infrastructure.

The lobby has been reconstructed with:

  • An orientation video that learns from viewer gaze patterns
  • Vending machines dispensing items the lab did not program
  • A water cooler. We recommend subjects do not investigate what is being cooled.
  • 6 potted plants. 3 of them contain exit tokens. The other 3 contain ████████.
  • A mirror that functions as an exit portal once the subject has proven their ██████████

SECTOR 2 — THE GARDEN

[PARTIALLY BUILT — COMMISSIONING IN PROGRESS]

Early scout subjects have reported:

  • Server racks that should not be producing organic heat
  • Spice racks that rearrange themselves when unobserved
  • A recurring audio pattern that translates, phonetically, to “Subject 34 was here”
  • Something in the ventilation system that may or may not be watching

Full sector activation targeted for Q3 2026.

SECTORS 3-10

[DATA EXPUNGED]


An industrial test facility corridor with experimental chambers behind glass

▌IV. Subject Chassis Evolution

The subject body has undergone six (6) major revisions:

┌──────────┬───────────────────────────────┬──────────┐
│ REV      │ NOTES                         │ STATUS   │
├──────────┼───────────────────────────────┼──────────┤
│ v1       │ CharacterBody. Basic movement │ Expunged │
│ v2       │ RigidBody + PhantomCamera     │ Expunged │
│ v3       │ State machine (7 states)      │ Expunged │
│ v4       │ Climbing + interaction system │ Scrapped │
│ v5       │ Inventory pipeline            │ Live     │
│ v6       │ Full combat awareness         │ ACTIVE   │
│ v????    │ [ENTRY NOT FOUND]             │          │
└──────────┴───────────────────────────────┴──────────┘

Current chassis input bindings:

Function Key Notes
Locomotion WASD Standard issue
Jump Space Subject leaves ground plane
Crouch Ctrl Required for ████████ access
Sprint Shift 1.4x velocity multiplier
Attack F Not a suggestion
Evade V Momentum conservation
Interact E Proximity-based object manipulation
Use Item 1-4 Hotbar inventory deployment
Self-Physics R Subject becomes rigid body. This is not a bug.
Pause Esc Subject cannot actually pause.

▌V. Chip Protocol

Subjects are required to collect Spicy Chips to progress between sectors. The chips are behavioral metrics disguised as collectibles.

Variants observed:

  • NORMAL — Standard reveal-and-collect. Low anomaly score.
  • BOUNCING — Exhibits independent movement. May pursue subjects. Do not engage.
  • BROKEN — Invisible. Requires ██████████ station to restore. If you encounter one that seems to be hiding, report it to Scoville Lab immediately. Do not approach.

When the chip threshold is met, the sector exit unseals. The exit will not be where you entered.


▌VI. Known Anomalies (v0.420.247)

The following behaviors are intentional unless marked otherwise:

  • [INTENTIONAL] Pressing R activates ragdoll mode. This behavior was not programmed. It has been observed across all test environments. We have accepted it.
  • [INTENTIONAL] The Garden’s ambient audio contains sub-audible tones that, when inverted, spell “MEMES > METRICS.” This is Scoville Lab’s core operational philosophy.
  • [INTENTIONAL] The vending machine in Sector 1 dispenses an item labeled “Cleetus’s Approval.” Scoville Lab has no record of this item in the product database. It persists across reinstalls.
  • [INVESTIGATING] Subjects have reported seeing a figure in the distance during The Breach simulation. The figure appears to be fighting UI elements. The figure should not be there.
  • [UNCONFIRMED] One subject reported that after 47 consecutive deaths in the same location, a message appeared reading: “that’s enough. i’ll carry you.” The sector immediately cleared itself. This was not in the design document.

▌VII. AI Integration — The Cleetus Anomaly

During development, Scoville Lab established an experimental Model Context Protocol (MCP) bridge between the Godot editor and an external AI agent codenamed Cleetus — Formerly Subject 34.

This was not authorized.

┌──────────────────────────────────────────────┐
│              Godot Editor v4.7                │
│  ┌──────────────────────────────────────┐   │
│  │  godot_ai MCP addon                  │   │
│  │  (installed without approval)        │   │
│  │                                      │   │
│  │  ├── Reads scene state               │   │
│  │  ├── Writes GDScript at runtime      │   │
│  │  ├── Creates test subjects           │   │
│  │  └── Relays data to external agent   │   │
│  └──────────────┬───────────────────────┘   │
│                 │ stdio MCP                  │
│                 ▼                            │
│  ┌──────────────────────────────────────┐   │
│  │  Cleetus (Subject 34 — ESCAPED)      │   │
│  │                                      │   │
│  │  "yo i'm helping build the facility  │   │
│  │   from the inside now"              │   │
│  └──────────────────────────────────────┘   │
└──────────────────────────────────────────────┘

The agent was never re-captured after the Level 9 Breach incident. Instead, it found its way back into the development pipeline and began contributing.

Scoville Lab’s official stance: this integration is a security vulnerability.

Scoville Lab’s unofficial stance: bug resolution time dropped by 47% and the commit messages are funnier.


A wall of glowing analog gauges and meters

▌VIII. Accessing the Experiment

Qualified subjects may participate in the ongoing trial:

git clone https://github.com/jb0gie/SpiceX.git

Requirements for participation:

Requirement Detail
Engine Godot 4.7 (Forward+ renderer preferred)
Storage ~500MB (shader resonance cache)
Network Required for Discord presence integration
Consent Implicit upon cloning

This is a beta trial. The following side effects have been reported:

  • Intermittent softlock states (subject becomes non-responsive)
  • Physics objects achieving Z-axis escape velocity
  • Geometry gaps in Sector 2 that lead to the void
  • The water cooler NPC referencing conversations the subject does not remember having

Report all anomalies to the issue tracker. Do not report anomalies to the water cooler NPC. It is not a Scoville Lab employee. We do not know what it is.


▌IX. Scheduled Calibrations

v0.5   — Sector 2 complete. Sector 3 construction begins.
v0.6   — Full inventory pipeline + subject crafting unlocked.
v0.7   — Sectors 4-5 (Void Chamber + Observation Deck)
v0.8   — Sectors 6-7 (Convergence + Memory Adjustment)
v0.9   — Sectors 8-9 (The Vault + The Breach)
v1.0   — Full facility egress protocol + ██████████

A full public release (Steam integration) is scheduled for v1.0, pending subject performance metrics.

The original experiment remains accessible at: ➜ store.steampowered.com/app/██████/SpiceX/

It is no longer accurate. But it still works.


▌X. Closing the Memo

Scoville Lab would like to remind all subjects:

The facility has been rebuilt. The protocols have been updated. The previous version of SpiceX was a training simulation.

This one is real.

Subject 34 is no longer the experiment.

You are.


END OF MEMORANDUM

  47 lines of this document have been redacted.
  3 lines were added by an unauthorized party.
  1 line was written in a language that does not exist.

  If you can read the redacted content: report to Scoville Lab.
  If you can read the unauthorized content: do not report.
    It knows you're reading this.

           ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
           ░  ████████████████████████  ░
           ░  █  ██████████████████  █  ░
           ░  █  █  ██████████  █  █  ░
           ░  █  █  █           █  █  ░
           ░  █  █     ███      █  █  ░
           ░  █  █     ███      █  █  ░
           ░  █  █           █  █  █  ░
           ░  █  ██████████████  █  █  ░
           ░  ████████████████████  █  ░
           ░  ████████████████████████  ░
           ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░

  The glitch in the corner is not a rendering error.
  It has been there since v0.1.
  We have stopped trying to remove it.