Ten nights

The campaign tells a small, precise story: a company growing slightly faster than its operations can absorb, over ten nights, ending on the busiest shopping night of the year. Every briefing is mechanically true — if Deniz says something is coming, it comes.

The inbox

During a shift you read your inbox by typing mail. Mails arrive on the in-game clock; some wait for a reply, and you give it with mail -r <id> <a|b>. Not replying is also a choice. The body of every mail changes its own sentences according to the path you have taken so far; the same mail does not say the same thing to two players.

Three people write to you:

A fourth voice, Murat, the technical contact at the biggest customer, comes in later in the story.

The branching path

The story forks in four places. Which night and which choice close each fork is not written here; only what they are about is:

Every night's briefing is rewritten according to the path you have reached. Your choices leave traces in the inbox: some mails only arrive if you have passed through a particular path. The price of some choices is paid in the next night's incident pool or in your wallet.

The campaign ends in seven distinct endings: Platform Team, Team Lead, Founding Team, Opposite Shore, Scapegoat, Outsourcing, and Night Owl. Which one you reach depends on your choices, and also on how you finish your shifts. Your reputation and your relationships have a share in it.

Night 1 — First Watch

First night. Two web boxes and a database — small, but all of it is yours. Watch the logs.

Three machines, guided. The tutorial runs here.

Night 2 — Release Night

The platform team shipped a release today. Something will break tonight; find it before the metrics do.

Leaks and filling disks open up — both are the kind of thing a fresh deployment causes. Still one incident at a time.

Night 3 — Rising Tide

Traffic is up a third and a load balancer joins the rack. Same drill, less slack.

The lb role arrives, which means bandwidth capacity and, in time, certificates to worry about. The first big fork closes at the end of the night.

Night 4 — Cache Warm-Up

Cache went live this afternoon. Two incidents can overlap now — triage before you type.

The concurrency limit really does go up to two. This is the first night that asks you to choose what to ignore. The night opens with a different inbox depending on the path you chose.

Night 5 — The Ad Spike

Marketing bought an ad slot. Expect a spike, and a second failure riding on it.

Night 6 — Muddy Signals

Nine machines, workers included. From here the signatures get muddy — read the logs twice.

Compound incidents begin and the distributed flood variant opens up. The warning about signatures is literally true: from here on a symptom is often the consequence of another incident.

Night 7 — Compound Fracture

Second database is in. Compound failures now: fixing the symptom will not clear the cause.

Night 8 — Double Everything

Fourteen boxes, two of everything. The budget grew, but so did the blast radius.

The grace window drops from 40 seconds to 30 — the harshest single-night tightening in the campaign.

Night 9 — Dress Rehearsal

Dress rehearsal. Four incidents can stack tonight — protect uptime, not your pride.

Concurrency reaches its ceiling of four. The line about pride is the closest the game comes to strategy advice: even a partial fix that costs uptime is better than an incident left open. The last fork closes at the end of this night.

Night 10 — Black Friday

Black Friday. Checkout traffic peaks after midnight and never lets go. Hold the line until 06:00.

Sixteen machines, a 1.90× pace, a 22-second grace window, and a surge that raises the pace another 1.35× once half the shift has passed. No surprises, no boss. The night simply does not stop, and the whole reward is the morning. The night's briefing and the morning's ending are written according to the path you chose over the previous nine nights.