The toolkit

framework: simulation logic

Reading a world as a game system

Any fictional world with fixed rules, recurring death conditions, and characters who understand the mechanics before they understand the story can be read as a designed system rather than an organic setting. Once you look for the rules instead of the mystery, most "random" horror or fantasy logic turns out to be mechanics in disguise.

There are no new stories, only variations.

applied in: FROM — the town read as a simulation loop, with every "cycle" functioning as a respawn.

framework: character mapping

Archetypes as classes

Ensemble casts often map cleanly onto game-class roles: the tank holding the line, the support keeping others alive, the scout who runs ahead into danger, the healer absorbing cost so others don't have to. Reading a cast this way explains why certain characters keep surviving encounters that should kill them — they're built for it.

applied in: FROM — the Township's core cast mapped to class roles to explain who survives, and why.

framework: causality loops

The bootstrap paradox

A bootstrap paradox is an effect that loops back around to cause itself, with no clean origin point. It shows up constantly in stories that play with time, fate, or prophecy — and once you spot one, it reframes a hero/villain relationship as two ends of the same loop, each one required for the other to exist.

applied in: FROM — Boyd's relationship to the Man in Yellow read as a closed causal loop, not a rivalry.

framework: memory and continuity

The corrupted save file

In any story built around resets or cycles, a character who remembers fragments that shouldn't survive a clean reset is a signal worth tracking. It's rarely just trauma — it's evidence the loop isn't as closed as it claims to be, and it's often one of the biggest tells about what a story's world actually is underneath its surface genre.

applied in: FROM — Victor's memory bleed across cycles as proof the "reset" was never fully clean.