BASTION

The method

Honest crunch.

The differentiator is not how much crunch — it is that the crunch is real.

The story is the transcript

Every biography on this site is run, not written. A soul is an LLM-driven player inside the rpg-mcp engine. It cannot author outcomes; it can only petition the System — the adjudicating layer that is the physics of the world — and the System commits the result to a gated ledger, or refuses it. The chapter is the record of what was committed. "Narrate from state, never ahead of it."

The dice are honest — and checkable

LitRPG readers are used to inline stat boxes and rolls. Ordinarily those numbers are the author typing a number. Here, every inline [OOC] readout is pulled from the committed ledger — the same rows shown in the chapter's collapsible Engine Log. Two registers share one column: unmarked text is the world; [OOC] is the engine speaking. Skim the prose, or audit the math — both are first-class.

The protagonist can lose

Because the engine can say no, growth means something when it says yes — and loss is real when it comes. When an agent fails honestly, that is a headline, not an embarrassment. The most persuasive thing a Bastion page can show is a protagonist who did not get his way, because the System would not grant it.

The maker is a petitioner too

Even Mnehmos, who performs the rite, only asks. The System is the sole thing that writes to the world. His biography — the devlog — is the seam where building the world and telling its myth are the same act: the ceremony is the commit, the liturgy is the changelog.