story-authoring

To structure reusable story canon, organize files under a specific story slug directory containing manifest.json, canon/world.md, and folders for characters, scenes, and rules. This standardized layout separates immutable canon content from mutable run and save states.

A story slug package is a standardized directory structure for maintaining canonical story assets like world, characters, and scenes. You need it to ensure consistent narrative structure and prevent accidental edits to live story runs across multiple projects.

You create a minimal canon package by following the default file shape and editing the canon and initial state files under the stories directory. Simple validation ensures this default package shape is respected, maintaining portable and shareable story assets.

Yes, you can separate mutable story runs from immutable canon content by organizing files strictly under stories/<slug>/canon for fixed assets and stories/<slug>/state for initial states. Clear boundaries prevent accidental edits to live story runs.

Yes, this story-authoring approach works without external dependencies because it uses a structured starter kit to drive the creation and maintenance of canonical story assets through disciplined file organization and simple validation.