Architecture

The game separates facts (game state) from laws (the rule engine plus registered chaos rule plugins).

        GUI (gui/)       text CLI (ui/, cli/)      agent CLI (agent/)
              \                  |                       /
               └──────── GameController (app/) ─────────┘
                                 │
                     GameLoop + GameState (core/)
               ┌─────────────────┼─────────────────┐
         RuleEngine (rules/)   items/        ChaosPipeline (ai/)
               │                                   │
         rules/plugins/*        prompts · permissions · LLM backend
               └──────────── Registry (registry/) ─┘

Plugins (chaos rules and items) register themselves by name and never import each other; core code resolves behaviour by name through the registry.
Front-ends never decide rules: they render the controller's view and call its commands.
The Chaos AI only emits structured JSON that is validated against permissions.

Tables and progression

The mode registry connects a table to its host, series, goal, Chaos rule pool and item pool. Collection and Shop group content by series. Player progression takes the run's stake from the player's chip vault, settles the result back into it, and records stats and achievement rewards. Meta upgrades and starter items are switched off in this version.

Cosmetics use asset aliases for presentation; they do not alter table rules or run balance. The wiki extracts these registries and balance rows through its adapter, while author-supplied drafts such as J-54 remain editorial content with an explicit draft banner.

How this wiki is built

The wiki is a separate repository. One adapter module imports the game from a clean checkout of main and extracts facts (ids, numbers, help text, art, a replayed agent transcript) into facts/facts.json. The site is rendered from those facts plus hand-written prose.