docs(design): define tyrant game stories

2026-08-14 22:08:35 -04:00
commit 470e372e47
21 changed files with 530 additions and 0 deletions
@@ -0,0 +1,19 @@
+---
+type: Design Concept
+title: Persistence Model
+description: Defines the durable state and timekeeping needed to restore a Tyrant game safely.
+---
+
+# Persistence Model
+
+State is keyed by player UUID while retaining the latest known player name for display. Durable global state includes lifecycle status, current and pending role holders, selection deadlines, paused durations, and the current Tyrant reign.
+
+Durable player state includes participation status, opt-out deadline, login history, role or class, Tyrant level, purchased unlocks, unspent choices, Follower relationship, ability cooldowns, daily intelligence use, bound-item delivery state, and captured mobs.
+
+Elapsed-time rules use UTC instants. Paused time is excluded from timers. Saves use atomic replacement where supported, preserve unknown fields where practical, and reject corrupt records rather than granting powers, assignments, or duplicated entities.
+
+## Related stories
+
+- [Inform players and manage participation](../user-stories/us-011-inform-and-manage-participation.md)
+- [Configure and persist game state](../user-stories/us-012-configure-and-persist-state.md)
+- [Use class ability items](../user-stories/us-014-use-class-ability-items.md)