The normative rules of Mundane. These documents are tight and pedantic by design: they state what is legal, what is rejected, and the exact order in which the engine checks. They are the human-readable mirror of the engine, and the engine is the source of truth — where the code and a spec disagree, the code wins and the spec is wrong and must be fixed.
For the same rules in plain language, with worked examples and a sample turn, read the
rulebook instead. The individual cards are published as JSON
card sets in mundane-cards; the
effects they name live with the engine.
| Document | Scope |
|---|---|
core.md |
Execution model, Composure (winning and losing), Time. |
cards.md |
The five card types and the card-definition format. |
card-sets.md |
The JSON set-file format for publishing cards in mundane-cards. |
turn-priority.md |
The five phases, priority, the stack, and timing. |
actions.md |
Every action’s preconditions and exact rejection messages. |
X“ means the engine raises IllegalAction carrying the message X and leaves
the state exactly as it was.apply_action, PLAN, time) refer to engine identifiers.