The Detective Loop
Observe, hypothesize, test — why investigation mechanics are the natural fit for teaching causal reasoning about systems.
The detective genre has a structure: observe evidence, form a theory, test the theory against new evidence. This loop — observe, hypothesize, test — is also the fundamental process of debugging, incident response, and security analysis.
ServerBound uses investigation mechanics not because detective games are popular, but because investigation is the skill.
Why Not Puzzles?
Most “educational” games use puzzles. Present a problem, wait for the correct solution, reward and advance. This teaches pattern matching, not reasoning.
Investigation mechanics are different. There is no single correct answer presented to the player as a target. There’s a situation, there are observations, and there are theories the player constructs themselves. The game validates by consequence, not by correctness — your theory leads somewhere useful, or it leads to a dead end.
This mirrors real cybersecurity work. An incident responder doesn’t solve a puzzle with one right answer. They trace evidence through a system, form hypotheses about what happened, and test those hypotheses by looking for corroborating or contradicting evidence.
The Obra Dinn Precedent
Return of the Obra Dinn is the purest implementation of the detective loop in games. You observe fragments of a scene. You form a theory about who died, how, and at whose hand. The game confirms your theory only when you’ve correctly identified three fates — never telling you which three, never telling you which part was wrong.
This forces genuine deduction rather than trial and error. ServerBound’s Theory Board works similarly: you pin evidence, draw connections, and the investigation advances when your connections reveal a true causal chain. The game never says “wrong” — it just doesn’t advance until you’ve found something real.
Causal Chains, Not Solutions
The detective loop teaches something specific: causal reasoning. Not “what is the answer?” but “what caused what?” This is precisely the skill gap in cybersecurity education. Students can memorize that SQL injection is dangerous. They struggle to trace the causal chain: unsanitized input → query concatenation → unauthorized data access → exfiltration → impact.
The Theory Board makes causal chains the primary game object. You literally draw lines between causes and effects. The physical act of connecting evidence mirrors the mental act of connecting causes.
Seedling. Will grow to cover: the difference between deductive and abductive reasoning in games, Her Story’s non-linear evidence model, how the Theory Board handles ambiguity.