The Overlord's ledger

The ledger is where you change how the dungeon runs. It sits on your table in your study (back left of the great hall): press E at the table to open it. It has five tabs.

Chambers & repos

One row per chamber. Visit walks you there. Switches for Auto-assign issues, Auto-merge and Browser testing (testers use a real browser through Playwright). You can dye the chamber one of eight period colours (ochre, woad, moss and the rest), link it to other chambers so its coders can read those repos, and Disconnect it: everyone in it is let go, nothing is deleted on GitHub, and the folder stays on disk.

Each row also shows whether your project folder is up to date with GitHub. After a merge it fast-forwards when that is safe; if it can't (local changes, another branch checked out), it says why, and Sync now tries again. Nothing is ever stashed or thrown away.

Add a project at the bottom connects a project folder or a GitHub repo, or starts a new one. Every project must be on GitHub, because issues and pull requests are how the guild works. A folder not yet on GitHub gets its repo straight away, then uploads what you have committed. The chamber shows how far the upload has got; a big project with art files can take most of an hour, and the guild starts once it is there.

DungeonMaster & recruits

The DungeonMaster's model and effort, the recruits waiting for you, and a project brief for each chamber: what it should build next. Re-study asks him to read the repo again and rethink the guild.

Guild

Everyone in every chamber: name, job title, specialty, coding agent, model, effort and look. Terminal opens their terminal; Let go lets them go.

Issues

File a new issue on any chamber's repo, and see the open ones.

Settings

• Default coding agent, model and effort for everyone (each person can override them in the Guild tab).
• Session limit: how many agents may work at once. Empty means no limit.
• Sessions while pacing: how many may run when Claude warns that usage is high (chapter IX).
• Recruiting: approve every recruit, or auto-approve up to the guild cap per chamber.
• Dungeon review every so many minutes: how often the DungeonMaster looks over everything (0 turns it off).
• How coders run: real terminals (recommended) or the Agent SDK.
• Your name, the name of your hold, the folder new projects are created in, your own domain for launched apps (chapter VIII), and Replay the tour.

When an update to the dungeon itself is ready, a row at the top of the ledger offers Update now or Later. Updating lets running sessions finish first, then restarts the dungeon.