seeders/guts

Coordinates between model and view, handles routing - **FileSystemSyncService**: Low-level file operations for saving JSON ### Game Runtime Flow ``` 1. Load index.html ↓ 2. Initialize game (client/server/editor) ↓ 3. Load libraries in dependency order ↓ 4. Initialize managers ↓ 5. Load collections (units, abilities, etc.) ↓ 6. Create game instance ↓ 7. Initialize game systems ↓ 8. Start main loop ↓ 9. Process input, update systems, render ``` **Key Components:** - **ECS Architecture**: Entity-Component-System for game logic - **Managers**: Coordinate subsystems (ComponentManager, GameManager) - **Systems**: Update logic for specific aspects (RenderSystem, GridSystem) - **Collections**: Data-driven game objects defined in JSON --- ## Deep Dive: GUTS Architecture ### Core Concepts #### Data-Driven Design Everything in GUTS is defined by data: - Game objects are JSON files - Behavior is defined by component configurations - Systems operate on component data - No hardcoded game logic in the engine #### Entity-Component-System (ECS) - **Entities**: Game objects identified by IDs - **