# First Run ### Overview This document describes the **initial runtime behavior of an EPIZO node after installation**, including system initialization, user access, and content setup. *** ### Initial Boot Sequence When the node starts: #### 1. Environment Initialization * Load configuration * Mount storage directories *** #### 2. Service Startup * AI service * Knowledge service * Map service * Supporting processes *** #### 3. Provider Registration * Services registered internally * API endpoints exposed *** #### 4. Health Check * Validate service availability * Ensure readiness *** ### Accessing the Node #### Local Access ``` http://localhost:8080 ``` *** #### Network Access ``` http://:8080 ``` Allows: * Multi-user access * Device-to-device usage *** ### Command Center Interface The Command Center provides: * Service management * Download manager * System status * Setup wizard *** ### Initial Setup Wizard On first access, users are guided through: #### 1. Content Selection * Knowledge (ZIM) * Maps * AI models * Education resources *** #### 2. Download Execution * Background job system * Progress tracking *** #### 3. Installation * Extract content * Register services *** ### Storage Initialization Directories created: ```bash storage/ ├── zim/ ├── maps/ ├── models/ ``` *** ### Post-Setup State After setup: * Node is fully offline-capable * All services operational * Data locally stored *** ### Multi-User Access Other users can connect via: ``` http://:8080 ``` *** ### Security Notes * No authentication by default * Designed for trusted local networks * External exposure not recommended *** ### First Run Constraints * Content must be downloaded before use * AI requires sufficient hardware * Large downloads may take time *** ### Verification Checklist After first run: * UI loads successfully * Services are active * Content accessible * No external dependencies required *** ### Result The node transitions into a **stable offline state**, capable of operating indefinitely without internet connectivity. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.projectepizo.com/installing/first-run.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.