How ksanadock/microverse works
Project type and purpose
• Purpose: simulate a micro-world of AI agents with independent memory, dialogue, tasks, and environment awareness.
File structure
• Top-level directories:
• asset/ (graphics, fonts, shaders, themes)
• scene/ (Godot .tscn scenes: characters, maps, UI prefabs)
• script/ (GDScript controllers):
– ai/ (AIAgent, APIManager, DialogManager, MemoryManager, ConversationManager, background_story, memory)
– ui/ (UI widgets: menus, labels, save/load, settings)
– root‐level scripts (CharacterController, TaskManager, RoomManager, GameSaveManager, CameraController, etc.)
• Config: project.godot, .gitignore, README, LICENSE.
• Storage: JSON-based local storage via GameSaveManager & MemoryManager.
• External integration: REST API calls to multiple AI service providers.
Key insights from README
• Core subsystems:
• APIManager – dispatches calls to LLM providers.
• DialogManager – orchestrates natural-language exchanges.
• MemoryManager – persists AI agents’ memories.
• CharacterManager – tracks agent states, personalities, interactions.
• TaskManager – generates and monitors agent tasks.
• Scenes: maps (Office.tscn), character prefabs, UI overlays.
• UI: settings, dialog bubbles, command console, save/load, AI model selector.
Elements
• Labels: exact component names (e.g., “MemoryManager”, “DialogManager”, “APIManager”).
• Blue for core engine & scenes
• Green for Manager subsystems
• Orange for UI components
• Gray for assets & storage
• Purple for external services
• Rectangles for modules
• Clouds for external services
Final recommendations
• Be as granular as possible: treat each manager as its own node.
• Both static structure (components) and dynamic flows (runtime interactions).
• Iterate with the engineering team to validate accuracy against actual Godot scene tree and script dependencies.