# Core values ### Core Values EPIZO is built on a set of foundational principles that guide every architectural, technical, and governance decision. These are not abstract ideas — they directly shape how the system is designed, deployed, and used in the real world. *** #### 🛡️ Resilience First Every component of EPIZO is designed to function **independently of the internet**. This means: * All critical services (AI, knowledge, maps, education) run locally on the node * No dependency on external APIs, cloud services, or DNS infrastructure * The system remains operational during: * internet shutdowns * natural disasters * infrastructure failures * censorship events Resilience is treated as a **primary requirement**, not a fallback feature.\ If a feature cannot operate offline, it is not considered core to EPIZO. *** #### 🌍 Radical Accessibility EPIZO is designed to be usable by **anyone, anywhere**, regardless of technical skill or economic constraints. This includes: * Running on low-cost hardware (starting from \~$50 devices such as Raspberry Pi) * Minimal system requirements for basic functionality * Simple, terminal-based installation with near-zero configuration * Browser-based interface — no specialized software required The goal is to remove barriers: * no cloud accounts * no API keys * no subscriptions * no advanced technical knowledge Accessibility is not only about usability — it is about **global inclusivity**, especially for underserved and underconnected communities. *** #### 🔐 Censorship Resistance EPIZO ensures that information, once distributed, **cannot be silently altered, removed, or manipulated**. This is achieved through: * Cryptographic hashing of content collections * Optional anchoring of content fingerprints on Ethereum * Local storage of verified data snapshots As a result: * Users can verify that their data is authentic * Governments or centralized actors cannot retroactively modify content * Knowledge remains consistent even in hostile or controlled environments EPIZO does not rely on trust in institutions — it relies on **verifiability and transparency**. *** #### 🧑‍🤝‍🧑 Community Ownership EPIZO is governed as a **decentralized system**, not controlled by a single company or authority. Key principles: * Governance decisions are made through a DAO (Decentralized Autonomous Organization) * Node operators, contributors, and token holders participate in decision-making * No centralized entity has unilateral control over: * protocol changes * content standards * funding allocation This ensures: * long-term sustainability * resistance to capture or control * alignment with the needs of real users and communities EPIZO is designed to be **owned by the network that runs it**. *** #### 🧩 Open Source Always EPIZO is fully open source and licensed under **Apache 2.0**. This guarantees: * Anyone can inspect, modify, and deploy the software * No vendor lock-in or proprietary restrictions * Full transparency across all system components Benefits: * Developers can extend and integrate EPIZO into new environments * Organizations can audit the system for security and trust * Communities can fork and adapt the project for local needs Open source is not just a licensing choice — it is a commitment to **transparency, collaboration, and long-term independence**. *** ### Summary These core values define EPIZO as: * **Resilient** — works without internet * **Accessible** — usable by anyone, anywhere * **Trustless** — verifiable, not controlled * **Decentralized** — governed by its community * **Open** — transparent and extensible Together, they form the foundation of a system designed to ensure that **knowledge, tools, and intelligence remain available under any conditions**. --- # 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/introduction/core-values.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.