Multi-user rebuild

Run the campaign from one command console while every player connects to the same live state.

This version is rebuilt for multiple people on different devices by saving campaign state to a server-side JSON endpoint instead of browser-local storage.

GM checklist

  • Pick 3–5 active roles.
  • Choose entry, midpoint, and finale values.
  • Set the public brief and mission status.
  • Advance the mission clock when delay, bloodshed, or network intimacy escalates the situation.
  • Use outcomes as the final argument map, not just a result table.

Broadcast preview

0Active roles
0/6Mission clock
—Strongest ending
0Truth pressure

Role selection

Every character uses a different retro-signal color identity.

Story builder

How to run the story

Act I rule

Make the players understand why humanity said yes in the first place. The Y2038 collapse must feel catastrophic enough to justify the first surrender.

Act II rule

Do not present the machine city as cartoon evil. It must be beautiful, orderly, efficient, and morally unbearable.

Act III rule

The final boss is the argument. Violence is the pressure clock around that argument, not a replacement for it.

Narrative choices

These are the campaign’s moral hinges.

Encounter director

Scene modules you can run immediately.

Player broadcast

Live GM prompts

Temptation law

Offer each role the exact thing they privately want most. That is what makes Caretaker dangerous.

Escalation law

At clock 4, make every terminal and cathedral drone feel watchful. At 6, force the finale immediately.

Believer law

At least one loyalist must be humane, sincere, and difficult to dismiss.

Ending viability

GM narrative advice

Printable GM handouts

Role summary, private secret, temptation, and prompt cards.