story-runtime

To run a single turn of a text-adventure, the runtime interprets player input against active scene and character files. It then outputs player-facing narration and a bounded state-update summary without rewriting the original canon.

Structured narration in state-management reads the mutable run state and active scene characters to interpret player actions. It produces bounded state updates and narrates consequences without altering the defined reusable canon.

You maintain a reversible run state by applying a defined turn contract during active play. The runtime reads the current mutable state, processes the action, and outputs a compact state-update summary while preserving the original canon.

Yes, you can narrate consequences as scene characters without rewriting canon. The runtime enforces a defined turn contract that separates reusable canon from the mutable run state, ensuring only bounded state updates occur.

No, the story-runtime requires no external dependencies to manage scene characters. It operates independently to read active scene files and output player-facing narration alongside compact state-update summaries.

The limitation of bounded state-update summaries is that updates are constrained by a defined turn contract. This prevents rewriting the reusable canon, meaning state changes must be compact and reversible within the active scene context.