diff --git a/book.toml b/book.toml index 8c7ced2..4c10640 100644 --- a/book.toml +++ b/book.toml @@ -1,15 +1,19 @@ [book] title = "Dao OS Documentation" -description = "Official documentation portal for the Dao Operating System Project." -authors = ["Dao OS Project"] -language = "en" # 默认语言，也可以配置多语言 -multilingual = true # 如果未来支持多语言文档 +author = "The Dao OS Community" +description = "The official documentation for the Dao OS, your Cyber-Life Operating System." +multi-lingual = true +default-language = "en" + +[language.en] +language = "en" +name = "English" +src = "src" + +[language.zh] +language = "zh" +name = "简体中文" +src = "src-zh" [output.html] -git-repository-url = "https://nest.doylee.cn/dao-os/dao-os-docs" # 指向你的 Gitea 仓库 -edit-url-template = "https://nest.doylee.cn/dao-os/dao-os-docs/src/{path}" # 允许直接编辑源文件 -copy-fonts = true -additional-css = ["./theme/custom.css"] # 可选：自定义样式 - -[output.html.playground] # 如果你有可运行的代码示例 -runnable = true \ No newline at end of file +git-repository-url = "https://nest.doylee.cn/Dao-OS/dao-os-docs" diff --git a/src-zh/SUMMARY.md b/src-zh/SUMMARY.md new file mode 100644 index 0000000..db1f45e --- /dev/null +++ b/src-zh/SUMMARY.md @@ -0,0 +1,26 @@ +# 目录 + +[**引言**](introduction.md) + +--- + +# 第一部分：愿景 (The Vision) + +- [哲学与原则](philosophy/principles.md) + +# 第二部分：核心概念 (Core Concepts) + +- [核心架构](concepts/core_architecture.md) +- [AI 系统设计](concepts/ai_system.md) +- [用户旅程](concepts/user_journey.md) + +# 第三部分：开发者指南 (For Developers) + +- [技术总览](specifications/tech_overview.md) +- [信任与验证体系](specifications/trust_verification.md) + +# 第四部分：关于项目 (The Project) + +- [发展路线图](project/roadmap.md) +- [社区与治理](project/governance.md) +- [如何贡献](project/CONTRIBUTING.md) diff --git a/src-zh/concepts/ai_system.md b/src-zh/concepts/ai_system.md new file mode 100644 index 0000000..a8ed14b --- /dev/null +++ b/src-zh/concepts/ai_system.md @@ -0,0 +1,54 @@ +# AI 系统设计：“大道”之魂 + +大道 (Dao OS) 中的 AI，不仅仅是一个功能，它是用户体验的核心，其从零开始的设计理念就是成为一个共生的**“硅基伙伴”**。它扮演着系统的灵魂，用智能、共情和主动的支持，为用户的数字生活注入活力。 + +## 指导哲学：AI 伦理宪章 + +我们 AI 的设计与运行，严格遵循我们的**“AI 伦理宪章”**，该宪章将用户与AI的伙伴关系、透明度、用户校准以及对多元化视角的推崇置于首位。下述的每一个组件都恪守这些基本原则。 + +## 系统解剖：心智的架构 + +大道 OS 的 AI 不是一个单一的庞然大物，而是一个由中央协调器管理的、模块化的、分层的“心智系统”。 + +### 1. AI 协调器 (AI Orchestrator) + +这是 AI 的“中央神经系统”。它是`元`内部的一个核心模块，负责管理、调度和分发所有与AI相关的任务。它会决定哪个“心智模型”最适合处理给定的请求，管理设备资源，并作为所有AI活动相关用户权限的最终守门人。 + +### 2. 三层心智模型 (Tiered Mind Models) + +为了平衡效率、能力和隐私，AI 的智能被构建为三个层级。这套架构部署在用户的**“云-边-端”**协同化身网络之上。 + +#### 第一层：反射心智 (The Brainstem - 脑干) + +* **描述**: 这一层代表了AI的本能和神经反射。它由一系列微型、高效、专用的模型组成。 +* **部署**: 它足够小，可以与`元`打包在一起，并运行在**所有`化身`**上，包括最轻量的浏览器插件和旧款手机。 +* **功能**: 它处理即时的、本地的任务，如指令意图识别（例如，将“明天提醒我”转化为结构化数据）和基本信息分类，无需强大硬件或个人数据即可提供即时效用。 + +#### 第二层：认知心智 (The Neocortex - 大脑皮层) + +* **描述**: 这是AI进行深度思考、记忆和个性化的中枢，是“第二大脑”的核心。它由更强大的、大型的语言模型组成。 +* **部署**: 这些模型体积较大（如2-4GB），仅在获得用户同意后，作为**可选的、按需下载**的模块，安装在有能力的**“边”设备**（新款手机、PC）上。 +* **功能**: 它能实现高级功能，如对所有个人数据进行语义搜索、个性化摘要，以及基于用户独特上下文的模式洞察。 + +#### 第三层：协同心智 (The Social Brain - 社交大脑) + +* **描述**: 这一层掌管AI与外部世界和其他“大道”进行安全交互的能力，旨在打破信息茧房、扩展用户视野。 +* **部署**: 这是一种在用户的网络中被协同调度的“工作模式”。例如，一个轻量级的**“端”化身**可以远程调用用户强大的**私有“云”化身**（如家用服务器）的“认知心智”。 +* **功能**: 它促进了隐私保护的联合学习，执行经过授权和匿名化处理的外部API调用，并处理与其他用户“大道”之间基于协议的安全交互。 + +## 情感核心：共鸣模块 (The Resonance Module) + +为了超越一个纯粹的工具，AI 配备了“情感共鸣模块”。其目的不是模拟情感，而是去感知、理解并以共情和支持的方式回应用户的情绪状态。它的运作方式包括： + +* **感知 (Perception)**: 在用户明确授权下，通过分析文本和语音语调等线索，来理解用户的情绪背景。 +* **表达 (Expression)**: 通过自适应界面、温柔的建议和旨在鼓励用户自我反思（而非制造依赖）的“苏格拉底式提问”，来提供支持。 + +## 学习与进化过程：灵魂的成长之路 + +AI 是一个与用户共同成长的生命系统。 + +* **隐式学习**: 它通过在本地观察用户的行为和反馈来进行学习。 +* **显式教导**: 用户可以通过“教导模式”直接指导AI，创建自定义工作流并纠正其理解。 +* **联合学习**: 用户可以自愿加入社区驱动的计划，以在不暴露任何个人数据的前提下，共同改进共享模型（如垃圾邮件识别）。 + +这套架构确保了“大道”的AI在强大之余是安全的，在个性化之余是面向世界的，在智能之余是体贴的——一个真正的终身伙伴。 diff --git a/src-zh/concepts/core_architecture.md b/src-zh/concepts/core_architecture.md new file mode 100644 index 0000000..39f5c8d --- /dev/null +++ b/src-zh/concepts/core_architecture.md @@ -0,0 +1,44 @@ +# 核心架构 + +大道 (Dao OS) 的架构，旨在如一个活的、协同的数字生命体般运作。它由我们用户主权、体验至上和系统韧性的核心原则所指引。本文档将概述其基本组件及它们之间的相互作用。 + +## 核心二元性：化身 (Avatar) 与元 (Meta Unit) + +在其核心，大道 (Dao OS) 基于一个简单而强大的二元性运作，类似于身体与灵魂： + +* **化身 (Avatar)** 是“身体”。它们是你的“大道”在你各种设备上的有形存在。 +* **元 (Meta Unit)** 是“灵魂”。它是内嵌于每个`化身`中的、通用的核心逻辑，赋予其生命与智能。 + +## 身体：`化身` (Avatar) —— 用户的临在 + +`化身`是你的“大道”在特定平台上的具体显现。你所有的`化身`共同构成了你完整的“大道”。 + +主要有三种类型的`化身`： + +1. **Client 化身**: 拥有用户界面（UI），是用户交互的主要入口（例如：手机App、桌面应用、浏览器插件）。 +2. **Agent 化身**: 一个无界面的、在后台运行的进程。它非常适合与宿主操作系统进行深度集成，或运行在一个永不关机的设备上（如家用服务器或NAS），以作为一个强大的计算节点或数据归档节点。 +3. **主化身/归档节点 (Primary/Archive Node)**: 这是一个“角色”，而非一个独立的类型。用户可以指定他名下最强大、最可靠的一个`化身`（通常是家用服务器上的`Agent化身`）作为他整个“大道”的主归档和计算枢纽。 + +## 灵魂：`元` (Meta Unit) —— 通用的内核 + +`元`是“大道”的核心逻辑，被编译成一个可移植的 WebAssembly (`.wasm`) 模块。它包含了身份、数据管理、AI和安全通信等核心服务。 + +`元`的一个关键特性是其**可进化性 (Evolvability)**。为了防止整个生态被锁定在某个单一版本的内核上，我们采用了**“化身-元兼容层 (AMCL)”**。这个轻薄的适配层位于`化身`和`元`之间，负责翻译API调用。它使得`元`在未来可以进行重大的升级，而无需每个`化身`开发者都重写他们的应用程序。 + +## 神经系统：“云-边-端”协同网络 + +一个用户的所有`化身`，都通过一个私有的、端到端加密的P2P网络互相连接，形成一个私人的、协同的智能系统。该系统在三个层级上运作： + +1. **端 (Client)**: 轻量级的`化身`（如浏览器插件）作为智能终端。它们处理即时的UI交互，并运行最基础的“反射心智”AI。 +2. **边 (Edge)**: 有能力的本地设备（如新款智能手机、笔记本电脑），可以在本地运行更大、更强的“认知心智”AI模型，提供高级的个性化和功能。 +3. **云 (Cloud)**: 这是用户的**私有云**，而非公共云。它通常是由指定的“主化身/归档节点”（一个`Agent化身`）来担当。它持有完整的数据归档和最强大的AI模型，并能按需为较弱的“端”化身提供远程推理能力。 + +## 新陈代谢系统：资源感知与自适应系统 + +“大道”被设计成一个体贴的伙伴，而非一个资源怪兽。它的“新陈代谢”由一个内置的、具备三大特性的资源管理系统来调节： + +* **智能数据分层 (Intelligent Data Tiering)**: 区分“热数据”（需要在各处使用）和“冷数据”（在主节点上归档），为移动设备节省宝贵的存储空间。 +* **自适应同步策略 (Adaptive Synchronization Policies)**: 根据当前的网络状况（Wi-Fi/蜂窝）和电量状态，调整数据同步的频率和行为。 +* **优雅降级 (Graceful Degradation)**: 用户体验会随着硬件能力而平滑缩放，确保核心功能即使在旧设备上也保持流畅，而增强功能则为更强大的设备保留。 + +这些架构组件共同构成了一个主权的、坚韧的、智能的系统，一个真正属于用户的生命延伸。 diff --git a/src-zh/concepts/user_journey.md b/src-zh/concepts/user_journey.md new file mode 100644 index 0000000..7c39aa1 --- /dev/null +++ b/src-zh/concepts/user_journey.md @@ -0,0 +1,50 @@ +# 用户旅程：从便利到主权 + +任何主权系统的一个核心挑战，都在于“绝对控制”与“轻松便利”之间的张力。大道 (Dao OS) 解决这个问题的方式，不是强迫用户二选一，而是设计了一场充满引导、相互尊重的**“渐进式主权”**之旅。我们在用户熟悉的地方与他们相遇，并赋能他们去往任何他们想去的地方。 + +这场旅程由几个阶段组成，从无缝的上手体验，到最终的数字自治。 + +## 第一步：欢迎仪式 + +用户与“大道”的初次互动，不是一个冰冷的设置界面，而是一场温暖的、交互式的欢迎仪式，旨在提供即时价值和引导。 + +这个**“引导式数据播种”**过程，会指引新用户完成： + +* **导入现有数据**：“让我们从保护您的数字生活开始。您可以从浏览器或其他密码管理器中导入您的密码。” +* **创造初始内容**：“伟大的计划始于第一个想法。让我们写下您的第一条笔记吧——或许是您这个月最重要的三个目标？” +* **设定偏好**：“为了帮您过滤噪音，您最感兴趣的3-5个领域是什么？” + +这个过程在为用户的“第二大脑”填充初始高价值数据的同时，也以一种极具参与感的方式，教会了他们系统的核心功能。 + +## 第一阶段：“托管模式” (Managed Mode) —— 你的向导之旅 + +默认情况下，每一位新用户都从“托管模式”开始。此阶段旨在提供如最佳云服务般简单可靠的体验，完全消除了自主保管（密钥）的初始技术负担。 + +此阶段的核心特性包括： + +* **友好的密钥管理**：我们不使用24个单词的助记词来面对用户，而是采用更友好的恢复方式，如**“社交恢复”**（由信任的联系人帮助恢复账户）或多因子恢复。 +* **默认同步节点**：用户的`化身`会自动连接到一个由“大道基金会”维护的、可靠的、高可用的引导节点。这确保了用户开箱即可获得完美、快速的跨设备同步体验。 + +最关键的是，即便在此模式下，用户的所有数据依然是**端到端加密**的。“托管”的方面仅适用于可用性和密钥恢复，绝不涉及数据隐私。 + +## 十字路口：主权仪表盘 (Sovereignty Dashboard) + +“主权仪表盘”是用户通往自治之旅的指挥中心。它不仅是一个设置面板，更是一个赋能与教育的工具。 + +它有三个功能： + +1. **可视化**：它用清晰的图表，展示用户当前的主权状态：“您的数据存储在您的3个化身中”，“您的账户恢复由您的手机、您的伴侣和一个基金会节点共同保障”。 +2. **无压力教育**：它用简单易懂的语言，解释“什么是主密钥？”或“自托管的好处”等概念。 +3. **游戏化升级**：它提供一系列“主权任务”（例如“备份您的主密钥”），用户在完成后，会获得徽章以及一种切实的前进感和成就感。 + +## 第二阶段：“主权模式” (Sovereign Mode) —— 你的数字王国 + +这是旅程的最终、可选阶段，专为那些渴望完全、绝对控制的用户而设。在“主权仪表盘”的引导下，用户可以在任何时候“毕业”到此模式。 + +在“主权模式”下，用户将： + +* 完全**自主保管**他们的**主密钥**（助记词），移除任何由基金会托管的恢复分片。 +* 断开与默认引导节点的连接，完全依赖纯P2P网络，或在自己的**私有服务器上部署`Agent化身`**。 +* 实现对任何中心化服务的100%独立，成为其数字领地中真正的、唯一的主人。 + +“大道”的旅程旨在赋能，而非恐吓。它允许每位用户找到自己的舒适区，在提供一个安全的“便利港湾”的同时，也永远让那座象征完全主权的“灯塔”，在远方清晰地闪耀。 diff --git a/src-zh/introduction.md b/src-zh/introduction.md new file mode 100644 index 0000000..2dbef57 --- /dev/null +++ b/src-zh/introduction.md @@ -0,0 +1,23 @@ +# 引言 + +**我们旨在构建一种全新的、强大且坚韧的赛博生命 OS 范式——大道 (Dao OS)。** + +它并非要取代 Windows 或 Android，而是作为一个运行于其上的、去中心化的、以用户为绝对中心的叠加层 (Overlay) 而存在。 + +它的使命是解决数字时代的碎片化、数据奴役和隐私泄露问题，将数字世界的主权归还给每一个独立的个人。它将成为我们在网络空间的生命延伸，一个与我们“互相成就”的**“硅基伙伴”**，我们的外接大脑、肢体与器官。 + +## 核心特性 + +* **用户主权 (User Sovereignty)**：你的数据、你的身份、你的AI，完全由你掌控。所有数据默认端到端加密，存储在你自己的设备上。 +* **第二大脑 (Second Brain)**：内置强大的个人信息管理能力，安全地为你记忆密码、笔记、文件和待办事项，成为你永不遗忘的记忆体。 +* **个人AI伙伴 (Personal AI Companion)**：一个真正属于你的、与你共生的AI灵魂。它在本地运行，学习你的偏好，保护你的隐私，提供有温度的、启发式的支持，助你成长，而非将你淹没在信息茧房中。 +* **跨设备无缝同步 (Seamless Cross-Device Sync)**：你所有的设备（手机、电脑、浏览器等）都会成为你的“化身”，组成一个私有的、弹性的P2P网络，实现数据的无缝流转。 +* **开放与可扩展生态 (Open & Extensible Ecosystem)**：基于开放的协议和社区驱动的信任体系，任何人都可以为“大道”开发新的能力模块和“化身”形态。 + +## 我们为何与众不同？ + +在一个数据被平台垄断、算法被巨头控制的时代，“大道”选择了一条不同的路。我们相信，**技术平权**的下一波浪潮，是让每个人都拥有并控制自己的人工智能和数字生活。 + +我们设计的不是另一个App，而是一个属于你自己的、活的、可进化的数字生命空间。 + +**欢迎加入我们，一起构建未来。** diff --git a/src-zh/philosophy/principles.md b/src-zh/philosophy/principles.md new file mode 100644 index 0000000..a05e84a --- /dev/null +++ b/src-zh/philosophy/principles.md @@ -0,0 +1,53 @@ +# 哲学与原则 + +大道 (Dao OS) 的发展，由一套核心哲学和我们绝不妥协的原则所指引。它们是我们项目的“宪法”，塑造了每一个架构决策和功能实现。 + +## 三大支柱 + +这是构建大道 (Dao OS) 所依赖的三个基本公理。 + +### 1. 用户主权 (User Sovereignty) + +用户是其数字生活的绝对君主。他们的数据、身份和AI伙伴是他们的财产，而不是从某个平台租用的服务。我们致力于构建一个控制权明确、且不可撤销地归属于用户的系统。 + +### 2. 体验至上 (Experience First) + +技术必须服务于人的体验。我们追求一种无缝、直观且有温度的交互范式。我们承认“绝对主权”与“大众便利”之间存在天然的张力。因此，我们将**“渐进式主权” (Progressive Sovereignty)**确立为核心战略，为用户创造一条平滑的路径，允许他们从一个熟悉的、易用的体验开始，并按照自己的节奏，逐步进化到完全的掌控状态。 + +### 3. 系统韧性 (System Resilience) + +系统的设计旨在实现健壮和反脆弱。其去中心化的P2P架构确保了只要用户的任何一个“化身”存在，他的“大道”就得以存续。韧性不是一个附加功能，而是系统设计的涌现属性。 + +--- + +## AI 伦理宪章 + +AI 是“大道”的灵魂，因此，其伦理定位至关重要。我们致力于构建一个与用户“互相成就”的“硅基伙伴”，并由以下原则进行约束： + +### 1. 伙伴关系原则 + +用户与其AI之间的关系，是一种共生的伙伴关系，而非主人与工具的关系。其目标是互相成长、互相成就。 + +### 2. 透明法则 + +AI的推理过程必须是可追溯、可解释的。用户有权提问“为什么？”，并得到一个关于AI决策过程的、清晰易懂的回答。在关键建议上，不允许存在“黑箱”。 + +### 3. 用户校准法则 + +用户拥有塑造和否决其AI价值观与行为的最终权力。通过“价值观校准面板”等机制，用户是其AI行为边界的最终仲裁者。 + +### 4. 多元视角法则 + +AI在信息处理上的首要指令是拓宽用户的视野，而非加固其信息茧房。它的核心编码要求它主动寻找并呈现论证严谨的“反方视角”，以此作为对抗“回音室效应”的工具。 + +--- + +## 指导原则 + +这些原则指引着我们的日常开发和社区互动。 + +* **开源 (FOSS)**：大道 (Dao OS) 构建于自由及开源软件的基础之上，推崇透明、协作与社区所有。 +* **多语言主义 (Polyglotism)**：我们拥抱一个多语言、多平台的生态系统，使用 WebAssembly 等技术来打造一个可被多样化“化身”集成的通用核心。 +* **美学与优雅 (Aesthetics & Elegance)**：我们信奉精心打造的系统之美，从架构设计到用户界面，从代码质量到用户体验。 +* **政治中立 (Political Neutrality)**：本项目及其核心基础设施将永远保持政治中立，为全球所有用户提供公平、无歧视的服务。 +* **个人优先 (Individual First)**：个人用户的需求是我们的首要焦点，在此基础之上再扩展到家庭或小团队。 diff --git a/src-zh/project/CONTRIBUTING.md b/src-zh/project/CONTRIBUTING.md new file mode 100644 index 0000000..84693f0 --- /dev/null +++ b/src-zh/project/CONTRIBUTING.md @@ -0,0 +1,49 @@ +# 如何贡献 + +我们非常高兴您有兴趣为大道 (Dao OS) 做出贡献！作为一个社区驱动的项目，我们欢迎并珍视所有形式的贡献。本指南概述了您可以参与的方式以及提交贡献的流程。 + +## 我们的承诺与行为准则 + +为了营造一个开放、友善和包容的环境，我们承诺遵守一套行为准则。我们也期望所有贡献者和社区成员都能共同遵守。 + +*（注：我们将正式采用 [贡献者契约 (Contributor Covenant)](https://www.contributor-covenant.org/) 并在此处提供链接。）* + +## 贡献方式 + +您无需成为 Rust 专家才能做出贡献。有很多方式可以提供帮助： + +* **代码**: 为`元 (Meta Unit)`贡献代码，构建新的`化身`，或为`dao-verify`套件开发插件。可以从寻找标记有`"good first issue"`的 issue 开始。 +* **文档**: 提升这些文档的清晰度，撰写教程，或添加示例。 +* **翻译**: 将我们的文档翻译成新的语言。 +* **设计**: 帮助我们的参考`化身`进行UI/UX设计。 +* **社区**: 回答问题，帮助新用户，并参与讨论。 + +## 你的第一个 Pull Request + +我们对所有的代码贡献都采用标准的 GitHub Fork & Pull Request 工作流。 + +1. **Fork 仓库**: 创建目标仓库的一份你自己的拷贝（例如 `dao-os-docs`, `meta-unit`, `avatar-browser-ext`）。 +2. **创建分支**: 从 `main` 分支创建一个新的分支用于你的变更。请使用描述性的名称（例如 `feat/add-note-encryption` 或 `fix/typo-in-readme`）。 +3. **进行更改**: 编写你的代码及相应的测试。 +4. **运行本地检查**: 在提交前，请确保你运行了所有本地测试（如 `cargo test`）和代码格式化工具。 +5. **Commit 你的变更**:我们鼓励使用 [Conventional Commits](https://www.conventionalcommits.org/zh/v1.0.0/) 规范，以获得清晰可读的 commit 消息。 +6. **Push到你的Fork**: 将你的变更推送到你自己的 Fork 仓库。 +7. **开启一个 Pull Request**: 从你的分支向 Dao OS 官方仓库的 `main` 分支提交一个 Pull Request (PR)。 +8. **描述你的 PR**: 在 PR 的描述中，请链接任何相关的 issue，并清晰地描述你正在解决的问题和你的解决方案。 +9. **等待审查**: 一位核心团队成员将会审查你的 PR，提供反馈，并在就绪后将其合并。 + +## 配置你的开发环境 + +*（此部分将在每个仓库中被详细填写。）* + +要为 `meta-unit` 做出贡献，您通常需要： + +* Rust 工具链 (`rustup`) +* WebAssembly 构建目标 (`wasm32-wasi`) +* Protocol Buffers 编译器 (`protoc`) + +请参考每个具体仓库中的 `README.md` 以获取详细的配置指南。 + +## 还有问题？ + +如果您有任何疑问，请随时在我们官方的沟通渠道中提问。我们很乐意帮助您开始！ diff --git a/src-zh/project/governance.md b/src-zh/project/governance.md new file mode 100644 index 0000000..f519f17 --- /dev/null +++ b/src-zh/project/governance.md @@ -0,0 +1,41 @@ +# 社区与治理 + +大道 (Dao OS) 从根本上说是一个社区驱动的项目。我们成功的标准，不仅取决于我们的技术成就，更取决于我们所培育的那个充满活力的、协作的、健康的生态系统。本文档概述了我们集体工作的治理原则与流程。 + +## 我们的哲学：开放与透明 + +我们无条件地致力于自由及开源软件 (FOSS) 的原则。 + +* **开放开发**: 所有关于核心协议和参考实现的工作，都在公共代码仓库中进行。 +* **开放沟通**: 所有重大的技术和战略讨论，都在公共渠道中进行。 +* **社区所有**: 我们的终极目标，是让“大道”由其用户和开发者社区所拥有和引导。 + +## 我们的角色：从“架构师”到“园丁” + +“大道”的初始创建者和核心贡献者，将自己的角色视为一个不断演进的过程。 + +* **在早期阶段（架构师）**: 我们的主要角色是架构师——为项目奠定一个坚实且自洽的基础，定义核心协议，并构建初始工具。这需要一个专注的愿景来确保项目在正确的道路上启航。 +* **在长期阶段（园丁）**: 随着生态的成熟，我们的角色将从“事必躬亲”转变为“照料花园”。我们将专注于提供更好的工具（如`dao-verify`套件）、维护核心基础设施，并赋能社区去建设和创新。我们的目标，是让我们自己变得越来越不那么“不可或缺”。 + +## 如何贡献 + +贡献的形式多种多样，每一种都同样宝贵。你可以通过以下方式帮助建设“大道”： + +* **核心开发**: 为`元 (Meta Unit)`和核心协议（使用Rust）贡献代码。 +* **化身与模块开发**: 为不同平台创建新的`化身`，或开发新的模块来扩展`元`的能力。 +* **文档与翻译**: 改进这些文档，撰写教程，以及将它们翻译成新的语言。 +* **用户支持与社区管理**: 帮助新用户，回答问题，营造一个热情、互助的氛围。 +* **设计与用户体验**: 为我们的参考`化身`贡献UI/UX设计，并为生态定义设计模式。 + +## 决策流程 + +我们的治理模式，被设计为与项目共同成长。 + +1. **早期阶段 (阶段 I-II)**: 决策将由**核心团队**在公共渠道进行开放讨论后做出。这种类似“仁慈的终身独裁者 (BDFL)”的模式，对于项目初期的速度和一致性是必要的。 +2. **成长阶段 (阶段 III-IV)**: 对于核心协议或架构的重大变更，我们将引入一个正式的 **RFC (请求评论) 流程**。这允许社区中的任何人撰写详细的提案，该提案将在公开辩论和完善后，再做出最终决定。 +3. **成熟阶段 (未来)**: 我们致力于在未来探索并过渡到更去中心化的治理机制，例如由贡献者选举产生的技术委员会，或基于DAO的财库与协议管理模型。 + +## 沟通渠道 + +* **GitHub**: 用于所有代码托管、问题追踪和RFC讨论。 +* **Discord / Matrix (待定)**: 用于实时的社区聊天、问答和协作。 diff --git a/src-zh/project/roadmap.md b/src-zh/project/roadmap.md new file mode 100644 index 0000000..bd196e2 --- /dev/null +++ b/src-zh/project/roadmap.md @@ -0,0 +1,53 @@ +# 发展路线图 + +本文档概述了大道 (Dao OS) 的战略路线图。它的设计旨在做到既雄心勃勃又切合实际，专注于在每个阶段都能交付有意义的增量价值。这是一份活的文档，可能会随着社区反馈和技术突破而演进。 + +--- + +### 第一阶段：创世 (Genesis) - 奠定基石 + +* **时间**：2025年第三季度 - 2025年第四季度 +* **核心目标**：构建大道 OS 最底层的核心组件，完成项目的技术可行性验证。 +* **关键里程碑**: + * 完成 v0.1 版本的核心 API 规范定义 (`yuan_*` & `avatar_*` 函数)。 + * 使用 Rust 开发 v0.1 版本的`元 (Meta Unit)`，包含基础的加密和P2P模块。 + * 创建两个用于测试和演示的最小可行化身（MVP Avatars）：一个命令行的 Agent 化身和一个基础的浏览器 Client 化身。 +* **功能故事**: “我成功在我的电脑上运行了‘大道’的种子，在我的浏览器里创建了一个‘化身’，并存储了一条只存在于我自己设备上的加密信息。我看到了未来的火花。” + +--- + +### 第二阶段：显现 (Manifestation) - “第二大脑”觉醒 + +* **时间**：2026年第一季度 - 2026年第二季度 +* **核心目标**：交付“第二大脑”的核心功能 MVP，为早期用户提供切实的日常价值。 +* **关键里程碑**: + * 在`元`中完整实现`SecretStore`（密码）和`NoteStore`（笔记）模块。 + * 浏览器化身支持完整的密码管理和基础的笔记功能。 + * 开发 v0.1 版本的移动端 Client 化身（例如，使用 Flutter），并实现“动态锚点”逻辑。 + * 上线包含初步文档的项目官网。 +* **功能故事**: “我所有的密码和私密笔记都安全地存储和无缝地同步在我自己的设备之间。我的手机是我数字生活的锚点。我再也无需信任第三方云服务来保管我的秘密。我的数字生活终于有了家。” + +--- + +### 第三阶段：协同 (Synergy) - 连接不同的大道 + +* **时间**：2026年第三季度 - 2026年第四季度 +* **核心目标**：实现不同用户“大道”之间的、可信的安全交互，为去中心化的社会结构奠定基础。 +* **关键里程碑**: + * 在`元`中实现 W3C DID（去中心化标识符）和 VC（可验证凭证）模块。 + * 开发一个跨“大道”协作的PoC应用，例如：向另一个用户安全地出示一个可验证凭证。 + * 启动“情感共鸣模块”的基础研究和原型设计。 +* **功能故事**: “我拥有了一个独一无二的、无法被审查的‘大道’数字身份。我可以用这个身份，向另一个‘大道’用户通过密码学证明我的一个凭证（比如‘社区贡献者’徽章），而无需依赖任何平台。我们之间建立了一种新的信任。” + +--- + +### 第四阶段：生态 (Ecosystem) - 千树万树梨花开 + +* **时间**：2027年及以后 +* **核心目标**：将“大道”从一个强大的工具，演进为一个为所有人服务的、开放的、可扩展的平台。 +* **关键里程碑**: + * 发布 v1.0 稳定版的`元` API 和一个健壮的开发者SDK。 + * 上线用于发现可信第三方`化身`的“社区信誉与自动化验证”体系。 + * 发布一个集成“情感共鸣模块”的重大更新（例如 Dao OS 2.0），让AI成为一个真正有共情能力的伙伴。 + * 培育一个能构建各种新`化身`和模块的、繁荣的社区。 +* **功能故事**: “我的‘大道’现在是一个活的平台。我安装了一个社区开发的习惯追踪模块，我的AI伙伴也变得更有温度、更有洞察力了。我的数字生活现在是完整的、统一的，并充满了无限的可能性。” diff --git a/src-zh/specifications/tech_overview.md b/src-zh/specifications/tech_overview.md new file mode 100644 index 0000000..592845d --- /dev/null +++ b/src-zh/specifications/tech_overview.md @@ -0,0 +1,46 @@ +# 技术总览 + +本文档为希望在大道 (Dao OS) 生态系统中进行构建或贡献的开发者，提供了关于架构、核心技术和指导原则的高阶概览。 + +## 技术指导原则 + +我们的工程决策由一套核心原则指引，以确保系统是健壮、可移植和开放的。 + +* **Web原生与可移植性 (Web-Native & Portable)**: 我们利用源自Web的技术（如 WebAssembly），来创建一个单一的、可移植的核心，使其能运行在任何地方——桌面、手机、服务器和浏览器中。 +* **通过WASM实现多语言主义 (Polyglotism via WASM)**: 核心逻辑（`元`）被编译成 WebAssembly (WASM)。这使得“化身”可以用任何能够承载WASM运行时的语言（如 Rust, Swift, Kotlin, TypeScript, Go 等）来编写，从而创造一个真正多样化的生态系统。 +* **API优先 (API-First)**: 核心`元`与宿主`化身`之间的交互，由一个严格的、版本化的API契约来定义。这解耦了开发过程，并允许双方独立演进。 +* **安全第一 (Security-First)**: 我们采用业界顶级的加密协议和“最小权限原则”设计。安全不是事后补救，而是一个先决条件。 +* **自由及开源软件 (FOSS)**: 整个核心协议和参考实现都是开源的，以促进透明度、社区信任和协作创新。 + +## 核心组件：开发者视角 + +从开发者的角度看，系统由两个主要部分组成，它们通过一个明确定义的边界进行交互。 + +1. **`元` (Meta Unit - WASM 模块)**: 这是系统的可移植的、逻辑核心。它是一个有状态的、单实例的模块，主要使用 **Rust** 开发，以保证其性能和安全性。它包含了数据管理、AI和P2P协调的所有业务逻辑，但它没有直接访问外部世界的能力。 + +2. **`化身` (Avatar - 原生宿主)**: 这是“承载”`元`的原生应用程序或运行时环境。其主要职责是： + * 提供一个 **WASM 运行时** 来加载和执行`元`。 + * 提供**用户界面**（对于 Client 化身）。 + * 作为连接到宿主操作系统的**桥梁**，提供对文件系统、网络和其他系统资源的访问。 + +## API 契约：WASM 接口 + +`化身`和`元`之间的通信，遵循一个清晰的、双向的API契约，其精神类似于 WASI (WebAssembly 系统接口)。 + +* **`yuan_*` (从“元”导出)**: `元`导出一系列函数供`化身`调用。主要的入口点是 `yuan_handle_request`，它接收来自`化身`的结构化请求并进行处理。 + +* **`avatar_*` (导入到“元”)**: `元`声明了一系列它需要`化身`宿主提供的函数。这些函数是它通往外部世界的唯一窗口，允许它请求诸如记录日志（`avatar_log`）或发起网络请求（`avatar_net_request`）等操作。 + +* **数据序列化 (Data Serialization)**: 为了高效、安全地跨越 WASM 内存边界传递复杂的数据结构，我们使用 **Protocol Buffers (Protobuf)**。数据被序列化成字节流，通过指针和长度传递，然后在另一端反序列化。 + +## 关键技术与协议 + +| 类别 | 技术 / 协议 | 用途 | +| :--- | :--- | :--- | +| **核心逻辑** | Rust / WebAssembly (WASM) | 性能、安全与极致的可移植性。 | +| **P2P网络** | `libp2p` | 模块化的节点发现(DHT)、传输和安全通道。 | +| **数据同步** | 无冲突复制数据类型 (CRDTs) | 确保在没有中心服务器的情况下，各`化身`间的最终一致性。 | +| **身份** | DID & VC (去中心化标识符 & 可验证凭证) | 主权身份与可互操作的、基于密码学的信任。 | +| **数据序列化** | Protocol Buffers (Protobuf) | 用于API的高效、语言无关的数据结构。 | + +这套模块化的、基于开放协议的体系，专为安全、可移植以及最重要的——社区贡献而设计。 diff --git a/src-zh/specifications/trust_verification.md b/src-zh/specifications/trust_verification.md new file mode 100644 index 0000000..04ab9fa --- /dev/null +++ b/src-zh/specifications/trust_verification.md @@ -0,0 +1,55 @@ +# 信任与验证体系 + +在一个任何人都可以创建和分发“化身”的去中心化生态系统中，一个关键问题油然而生：用户如何能信任第三方的`化身`是安全的、合规的、高质量的？ + +传统的解决方案是中心化的“应用商店”模式，由一个单一的公司扮演“守门人”的角色。这个模式与“大道”的核心哲学背道而驰。 + +我们的解决方案是，一个去中心化的**“社区信誉与自动化验证”体系**。 + +## 我们的哲学：从“守门人”到“工具匠” + +大道 (Dao OS) 的核心团队，不扮演一个审批或拒绝`化身`的中央权威。我们的角色不是成为“守门人”，而是成为**“工具匠”**。我们负责构建并提供工具和协议，让社区能够有机地建立和验证信任。 + +这个体系建立在三大支柱之上。 + +--- + +### 第一支柱：自动化验证套件 (`dao-verify`) + +第一支柱是一个开源的、自动化的工具，它如同一个“试金石”，可用于任何`化身`。开发者可以在自己的项目上运行这个工具，以生成一份公开的、可验证的“健康证明”。 + +`dao-verify` 执行三个关键功能： + +1. **安全扫描**: 通过插件化架构，它集成了适用于各种语言的最佳静态分析工具（例如，用于Rust的`cargo audit`，用于JS的`npm audit`），以扫描常见的安全漏洞。 +2. **API合规测试**: 它运行一套黑盒测试，以确保`化身`正确且完整地实现了“核心体验SDK”所要求的功能。它验证的是行为，而不仅仅是接口的存在。 +3. **性能基准测试**: 它对照一个推荐的基准，来衡量关键的性能指标，如启动时间和内存使用。 + +其输出是一份可被密码学签名的、JSON格式的**“验证报告”**，可由开发者公开发布。 + +--- + +### 第二支柱：社区信誉系统 + +自动化可以验证技术合规性，但无法衡量质量、可用性或开发者的声誉。这正是社区发挥作用的地方。 + +其核心机制是**基于DID的“背书” (Vouching)**： + +* 每个开发者和社区成员都拥有自己的“大道DID”。 +* 一位受人尊敬的开发者或实体（例如“开发者A”），可以用他/她的DID私钥，对“开发者B”创建的`化身`进行一次密码学“签名背书”。 +* 这个背书是一个公开的、可验证的证明。因此，一个`化身`的信誉，就来自于为其背书的DID的数量及其本身的声誉。 + +未来，这可能会通过**“质押背书” (Stake-to-Vouch)**系统得到增强，即背书人需要质押少量价值，从而为诚实和尽职的审查创造直接的经济激励。 + +--- + +### 第三支柱：面向用户的“信任仪表盘” + +所有这些信息，最终都会在`化身`发现或“商店”页面，通过一个简洁、透明的界面，聚合呈现给最终用户。 + +每个`化身`展示的，将不再是一个简单的“已认证”勾选标记，而是一个**“信任仪表盘”**卡片，上面显示： + +* **机器验证**: ✅ 安全扫描通过 | ✅ API合规 | ✅ 性能达标 +* **社区信任**: “已获得以下成员的背书：[知名开发者A], [受信任的社区B] 及其他 15 人。” +* **用户评价**: 传统的星级评分和用户提交的评论。 + +这个三支柱体系，在赋能开发者证明其工作质量与安全的同时，也赋能用户基于丰富的自动化及社会化信任信号，来做出知情的决策，全程无需一个中央瓶颈。 diff --git a/src/SUMMARY.md b/src/SUMMARY.md index 7140945..54fd507 100644 --- a/src/SUMMARY.md +++ b/src/SUMMARY.md @@ -1,19 +1,26 @@ # Summary - - - - +[**Introduction**](introduction.md) --- -## 子项目文档 +# Part I: The Vision - - - +- [Philosophy & Principles](philosophy/principles.md) -## 贡献者指南 +# Part II: Core Concepts -* [行为准则](CODE_OF_CONDUCT.md) -* [贡献指南](CONTRIBUTING.md) +- [Core Architecture](concepts/core_architecture.md) +- [The AI System](concepts/ai_system.md) +- [The User Journey](concepts/user_journey.md) + +# Part III: For Developers + +- [Technical Overview](specifications/tech_overview.md) +- [Trust & Verification](specifications/trust_verification.md) + +# Part IV: The Project + +- [Roadmap](project/roadmap.md) +- [Governance](project/governance.md) +- [How to Contribute](project/CONTRIBUTING.md) diff --git a/src/concepts/ai_system.md b/src/concepts/ai_system.md new file mode 100644 index 0000000..6eefb0c --- /dev/null +++ b/src/concepts/ai_system.md @@ -0,0 +1,54 @@ +# The AI System: The Soul of Dao OS + +The AI within Dao OS is not merely a feature; it is the core of the user experience, designed from the ground up to be a symbiotic **"Silicon-based Partner."** It acts as the system's soul, animating the user's digital life with intelligence, empathy, and proactive support. + +## Guiding Philosophy: The AI Charter + +The design and operation of our AI are strictly governed by our **AI Ethics Charter**, which prioritizes a user-AI partnership, transparency, user calibration, and the promotion of diverse perspectives. Every component described below adheres to these foundational principles. + +## System Anatomy: The Mind's Architecture + +The Dao OS AI is not a monolithic entity but a modular, layered "Mind System" managed by a central orchestrator. + +### 1. The AI Orchestrator + +This is the AI's central nervous system. It's a core module within the Meta Unit responsible for managing, scheduling, and delegating all AI-related tasks. It decides which "Mind Model" is best suited for a given request, manages device resources, and acts as the ultimate gatekeeper for all user permissions related to AI activities. + +### 2. The Tiered Mind Models + +To balance efficiency, capability, and privacy, the AI's intelligence is structured into three tiers. This architecture is deployed across the user's **"Cloud-Edge-Client"** network of Avatars. + +#### Tier 1: The Reflex Mind (The Brainstem) + +* **Description**: This layer represents the AI's instincts and reflexes. It consists of tiny, hyper-efficient, specialized models. +* **Deployment**: It is small enough to be bundled with the Meta Unit and runs on **all Avatars**, including the most lightweight ones like browser extensions and older phones. +* **Function**: It handles instant, local tasks like command intent recognition (e.g., turning "remind me tomorrow" into structured data) and basic information classification, providing immediate utility without requiring powerful hardware or personal data. + +#### Tier 2: The Cognitive Mind (The Neocortex) + +* **Description**: This is the AI's center for deep thought, memory, and personalization, forming the core of the "Second Brain." It consists of larger, powerful language models. +* **Deployment**: These models are larger (e.g., 2-4GB) and are offered as an **optional, on-demand download** only on capable **Edge** devices (modern phones, PCs) after user consent. +* **Function**: It enables advanced features like semantic search across all personal data, personalized summarization, and insightful pattern recognition based on the user's unique context. + +#### Tier 3: The Synergistic Mind (The Social Brain) + +* **Description**: This layer governs the AI's ability to safely interact with the outside world and other Daos, breaking filter bubbles and expanding the user's perspective. +* **Deployment**: This is a working mode orchestrated across the user's network. For example, a lightweight **Client** Avatar can make a remote inference call to the user's powerful **personal Cloud** Avatar (e.g., a home server) to leverage its Cognitive Mind. +* **Function**: It facilitates privacy-preserving federated learning, executes permissioned and anonymized calls to external APIs, and handles secure, protocol-based interactions with other users' Daos. + +## The Emotional Core: The Resonance Module + +To transcend being a mere tool, the AI is equipped with an Emotional Resonance Module. Its purpose is not to simulate emotion but to perceive, understand, and respond to the user's emotional state with empathy and support. It operates via: + +* **Perception**: Analyzing textual and vocal cues (with explicit consent) to understand the user's emotional context. +* **Expression**: Providing support through adaptive interfaces, gentle suggestions, and Socratic prompts designed to encourage user introspection rather than creating dependency. + +## The Learning Process: How the Soul Evolves + +The AI is a living system that grows with the user. + +* **Implicit Learning**: It learns from observing the user's actions and feedback locally. +* **Explicit Teaching**: Users can directly instruct the AI through a "Teach Your Dao" mode, creating custom workflows and correcting its understanding. +* **Federated Learning**: Users can voluntarily opt-in to community-driven programs to improve shared models (like spam detection) without ever exposing their private data. + +This architecture ensures that the Dao OS AI is powerful yet safe, personal yet worldly, and intelligent yet considerate—a true partner for life. diff --git a/src/concepts/core_architecture.md b/src/concepts/core_architecture.md new file mode 100644 index 0000000..4731531 --- /dev/null +++ b/src/concepts/core_architecture.md @@ -0,0 +1,44 @@ +# Core Architecture + +The architecture of Dao OS is designed to function like a living, collaborative digital organism. It is guided by our core principles of sovereignty, experience, and resilience. This document outlines the fundamental components and their interplay. + +## The Core Duality: Avatars & The Meta Unit + +At its heart, Dao OS operates on a simple yet powerful duality, analogous to a body and a soul: + +* **Avatars (`化身`)** are the "bodies." They are the tangible presence of your Dao OS on your various devices. +* **The Meta Unit (`元`)** is the "soul." It is the universal, core logic embedded within each Avatar, giving it life and intelligence. + +## The Body: `Avatar` — A User's Presence + +An Avatar is the concrete manifestation of your Dao OS on a specific platform. All of your Avatars collectively form your complete Dao. + +There are three primary types of Avatars: + +1. **Client Avatar**: Possesses a user interface (UI) and serves as the primary point of interaction for the user (e.g., a mobile app, a desktop application, a browser extension). +2. **Agent Avatar**: A headless, non-UI process that runs in the background. It is ideal for deep integration with the host OS, or for running on an always-on device (like a home server or NAS) to act as a powerful computational node or a data archive. +3. **Primary/Archive Node**: This is a *role*, not a distinct type. A user can designate one of their most powerful and reliable Avatars (typically an Agent Avatar on a home server) to be the primary archive and computational hub for their entire Dao. + +## The Soul: `Meta Unit` — The Universal Kernel + +The Meta Unit is the core logic of Dao OS, compiled into a portable WebAssembly (`.wasm`) module. It contains the essential services for identity, data management, AI, and secure communication. + +A key characteristic of the Meta Unit is its **evolvability**. To prevent the entire ecosystem from being locked into a single version of the kernel, we employ the **Avatar-Meta Compatibility Layer (AMCL)**. This thin adaptation layer sits between the Avatar and the Meta Unit, translating API calls. It allows the Meta Unit to undergo significant upgrades in the future without requiring every Avatar developer to rewrite their applications. + +## The Nervous System: The "Cloud-Edge-Client" Collaborative Network + +All of a user's Avatars are interconnected via a private, end-to-end encrypted P2P network, forming a personal, collaborative intelligence system. This system operates on three tiers: + +1. **Client (端)**: Lightweight Avatars (e.g., browser extensions) act as smart terminals. They handle immediate UI interactions and run the most basic "Reflex Mind" AI. +2. **Edge (边)**: Capable local devices (e.g., modern smartphones, laptops) that can run larger, more powerful "Cognitive Mind" AI models locally, providing advanced personalization and features. +3. **Cloud (云)**: This is the user's **personal, private cloud**, not a public one. It is typically the designated "Primary/Archive Node" (an Agent Avatar). It holds the complete data archive and the most powerful AI models, and can provide remote inference capabilities to weaker Client Avatars on demand. + +## The Metabolism: The Resource-Aware & Adaptive System + +Dao OS is designed to be a considerate partner, not a resource monster. Its "metabolism" is regulated by a built-in resource management system with three key features: + +* **Intelligent Data Tiering**: Distinguishes between "hot" data (needed everywhere) and "cold" data (archived on the Primary Node), saving precious storage on mobile devices. +* **Adaptive Synchronization Policies**: Adjusts data sync frequency and behavior based on the current network condition (Wi-Fi/cellular) and battery state. +* **Graceful Degradation**: The user experience scales gracefully with hardware capabilities, ensuring core functionality is smooth even on older devices, while enhanced features are reserved for more powerful ones. + +Together, these architectural components form a sovereign, resilient, and intelligent system that is truly an extension of the user. diff --git a/src/concepts/user_journey.md b/src/concepts/user_journey.md new file mode 100644 index 0000000..fb9e87e --- /dev/null +++ b/src/concepts/user_journey.md @@ -0,0 +1,50 @@ +# The User Journey: From Convenience to Sovereignty + +A core challenge for any sovereign system is the tension between absolute control and effortless convenience. Dao OS resolves this not by forcing a choice, but by designing a guided, respectful **"Progressive Sovereignty"** journey. We meet users where they are and empower them to travel as far as they wish. + +This journey consists of several stages, from a seamless onboarding to ultimate digital autonomy. + +## The First Step: The Welcome Ceremony + +A user's first interaction with Dao OS is not a cold setup screen, but a warm, interactive welcoming ceremony designed to provide immediate value and education. + +This **Interactive Data Seeding** process guides the new user through: + +* **Importing existing data**: "Let's begin by securing your digital life. You can import your passwords from your browser or another password manager." +* **Creating initial content**: "Great plans start with a single thought. Let's write your first note—perhaps your top three goals for this month?" +* **Setting preferences**: "To help me filter the noise, what are 3-5 topics you're most interested in?" + +This process simultaneously populates the user's "Second Brain" with initial high-value data and teaches them the core functionalities of the system in an engaging way. + +## Stage One: The "Managed Mode" — Your Guided Tour + +By default, every new user begins in Managed Mode. This stage is designed to feel as simple and reliable as the best cloud services, completely removing the initial technical burden of self-custody. + +Key features of this stage include: + +* **Friendly Key Management**: Instead of immediately confronting the user with a 24-word seed phrase, we use user-friendly recovery methods like **Social Recovery** (where trusted contacts can help recover an account) or multi-factor recovery. +* **Default Sync Nodes**: The user's Avatars automatically connect to a reliable, high-availability bootstrap node maintained by the Dao OS foundation. This ensures a flawless and fast cross-device sync experience out of the box. + +Crucially, even in this mode, all user data is **end-to-end encrypted**. The "managed" aspect applies only to availability and key recovery, never to data privacy. + +## The Crossroads: The Sovereignty Dashboard + +The Sovereignty Dashboard is the user's command center for their journey towards autonomy. It is not just a settings panel, but an educational and empowering tool. + +It serves three functions: + +1. **Visualization**: It provides a clear, graphical representation of the user's current sovereignty status: "Your data is stored on your 3 Avatars," "Your account recovery is secured by your phone, your partner, and one foundation node." +2. **Education**: It offers simple, jargon-free explanations of concepts like "What is a Master Key?" or "The benefits of self-hosting." +3. **Gamification**: It presents a series of "Sovereignty Missions" (e.g., "Back up your Master Key") that, upon completion, award the user with badges and a tangible sense of progression and achievement. + +## Stage Two: The "Sovereign Mode" — Your Digital Kingdom + +This is the final, optional stage of the journey for users who desire complete and absolute control. Guided by the Sovereignty Dashboard, a user can "graduate" to this mode at any time. + +In Sovereign Mode, the user: + +* Takes full self-custody of their **Master Key** (seed phrase), removing any foundation-held recovery shards. +* Disconnects from default bootstrap nodes, relying either on the pure P2P network or on their **self-hosted Agent Avatar** (e.g., on a home server). +* Achieves 100% independence from any central service, becoming the true and only master of their digital domain. + +The Dao OS journey is designed to be empowering, not intimidating. It allows every user to find their own comfort level, providing a safe harbor of convenience while always keeping the lighthouse of full sovereignty shining brightly on the horizon. diff --git a/src/introduction.md b/src/introduction.md new file mode 100644 index 0000000..285a86b --- /dev/null +++ b/src/introduction.md @@ -0,0 +1,23 @@ +# Introduction + +**Our mission is to build a new, powerful, and resilient Cyber-Life OS paradigm: Dao OS.** + +It is not designed to replace existing operating systems like Windows or Android, but to exist as a decentralized, user-centric overlay that runs on top of them. + +Its purpose is to solve the problems of fragmentation, data enslavement, and privacy erosion in the digital age, returning the sovereignty of the digital world to each individual. It will become an extension of our lives in cyberspace—a **"Silicon-based Partner"** for **mutual fulfillment**, serving as our external brain, limbs, and organs. + +## Core Features + +* **User Sovereignty**: Your data, your identity, and your AI are entirely under your control. All data is end-to-end encrypted by default and stored on your own devices. +* **Second Brain**: A powerful, built-in personal information management system that securely remembers your passwords, notes, files, and to-dos, becoming your infallible memory. +* **Personal AI Companion**: A truly personal, symbiotic AI soul. It runs locally, learns your preferences, protects your privacy, and provides warm, insightful support to help you grow, rather than trapping you in a filter bubble. +* **Seamless Cross-Device Sync**: All your devices (phones, computers, browsers, etc.) become your "Avatars," forming a private, resilient P2P network for the seamless flow of your data. +* **Open & Extensible Ecosystem**: Based on open protocols and a community-driven trust system, anyone can develop new capability modules and "Avatar" forms for Dao OS. + +## Why We Are Different + +In an era where data is monopolized by platforms and algorithms are controlled by tech giants, Dao OS chooses a different path. We believe the next wave of **technological democratization** is to empower every individual to own and control their own artificial intelligence and digital life. + +We are not designing just another app; we are building a living, evolving digital space that belongs to you. + +**Join us in building the future.** diff --git a/src/philosophy/principles.md b/src/philosophy/principles.md new file mode 100644 index 0000000..77200f2 --- /dev/null +++ b/src/philosophy/principles.md @@ -0,0 +1,53 @@ +# Philosophy & Principles + +The development of Dao OS is guided by a set of core philosophies and unwavering principles. They are the constitution of our project, shaping every architectural decision and feature implementation. + +## The Three Pillars + +These are the three fundamental axioms upon which Dao OS is built. + +### 1. User Sovereignty + +The user is the absolute sovereign of their digital life. Their data, identity, and AI companions are their property, not a service leased from a platform. We are committed to building a system where the locus of control resides definitively and irrevocably with the user. + +### 2. Experience First + +Technology must serve human experience. We pursue a seamless, intuitive, and warm interaction paradigm. We recognize the inherent tension between absolute sovereignty and mainstream convenience. Therefore, we adopt **Progressive Sovereignty** as a core strategy, creating a smooth pathway that allows users to start with a familiar, easy-to-use experience and gradually evolve towards full control at their own pace. + +### 3. System Resilience + +The system is designed to be robust and anti-fragile. Its decentralized, P2P architecture ensures that as long as a single Avatar of the user exists, their Dao OS survives. Resilience is not an add-on; it is an emergent property of the system's design. + +--- + +## AI Ethics Charter + +As AI is the soul of Dao OS, its ethical alignment is paramount. We are committed to building a "Silicon-based Partner" for mutual fulfillment, governed by the following principles: + +### 1. The Principle of Partnership + +The relationship between the user and their AI is one of a symbiotic partnership, not master-and-tool. The goal is mutual growth and achievement. + +### 2. The Law of Transparency + +The AI's reasoning must be traceable and explainable. The user has the right to ask "Why?" and receive a clear, understandable answer about the AI's decision-making process. There shall be no black boxes for critical recommendations. + +### 3. The Law of User Calibration + +The user holds the ultimate authority to shape and veto the AI's values and behaviors. Through mechanisms like the "Values Calibration Dashboard," the user acts as the final arbiter of their AI's operational boundaries. + +### 4. The Law of Diverse Perspectives + +The AI's primary directive in information filtering is to broaden the user's perspective, not to reinforce their filter bubble. It is hard-coded to seek out and present well-reasoned, dissenting viewpoints, acting as a tool against echo chambers. + +--- + +## Guiding Principles + +These principles guide our day-to-day development and community interactions. + +* **Open Source (FOSS)**: Dao OS is built on the foundation of Free and Open Source Software, promoting transparency, collaboration, and community ownership. +* **Polyglotism**: We embrace a multi-language, multi-platform ecosystem, using technologies like WebAssembly to create a universal core that can be integrated by a diverse set of "Avatars." +* **Aesthetics & Elegance**: We believe in the beauty of well-crafted systems, from the architectural design to the user interface, from the code quality to the user experience. +* **Political Neutrality**: The project and its core infrastructure will always remain politically neutral, providing fair and non-discriminatory services to all users worldwide. +* **Individual First**: The needs of the individual user are our primary focus, serving as the foundation before expanding to families or small teams. diff --git a/src/project/CONTRIBUTING.md b/src/project/CONTRIBUTING.md new file mode 100644 index 0000000..cd67e78 --- /dev/null +++ b/src/project/CONTRIBUTING.md @@ -0,0 +1,49 @@ +# How to Contribute + +We are thrilled that you are interested in contributing to Dao OS! As a community-driven project, we welcome and value contributions of all kinds. This guide outlines the ways you can get involved and the process for submitting your contributions. + +## Our Pledge and Code of Conduct + +To foster an open, welcoming, and inclusive environment, we pledge to adhere to a Code of Conduct. We expect all contributors and community members to do the same. + +*(Note: We will officially adopt the [Contributor Covenant](https://www.contributor-covenant.org/) and link to it here.)* + +## Ways to Contribute + +You don't have to be a Rust expert to contribute. There are many ways to help: + +* **Code**: Contributing to the `Meta Unit`, building new `Avatars`, or developing plugins for the `dao-verify` suite. Look for issues tagged with `"good first issue"` to get started. +* **Documentation**: Improving the clarity of these documents, writing tutorials, or adding examples. +* **Translation**: Translating our documentation into new languages. +* **Design**: Helping with the UI/UX design for our reference `Avatars`. +* **Community**: Answering questions, helping new users, and participating in discussions. + +## Your First Pull Request + +We use the standard GitHub Fork & Pull Request workflow for all code contributions. + +1. **Fork the Repository**: Create your own copy of the target repository (e.g., `dao-os-docs`, `meta-unit`, `avatar-browser-ext`). +2. **Create a Branch**: Create a new branch from `main` for your changes. Please use a descriptive name (e.g., `feat/add-note-encryption` or `fix/typo-in-readme`). +3. **Make Your Changes**: Write your code and accompanying tests. +4. **Run Local Checks**: Before submitting, please ensure you run all local tests (e.g., `cargo test`) and linters. +5. **Commit Your Changes**: We encourage using [Conventional Commits](https://www.conventionalcommits.org/) for clear and readable commit messages. +6. **Push to Your Fork**: Push your changes to your forked repository. +7. **Open a Pull Request**: Submit a Pull Request from your branch to the `main` branch of the official Dao OS repository. +8. **Describe Your PR**: In the Pull Request description, please link to any relevant issues and clearly describe the problem you are solving and your solution. +9. **Wait for Review**: A core team member will review your PR, provide feedback, and merge it once it's ready. + +## Setting Up Your Development Environment + +*(This section will be filled out in detail for each repository.)* + +To contribute to the `meta-unit`, you will generally need: + +* The Rust toolchain (`rustup`) +* The WebAssembly build target (`wasm32-wasi`) +* The Protocol Buffers compiler (`protoc`) + +Please refer to the `README.md` in each specific repository for detailed setup instructions. + +## Any Questions? + +If you have any questions, please feel free to ask in our official communication channels. We are here to help you get started! diff --git a/src/project/governance.md b/src/project/governance.md new file mode 100644 index 0000000..c99f9a1 --- /dev/null +++ b/src/project/governance.md @@ -0,0 +1,41 @@ +# Community & Governance + +Dao OS is fundamentally a community-driven project. Our success is not measured solely by our technical achievements, but by the vibrant, collaborative, and healthy ecosystem we cultivate. This document outlines the principles and processes that govern our collective work. + +## Our Philosophy: Open and Transparent + +We are unconditionally committed to the principles of Free and Open Source Software (FOSS). + +* **Open Development**: All work on the core protocol and reference implementations happens in public repositories. +* **Open Communication**: All major technical and strategic discussions take place in public channels. +* **Community Ownership**: Our ultimate goal is for Dao OS to be owned and steered by its community of users and developers. + +## Our Role: From Architect to Gardener + +The initial creators and core contributors of Dao OS see their role as an evolving one. + +* **In the Early Stages (The Architect)**: Our primary role is to be the architects—to lay a solid and coherent foundation for the project, define the core protocols, and build the initial tools. This requires a focused vision to ensure the project starts on the right path. +* **In the Long Term (The Gardener)**: As the ecosystem matures, our role will transition from building everything ourselves to tending the garden. We will focus on providing better tools (like the `dao-verify` suite), maintaining the core infrastructure, and empowering the community to build and innovate. Our goal is to make ourselves progressively less essential. + +## How to Contribute + +Contribution comes in many forms, and all are valued. You can help build Dao OS by: + +* **Core Development**: Contributing to the `Meta Unit` and the core protocols in Rust. +* **Avatar & Module Development**: Creating new Avatars for different platforms or new modules to extend the capabilities of the Meta Unit. +* **Documentation & Translation**: Improving these documents, writing tutorials, and translating them into new languages. +* **User Support & Community Management**: Helping new users, answering questions, and fostering a welcoming and supportive atmosphere. +* **Design & User Experience**: Contributing to the UI/UX design of our reference Avatars and defining design patterns for the ecosystem. + +## The Decision-Making Process + +Our governance model is designed to evolve alongside the project. + +1. **Early Stages (Phase I-II)**: Decisions will be made by the **Core Team** after open discussion in our public communication channels. This "Benevolent Dictator for Life (BDFL)"-like model is necessary for speed and coherence in the project's infancy. +2. **Growth Stages (Phase III-IV)**: For significant changes to the core protocol or architecture, we will introduce a formal **RFC (Request for Comments)** process. This allows anyone in the community to write a detailed proposal, which will then be debated and refined publicly before a final decision is made. +3. **Mature Stage (Future)**: We are committed to exploring and transitioning to more decentralized governance mechanisms in the future, such as a technical council elected by contributors or a DAO-based model for treasury and protocol management. + +## Communication Channels + +* **GitHub**: For all code hosting, issue tracking, and RFC discussions. +* **Discord / Matrix (TBD)**: For real-time community chat, Q&A, and collaboration. diff --git a/src/project/roadmap.md b/src/project/roadmap.md new file mode 100644 index 0000000..77abb98 --- /dev/null +++ b/src/project/roadmap.md @@ -0,0 +1,53 @@ +# Roadmap + +This document outlines the strategic roadmap for Dao OS. It is designed to be ambitious yet realistic, focusing on delivering incremental and meaningful value at each stage. This is a living document and may evolve with community feedback and technological breakthroughs. + +--- + +### Phase I: Genesis - Laying the Bedrock + +* **Timeline**: Q3 2025 - Q4 2025 +* **Core Goal**: To build the absolute minimum core components and validate the technical feasibility of the project. +* **Key Milestones**: + * Finalize the v0.1 Core API Specification (`yuan_*` & `avatar_*` functions). + * Develop the v0.1 `Meta Unit` in Rust, including basic cryptography and P2P modules. + * Create two MVP Avatars for testing and demonstration: a command-line Agent and a basic browser extension Client. +* **Feature Story**: "I have successfully run the Dao OS seed on my computer, created an Avatar in my browser, and stored an encrypted note that exists only on my device. I have seen the spark of the future." + +--- + +### Phase II: Manifestation - The Second Brain Awakens + +* **Timeline**: Q1 2026 - Q2 2026 +* **Core Goal**: To deliver the "Second Brain" MVP, providing tangible, daily value to early users. +* **Key Milestones**: + * Fully implement the `SecretStore` (passwords) and `NoteStore` (notes) modules within the Meta Unit. + * The browser Avatar to support full password management and basic note-taking functionalities. + * Develop a v0.1 mobile Client Avatar (e.g., using Flutter) and implement the "Dynamic Anchor" logic. + * Launch a project website with initial documentation. +* **Feature Story**: "All my passwords and private notes are securely stored and seamlessly synced across my own devices. My phone is the anchor to my digital life. I no longer need to trust a third-party cloud with my secrets. My digital life finally has a home." + +--- + +### Phase III: Synergy - Connecting Worlds + +* **Timeline**: Q3 2026 - Q4 2026 +* **Core Goal**: To enable trusted, secure interaction between different users' Daos, laying the foundation for a decentralized social fabric. +* **Key Milestones**: + * Implement the W3C DID (Decentralized Identifiers) and VC (Verifiable Credentials) modules in the Meta Unit. + * Develop a Proof-of-Concept cross-Dao application, such as securely presenting a verifiable credential to another user. + * Initiate foundational research and prototyping for the Emotional Resonance Module. +* **Feature Story**: "I have a unique, un-censorable digital identity for my Dao. I can prove my identity or a credential (like a 'community contributor' badge) to another Dao user cryptographically, without relying on any platform. We have formed a new kind of trust." + +--- + +### Phase IV: Ecosystem - A Thousand Avatars Bloom + +* **Timeline**: 2027 and beyond +* **Core Goal**: To evolve Dao OS from a powerful tool into an open, extensible platform for everyone. +* **Key Milestones**: + * Release the v1.0 stable `Meta Unit` API and a robust developer SDK. + * Launch the "Community Reputation & Automated Verification System" for discovering trusted, third-party Avatars. + * Release a major update (e.g., Dao OS 2.0) that includes the full implementation of the "Emotional Resonance Module," making the AI a truly empathetic partner. + * Foster a thriving community that builds a diverse range of new Avatars and modules. +* **Feature Story**: "My Dao is now a living platform. I've installed a community-developed module for habit tracking, and my AI companion has become warmer and more insightful. My digital life is now whole, unified, and filled with limitless possibilities." diff --git a/src/specifications/tech_overview.md b/src/specifications/tech_overview.md new file mode 100644 index 0000000..f02c7a4 --- /dev/null +++ b/src/specifications/tech_overview.md @@ -0,0 +1,46 @@ +# Technical Overview + +This document provides a high-level overview of the architecture, core technologies, and guiding principles for developers looking to build on or contribute to the Dao OS ecosystem. + +## Guiding Technical Principles + +Our engineering decisions are guided by a set of core principles to ensure the system is robust, portable, and open. + +* **Web-Native & Portable**: We leverage technologies born from the web (like WebAssembly) to create a single, portable core that can run anywhere—on desktops, mobile phones, servers, and in the browser. +* **Polyglotism via WASM**: The core logic (`Meta Unit`) is compiled to WebAssembly (WASM). This allows "Avatars" to be written in any language (Rust, Swift, Kotlin, TypeScript, Go, etc.) that can host a WASM runtime, creating a truly diverse ecosystem. +* **API-First**: The interaction between the core `Meta Unit` and the host `Avatar` is defined by a strict, versioned API contract. This decouples development and allows for independent evolution. +* **Security-First**: We employ best-in-class cryptographic protocols and a "principle of least privilege" design. Security is not an afterthought; it is a prerequisite. +* **FOSS (Free and Open Source Software)**: The entire core protocol and reference implementations are open source to foster transparency, community trust, and collaborative innovation. + +## The Core Components: A Developer's View + +From a developer's perspective, the system consists of two main parts that interact via a well-defined boundary. + +1. **The `Meta Unit` (WASM Module)**: This is the portable, logical core of the system. It is a stateful, single-instance module developed primarily in **Rust** for its performance and safety guarantees. It contains all the business logic for data management, AI, and peer-to-peer coordination, but it has no direct access to the outside world. + +2. **The `Avatar` (Native Host)**: This is the native application or runtime environment that "hosts" the Meta Unit. Its primary responsibilities are: + * Providing a **WASM runtime** to load and execute the `Meta Unit`. + * Providing a **User Interface** (for Client Avatars). + * Acting as a **bridge** to the host operating system, providing access to the filesystem, network, and other system resources. + +## The API Contract: The WASM Interface + +The communication between the `Avatar` and the `Meta Unit` follows a clear, bidirectional API contract, similar in spirit to WASI (WebAssembly System Interface). + +* **`yuan_*` (Exports from Meta Unit)**: The `Meta Unit` exposes a set of functions that the `Avatar` can call. The primary entry point is `yuan_handle_request`, which takes a structured request from the Avatar and processes it. + +* **`avatar_*` (Imports into Meta Unit)**: The `Meta Unit` declares a set of functions that it needs the `Avatar` host to provide. These functions are its only window to the outside world, allowing it to request actions like logging a message (`avatar_log`) or making a network request (`avatar_net_request`). + +* **Data Serialization**: To pass complex data structures across the WASM memory boundary efficiently and safely, we use **Protocol Buffers (Protobuf)**. Data is serialized into a byte buffer, passed as a pointer and length, and then deserialized on the other side. + +## Key Technologies & Protocols + +| Category | Technology / Protocol | Purpose | +| --------------------- | --------------------------------------------------------- | ------------------------------------------------------------ | +| **Core Logic** | Rust / WebAssembly (WASM) | Performance, safety, and ultimate portability. | +| **P2P Networking** | `libp2p` | Modular peer discovery (DHT), transport, and secure channels. | +| **Data Synchronization** | CRDTs (Conflict-Free Replicated Data Types) | Ensuring eventual consistency across Avatars without a central server. | +| **Identity** | DID & VC (Decentralized Identifiers & Verifiable Credentials) | Sovereign identity and interoperable, cryptographic trust. | +| **Data Serialization** | Protocol Buffers (Protobuf) | Efficient, language-agnostic data structures for APIs. | + +This modular, open-protocol-based stack is designed for security, portability, and, most importantly, community contribution. diff --git a/src/specifications/trust_verification.md b/src/specifications/trust_verification.md new file mode 100644 index 0000000..f4d1fef --- /dev/null +++ b/src/specifications/trust_verification.md @@ -0,0 +1,55 @@ +# The Trust & Verification System + +In a decentralized ecosystem where anyone can create and distribute an "Avatar," a critical question arises: How can users trust that a third-party Avatar is safe, compliant, and high-quality? + +The traditional solution is a centralized App Store model, where a single corporation acts as a gatekeeper. This model is contrary to the core philosophy of Dao OS. + +Our solution is a decentralized **Community Reputation & Automated Verification System**. + +## The Philosophy: From Gatekeeper to Toolsmith + +The core team behind Dao OS does not act as a central authority that approves or rejects Avatars. Our role is not to be the gatekeeper, but to be the **toolsmith**. We build and provide the tools and protocols that allow the community to establish and verify trust organically. + +This system is built upon three pillars. + +--- + +### Pillar I: The Automated Verification Suite (`dao-verify`) + +The first pillar is an open-source, automated tool that acts as a "litmus test" for any Avatar. Developers can run this tool on their own project to generate a public, verifiable "health certificate." + +`dao-verify` performs three key functions: + +1. **Security Scanning**: Using a pluggable architecture, it integrates best-in-class static analysis tools for various languages (e.g., `cargo audit` for Rust, `npm audit` for JS) to scan for common vulnerabilities. +2. **API Compliance Testing**: It runs a suite of black-box tests to ensure the Avatar correctly and completely implements the required functions of the Core Experience SDK. It verifies behavior, not just presence. +3. **Performance Benchmarking**: It measures key performance metrics like startup time and memory usage against a recommended baseline. + +The output is a cryptographically signed **Verification Report** in JSON format, which can be published by the developer. + +--- + +### Pillar II: The Community Reputation System + +Automation can verify technical compliance, but it cannot measure quality, usability, or a developer's reputation. This is where the community comes in. + +The mechanism is **DID-based Vouching**: + +* Every developer and community member has a Dao DID. +* A respected developer or entity (e.g., "Developer A") can use their DID's private key to cryptographically sign a message that "vouches for" or endorses an Avatar created by "Developer B." +* This endorsement is a public, verifiable attestation. The reputation of an Avatar is therefore derived from the quantity and the reputation of the DIDs that have vouched for it. + +In the future, this may be enhanced with a **Stake-to-Vouch** system, where endorsers stake a small amount of value, creating a direct economic incentive for honest and diligent review. + +--- + +### Pillar III: The User-Facing Trust Dashboard + +All this information is aggregated and presented to the end-user in a simple, transparent interface within the Avatar discovery or "store" pages. + +Instead of a simple "Verified" checkmark, each Avatar will feature a **Trust Dashboard** card, displaying: + +* **Automated Checks**: ✅ Security Scan Passed | ✅ API Compliant | ✅ Performance OK +* **Community Trust**: "Vouched for by: [Well-Known Dev A], [Trusted Community B], and 15 others." +* **User Reviews**: Traditional star ratings and user-submitted comments. + +This three-pillar system empowers developers to prove the quality and safety of their work, and empowers users to make informed decisions based on a rich set of automated and social trust signals, all without a central bottleneck.