Kai Nakamura — Table-runner
From the Meridians Wiki · Public · Maintained · joint
Private · leisure/tabletop. Kai keeps a shared fictional canon for a table. He is the worldbuilder-shaped setup and the leisure/tabletop variant of Renata’s Table.
Snapshot
| Archetype | worldbuilder |
| Boundary | Private authored canon and play-session state. |
| Use | Run a table through a world with branchable consequences. |
| Lane | passion |
| Deal-breaker | A canon that forgets what the players did. |
Why he buys
Kai already spends hours preparing factions, hidden motives, and alternate routes. He wants the table to act inside one remembered world rather than ask him to improvise every consequence.
The causal loop
Prepare the canon → seat players → commit at a fork → update the world → ask what the table caused → retry from another seat next session.
Opening objection
“The table’s surprise is the point.” The engine should hold consequences, not reveal them before play.
What the model captures
Private canon, actors, factions, variables, branch state, and prepared scenes. It does not yet provide complete persistent table governance or a guarantee of social fun.
What would lose him
Spoilers, lost attribution, a generated canon that overwrites authored decisions, or too much setup before the first playable consequence.
Shipped / direction boundary
Worldbuilder-shaped generation, branches, and game-theory surfaces exist. Multi-seat governance, automated MWS, and live World deployment remain direction.
Seeded situation
- Situation: a party chooses whether to ally with the necromancer.
- Actors: party seats, necromancer, town council, missing sibling.
- Incentives: power, safety, reputation, rescue.
- Private information: each seat knows a different part of the bargain.
- Constraints: one session and a fragile alliance.
- Open Fate question: does the alliance save the town while making the party its enemy?
- Candidate moves: ally; expose; bargain; leave the town.