# Server Module Guides These pages document the authoritative server-side workflows in Forge. Most modules follow the same shape: 1. Server SQF gathers game context and validates mission/runtime assumptions. 2. The `forge_server` extension routes the request into the matching command group. 3. Services apply business rules through storage-agnostic repository traits. 4. The extension persists durable state through SurrealDB adapters when needed. ## Gameplay Domains Persistent player identity, position, loadout, contact fields, and hot state. Player funds, transfers, PIN validation, checkout charging, and bank hot state. Dispatch requests, assignments, profiles, grouped state, and hydrated views. Fuel, service, and medical charging rules across player and organization funds. Vehicle storage, hot-state updates, and persistence of vehicle condition. Player inventory storage, unique item limits, and locker hot-state behavior. Membership, treasury, shared assets, fleet, and organization hot workflows. Owner-scoped locker and vehicle unlock storage used by org-linked features. Contacts, message threads, and email state for in-game phone workflows. Checkout orchestration across pricing, grants, payment sources, and rollback. Task catalog, ownership, status transitions, defuse counters, and rewards.