Tianshu
How it works

Read once. Play forever.

Tianshu reads your book once, at build time. A small deterministic engine plays what you approved — same seed, same log, same fight.

Compile your rulebook
Plate i · the tome
i. Compile

Drop in the PDF. Tianshu reads it once and builds the ruleset — actions, rolls, conditions — with five visible steps and a page that says what broke.

ii. Review

The ruleset sheet, in plain words. Fix a broken action in place, add house rules in English, approve. Nothing plays that you have not read.

iii. Play

Invite by link; players sit down from a phone and can keep their character, experience and all, for the next session. Story, fight and what-happens-next, with every roll resolved by the book.

iv. Replay

One event log per session. Step back through any fight, and give every player a recap and a shareable pin afterwards.

House rules · in plain English

Say it once.
The table enforces it.

Prose in, an enforced delta out — add, merge or remove per action, so a typo can’t silently no-op. Nobody else does this.

You said “A creature reduced to 0 HP by an Enhanced Attack dies outright — no STR save.”
Compiles to · enforced
  • Enhanced Attack · save STR → condition dead
  • New condition dead · permanent
schema okplays ok
Nothing improvises at the table

The ruleset is data.
The engine is arithmetic.

A ruling is a lookup in the ruleset you approved; a roll is a seeded die. That is why every session replays exactly.

One real build · Cairn 1e Compiled from a rulebook it had never seen. Both gates green first try. Three review edits against eight actions and six conditions it got right unassisted. Then a live table and a replay-verified fight — and one bug the review step caught, fixed the same day. Read the fifth-system diary
What it won’t do Core resolution and combat — not exploration, downtime or magic subsystems. Never “the whole book, perfectly”. A wrong ruling is a compile bug we fix, not something the engine improvises around.