docs(design): define tyrant game stories

design/user-stories/us-001-start-pause-and-administer.md

@@ -0,0 +1,26 @@
+---
+type: User Story
+title: "US-001: Start, pause, and administer the game"
+description: Give server operators safe control over the Tyrant game's lifecycle and state.
+status: backlog
+---
+
+# US-001: Start, pause, and administer the game
+
+As a **server operator**, I want to start, pause, resume, and inspect the game so that it can coexist safely with maintenance and other server events.
+
+## Acceptance criteria
+
+- [ ] An administrator can start the first game by assigning the initial Tyrant.
+- [ ] The administrator may assign the first Vigilante or allow random selection from eligible recently active players.
+- [ ] An administrator can pause and resume the game without deleting game state.
+- [ ] Pausing freezes progression, cooldowns, daily-use timers, inactivity checks, and pending-selection deadlines.
+- [ ] Role and class effects are suppressed while paused and restored when play resumes.
+- [ ] Administrative commands require the `spigottyrant.admin` permission, granted to server operators by default.
+- [ ] Administrators can inspect lifecycle state, roles, classes, Followers, purchases, levels, cooldowns, participation, and pending selections.
+- [ ] Destructive administrative operations require explicit confirmation.
+
+## Related
+
+- [Tyrant game state machine](../concepts/game-state-machine.md)
+- [Configure and persist game state](us-012-configure-and-persist-state.md)