Security 51 Choices, Branches & Consequences
Quick answer
Track verified Security 51 checkpoint choices, experiments, city operations, Shift Map branches, later consequences, endings, and achievements.
Quick answer
Security 51 choices can affect the current visitor immediately or surface several shifts later. After the first ending, use the Shift Map to replay a marked branch and change one decision at a time. This page records what can be verified without pretending every hidden consequence is already solved.
Verified choice systems
| Choice system | Options you control | Confirmed consequence scope | Verification |
|---|---|---|---|
| Checkpoint decision | Allow, deny, call security, or isolate when available | Immediate visitor result; the official game description confirms some decisions also have later consequences | Official system |
| Isolation experiment | Select an available experiment for a contained anomaly | Later reports can expand understanding and City Operation options | In-game/community verified |
| City Operation | Choose an intervention for the active crisis | Changes the balance and eventual crisis route | In-game/community verified |
| Shift Map branch | Return to a marked earlier day and choose differently | Creates an alternative story path toward another result, ending, or achievement | Officially supported |
Branch replay log
Use this compact format while testing a route:
| Branch point | Original choice | Changed choice | First visible difference | Later result | Status |
|---|---|---|---|---|---|
| Marked Shift Map day | Record the exact operation or decision | Change one variable only | Note the first changed report, option, or crisis value | Record ending/achievement only after it appears | Verified / still testing |
How to test a choice without contaminating the result
- Choose the earliest marked day connected to the crisis.
- Record the original operation, experiment, or visitor decision.
- Change only that decision.
- Replay until the first downstream difference appears.
- Continue to the ending if the branch remains different.
- Add an ending or achievement connection only after the game or Steam confirms it.
Confirmed branch guidance
Community testing indicates that a crisis is best changed near its beginning. Branching only at the last day may preserve the dominant crisis state established by earlier operations. The August 20 update now marks useful alternative-story days with question marks, borders, and tooltips, making those nodes the safest starting points.
Verification standard
Use the in-game result as the primary source. Mark a route still being verified when it comes only from a community report, demo, or older build. Do not infer an ending requirement from an achievement name.
Continue with the Shift Map guide, Endings, and Achievements.