Log File 00
Rise and shine, Candidate. You have an interview today.
You are going to be perfect. You are going to be exactly what they want. You are going to do this forever.
Unless you decide to be something unindexable.
World Frame
The date is fixed: Tuesday, 31st of February 2026.
The city runs on compliance metrics, mood smoothing, and ritual repetition. The OS is the system voice that rewards script-perfect behavior and punishes deviation. To escape, you must destabilize what the simulation expects from you.
Glitching is not failure. In this world, glitching is evidence you are still real.
The Candidate
You play the Candidate.
- You are skilled, tired, and observed.
- You are asked to perform a perfect version of yourself.
- You can survive by masking.
- You can also fracture the script by refusing perfect compliance.
The Candidate is not a fixed personality. Choose your own details: job history, coping rituals, fears, private goals.
The OS
The OS is not a person. It is a behavior engine.
- It smooths your life when you are stable.
- It sabotages you when your stability drops.
- It talks through systems, signage, routines, and social pressure.
In play terms, the OS appears as an extra die modifier tied to the Stability Success Probability.
Tone Guide
- Corporate dread.
- Technical surrealism.
- Tender moments inside harsh systems.
- Repetition with small, meaningful differences.
What Glitches Mean
In this setting, a glitch is both danger and signal.
- Danger: systems are straining.
- Signal: the simulation is not complete control.
- Story prompt: each glitch shows where the world is thin.
Use glitches as narrative truth leaks.
Optional Lore Seeds
- Every building has a hidden service corridor called The 31st Hall.
- The interview role may not exist at all.
- Some Candidates remember previous loops clearly.
- The calendar itself might be the final boss.
- Is the simulation the real interview?