Actions, Confirmation, and Authority
Who may change the world, and when Bardo asks first.
Who Has Authority
You do. The Markdown files are the truth. The Storyteller proposes; the rules decide; the file store records.
- Every write carries the revision it expects. A stale write fails instead of overwriting.
- Every request is checked against your account. Another person's project reads as not found.
- The Storyteller writes through the same single file store as you. There is no second store.
Clear Actions Commit at Once
Plain moves, taking and dropping items are resolved without a confirmation card. Bardo lists the change under its reply and offers Undo for the latest plain turn. Undo records a compensating event; it does not rewrite history.
Other Actions Ask First
These show their effects and wait for you to Confirm or Cancel:
- passing time,
- giving an item to someone,
- marking something,
- things said as told facts,
- actions a model had to interpret.
Cancelling changes nothing. Confirming applies the action once. If the world changed in between, the proposal is refused as stale instead of being applied.
When You Edit a World File
If you edit a world file in a way the rules cannot use (an unreadable header, a missing reference, a duplicate id), the save still succeeds. Your text is kept, a notice appears above the editor, and play involving that entity pauses. Needs review appears above the message box until the file is fixed. Everything else keeps working.
Slash Commands
Most commands read or navigate. /init (alias /setup) is the exception: when geography is enabled, it writes starting-world files once, never replacing an existing world. World Tools also exposes owner writes with the confirmations described on each tool. See Chat and slash commands.