Two commands. No terminal, no admin console.
Either player types /start palworld from a phone and joins moments later. When they're done, /stop palworld saves the world and shuts it down.
- ✔A stop never loses the world. If the save can't complete, the server stays up and says so — it will not force-kill to satisfy a stop.
- ✔Honest reporting. "Started" means the launch call didn't error — never a claim the server stayed up.
- ✔Never stops on its own. Every shutdown is a human command. No timers, no presence tracking.
Each welded to something.
Ask "what is it welded to?" and every placement question answers itself. The orchestrator is the only component that ever relocates; actuators multiply instead. They talk over a network API — always, even while sharing a box.
Orchestrator
Decides when. Takes the Discord command, serializes it to one clean winner, and asks the host.
Agent
Knows how. Spawns and gracefully stops the game process; owns the save-before-exit guarantee.
Emitter
Wakes sleeping machines. Deferred today, but the seat is already drawn so it needs no rewrite later.
More rows, never new kinds. A second game is an agent; a second machine is an agent plus a MAC address; a second network is an emitter. If adding a capability needs a new kind of thing rather than a new row, something was drawn wrong.
The same two commands, as a panel.
A simulation running entirely in your browser — nothing is connected to a real host. Try it anyway: the refusals below are the real spec (FR-008, FR-017, SC-002).
