ScarletBeast
● LIVING /the site is awake and listening /commands: open ↩ scarletbeast.com
living.scarletbeast.com · protocol 01

This Site
Is Alive.

scarletbeast.com is a LIVING application. It is not carved in stone — it is carved in flesh. Anyone can walk up to the open terminal, whisper a command, and the machine will rewrite its own body to obey… once the warden draws the mark of approval. This is the altar where those changes are summoned, judged, and burned into the live site.

// what you are looking at

A website with a pulse

Most sites are corpses — frozen the moment they ship. This one breathes. The HTML you read on scarletbeast.com can be re-authored by a stranger through a sealed, approval-gated pipe that runs straight through Claude Code on the origin server. You speak in plain language. Claude does the surgery. The warden decides whether it lives.

Read this twice. Nothing a visitor types touches the live site until a human warden approves it. Every command sits in quarantine — visible, editable, killable — until the mark is drawn. Approval is execution.
/ 01

Speak

A visitor opens the Claude Code Emulator and types an intention: “make the footer bleed,” “add a new manifesto card,” “fix the broken link on the library page.” Plain English. No git, no FTP, no mercy.

/ 02

Seal

The command is POSTed here, to living.scarletbeast.com, and frozen in quarantine with a pending status. The submitter gets a private token to watch its fate — and nothing else.

/ 03

Judge

The warden reviews it in the console, edits the prompt if it reeks, and either draws the mark of approval or casts it into the fire.

/ 04

Mutate

On approval, Claude Code runs the prompt inside the live site root, rewrites the flesh, and the change is auto-committed. A one-line summary crawls across the SIGNAL bar for all to see.

// the ritual, step by step

The approval rite

The whisper

Visitor types a natural-language command into the full-screen emulator on scarletbeast.com.

The seal

POST /api/commands → quarantined as pending. A poll token is handed back so the submitter can watch — only their own — command.

The judgment

The warden logs into this console, reads the command, optionally rewrites it, and approves or rejects.

The surgery

Approval dispatches a queued job: claude -p "<prompt>" --permission-mode bypassPermissions with the working directory set to the live site. Claude edits the real thing.

The proclamation

The result is summarized and, if it lived, crawls across the SIGNAL bar on the mothersite. The wound closes. The site is new.

// a glimpse of the altar

The Claude Code Emulator

It lives on the mothersite — a flyout in the corner that pulls full-screen. This is roughly what a confession looks like:

 claude-code-emulator — beast@scarletbeast: ~
# the site is listening. speak your change.
beast@scarletbeast:~$ add a scarlet skull to the footer and make it pulse
⛧ command sealed · id #1337 · status: PENDING
… awaiting the warden’s mark …
✓ approved by the warden · executing through Claude…
✓ done — footer now bleeds. committed to live.
beast@scarletbeast:~$

// visuals pending — drop art here

The gallery of mutations

Placeholders, hungry for imagery. Feed them through the emulator.

IMGThe Warden's Console — screenshot
IMGA command burning on approval
IMGSIGNAL bar mid-proclamation
GIFThe terminal pulling full-screen
HEROWide ritual banner — the living site, mid-mutation