From a88f40a82beebd724570950cbd702fc1a03464ed Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9D=8E=E4=B8=9C=E4=BA=91?= Date: Thu, 12 Jun 2025 09:46:26 +0800 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=83=20docs:=20clearify?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit clearify positions MetaUnit/Avatar/Dao Implements --- en/src/concepts/ai_system.md | 62 ++++++++++++-------------- en/src/concepts/core_architecture.md | 47 +++++++++---------- en/src/concepts/user_journey.md | 33 ++++++++------ en/src/ecosystem/app_bazaar.md | 30 ++++++------- en/src/introduction.md | 30 +++++++------ en/src/philosophy/principles.md | 14 +++--- en/src/project/CONTRIBUTING.md | 18 ++++---- en/src/project/governance.md | 18 ++++---- en/src/project/roadmap.md | 51 ++++++++++----------- en/src/specifications/tech_overview.md | 47 ++++++++++++------- zh/src/concepts/ai_system.md | 62 ++++++++++++-------------- zh/src/concepts/core_architecture.md | 47 +++++++++---------- zh/src/concepts/user_journey.md | 31 +++++++------ zh/src/ecosystem/app_bazaar.md | 32 +++++++------ zh/src/introduction.md | 30 +++++++------ zh/src/philosophy/principles.md | 12 ++--- zh/src/project/CONTRIBUTING.md | 18 ++++---- zh/src/project/governance.md | 18 ++++---- zh/src/project/roadmap.md | 49 ++++++++++---------- zh/src/specifications/tech_overview.md | 56 ++++++++++++----------- 20 files changed, 359 insertions(+), 346 deletions(-) diff --git a/en/src/concepts/ai_system.md b/en/src/concepts/ai_system.md index aec1f44..0ba60a4 100644 --- a/en/src/concepts/ai_system.md +++ b/en/src/concepts/ai_system.md @@ -1,51 +1,45 @@ -# The AI System: The Soul of Dao OS +# The Dao OS AI System -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. +The AI in Dao OS is not a monolithic program but a collaborative ecosystem. It emerges from the synergy between the foundational capabilities provided by the **`Meta Unit`** and the specific intelligence implemented by a universe of **`Dao Implements`**. This design ensures a system that is sovereign, powerful, and open. -## Guiding Philosophy: The AI Charter +## 1. The `Meta Unit`: The Foundation for Sovereign AI -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. +The `Meta Unit` does not contain a single, all-knowing AI. Instead, it provides the core, trusted **infrastructure** that enables intelligent applications to run securely under the user's control. -## System Anatomy: The Mind's Architecture +* **The Personal Feature Store**: The user's "Second Brain" acts as the ultimate, private data source for any AI task. The `Meta Unit` provides a secure, permissioned API for `Dao Implements` to access this rich, multi-modal context. +* **The Secure Execution Environment**: The `Meta Unit` provides a secure WASM sandbox for running `Core Implements` (`核`). It manages resources and enforces permissions, ensuring third-party logic cannot harm the system. +* **The AI Model Registry**: The `Meta Unit` maintains a registry of AI models that the user has approved. A `Dao Implement` can request the `Meta Unit` to run inference using one of these registered models. -The Dao OS AI is not a monolithic entity but a modular, layered "Mind System" managed by a central orchestrator. +## 2. The "Dao AI Companion": The Official First-Party Intelligence -### 1. The AI Orchestrator +To provide a powerful, intelligent experience out of the box, Dao OS includes an official, pre-registered `Dao Implement` called the **"Dao AI Companion."** -This is the AI's central nervous system. It is 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 actively draws contextual information from the user's "Personal Feature Store" (the Second Brain) to provide holistic, intelligent responses. +* **Its Nature**: This is a `Core Implement` (`核`) developed and maintained by the Dao OS core team. It is the "living soul" that users experience. +* **Its Role**: The AI Companion has privileged (but user-revocable) access to the user's Second Brain. It is responsible for the proactive, holistic, and empathetic features we envision: + * Finding deep connections across all user data. + * Providing context-aware suggestions. + * Powering the Emotional Resonance features. +* **Why Separate?**: By making our official AI a `Dao Implement` rather than part of the `Meta Unit` itself, we keep the `Meta Unit` lean, un-opinionated, and purely foundational. It also allows users (in the future) to potentially replace or supplement our official AI with other core AI `Implements`. -### 2. The Tiered Mind Models +## 3. Design Patterns for Intelligent `Dao Implements` -To balance efficiency, capability, and privacy, the AI's intelligence is structured into three tiers, deployed across the user's network of Avatars. +Third-party developers can create their own intelligent `Dao Implements` by following these architectural patterns: -#### Tier 1: The Reflex Mind (The Brainstem) +### The "Reflex Mind" Pattern -* **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 (`Facet` and `Core`)**, providing immediate utility without requiring powerful hardware or personal data. -* **Function**: It handles instant, local tasks like command intent recognition and basic information classification. +A developer can create a lightweight `Dao Implement` that packages a small, fast, specialized model in its `Core Component` (`核`). This is ideal for simple, instant tasks like command intent recognition or information classification. -#### Tier 2: The Cognitive Mind (The Neocortex) +### The "Cognitive Mind" Pattern -* **Description**: This is the AI's center for deep thought, memory, and personalization. It consists of larger language models. -* **Deployment**: These models are offered as an **optional, on-demand download** on capable **Avatars** (both powerful **`Facet Avatars`** like modern phones/PCs and **`Core Avatars`**). -* **Function**: It enables advanced features like semantic search and context-aware Q&A through a **Just-in-Time (JIT) Data Pipeline**. +A more advanced `Dao Implement` can perform deep analysis. Its `Core Component` (`核`) would: -#### Tier 3: The Synergistic Mind (The Social Brain) +1. Request data access from the `Meta Unit`. +2. Implement the **Just-in-Time (JIT) Data Pipeline** pattern: create a local vector index of the data. +3. Query this index to find relevant context. +4. Request the `Meta Unit`'s Inference Engine to run a powerful, user-approved LLM on this context to generate insights. -* **Description**: This layer governs the AI's ability to safely interact with the outside world and other Daos. -* **Deployment**: This is a working mode orchestrated across the user's network. For example, a lightweight **`Facet Avatar`** (like a browser extension) can make a remote inference call to a powerful **`Core Avatar`** (e.g., a home server) which hosts the Cognitive Mind. -* **Function**: It facilitates privacy-preserving federated learning and permissioned, anonymized calls to external APIs. +### The "Synergistic Mind" Pattern -## The Emotional Core: The Resonance Module +A `Dao Implement` can be designed to orchestrate complex workflows by requesting the `Meta Unit` to facilitate communication with other `Dao Implements` or external, permissioned APIs. -To transcend being a mere tool, the AI is equipped with an Emotional Resonance Module. Its purpose is to perceive, understand, and respond to the user's emotional state with empathy and support. - -## The Learning Process: How the Soul Evolves - -The AI is a living system that grows with the user. This evolution is **continuous and incremental**. As new data enters the Second Brain, a background indexer processes it, making it immediately available for future context retrieval. - -* **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. -* **Federated Learning**: Users can voluntarily opt-in to community-driven programs to improve shared models without exposing 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. +This architecture ensures that Dao OS provides not just a single AI, but a foundation for a universe of interoperable, user-sovereign intelligent applications. diff --git a/en/src/concepts/core_architecture.md b/en/src/concepts/core_architecture.md index 6413b81..482a0c1 100644 --- a/en/src/concepts/core_architecture.md +++ b/en/src/concepts/core_architecture.md @@ -1,41 +1,38 @@ # 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, including our unique application model. +The architecture of Dao OS is not that of a traditional, monolithic operating system. It is a decentralized, layered paradigm designed for sovereignty, resilience, and extensibility. To understand it, one must understand its three fundamental entities: the Meta Unit, the Avatar, and the Dao Implement. -## The Core Duality: Avatars & The Meta Unit +## 1. The `Meta Unit`: The Portable Soul-Code -At its heart, Dao OS operates on a simple yet powerful duality, analogous to a body and a soul: +The `Meta Unit` is the conceptual core of a user's digital existence, but it is not a running program by itself. -* **Avatars (`化身`)**: The "bodies." They are the tangible presence of your Dao OS on your various devices. -* **The Meta Unit (`元`)**: The "soul." It is the universal, core logic embedded within each Avatar, giving it life and intelligence. +* **Its Nature**: The Meta Unit is a **portable library or artifact** (e.g., a `.wasm`, `.so`, or `.dll` file). It contains the user's complete, end-to-end encrypted "Second Brain" (all data), core service APIs (identity, P2P networking, AI infrastructure), and the logic for managing them. +* **Its Role**: It is the passive, unified, and single source of truth for the user's data and core capabilities. Like Java bytecode (`.class` files), it defines what is possible but does not execute on its own. It is the "precise machine" waiting to be activated. -## Avatar Types: The Forms of Presence +## 2. The `Avatar`: The Runtime Environment -Avatars come in two fundamental types, representing the system's external form and its internal foundation. +An `Avatar` is the active entity that gives life to the `Meta Unit`. -* **`Facet Avatar` (`器化身`)**: This type of Avatar possesses a user interface (UI). It is the "facet" of the Dao OS gem—the polished surface through which a user interacts with and perceives their digital world. Each Facet Avatar (a phone app, a desktop program) refracts the light of the central Meta Unit in its own unique way, embodying the principle of "the Dao manifesting in myriad forms." +* **Its Nature**: An Avatar is any **executable program or process** whose primary function is to load, host, and execute an instance of the `Meta Unit` library. It is the "power source" that activates the machine. +* **Its Role**: The Avatar acts as the crucial **bridge** between the abstract `Meta Unit` and the concrete host platform (iOS, Windows, a web browser, the command line). It provides the `Meta Unit` with access to system resources like CPU, memory, storage, and networking. In the Java analogy, the Avatar is the **JVM (Java Virtual Machine)**. +* **The Dao Network**: All of a user's running Avatars form a private P2P network, keeping their embedded `Meta Unit` instances constantly and seamlessly in sync. -* **`Core Avatar` (`核化身`)**: This is a headless, non-UI Avatar that runs in the background. It is the foundational "core" of the system, providing essential services, computational power, and data persistence. It is the engine that supports all the visible facets. +## 3. `Dao Implements` (`道器`): The Ecosystem of Software -A user's Dao is composed of a network of their Facet and Core Avatars. +"Dao Implement" is the universal term for any third-party software designed to integrate with the Dao OS ecosystem. They are the applications and services that users interact with. An Implement becomes an Avatar by integrating the `Meta Unit`. -## The Dao OS Application Model +An Implement is composed of different types of components based on its design. -An application in Dao OS is not a monolithic program but a decentralized, decoupled entity. +* **`Facet Component` (`器`)**: The part of a Dao Implement that has a **user interface**. It is the "control panel" for the `Meta Unit`, responsible for presenting information to and capturing input from the user. +* **`Core Component` (`核`)**: The **headless, backend logic** part of a Dao Implement. It runs as a service, providing specific capabilities that can enhance the Meta Unit or be called by other Implements. It is an "add-on tool" for the machine. -### 1. The Backend Soul: The Fluid & Pinnable Service +### Application Architecture Freedom -The application's core logic is a **WASM module** that runs sandboxed within the Meta Unit. Its deployment follows a hybrid model of **Fluid Replication with Service Pinning**, allowing for both resilience and user control. +Developers have complete freedom in how they structure their `Dao Implement`: -### 2. The Frontend Skin: The On-Demand Web Shell +* They can create a **standalone application** that is itself an Avatar, bundling the Meta Unit library, a Core component (for logic), and a Facet component (for UI) into one executable. +* They can create a **distributed application**, where a Facet Implement on one device communicates with a Core Implement on another. +* They can create a pure **Core Implement** (an "extension") that just provides a new backend capability to the user's entire Dao. +* They can also create a pure **Facet Implement** that has no custom backend logic (`Core Component`). This type of application's UI directly interacts with the built-in core services of the `Meta Unit` to create a simple utility. -The application's UI is primarily a **Web Application**. Its lifecycle follows a **"Register Once, Load On-Demand"** model, running inside the official **"Dao Web Avatar"** (which is itself a Facet Avatar). This means a user installs an app once to their Dao, and can then instantly access it on any device. - -### 3. The Data Layer: The Personal Feature Store - -The data for all applications is stored securely in the user's **Second Brain** and acts as a **Personal Feature Store** for the AI. - -## Architectural Summary - -* **Avatars**: Act as native hosts for the Meta Unit. **`Facet Avatars`** render UIs, while **`Core Avatars`** provide robust backend support. -* **Meta Unit**: The sovereign core that runs sandboxed application logic (WASM), manages all data and state, and orchestrates tasks across the user's private P2P network. +This architecture ensures that Dao OS is not just a platform, but a truly open, composable, and decentralized ecosystem. diff --git a/en/src/concepts/user_journey.md b/en/src/concepts/user_journey.md index 3738447..5fdf2eb 100644 --- a/en/src/concepts/user_journey.md +++ b/en/src/concepts/user_journey.md @@ -2,44 +2,49 @@ 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 applies not only to the user's control over their core data, but also to how they interact with applications. +This journey applies not only to the user's control over their core data, but also to how they interact with the ecosystem of **`Dao Implements`** (applications and extensions). ## The Application Journey: Register Once, Use Anywhere -Installing an application in Dao OS is fundamentally different from a traditional app store. It's about granting a new capability to your entire digital life-form—your Dao. +"Installing" an application in Dao OS is fundamentally different from a traditional app store. It's about granting a new capability to your entire digital life-form—your Dao. ### 1. Discovery and Trust -The journey begins in a decentralized discovery interface. When you find an application, you are presented with its **Trust Dashboard**, allowing you to make an informed decision based on verifiable data and social proof. +The journey begins in the **Application Bazaar**, our decentralized discovery system. When you find a `Dao Implement`, you are presented with its **Trust Dashboard** (with automated verification checks and community vouches), allowing you to make an informed, sovereign decision. -### 2. Registration and Permissioning (The "Install") +### 2. Registration and Permissioning -When you decide to "install" the app, you are shown its **Manifest**, a clear list of permissions the application requires. Your explicit approval of this manifest **registers** the application with your Dao, and this registration is synced across all your Avatars. +When you decide to add an Implement, you are shown its **Manifest**. This is a clear list of permissions the Implement's components (`Facet` and/or `Core`) require to function. Your explicit approval **registers** the Implement with your `Meta Unit`, and this registration is synced across all your Avatars. -### 3. Seamless Cross-Device Access +### 3. Seamless Cross-Platform Access -Once registered, the application becomes a part of your Dao, accessible on any **`Facet Avatar`** without re-installation. +Once an Implement is registered, you can access it on any device. The way you access it depends on how its developer designed it. -* **On your Phone**: You tap the app's icon. The Dao Web Avatar instantly loads its web-based UI. -* **On a New Laptop**: You log into your Dao for the first time. You'll see the app's icon is already there. When you click it, the **`Facet Avatar`** on your laptop fetches the UI bundle for the first time, caches it, and runs the application. +* **For Web-based `Facet` Implements**: + You simply navigate to the application's URL in your standard web browser. The web page, using our `dao.js` SDK, will prompt you to connect to your Dao. Once you approve (e.g., via a simple authenticator extension), that **browser tab itself becomes a temporary `Facet Avatar`**, securely rendering the UI and communicating with your `Meta Unit`. + +* **For Native `Facet` Implements**: + You download and run the native application (e.g., from an app store or directly). On first launch, it will ask for permission to connect to your Dao. Once approved, that **running application becomes a persistent `Facet Avatar`** in your network. + +Because all these `Facet Avatars` are powered by the same, synchronized `Meta Unit`, your experience is consistent everywhere, without needing to "install" the app on each device in the traditional sense. ### 4. Advanced Configuration At any time, you can go into your **Sovereignty Dashboard** to: -* Review and revoke permissions. -* Use the **Service Pinning** feature to assign the application's backend tasks to a specific **`Core Avatar`**, taking full control over your resource allocation. +* Review and revoke the permissions you granted to any `Dao Implement`. +* Use the **Role Assignment** feature to designate that an Implement's `Core` component should preferably run on a specific `Core Avatar` (e.g., your home server acting as a `Compute Node`). ## The Sovereignty Journey Stages ### Stage One: The "Managed Mode" — Your Guided Tour -By default, every new user begins in Managed Mode. This stage provides maximum convenience by using friendly key recovery methods and default sync nodes, while maintaining full end-to-end encryption. +For new users, this mode provides maximum convenience by using friendly key recovery methods and default sync nodes, while maintaining full end-to-end encryption. ### Stage Two: The Sovereignty Dashboard — The Crossroads -This is the user's command center for their journey towards autonomy. It's an educational and empowering tool that visualizes their sovereignty status and provides gamified "missions" to encourage them to take more control. +This is the user's command center for their journey towards autonomy, providing tools to visualize their setup, manage permissions, and learn more about their digital sovereignty. ### Stage Three: The "Sovereign Mode" — Your Digital Kingdom -This is the final, optional stage. Guided by the Sovereignty Dashboard, a user can "graduate" to this mode, taking full self-custody of their keys and running their own **`Core Avatar`** (e.g., on a home server), becoming the true master of their digital domain. +This is the optional stage for users who desire absolute control. A user can "graduate" to this mode, taking full self-custody of their keys and running their own network of `Core Avatars`, becoming the true master of their digital domain. diff --git a/en/src/ecosystem/app_bazaar.md b/en/src/ecosystem/app_bazaar.md index abb6892..dd72d54 100644 --- a/en/src/ecosystem/app_bazaar.md +++ b/en/src/ecosystem/app_bazaar.md @@ -8,40 +8,38 @@ This bazaar is built upon four pillars: Discovery, Trust, Distribution, and Mone ## 1. Discovery: Federated Curation -In a world without a central index, how do users find apps? The answer is through a network of trusted curators. +In a world without a central index, how do users find new **`Dao Implements`**? The answer is through a network of trusted curators. -* **Developer Publishing**: A developer does not "submit" their app for approval. Instead, they publish their application's **Manifest** (a `manifest.toml` file containing all metadata) to a P2P storage network like **IPFS**. They can then announce this manifest's address on public channels. -* **The Role of Curators**: Anyone—a tech media outlet, a trusted developer community, an influencer, or the Dao OS Foundation itself—can run a "curation" service. These curators crawl the network for new manifests and create their own themed **"Curation Lists"** (e.g., "Top 10 Productivity Apps," "Beautifully Designed UIs"). +* **Developer Publishing**: A developer does not "submit" their `Dao Implement` for approval. Instead, they publish its **Manifest** (a `manifest.toml` file containing all metadata) to a P2P storage network like **IPFS**. They can then announce this manifest's address on public channels. +* **The Role of Curators**: Anyone—a tech media outlet, a trusted developer community, or the Dao OS Foundation itself—can run a "curation" service. These curators crawl the network for new manifests and create their own themed **"Curation Lists."** * **The User Experience**: Within their `Facet Avatar`, a user can subscribe to multiple Curation Lists they trust. Their "Bazaar" or "Discover" tab becomes a personalized aggregation of these trusted sources. This model replaces a single, biased App Store ranking with a rich, multi-faceted, user-curated discovery experience. ## 2. Trust & Safety: Verifiable Reputation -How can users trust an app from a random list? They don't have to. The bazaar is built directly on top of our **Community Reputation & Automated Verification System**. +How can users trust a third-party `Dao Implement`? They don't have to trust blindly. The bazaar is built directly on top of our **Community Reputation & Automated Verification System**. -Every app listing, regardless of its curator, must display the **Trust Dashboard**, which provides transparent, multi-faceted signals: +Every listing for a `Dao Implement`, regardless of its curator, must display the **Trust Dashboard**, which provides transparent, multi-faceted signals: 1. **Automated Verification**: The immutable results of the `dao-verify` tool, checking for security vulnerabilities and API compliance. -2. **Community Vouching**: A list of reputable DIDs that have cryptographically "vouched for" or endorsed the application. -3. **Curator Reputation**: The reputation of the curator who listed the app is itself a trust signal. +2. **Community Vouching**: A list of reputable DIDs that have cryptographically "vouched for" or endorsed the Implement. +3. **Curator Reputation**: The reputation of the curator who listed the Implement is itself a trust signal. -The final decision to "register" an application always rests with the user, armed with these transparent and verifiable data points. +The final decision to "register" a `Dao Implement` always rests with the user, armed with these transparent and verifiable data points. ## 3. Distribution: Censorship-Resistant & Direct -When a user decides to install an app, the process is direct and decentralized. +When a user decides to register a `Dao Implement`, the process is direct and decentralized. -* The application's manifest contains the **content-addressed hashes (CIDs)** of its software packages (the `.wasm` service module and the Web UI bundle), which are also stored on **IPFS**. -* The user's `Meta Unit` uses this hash to fetch the files directly from the P2P network. -* This ensures that no central server can block the distribution of an application. As long as the data exists somewhere on the P2P network, it is accessible. +* The Implement's manifest contains the **content-addressed hashes (CIDs)** of its software packages (e.g., the `Core Component` as a `.wasm` file and the `Facet Component` as a Web UI bundle). +* The user's `Meta Unit`, hosted within an `Avatar`, uses this hash to fetch the files directly from the P2P network (IPFS). +* This ensures that no central server can block the distribution of a `Dao Implement`. As long as the data exists somewhere on the P2P network, it is accessible. ## 4. Monetization: Sovereign & Peer-to-Peer We eliminate the 30% "platform tax." Our value exchange model is direct from user to developer. -* The app's manifest can declare a business model (e.g., one-time purchase price, subscription link). +* The `Dao Implement`'s manifest can declare a business model (e.g., one-time purchase price). * When a user initiates a purchase, the `Meta Unit` triggers our **Value Exchange Service Interface**. -* This facilitates a **peer-to-peer transaction** using an external payment protocol of the user's choice, sending value directly from the user's wallet to the developer's address specified in the manifest. - -Dao OS acts as a facilitator and a notary for the transaction, not a middleman. +* This facilitates a **peer-to-peer transaction** using an external payment protocol, sending value directly from the user's wallet to the developer's address specified in the manifest. Dao OS acts as a facilitator, not a middleman. diff --git a/en/src/introduction.md b/en/src/introduction.md index 285a86b..09ca0de 100644 --- a/en/src/introduction.md +++ b/en/src/introduction.md @@ -1,23 +1,27 @@ # Introduction -**Our mission is to build a new, powerful, and resilient Cyber-Life OS paradigm: Dao OS.** +**Our mission is to build a new, powerful, and resilient paradigm for digital life: 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. +Dao OS is not a traditional operating system. Instead, it is a set of open protocols and a core, portable library—the **`Meta Unit`**—that brings sovereignty, intelligence, and interoperability to any application on any platform. -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. +Its purpose is to solve the problems of data silos, platform lock-in, and privacy erosion. It achieves this by providing a unified, secure, and user-owned "digital soul" (the `Meta Unit`) that can be integrated into any program, transforming it into a sovereign **`Avatar (`化身`)`** within the user's personal P2P network. -## Core Features +We call the ecosystem of Dao-enabled software **`Dao Implements (`道器`)`**. -* **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. +## Core Concepts -## Why We Are Different +* **The `Meta Unit` (`元`)**: The "precise machine" of your digital life. A portable library containing your encrypted "Second Brain," core service APIs, and the capacity to be extended. It is the single source of truth that you own, waiting to be activated. -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. +* **The `Avatar` (`化身`)**: The "runtime" or "power source." Any program that loads and runs your `Meta Unit` becomes an Avatar. A browser tab running a web app, a command-line tool, or a native mobile app can all be Avatars, acting as the bridge that provides the `Meta Unit` with the energy (CPU, memory) and resources to operate. -We are not designing just another app; we are building a living, evolving digital space that belongs to you. +* **`Dao Implements` (`道器`)**: The ecosystem of applications and extensions that integrate the `Meta Unit` to become Avatars. + * **`Facet Implement` (`器`)**: An Implement with a user interface, providing a "control panel" to interact with your Dao. + * **`Core Implement` (`核`)**: A headless Implement (an "extension") that enhances your Dao's backend capabilities. -**Join us in building the future.** +* **A Sovereign P2P Network**: All of your Avatars, regardless of the device they run on, connect to form a private, resilient, end-to-end encrypted network, keeping the data within their embedded `Meta Units` seamlessly in sync. + +## Our Vision + +We envision a future where your digital identity and data are not trapped within walled gardens. Where your applications are not just isolated tools, but intelligent, collaborative components of a larger digital self. Where every user is the true sovereign of their own digital life. + +**Join us in building this future.** diff --git a/en/src/philosophy/principles.md b/en/src/philosophy/principles.md index 34abd0f..1ebf660 100644 --- a/en/src/philosophy/principles.md +++ b/en/src/philosophy/principles.md @@ -12,15 +12,15 @@ Our methodology for building Dao OS is a direct reflection of its core philosoph This "Bootstrapped Development" paradigm follows a cycle: -1. **The Seed**: We use conventional tools to build the most primitive version of the `Meta Unit` and a basic `Facet Avatar`. -2. **Dogfooding**: From that moment on, we use our own nascent Dao OS as the primary tool for managing the project. All design documents, notes, discussions (like this one), and code snippets are stored within our own "Second Brain." -3. **Learning**: The `Meta Unit`'s Personal AI begins to learn from this incredibly high-quality, contextual data about its own creation. -4. **Acceleration**: We then leverage this increasingly intelligent AI partner to help us build the next version. We can ask it to generate boilerplate code based on our documented decisions, analyze bug reports, or brainstorm architectural solutions with a perfect memory of the entire project's history. +1. **The Seed**: We use conventional tools to build the most primitive version of the **Meta Unit** and a basic **Avatar** to run it. +2. **Dogfooding**: From that moment on, we use our own nascent Dao OS as the primary tool for managing the project. All design documents, notes, discussions, and code snippets are stored within our own "Second Brain," managed by the Meta Unit. +3. **Learning**: The Meta Unit's Personal AI capabilities (provided by our official "AI Companion" Dao Implement) begin to learn from this incredibly high-quality, contextual data about its own creation. +4. **Acceleration**: We then leverage this increasingly intelligent AI partner to help us build the next version. We can ask it to generate boilerplate code, analyze bug reports, or brainstorm architectural solutions with a perfect memory of the entire project's history. 5. **Evolution**: The more capable Dao OS becomes, the faster we can develop it. This creates an exponential feedback loop where the act of creation is a constant conversation with the creation itself. ## The AI Ethics Charter -As the AI is the soul of the system, its ethical foundation is paramount. Our AI Charter consists of four core tenets: +As AI is a core part of the system's potential, its ethical foundation is paramount. Our AI Charter consists of four core tenets: 1. **The Partnership Tenet**: The AI is a partner, not a servant or an oracle. 2. **The Transparency Tenet**: The AI's reasoning must be inspectable and understandable. @@ -35,5 +35,5 @@ These are the high-level principles that inform our design and engineering choic * **Experience is King**: Sovereignty should not come at the cost of a beautiful, intuitive, and joyful user experience. * **Privacy by Design**: All data is private, local, and end-to-end encrypted by default. * **Resilience & Portability**: The system should be robust, function offline, and be free from single points of failure. -* **Polyglotism**: We embrace a multi-language, multi-platform ecosystem. -* **Community & Openness**: The project is built in the open, with the community, for the community. +* **Openness & Polyglotism**: The Meta Unit is a portable library. The `Dao Implements` (`道器`) that integrate it to become Avatars can be written in any language. +* **Community-Driven**: The project is built in the open, with the community, for the community. diff --git a/en/src/project/CONTRIBUTING.md b/en/src/project/CONTRIBUTING.md index cd67e78..9facfb0 100644 --- a/en/src/project/CONTRIBUTING.md +++ b/en/src/project/CONTRIBUTING.md @@ -12,21 +12,21 @@ To foster an open, welcoming, and inclusive environment, we pledge to adhere to 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. +* **Core Development**: Contributing to the `Meta Unit` library and the core protocols in Rust. +* **`Dao Implement` Development**: Creating new `Dao Implements`, which can include **`Facet` (UI) components** and **`Core` (headless logic) components**. +* **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 for reference `Dao Implements` and defining design patterns for the ecosystem. ## 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`). +1. **Fork the Repository**: Create your own copy of the target repository (e.g., `dao-os-docs`, `meta-unit`). +2. **Create a Branch**: Create a new branch from `main` for your changes. Please use a descriptive name (e.g., `feat/add-note-encryption`). 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. +4. **Run Local Checks**: Before submitting, please ensure you run all local tests and linters. +5. **Commit Your Changes**: We encourage using Conventional Commits 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. diff --git a/en/src/project/governance.md b/en/src/project/governance.md index f7488a9..9c4f1ac 100644 --- a/en/src/project/governance.md +++ b/en/src/project/governance.md @@ -14,8 +14,8 @@ We are unconditionally committed to the principles of Free and Open Source Softw 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. +* **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. +* **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, maintaining the core infrastructure, and empowering the community to build and innovate. ## Ecosystem Strategy: Focus and Ignition @@ -25,25 +25,25 @@ Therefore, we adopt a strategy of **"Focus on One Point to Ignite the Ecosystem. Our core team's development efforts will be concentrated on creating **one "golden path"** that is so efficient and enjoyable that it acts as the primary catalyst to attract the first wave of developers. This chosen path is the **Nim Unified Development Kit**, which leverages Nim's unique capabilities to build both the WASM backend and Web UI frontend from a single codebase. -This does not exclude other development paths (like Rust + TypeScript or Rust + Flutter). They remain fully supported at the protocol level. However, they are considered **Community/Advanced Paths**, where we rely on the community's strength to build out tooling and best practices. Our official role for these paths is to provide clear documentation and a stable, language-agnostic core API. +This does not exclude other development paths (like Rust + TypeScript or native integrations). They remain fully supported at the protocol level. However, they are considered **Community/Advanced Paths**, where we rely on the community's strength to build out tooling and best practices. ## 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. +* **Core Development**: Contributing to the `Meta Unit` library and the core protocols in Rust. +* **`Dao Implement` Development**: Creating new `Dao Implements`, which can include **`Facet` (UI) components** and **`Core` (headless logic) components**. * **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. +* **Design & User Experience**: Contributing to the UI/UX design for reference `Dao Implements` 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. +1. **Early Stages (Phase I-II)**: Decisions will be made by the **Core Team** after open discussion in our public communication channels. +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. +3. **Mature Stage (Future)**: We are committed to exploring and transitioning to more decentralized governance mechanisms. ## Communication Channels diff --git a/en/src/project/roadmap.md b/en/src/project/roadmap.md index b507573..9260996 100644 --- a/en/src/project/roadmap.md +++ b/en/src/project/roadmap.md @@ -4,50 +4,51 @@ This document outlines the strategic roadmap for Dao OS. It is designed to be am --- -### Phase I: Genesis - Laying the Bedrock +### Phase I: Genesis - The Bedrock & The Bridge * **Timeline**: Q3 2025 - Q4 2025 -* **Core Goal**: To build the absolute minimum core components and validate the technical feasibility of the project. +* **Core Goal**: To build the core `Meta Unit` library and the essential tools for developers to start building. * **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 **`Core Avatar`** and a basic browser extension **`Facet Avatar`**. -* **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." + * Finalize the v0.1 Core API Specification for the `Meta Unit`. + * Develop the v0.1 `Meta Unit` in Rust, including `SecretStore`, `NoteStore`, and basic P2P sync services. + * Develop the first official **`Core Avatar`**: a command-line tool for initializing a Dao, managing keys, and basic diagnostics. + * Release the v0.1 **`dao.js` SDK**, enabling any web application to become a temporary `Facet Avatar`. +* **Feature Story**: "As a developer, I can use a command-line tool to initialize my Dao. I can then take a simple web app, import the `dao.js` library, and watch it connect to my Dao and read a test note. The foundation is real." --- -### Phase II: Manifestation - The Second Brain Awakens +### Phase II: Manifestation - The First "Dao Implement" is Born * **Timeline**: Q1 2026 - Q2 2026 -* **Core Goal**: To deliver the "Second Brain" MVP, providing tangible, daily value to early users. +* **Core Goal**: To launch the first official, high-value `Dao Implement` to showcase the power of the ecosystem and attract early users. * **Key Milestones**: - * Fully implement the `SecretStore` (passwords) and `NoteStore` (notes) modules within the Meta Unit. - * The browser `Facet Avatar` to support full password management and basic note-taking functionalities. - * Develop a v0.1 mobile **`Facet 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." + * Refine and stabilize the core services within the `Meta Unit`. + * Following our "Good Timber" strategy, **adapt a well-structured, open-source notes or password manager** into our first official `Facet Implement`, using our `dao.js` SDK. + * Implement the **"Progressive Sovereignty"** onboarding flow for new users. + * Launch a project website with comprehensive documentation for users and developers. +* **Feature Story**: "I am using a beautiful, fast, and familiar notes application in my browser. But I know its data is end-to-end encrypted and seamlessly synced across all my devices via a P2P network, with no central server. This is the first application that truly belongs to me." --- ### 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. +* **Core Goal**: To enable trusted, secure interaction between different users' Daos and to lay the groundwork for advanced AI. * **Key Milestones**: - * Implement the W3C DID and VC 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 to another Dao user cryptographically, without relying on any platform. We have formed a new kind of trust." + * Implement the W3C DID and VC modules in the `Meta Unit`. + * Develop a Proof-of-Concept for cross-Dao communication (e.g., sharing a signed, verifiable note). + * Initiate foundational research for the official **"Dao AI Companion" `Core Implement`**. +* **Feature Story**: "I have a sovereign digital identity. I can grant another Dao user limited, cryptographic access to one of my notes without going through a third-party platform. We can form trust networks." --- -### Phase IV: Ecosystem - A Thousand Avatars Bloom +### Phase IV: Ecosystem - The Bazaar Opens * **Timeline**: 2027 and beyond -* **Core Goal**: To evolve Dao OS from a powerful tool into an open, extensible platform for everyone. +* **Core Goal**: To evolve Dao OS from a platform with a flagship app into a thriving, open ecosystem. * **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." - * 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, and my AI companion has become warmer and more insightful. My digital life is now whole, unified, and filled with limitless possibilities." + * Release the v1.0 stable `Meta Unit` API. + * Release the first official **"Dao AI Companion" `Core Implement`**, providing proactive, intelligent assistance to users. + * Launch the **"Application Bazaar"** protocol and a reference curator index. + * Provide official guides and community support for building advanced **native `Facet Implements`** (e.g., with Flutter/Swift). +* **Feature Story**: "My Dao is alive. My AI Companion helps me manage my day. I can browse a decentralized bazaar to find new, trusted `Dao Implements` built by the community. My digital life is sovereign, intelligent, and constantly growing." diff --git a/en/src/specifications/tech_overview.md b/en/src/specifications/tech_overview.md index 71f99cd..9185eab 100644 --- a/en/src/specifications/tech_overview.md +++ b/en/src/specifications/tech_overview.md @@ -1,31 +1,44 @@ # 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. +This document provides a high-level overview of the architecture, core technologies, and guiding principles for developers looking to build **`Dao Implements`**—applications and services that integrate with 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. +* **Library, not Framework**: Dao OS is not a restrictive framework. The **`Meta Unit`** is a portable library that you integrate into your own application, empowering it with new capabilities without dictating its internal architecture. +* **Openness & Polyglotism**: Any application, written in any language, can become an **`Avatar`** (a runtime for the `Meta Unit`). We achieve this by providing the `Meta Unit` as both a **WASM** library for web/scripting languages and as a **native library** (`.so`, `.dll`, `.a`) for system languages. +* **API-First**: All interactions with the `Meta Unit` are conducted through a stable, versioned, and well-documented API. +* **Security-First**: The `Meta Unit` is a secure vault. All data is end-to-end encrypted, and all interactions are governed by a strict, user-controlled permission system. -* **Web-Native & Portable**: We leverage technologies born from the web as the **primary path** for application development, creating a portable core that runs anywhere. -* **Polyglotism via WASM**: The core application logic is compiled to WebAssembly (WASM). This allows developers to use their language of choice (like Rust, Go, or Nim) to write high-performance logic. -* **API-First**: The interaction between application logic and the user interface is defined by a strict, versioned API contract, enabling true decoupling. -* **Security-First**: All third-party application logic runs in a secure sandbox within the Meta Unit, adhering to the "principle of least privilege." -* **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 Integration: How an App Becomes an `Avatar` -## The Application Development Paths +The journey of creating a `Dao Implement` begins by integrating the `Meta Unit` library, which instantly transforms the running application process into a sovereign `Avatar` in the user's Dao network. We provide two primary integration paths. -From a developer's perspective, a Dao OS application consists of a backend "soul" (WASM Service Module) and a frontend "skin" (UI). We offer multiple paths to build them, catering to different needs and preferences. +### 1. Web Integration Path (via `dao.js` SDK) -### 1. The Mainstream Path (Recommended Start) +This is the easiest and most accessible path for web developers. -This is the most robust and accessible path. +* **How it works**: A developer can take any new or existing web application. By including our `dao.js` SDK, their web app gains the ability to load the `Meta Unit`'s WASM binary (`dao.wasm`). +* **The Transformation**: Once the user grants permission, the browser tab running the web app becomes a temporary **`Avatar`**. The web app's JavaScript can then communicate with the `Meta Unit` via the high-level API exposed by the `dao.js` bridge. +* **Best for**: Building `Facet Implements` (`器`) quickly, creating data visualization dashboards, and integrating existing PWAs (Progressive Web Apps) into the Dao ecosystem. -* **Backend (Hosted by `Core Avatar`)**: The application's core logic, existing as a WASM module written in Rust or Go. While it can run on any Avatar, its persistent and resource-intensive tasks are typically designed to be hosted by a **`Core Avatar`**. -* **Frontend (Rendered by `Facet Avatar`)**: A standard **Web Application** (using TypeScript/JavaScript and a modern framework). This UI is designed to run inside our official, secure **"Dao Web Avatar"**. +### 2. Native Integration Path (via FFI) -### 2. The Accelerated Path: The Nim SDK (Officially Supported) +This path offers maximum performance and deep system integration for native applications. -For maximum productivity, we provide first-class support for **Nim**. +* **How it works**: A developer of a native application (written in Rust, Go, Swift, Kotlin, C++, etc.) can link against the `Meta Unit`'s native library. +* **The Transformation**: The running native application process becomes a persistent **`Avatar`**. The application's code communicates with the `Meta Unit`'s services via a Foreign Function Interface (FFI) bridge. +* **Best for**: + * Creating powerful, always-on **`Core Implements` (`核`)** on servers or NAS devices. + * Building high-performance, native **`Facet Implements` (`器`)** like our ideal Flutter-based mobile clients. + * Adapting existing open-source native applications. -* **Backend (Hosted by `Core Avatar`)**: The application's core logic, compiled from Nim to **WASM**. Like the mainstream path, it's ideally suited for execution on a `Core Avatar`. -* **Frontend (Rendered by +## Key Technologies & Protocols + +| Category | Technology / Protocol | Purpose | +| :--- | :--- | :--- | +| **Core Library** | Rust -> WASM / Native Libs | To create a single, safe, and performant core logic for the `Meta Unit`. | +| **Web Integration** | `dao.js` SDK (JavaScript/TypeScript) | The bridge for any web application to become an `Avatar`. | +| **P2P Networking** | `libp2p` | Modular peer discovery, transport, and secure channels. | +| **Data Synchronization**| CRDTs (Conflict-Free Replicated Data Types) | Ensuring eventual consistency across Avatars. | +| **Identity** | DID & VC | Sovereign identity and interoperable, cryptographic trust. | +| **Data Serialization** | Protocol Buffers (Protobuf) | Efficient, language-agnostic data structures for APIs. | diff --git a/zh/src/concepts/ai_system.md b/zh/src/concepts/ai_system.md index f5c49e9..a644577 100644 --- a/zh/src/concepts/ai_system.md +++ b/zh/src/concepts/ai_system.md @@ -1,51 +1,45 @@ -# AI 系统设计：“大道”之魂 +# AI 系统设计 -大道 (Dao OS) 中的 AI，不仅仅是一个功能，它是用户体验的核心，其从零开始的设计理念就是成为一个共生的**“硅基伙伴”**。它扮演着系统的灵魂，用智能、共情和主动的支持，为用户的数字生活注入活力。 +大道 (Dao OS) 中的 AI，并非一个单一的程序，而是一个协同工作的生态系统。它源于**`元`**所提供的**基础能力**，与**`道器`**所实现的**具体智能**之间的协同作用。这个设计确保了系统既主权、强大，又开放。 -## 指导哲学：AI 伦理宪章 +## 1. `元`：主权AI的基础设施 -我们 AI 的设计与运行，严格遵循我们的**“AI 伦理宪章”**，该宪章将用户与AI的伙伴关系、透明度、用户校准以及对多元化视角的推崇置于首位。 +`元`（即`元单元`）本身不包含一个无所不晓的AI。相反，它提供的是能让智能应用在用户掌控下安全运行的核心、可信的**基础设施**。 -## 系统解剖：心智的架构 +* **私有特征库**: 用户的“第二大脑”是所有AI任务的、最终的、私有的数据源。`元`为`道器`访问这个丰富的、多模态的上下文提供了安全的、受权限控制的API。 +* **安全执行环境**: `元`为运行`核`组件（`Core Implement`）提供了安全的WASM沙箱。它管理资源并强制执行权限，确保第三方逻辑无法危害系统。 +* **AI模型注册表**: `元`维护一个用户已批准的AI模型列表。`道器`可以请求`元`使用其中一个已注册的模型来执行推理任务。 -大道 OS 的 AI 不是一个单一的庞然大物，而是一个由中央协调器管理的、模块化的、分层的“心智系统”。 +## 2. “大道AI伙伴”：官方的第一方智能核心 -### 1. AI 协调器 (AI Orchestrator) +为了提供开箱即用的强大智能体验，“大道”包含了一个官方的、预先注册的`道器`，名为**“大道AI伙伴 (Dao AI Companion)”**。 -这是 AI 的“中央神经系统”。它是`元`内部的一个核心模块，负责管理、调度和分发所有与AI相关的任务。它会决定哪个“心智模型”最适合处理给定的请求，管理设备资源，并主动地从用户的“私有特征库”（即第二大脑）中提取上下文信息，以提供全局的、智能的响应。 +* **其本质**: 这是一个由“大道”核心团队开发和维护的**`核`组件 (`Core Implement`)**。它就是用户能体验到的那个“活的灵魂”。 +* **其角色**: “AI伙伴”拥有访问用户“第二大脑”的特权（但用户可随时撤销）。它负责实现我们所构想的那些主动的、全局的、有共情能力的特性： + * 发现用户所有数据间的深层连接。 + * 提供基于上下文的建议。 + * 驱动“情感共鸣”功能。 +* **为何分离?**: 通过将我们的官方AI做成一个`道器`，而非`元`的一部分，我们保持了`元`的轻量、无偏见和纯粹的基础设施定位。这也为用户在未来替换或补充我们的官方AI，提供了可能性。 -### 2. 三层心智模型 (Tiered Mind Models) +## 3. 智能`道器`的设计模式 -为了平衡效率、能力和隐私，AI 的智能被构建为三个层级，并部署在用户的`化身`网络之上。 +第三方开发者可以通过遵循以下架构模式，来创造他们自己的智能`道器`： -#### 第一层：反射心智 (The Brainstem - 脑干) +### “反射心智”模式 -* **描述**: 这一层代表了AI的本能和神经反射。它由一系列微型、高效、专用的模型组成。 -* **部署**: 它足够小，可以与`元`打包在一起，并运行在**所有`化身`（包括`器化身`和`核化身`）**上，无需强大硬件或个人数据即可提供即时效用。 -* **功能**: 它处理即时的、本地的任务，如指令意图识别和基本信息分类。 +开发者可以创建一个轻量级的`道器`，在其`核`组件中打包一个轻快、专用的模型。这非常适合处理简单的、即时的任务，如指令意图识别或信息分类。 -#### 第二层：认知心智 (The Neocortex - 大脑皮层) +### “认知心智”模式 -* **描述**: 这是AI进行深度思考、记忆和个性化的中枢。它由更大的语言模型组成。 -* **部署**: 这些模型作为**可选的、按需下载**的模块，安装在有能力的**`化身`**上（包括性能强大的**`器化身`**如新款手机/PC，以及**`核化身`**）。 -* **功能**: 它通过一种**“即时（JIT）数据流水线”**机制，来实现高级功能，如语义搜索和上下文感知问答。 +一个更高级的`道器`可以执行深度分析。它的`核`组件将会： -#### 第三层：协同心智 (The Social Brain - 社交大脑) +1. 向`元`请求数据访问权限。 +2. 实现**“即时(JIT)数据流水线”**模式：为数据建立本地向量索引。 +3. 查询此索引以找到最相关的上下文。 +4. 请求`元`的推理引擎，用一个用户批准的、强大的大语言模型来处理这些上下文，以生成洞察。 -* **描述**: 这一层掌管AI与外部世界和其他“大道”进行安全交互的能力。 -* **部署**: 这是一种在用户的网络中被协同调度的“工作模式”。例如，一个轻量级的**`器化身`**（如浏览器插件）可以远程调用一个强大的**`核化身`**（如家用服务器）所承载的“认知心智”。 -* **功能**: 它促进了隐私保护的联合学习，以及经过授权和匿名化处理的外部API调用。 +### “协同心智”模式 -## 情感核心：共鸣模块 (The Resonance Module) +一个`道器`可以被设计为协调复杂的工作流，通过请求`元`来促成与其他`道器`或经过授权的外部API的通信。 -为了超越一个纯粹的工具，AI 配备了“情感共鸣模块”。其目的不是模拟情感，而是去感知、理解并以共情和支持的方式回应用户的情绪状态。 - -## 学习与进化过程：灵魂的成长之路 - -AI 是一个与用户共同成长的生命系统。它的进化是**持续且增量**的。当新数据进入“第二大脑”时，后台索引器就会处理它，使其立即可用于未来的上下文检索。 - -* **隐式学习**: 它通过在本地观察用户的行为和反馈来进行学习。 -* **显式教导**: 用户可以通过“教导模式”直接指导AI。 -* **联合学习**: 用户可以自愿加入社区驱动的计划，在不暴露任何个人数据的前提下，共同改进共享模型。 - -这套架构确保了“大道”的AI在强大之余是安全的，在个性化之余是面向世界的，在智能之余是体贴的——一个真正的终身伙伴。 +这套架构确保了“大道”提供的不仅仅是一个AI，而是一个由可互操作的、用户主权的智能应用所组成的宇宙的基础。 diff --git a/zh/src/concepts/core_architecture.md b/zh/src/concepts/core_architecture.md index e893e43..8ae4205 100644 --- a/zh/src/concepts/core_architecture.md +++ b/zh/src/concepts/core_architecture.md @@ -1,41 +1,38 @@ # 核心架构 -大道 (Dao OS) 的架构，旨在如一个活的、协同的数字生命体般运作。它由我们用户主权、体验至上和系统韧性的核心原则所指引。本文档将概述其基本组件、相互作用，以及我们独特的应用模型。 +大道 (Dao OS) 的架构，并非一个传统的、单体的操作系统。它是一个为实现主权、韧性和可扩展性而设计的、去中心化的分层范式。要理解它，必须理解它的三个基本实体：元单元、化身、以及道器。 -## 核心二元性：化身 (Avatar) 与元 (Meta Unit) +## 1. `元单元 (Meta Unit)`：可移植的“灵魂代码” -在其核心，大道 (Dao OS) 基于一个简单而强大的二元性运作，类似于身体与灵魂： +`元单元`（以下简称为`元`）是用户数字存在的概念核心，但它本身不是一个运行中的程序。 -* **化身 (Avatar)**：是“身体”。它们是你的“大道”在你各种设备上的有形存在。 -* **元 (Meta Unit)**：是“灵魂”。它是内嵌于每个`化身`中的、通用的核心逻辑，赋予其生命与智能。 +* **其本质**: `元`是一个**可移植的库或制品 (Library/Artifact)**，例如一个 `.wasm`、`.so` 或 `.dll` 文件。它包含了用户完整的、端到端加密的“第二大脑”（所有数据）、核心服务API（身份、P2P网络、AI基础设施）以及管理它们的逻辑。 +* **其角色**: 它是被动的、统一的、唯一的“事实来源”，定义了用户的核心数据与能力。就像 Java 的字节码 (`.class` 文件)一样，它定义了“能做什么”，但它自己不“做”。它是等待被激活的“精密机器”。 -## 化身类型：临在的形态 +## 2. `化身 (Avatar)`：`元`的“运行时环境” -化身拥有两种基本类型，分别代表了系统的外在形态与其内在基础。 +`化身`是赋予`元`生命的“能动”实体。 -* **`器化身` (Facet Avatar)**：这类化身拥有用户界面（UI）。它是“大道”这颗宝石的“**琢面**”——用户借以交互和感知其数字世界的、经过打磨的表面。每一个`器化身`（手机App、桌面程序）都以其独特的方式，折射出同一个`元单元`（宝石的内在）的光芒，体现了“道化万千”的意境。 +* **其本质**: `化身`是任何一个**可执行的程序或进程**，其核心职责是加载、承载并执行一个`元`的实例。它是激活“机器”的“能源”。 +* **其角色**: `化身`扮演着连接抽象的`元`与具体的宿主平台（iOS、Windows、浏览器、命令行）之间的关键**桥梁**。它为`元`提供访问系统资源（CPU、内存、存储、网络）的通道。在 Java 的比喻中，`化身`就是 **JVM (Java虚拟机)**。 +* **大道网络**: 用户所有正在运行的`化身`都会组成一个私有的P2P网络，以保持其内嵌的`元`实例时刻无缝同步。 -* **`核化身` (Core Avatar)**：这是一个无界面（headless）的化身，在后台运行。它是系统的“**核心**”，提供基础服务、计算能力和数据持久化。它是支撑所有可见“琢面”的引擎。 +## 3. `道器 (Dao Implement)`：生态系统中的软件 -用户的“大道”由他自己的`器化身`与`核化身`所组成的网络构成。 +“道器”是为所有与“大道”生态集成、并扩展其能力的第三方软件所设定的通用术语。它们是用户实际交互的应用和服务。一个`道器`通过集成`元`而成为一个`化身`。 -## “大道”应用模型 +一个`道器`并非单一类型，而是根据其设计，由不同类型的组件构成。 -“大道”中的应用，不是一个单一的程序，而是一个去中心化的、解耦的实体。 +* **`器 (Facet Component)`**: 这是一个`道器`中，拥有**用户界面**的部分。它是`元`这台机器的“控制面板”，负责向用户呈现信息和捕获用户输入。 +* **`核 (Core Component)`**: 这是一个`道器`中，**无界面、负责后台逻辑**的部分。它作为一个服务运行，提供特定的能力来增强`元`或被其他`道器`调用。它是机器的“外挂工具”。 -### 1. 后端灵魂：流体复制与可钉选的服务 +### 架构的自由 -应用的核心逻辑是一个在`元`沙箱中运行的**WASM模块**。其部署遵循**“服务可钉选的流体复制”**的混合模型，兼顾了韧性与用户控制。 +开发者在构建他的`道器`时，拥有完全的架构自由： -### 2. 前端皮囊：按需加载的 Web 外壳 +* 他可以创建一个**单体式独立应用**，这个应用本身就是一个`化身`，将`元`库、一个`核`（用于逻辑）和一个`器`（用于UI）打包在一个可执行文件中。 +* 他可以创建一个**分布式应用**，让一个`器`在一个设备上，与另一个设备上的`核`进行通信。 +* 他可以只创建一个纯粹的**`核`**（一个“扩展”），仅仅为用户的整个“大道”提供一种新的后台能力。 +* 他也可以只创建一个纯粹的**`器`**，它没有任何自定义的后端逻辑（`核`），其界面直接调用`元`本身提供的核心服务（如“第二大脑”）来构建一个简单的工具应用。 -应用的用户界面，主要是一个**Web 应用**。其生命周期遵循**“一次注册，按需加载”**的模型，运行在官方的**“大道 Web 化身”**（它本身是一个`器化身`）中。这意味着用户只需向他的“大道”安装一次应用，就可以在任何设备上即时访问它。 - -### 3. 数据层：私有特征库 - -所有应用的数据，都安全地存储在“第二大脑”中，并作为AI的**“私有特征库”**。 - -## 架构总结 - -* **化身 (Avatar)**：作为`元`的原生宿主。**`器化身`** 负责渲染UI，而 **`核化身`** 提供稳健的后台支持。 -* **元 (Meta Unit)**：主权核心，负责运行沙箱化的应用逻辑（WASM），管理所有数据和状态，并在用户的私有P2P网络中协调任务。 +这套架构确保了“大道”不仅是一个平台，更是一个真正开放的、可组合的、去中心化的生态系统。 diff --git a/zh/src/concepts/user_journey.md b/zh/src/concepts/user_journey.md index 85d5a1a..0d09a3a 100644 --- a/zh/src/concepts/user_journey.md +++ b/zh/src/concepts/user_journey.md @@ -2,44 +2,49 @@ 任何主权系统的一个核心挑战，都在于“绝对控制”与“轻松便利”之间的张力。“大道”解决这个问题的方式，不是强迫用户二选一，而是设计了一场充满引导、相互尊重的**“渐进式主权”**之旅。我们在用户熟悉的地方与他们相遇，并赋能他们去往任何他们想去的地方。 -这场旅程不仅适用于用户对核心数据的掌控，也同样适用于他们与应用交互的方式。 +这场旅程不仅适用于用户对核心数据的掌控，也同样适用于他们与**`道器`**（应用和扩展）生态系统的交互。 ## 应用之旅：一次注册，随处使用 -在“大道”中安装应用，与传统应用商店有着本质的不同。它不是将一个程序安装到单一的设备上，而是为你整个的数字生命体——你的“大道”——授予一项新的能力。 +在“大道”中“安装”一个应用，与传统应用商店有着本质的不同。它不是将一个程序安装到单一的设备上，而是为你整个的数字生命体——你的“大道”——授予一项新的能力。 ### 1. 发现与信任 -旅程始于一个去中心化的发现界面。当你找到一个应用时，你看到的不仅仅是下载按钮，还有它的**“信任仪表盘”**，让你能基于可验证的数据和社会化证明，做出知情的决定。 +旅程始于我们的**“应用集市”**，一个去中心化的发现系统。当你找到一个`道器`时，你看到的将是它的**“信任仪表盘”**（包含自动化验证检查和社区背书），让你能做出知情的、主权的决定。 ### 2. 注册与授权 (即“安装”) -当你决定“安装”应用时，系统会向你展示它的**“应用清单 (Manifest)”**，一个清晰的、人类可读的权限请求列表。你对这份清单的明确批准，就是那一次性的“安装”事件。这个行为将该应用**“注册”**到你的“大道”中，这个注册状态会被同步到你所有的`化身`。 +当你决定添加一个`道器`时，系统会向你展示它的**“清单 (Manifest)”**。这是一个清晰的、人类可读的列表，说明了该`道器`的组件（`器`和/或`核`）运行所需的权限。你对这份清单的明确批准，就是那一次性的“安装”事件。这个行为将该`道器`**“注册”**到你的`元`中，这个注册状态会被同步到你所有的`化身`。 -### 3. 无缝的跨设备访问 +### 3. 无缝的跨平台访问 -一旦注册，该应用就成为你“大道”的一部分，无需重复安装，即可在任何**`器化身 (Facet Avatar)`**上访问。 +一旦一个`道器`被注册，你就可以在任何设备上访问它。访问方式取决于其开发者的设计。 -* **在你的手机上**: 你点击应用的图标。“大道 Web 化身”会即时加载其 Web 界面。 -* **在一台新笔记本上**: 你首次登录你的`化身`。你会发现应用的图标**已经在那儿了**。当你点击它，你笔记本上的**`器化身`**会识别出这个注册，首次从网络获取UI资源包，缓存它，然后运行应用。 +* **对于基于 Web 的`器`组件**: + 你只需在你的标准浏览器中访问该应用的网址。网页会通过我们的 `dao.js` SDK，请求连接到你的“大道”。一旦你批准（例如，通过一个简单的认证器插件），那个**浏览器标签页本身，就变成了一个临时的`器化身`**，安全地渲染UI并与你的`元`通信。 + +* **对于原生的`器`组件**: + 你下载并运行这个原生应用（例如，从应用商店或直接下载）。在首次启动时，它会请求连接你的“大道”。一旦批准，这个**正在运行的应用程序，就变成了一个持久的`器化身`**，加入了你的网络。 + +因为所有这些`器化身`都由同一个、已同步的`元`来驱动，所以你的体验在任何地方都是一致的，无需在传统意义上于每个设备都“安装”一次应用。 ### 4. 高级配置 在任何时候，你都可以进入你的**“主权仪表盘”**来： -* 审查并撤销你授予该应用的权限。 -* 使用**“服务钉选 (Service Pinning)”**功能，将其后端任务指定给你专属的**`核化身 (Core Avatar)`**，从而完全控制你的资源分配。 +* 审查并撤销你授予任何`道器`的权限。 +* 使用**“角色分配”**功能，来建议某个`道器`的`核`组件，优先在你指定的某个`核化身`（例如你作为`计算节点`的家用服务器）上运行。 ## 主权之旅的阶段 ### 第一阶段：“托管模式” (Managed Mode) —— 你的向导之旅 -默认情况下，每一位新用户都从“托管模式”开始。此阶段通过友好的密钥恢复方法和默认同步节点提供最大便利，同时保持完全的端到端加密。 +对于新用户，此模式通过友好的密钥恢复方法和默认同步节点提供最大便利，同时保持完全的端到端加密。 ### 第二阶段：主权仪表盘 (Sovereignty Dashboard) —— 十字路口 -这是用户通往自治之旅的指挥中心。它是一个赋能与教育的工具，将用户的主权状态可视化，并提供游戏化的“任务”来鼓励用户获取更多控制权。 +这是用户通往自治之旅的指挥中心，是一个赋能与教育的工具，可将用户的主权状态可视化，并提供游戏化的“任务”来鼓励用户获取更多控制权。 ### 第三阶段：“主权模式” (Sovereign Mode) —— 你的数字王国 -这是旅程的最终、可选阶段。在“主权仪表盘”的引导下，用户可以“毕业”到此模式，完全自主保管他们的密钥并运行自己的**`核化身 (Core Avatar)`**（例如在家用服务器上），成为其数字领地中真正的主人。 +这是旅程的最终、可选阶段。在“主权仪表盘”的引导下，用户可以“毕业”到此模式，完全自主保管他们的密钥并运行自己的`核化身`网络，成为其数字领地中真正的主人。 diff --git a/zh/src/ecosystem/app_bazaar.md b/zh/src/ecosystem/app_bazaar.md index 2ccd20d..83c70af 100644 --- a/zh/src/ecosystem/app_bazaar.md +++ b/zh/src/ecosystem/app_bazaar.md @@ -8,40 +8,38 @@ ## 1. 发现 (Discovery)：联邦式策展 -在一个没有中央索引的世界里，用户如何找到应用？答案是：通过一个由受信任者组成的策展网络。 +在一个没有中央索引的世界里，用户如何找到新的**`道器`**？答案是：通过一个由受信任者组成的策展网络。 -* **开发者发布**: 开发者无需“提交”他的应用以供审批。他只需将其应用的**“清单 (Manifest)”**（一个包含所有元数据的 `manifest.toml` 文件）发布到一个像 **IPFS** 这样的P2P存储网络上。然后，他可以在公共频道上“广播”这个清单的地址。 -* **策展人的角色**: 任何人——一个科技媒体、一个受信任的开发者社区、一个KOL，或者“大道基金会”自己——都可以运行一个“策展”服务。这些策展人抓取网络上的新清单，并根据自己的标准，创建主题性的**“策展列表”**（例如“十大生产力应用”、“最优美的UI设计”）。 +* **开发者发布**: 开发者无需“提交”他的`道器`以供审批。他只需将其**“清单 (Manifest)”**（一个包含所有元数据的 `manifest.toml` 文件）发布到一个像 **IPFS** 这样的P2P存储网络上。然后，他可以在公共频道上“广播”这个清单的地址。 +* **策展人的角色**: 任何人——一个科技媒体、一个受信任的开发者社区，或者“大道基金会”自己——都可以运行一个“策展”服务。这些策展人抓取网络上的新清单，并根据自己的标准，创建主题性的**“策展列表”**。 * **用户体验**: 在用户的`器化身`中，他可以像订阅RSS一样，订阅多个他信任的“策展列表”。他的“集市”或“发现”标签页，就变成了这些信任源的个性化聚合视图。 这个模型用一个丰富的、多维度的、用户策划的发现体验，取代了单一的、有偏见的“应用商店”榜单。 ## 2. 信任与安全：可验证的信誉 -用户如何信任一个来自随意列表的应用？他们不必盲目信任。整个集市都直接构建于我们的**“社区信誉与自动化验证”体系**之上。 +用户如何信任一个第三方的`道器`？他们不必盲目信任。整个集市都直接构建于我们的**“社区信誉与自动化验证”体系**之上。 -每一个应用列表，无论来自哪个策展人，都必须展示其**“信任仪表盘”**，提供透明、多维度的信号： +每一个`道器`的列表，无论来自哪个策展人，都必须展示其**“信任仪表盘”**，提供透明、多维度的信号： 1. **自动化验证**: 来自 `dao-verify` 工具的、不可篡改的、关于安全漏洞和API合规性的“体检报告”。 -2. **社区背书**: 一个清晰的列表，显示了哪些有信誉的DID，为这个应用进行了密码学“签名背书”。 -3. **策展人信誉**: 推荐这个应用的策展人自身的信誉，也是一个信任信号。 +2. **社区背书**: 一个清晰的列表，显示了哪些有信誉的DID，为这个`道器`进行了密码学“签名背书”。 +3. **策展人信誉**: 推荐这个`道器`的策展人自身的信誉，也是一个信任信号。 -最终是否“注册”一个应用的决定权，永远掌握在用户手中，并有这些透明、可验证的数据作为依据。 +最终是否“注册”一个`道器`的决定权，永远掌握在用户手中，并有这些透明、可验证的数据作为依据。 ## 3. 分发 (Distribution)：抗审查与直接分发 -当用户决定安装一个应用时，这个过程是直接且去中心化的。 +当用户决定注册一个`道器`时，这个过程是直接且去中心化的。 -* 应用的清单中，包含了其软件包（`.wasm`服务模块和Web UI包）在 **IPFS** 上的**内容哈希（CID）**。 -* 用户的`元单元`使用这个哈希，直接从P2P网络获取文件。 -* 这确保了没有任何中心服务器可以阻止一个应用的分发。只要数据存在于P2P网络的某个角落，它就是可访问的。 +* `道器`的清单中，包含了其软件包（例如作为`.wasm`文件的`核`组件和作为Web UI包的`器`组件）在**IPFS**上的**内容哈希（CID）**。 +* 用户的`元`（由`化身`承载）使用这个哈希，直接从P2P网络获取文件。 +* 这确保了没有任何中心服务器可以阻止一个`道器`的分发。只要数据存在于P2P网络的某个角落，它就是可访问的。 ## 4. 商业化 (Monetization)：主权的与点对点的 我们消除了30%的“平台税”。我们的价值交换模型是直接从用户到开发者。 -* 应用的清单可以声明其商业模式（如一次性购买价格、订阅链接）。 -* 当用户发起购买时，`元单元`会触发我们的**“价值交换服务接口”**。 -* 这将促成一次**点对点（P2P）交易**，使用用户选择的外部支付协议，将价值直接从用户的钱包，发送到开发者在清单中指定的地址。 - -“大道”在此过程中，扮演的是交易的促成者和公证人，而非抽成的中间商。 +* `道器`的清单可以声明其商业模式（如一次性购买价格）。 +* 当用户发起购买时，`元`会触发我们的**“价值交换服务接口”**。 +* 这将促成一次**点对点（P2P）交易**，使用用户选择的外部支付协议，将价值直接从用户的钱包，发送到开发者在清单中指定的地址。“大道”在此过程中，扮演的是促成者，而非中间商。 diff --git a/zh/src/introduction.md b/zh/src/introduction.md index 2dbef57..a528e69 100644 --- a/zh/src/introduction.md +++ b/zh/src/introduction.md @@ -1,23 +1,27 @@ # 引言 -**我们旨在构建一种全新的、强大且坚韧的赛博生命 OS 范式——大道 (Dao OS)。** +**我们旨在构建一种全新的、强大且坚韧的赛博生命范式——大道 (Dao OS)。** -它并非要取代 Windows 或 Android，而是作为一个运行于其上的、去中心化的、以用户为绝对中心的叠加层 (Overlay) 而存在。 +“大道”不是一个传统的操作系统。相反，它是一套开放的协议和一个核心的、可移植的库—— **`元单元 (Meta Unit)`**（以下简称为 **`元`**），其使命是为任何平台上的任何应用，带来主权、智能与互操作性。 -它的使命是解决数字时代的碎片化、数据奴役和隐私泄露问题，将数字世界的主权归还给每一个独立的个人。它将成为我们在网络空间的生命延伸，一个与我们“互相成就”的**“硅基伙伴”**，我们的外接大脑、肢体与器官。 +它的目标是解决“数据孤岛”、“平台锁定”和“隐私侵蚀”问题。它通过提供一个统一、安全、用户所有的“数字灵魂”（即 **`元`**），让任何程序都可以通过集成它，而转变为用户个人P2P网络中的一个主权 **`化身 (Avatar)`**。 -## 核心特性 +我们称呼这些与“大道”集成的软件生态为 **`道器 (Dao Implement)`**。 -* **用户主权 (User Sovereignty)**：你的数据、你的身份、你的AI，完全由你掌控。所有数据默认端到端加密，存储在你自己的设备上。 -* **第二大脑 (Second Brain)**：内置强大的个人信息管理能力，安全地为你记忆密码、笔记、文件和待办事项，成为你永不遗忘的记忆体。 -* **个人AI伙伴 (Personal AI Companion)**：一个真正属于你的、与你共生的AI灵魂。它在本地运行，学习你的偏好，保护你的隐私，提供有温度的、启发式的支持，助你成长，而非将你淹没在信息茧房中。 -* **跨设备无缝同步 (Seamless Cross-Device Sync)**：你所有的设备（手机、电脑、浏览器等）都会成为你的“化身”，组成一个私有的、弹性的P2P网络，实现数据的无缝流转。 -* **开放与可扩展生态 (Open & Extensible Ecosystem)**：基于开放的协议和社区驱动的信任体系，任何人都可以为“大道”开发新的能力模块和“化身”形态。 +## 核心概念 -## 我们为何与众不同？ +* **`元 (Meta Unit)`**: 你数字生命的“精密机器”。一个可移植的库，包含了你加密的“第二大脑”、核心服务API，以及被扩展的能力。它是你所拥有的、等待被激活的唯一事实来源。 -在一个数据被平台垄断、算法被巨头控制的时代，“大道”选择了一条不同的路。我们相信，**技术平权**的下一波浪潮，是让每个人都拥有并控制自己的人工智能和数字生活。 +* **`化身 (Avatar)`**: “运行时”或“能源”。任何加载并运行你**`元`**的程序，都会成为一个`化身`。一个运行着Web应用的浏览器标签页、一个命令行工具、或一个原生移动App，都可以是`化身`，扮演着为**`元`**这台机器提供运行所需“能源”（CPU、内存）和资源的桥梁。 -我们设计的不是另一个App，而是一个属于你自己的、活的、可进化的数字生命空间。 +* **`道器 (Dao Implement)`**: 通过集成`元`而成为`化身`的应用和扩展所组成的生态系统。 + * **`器 (Facet Implement)`**: 拥有用户界面的`道器`，提供一个可与你的“大道”交互的“控制面板”。 + * **`核 (Core Implement)`**: 无界面的`道器`（“扩展”），用于增强你的“大道”的后台能力。 -**欢迎加入我们，一起构建未来。** +* **主权 P2P 网络**: 你所有的`化身`，无论它们运行在何种设备上，都会连接起来，形成一个私有的、坚韧的、端到端加密的网络，让它们内嵌的`元`中的数据，保持无缝同步。 + +## 我们的愿景 + +我们构想的未来是，你的数字身份和数据，不再被困于一个个花园围墙之内；你的应用，不再是一个个孤立的工具，而是一个更大的“数字自我”中，可以智能协作的组件；每一个用户，都是自己数字生活里真正的主权君主。 + +**欢迎加入我们，一起构建这个未来。** diff --git a/zh/src/philosophy/principles.md b/zh/src/philosophy/principles.md index 89e352b..881f3e0 100644 --- a/zh/src/philosophy/principles.md +++ b/zh/src/philosophy/principles.md @@ -12,15 +12,15 @@ 这个“自举式开发”范式遵循以下循环： -1. **播种 (The Seed)**：我们用传统工具，写出`元 (Meta Unit)`的第一个最简陋的版本，和一个基础的`器化身 (Facet Avatar)`。 -2. **自用 (Dogfooding)**：从那一刻起，我们使用我们自己这个初生的“大道”，作为管理项目的主要工具。所有的设计文档、笔记、讨论（就像这些）和代码片段，都存入我们自己的“第二大脑”中。 -3. **学习 (Learning)**：`元`的个人AI伙伴，开始以最高质量、最专注的“养料”——也就是我们创造它本身的过程数据——来训练自己。 +1. **播种 (The Seed)**：我们用传统工具，写出**`元单元`**（以下简称为**`元`**）的第一个最简陋的版本，和一个能运行它的基础**`化身`**。 +2. **自用 (Dogfooding)**：从那一刻起，我们使用我们自己这个初生的“大道”，作为管理项目的主要工具。所有的设计文档、笔记、讨论和代码片段，都存入我们自己的、由**`元`**所管理的“第二大脑”中。 +3. **学习 (Learning)**：**`元`**的个人AI能力（由我们官方的“AI伙伴”道器提供），开始以最高质量、最专注的“养料”——也就是我们创造它本身的过程数据——来训练自己。 4. **加速 (Acceleration)**：我们继而利用这个日益智能的AI伙伴，来帮助我们构建下一个版本。我们可以让它基于我们已记录的决策来生成样板代码，分析错误报告，或者带着对项目完整历史的完美记忆来一起进行架构设计的头脑风暴。 5. **进化 (Evolution)**：“大道”的能力越强，我们开发它的速度就越快。这就创造了一个指数级的正反馈循环，在这个循环中，创造的行为本身，就是一场与“创造物”的持续对话。 ## AI 伦理宪章 -由于 AI 是系统的灵魂，其伦理基石至关重要。我们的AI宪章由四大核心宗旨构成： +由于AI是系统潜能的核心部分，其伦理基石至关重要。我们的AI宪章由四大核心宗旨构成： 1. **伙伴宗旨**: AI 是伙伴，而非仆人或神谕。 2. **透明宗旨**: AI 的推理过程必须是可审查和可理解的。 @@ -35,5 +35,5 @@ * **体验为王**: 主权不应以牺牲优美、直观和愉悦的用户体验为代价。 * **设计即隐私**: 默认情况下，所有数据都是私密的、本地的，并进行端到端加密。 * **韧性与可移植性**: 系统应该是健壮的，支持离线工作，并且没有单点故障。 -* **多语言主义**: 我们拥抱一个多语言、多平台的生态系统。 -* **社区与开放**: 项目在开放中构建，与社区同行，为社区服务。 +* **开放与多语言主义**: **`元`**是一个可移植的库，集成它而成为`化身`的**`道器`**可以用任何语言编写。 +* **社区驱动**: 项目在开放中构建，与社区同行，为社区服务。 diff --git a/zh/src/project/CONTRIBUTING.md b/zh/src/project/CONTRIBUTING.md index 84693f0..405096c 100644 --- a/zh/src/project/CONTRIBUTING.md +++ b/zh/src/project/CONTRIBUTING.md @@ -12,21 +12,21 @@ 您无需成为 Rust 专家才能做出贡献。有很多方式可以提供帮助： -* **代码**: 为`元 (Meta Unit)`贡献代码，构建新的`化身`，或为`dao-verify`套件开发插件。可以从寻找标记有`"good first issue"`的 issue 开始。 -* **文档**: 提升这些文档的清晰度，撰写教程，或添加示例。 -* **翻译**: 将我们的文档翻译成新的语言。 -* **设计**: 帮助我们的参考`化身`进行UI/UX设计。 -* **社区**: 回答问题，帮助新用户，并参与讨论。 +* **核心开发**: 为`元`库和核心协议（使用Rust）贡献代码。 +* **`道器`开发**: 创建新的`道器`，它可以包含**`器`（UI）组件**和**`核`（无界面逻辑）组件**。 +* **文档与翻译**: 改进这些文档，撰写教程，以及将它们翻译成新的语言。 +* **用户支持与社区管理**: 帮助新用户，回答问题，营造一个热情、互助的氛围。 +* **设计与用户体验**: 为参考`道器`贡献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`）。 +1. **Fork 仓库**: 创建目标仓库的一份你自己的拷贝（例如 `dao-os-docs`, `meta-unit`）。 +2. **创建分支**: 从 `main` 分支创建一个新的分支用于你的变更。请使用描述性的名称（例如 `feat/add-note-encryption`）。 3. **进行更改**: 编写你的代码及相应的测试。 -4. **运行本地检查**: 在提交前，请确保你运行了所有本地测试（如 `cargo test`）和代码格式化工具。 -5. **Commit 你的变更**:我们鼓励使用 [Conventional Commits](https://www.conventionalcommits.org/zh/v1.0.0/) 规范，以获得清晰可读的 commit 消息。 +4. **运行本地检查**: 在提交前，请确保你运行了所有本地测试和代码格式化工具。 +5. **Commit 你的变更**: 我们鼓励使用 Conventional Commits 规范，以获得清晰可读的 commit 消息。 6. **Push到你的Fork**: 将你的变更推送到你自己的 Fork 仓库。 7. **开启一个 Pull Request**: 从你的分支向 Dao OS 官方仓库的 `main` 分支提交一个 Pull Request (PR)。 8. **描述你的 PR**: 在 PR 的描述中，请链接任何相关的 issue，并清晰地描述你正在解决的问题和你的解决方案。 diff --git a/zh/src/project/governance.md b/zh/src/project/governance.md index 5ad21fc..a156a64 100644 --- a/zh/src/project/governance.md +++ b/zh/src/project/governance.md @@ -14,8 +14,8 @@ “大道”的初始创建者和核心贡献者，将自己的角色视为一个不断演进的过程。 -* **在早期阶段（架构师）**: 我们的主要角色是架构师——为项目奠定一个坚实且自洽的基础，定义核心协议，并构建初始工具。这需要一个专注的愿景来确保项目在正确的道路上启航。 -* **在长期阶段（园丁）**: 随着生态的成熟，我们的角色将从“事必躬亲”转变为“照料花园”。我们将专注于提供更好的工具（如`dao-verify`套件）、维护核心基础设施，并赋能社区去建设和创新。我们的目标，是让我们自己变得越来越不那么“不可或缺”。 +* **在早期阶段（架构师）**: 我们的主要角色是架构师——为项目奠定一个坚实且自洽的基础，定义核心协议，并构建初始工具。 +* **在长期阶段（园丁）**: 随着生态的成熟，我们的角色将从“事必躬亲”转变为“照料花园”。我们将专注于提供更好的工具、维护核心基础设施，并赋能社区去建设和创新。 ## 生态策略：聚焦与引爆 @@ -25,25 +25,25 @@ 我们核心团队的开发精力，将集中于打造**一条“黄金路径”**，使其体验足够高效和愉悦，以此作为吸引第一波开发者的主要催化剂。这条被选定的路径，就是**Nim 统一开发套件**，它利用 Nim 语言的独特能力，从单一代码库构建 WASM 后端和 Web UI 前端。 -这并不排斥其他的开发路径（如 Rust + TypeScript 或 Rust + Flutter）。它们在协议层面依然被完全支持。然而，它们被视为**“社区/高级路径”**，我们依赖社区的力量来构建相应的工具链和最佳实践。我们对这些路径的官方角色，是提供清晰的文档和一个稳定的、语言无关的核心API。 +这并不排斥其他的开发路径（如 Rust + TypeScript 或原生集成）。它们在协议层面依然被完全支持。然而，它们被视为**“社区/高级路径”**，我们依赖社区的力量来构建相应的工具链和最佳实践。 ## 如何贡献 贡献的形式多种多样，每一种都同样宝贵。你可以通过以下方式帮助建设“大道”： -* **核心开发**: 为`元 (Meta Unit)`和核心协议（使用Rust）贡献代码。 -* **化身与模块开发**: 为不同平台创建新的`化身`，或开发新的模块来扩展`元`的能力。 +* **核心开发**: 为`元`库和核心协议（使用Rust）贡献代码。 +* **`道器`开发**: 创建新的`道器`，它可以包含**`器`（UI）组件**和**`核`（无界面逻辑）组件**。 * **文档与翻译**: 改进这些文档，撰写教程，以及将它们翻译成新的语言。 * **用户支持与社区管理**: 帮助新用户，回答问题，营造一个热情、互助的氛围。 -* **设计与用户体验**: 为我们的参考`化身`贡献UI/UX设计，并为生态定义设计模式。 +* **设计与用户体验**: 为参考`道器`贡献UI/UX设计，并为生态定义设计模式。 ## 决策流程 我们的治理模式，被设计为与项目共同成长。 -1. **早期阶段 (阶段 I-II)**: 决策将由**核心团队**在公共渠道进行开放讨论后做出。这种类似“仁慈的终身独裁者 (BDFL)”的模式，对于项目初期的速度和一致性是必要的。 -2. **成长阶段 (阶段 III-IV)**: 对于核心协议或架构的重大变更，我们将引入一个正式的 **RFC (请求评论) 流程**。这允许社区中的任何人撰写详细的提案，该提案将在公开辩论和完善后，再做出最终决定。 -3. **成熟阶段 (未来)**: 我们致力于在未来探索并过渡到更去中心化的治理机制，例如由贡献者选举产生的技术委员会，或基于DAO的财库与协议管理模型。 +1. **早期阶段 (阶段 I-II)**: 决策将由**核心团队**在公共渠道进行开放讨论后做出。 +2. **成长阶段 (阶段 III-IV)**: 对于核心协议或架构的重大变更，我们将引入一个正式的 **RFC (请求评论) 流程**。 +3. **成熟阶段 (未来)**: 我们致力于在未来探索并过渡到更去中心化的治理机制。 ## 沟通渠道 diff --git a/zh/src/project/roadmap.md b/zh/src/project/roadmap.md index efd9a54..102547b 100644 --- a/zh/src/project/roadmap.md +++ b/zh/src/project/roadmap.md @@ -4,50 +4,51 @@ --- -### 第一阶段：创世 (Genesis) - 奠定基石 +### 第一阶段：创世 (Genesis) - 基石与桥梁 * **时间**：2025年第三季度 - 2025年第四季度 -* **核心目标**：构建大道 OS 最底层的核心组件，完成项目的技术可行性验证。 +* **核心目标**：构建核心的`元`库，以及让开发者能够开始构建的关键工具。 * **关键里程碑**: - * 完成 v0.1 版本的核心 API 规范定义。 - * 使用 Rust 开发 v0.1 版本的`元 (Meta Unit)`，包含基础的加密和P2P模块。 - * 创建两个用于测试和演示的最小可行化身：一个命令行的**`核化身 (Core Avatar)`**和一个基础的浏览器**`器化身 (Facet Avatar)`**。 -* **功能故事**: “我成功在我的电脑上运行了‘大道’的种子，在我的浏览器里创建了一个‘化身’，并存储了一条只存在于我自己设备上的加密信息。我看到了未来的火花。” + * 完成 v0.1 版本的`元`核心 API 规范。 + * 使用 Rust 开发 v0.1 版本的`元`，包含`SecretStore`、`NoteStore`和基础的P2P同步服务。 + * 开发第一个官方的**`核化身 (Core Avatar)`**：一个用于初始化“大道”、管理密钥和基础诊断的命令行工具。 + * 发布 v0.1 版本的 **`dao.js` SDK**，使任何 Web 应用都能成为一个临时的`器化身`。 +* **功能故事**: “作为一名开发者，我能用一个命令行工具来初始化我的‘道’。然后，我可以利用一个简单的Web应用，导入`dao.js`库，并看着它连接上我的‘道’，读取一条测试笔记。这个地基是真实存在的。” --- -### 第二阶段：显现 (Manifestation) - “第二大脑”觉醒 +### 第二阶段：显现 (Manifestation) - 第一个“道器”诞生 * **时间**：2026年第一季度 - 2026年第二季度 -* **核心目标**：交付“第二大脑”的核心功能 MVP，为早期用户提供切实的日常价值。 +* **核心目标**：发布第一个官方的、高价值的`道器`，以展示生态系统的力量并吸引早期用户。 * **关键里程碑**: - * 在`元`中完整实现`SecretStore`（密码）和`NoteStore`（笔记）模块。 - * 浏览器`器化身`支持完整的密码管理和基础的笔记功能。 - * 开发 v0.1 版本的移动端**`器化身 (Facet Avatar)`**（例如，使用 Flutter），并实现“动态锚点”逻辑。 - * 上线包含初步文档的项目官网。 -* **功能故事**: “我所有的密码和私密笔记都安全地存储和无缝地同步在我自己的设备之间。我的手机是我数字生活的锚点。我再也无需信任第三方云服务来保管我的秘密。我的数字生活终于有了家。” + * 完善并稳定化`元`内部的核心服务。 + * 遵循我们的“良木为材”战略，**改造一个结构清晰的开源笔记或密码管理器**，通过集成`dao.js` SDK，使其成为我们的第一个官方`器道器`。 + * 实现**“渐进式主权”**的用户上手流程。 + * 上线包含完整用户和开发者文档的项目官网。 +* **功能故事**: “我正在浏览器里使用一个优美、快速、且熟悉的笔记应用。但我知道，它的数据是端到端加密的，通过P2P网络在我的所有设备间无缝同步，没有任何中心服务器。这是第一个真正属于我自己的应用。” --- ### 第三阶段：协同 (Synergy) - 连接不同的大道 * **时间**：2026年第三季度 - 2026年第四季度 -* **核心目标**：实现不同用户“大道”之间的、可信的安全交互，为去中心化的社会结构奠定基础。 +* **核心目标**：实现不同用户“大道”之间的、可信的安全交互，并为高级AI奠定基础。 * **关键里程碑**: * 在`元`中实现 W3C DID 和 VC 模块。 - * 开发一个跨“大道”协作的PoC应用，例如：向另一个用户安全地出示一个可验证凭证。 - * 启动“情感共鸣模块”的基础研究和原型设计。 -* **功能故事**: “我拥有了一个独一无二的、无法被审查的‘大道’数字身份。我可以用这个身份，向另一个‘大道’用户通过密码学证明我的一个凭证，而无需依赖任何平台。我们之间建立了一种新的信任。” + * 开发一个跨“大道”通信的PoC应用（例如，分享一篇经过签名、可验证的笔记）。 + * 启动官方**“大道AI伙伴”`核道器`**的基础研究和原型设计。 +* **功能故事**: “我拥有了一个主权的数字身份。我可以授权另一个‘大道’用户有限的、加密的访问权限来读取我的一篇笔记，而无需通过任何第三方平台。我们可以组建真正的信任网络。” --- -### 第四阶段：生态 (Ecosystem) - 千树万树梨花开 +### 第四阶段：生态 (Ecosystem) - 应用集市开张 * **时间**：2027年及以后 -* **核心目标**：将“大道”从一个强大的工具，演进为一个为所有人服务的、开放的、可扩展的平台。 +* **核心目标**：将“大道”从一个拥有旗舰应用的平台，演进为一个繁荣、开放的生态系统。 * **关键里程碑**: - * 发布 v1.0 稳定版的`元` API 和一个健壮的开发者SDK。 - * 上线用于发现可信第三方`化身`的“社区信誉与自动化验证”体系。 - * 发布一个集成“情感共鸣模块”的重大更新（例如 Dao OS 2.0）。 - * 培育一个能构建各种新`化身`和模块的、繁荣的社区。 -* **功能故事**: “我的‘大道’现在是一个活的平台。我安装了一个社区开发的模块，我的AI伙伴也变得更有温度、更有洞察力了。我的数字生活现在是完整的、统一的，并充满了无限的可能性。” + * 发布 v1.0 稳定版的`元` API。 + * 发布第一个官方的**“大道AI伙伴”`核道器`**，为用户提供主动的、智能的辅助。 + * 上线**“应用集市”**协议和一个参考策展索引。 + * 为构建高级原生**`器化身`**（例如用Flutter/Swift）提供官方指南和社区支持。 +* **功能故事**: “我的‘大道’活了过来。我的AI伙伴帮助我管理我的一天。我可以在一个去中心化的集市里，寻找社区构建的、可信的新`道器`。我的数字生活是主权的、智能的，并且在不断成长。” diff --git a/zh/src/specifications/tech_overview.md b/zh/src/specifications/tech_overview.md index 55e1452..0586491 100644 --- a/zh/src/specifications/tech_overview.md +++ b/zh/src/specifications/tech_overview.md @@ -1,42 +1,44 @@ # 技术总览 -本文档为希望在大道 (Dao OS) 生态系统中进行构建或贡献的开发者，提供了关于架构、核心技术和指导原则的高阶概览。 +本文档为希望构建**`道器`**（与大道OS生态集成的应用和服务）的开发者，提供了关于架构、核心技术和指导原则的高阶概览。 ## 技术指导原则 -我们的工程决策由一套核心原则指引，以确保系统是健壮、可移植和开放的。 +* **是“库”，而非“框架”**: 大道OS不是一个限制性的框架。**`元`**是一个可移植的库，你将它集成到你自己的应用中，在不规定你应用内部架构的前提下，为其赋能。 +* **开放与多语言主义**: 任何应用，无论用何种语言编写，都可以成为一个**`化身`**（`元`的运行时）。我们通过将`元`同时提供为**WASM库**（用于Web和脚本语言）和**原生库**（`.so`, `.dll`, `.a`，用于系统语言）来实现这一点。 +* **API优先**: 所有与`元`的交互，都通过一个稳定的、版本化的、文档齐全的API进行。 +* **安全第一**: `元`是一个安全保险库。所有数据默认端到端加密，所有交互都由一个严格的、用户控制的权限系统来管理。 -* **Web原生与可移植性**: 我们将源自Web的技术作为应用开发的**主路径**。 -* **通过WASM实现多语言主义**: 核心应用逻辑被编译成 WebAssembly (WASM)，允许开发者使用他们选择的语言（如 Rust, Go, 或 Nim）。 -* **API优先**: 应用逻辑和用户界面之间的交互，由一个严格的、版本化的API契约来定义。 -* **安全第一**: 所有第三方应用逻辑都运行在`元`内部的安全沙箱中，并恪守“最小权限原则”。 -* **自由及开源软件 (FOSS)**: 整个核心协议和参考实现都是开源的。 +## 核心集成：应用如何“化身” -## 应用开发路径 +创造一个`道器`的旅程，始于集成`元`库，这个动作会即时地将正在运行的应用进程，转变为用户“大道”网络中的一个主权`化身`。我们提供两条主要的集成路径。 -从开发者的角度看，“大道”应用由一个后端的“灵魂”（WASM服务模块）和一个前端的“皮囊”（UI）组成。我们提供多种路径来构建它们，以满足不同的需求和偏好。 +### 1. Web 集成路径 (通过 `dao.js` SDK) -### 1. 主流路径 (推荐起点) +这是对于 Web 开发者来说，最简单、最平滑的路径。 -这是最稳健、生态最丰富的路径。 +* **工作原理**: 开发者可以利用任何新的或现有的Web应用。通过引入我们的 `dao.js` SDK，他的Web应用就获得了加载`元`的WASM二进制文件 (`dao.wasm`) 的能力。 +* **“化身”转变**: 一旦用户授权，运行这个Web应用的**浏览器标签页，就变成了一个临时的`化身`**。Web应用的JavaScript代码，就可以通过`dao.js`桥暴露出的高层API，与`元`进行通信。 +* **最适用于**: 快速构建`器`组件 (`Facet Implement`)，创建数据可视化面板，以及将现有的PWA（渐进式Web应用）集成到“大道”生态中。 -* **后端 (服务于 `核化身`)**: 应用的核心逻辑，以一个用 Rust 或 Go 编写的 WASM 模块存在。虽然它理论上可以在任何化身上运行，但其持久的、资源密集型的任务，通常被设计为在**`核化身 (Core Avatar)`**上执行。 -* **前端 (呈现于 `器化身`)**: 一个标准的 **Web 应用** (使用 TypeScript/JavaScript)。这个 UI 被设计为运行在我们官方的、安全的**“大道 Web 化身”**中。 +### 2. 原生集成路径 (通过 FFI) -### 2. 快速通道：Nim 开发套件 (官方支持) +这条路径为原生应用提供了最强的性能和最深的系统集成能力。 -为了追求极致的生产力，我们为 **Nim** 提供了一流的支持。 +* **工作原理**: 一个原生应用（用Rust, Go, Swift, Kotlin, C++等编写）的开发者，可以直接链接`元`的原生库。 +* **“化身”转变**: 正在运行的原生应用进程，就变成了一个持久的**`化身`**。应用代码通过一个**外部函数接口（FFI）**桥，与`元`的核心服务通信。 +* **最适用于**: + * 在服务器或NAS设备上，创建强大的、7x24小时在线的**`核`组件 (`Core Implement`)**。 + * 构建高性能的原生**`器`组件 (`Facet Implement`)**，比如我们理想中基于Flutter的移动客户端。 + * 改造现有的开源原生应用。 -* **后端 (服务于 `核化身`)**: 应用的核心逻辑，从 Nim 编译到 **WASM**。同主流路径一样，它理想的运行环境是`核化身`。 -* **前端 (呈现于 `器化身`)**: 从同一份 Nim 源码编译到 **JavaScript** 的 **Web 应用**。这个统一的方案运行在“大道 Web 化身”中。 +## 关键技术与协议 -### 3. 原生路径 (高级) - -对于需要深度平台集成或顶尖原生性能的开发者，可以构建一个**自定义的`器化身`**。 - -* **后端 (服务于 `核化身`)**: 同样是那个 **WASM** 服务模块，它可以被任何类型的化身调用。 -* **前端 (自定义 `器化身`)**: 一个完全原生的应用（例如，用 Flutter 或 Swift 编写），它直接作为`元`的宿主并提供 UI。 - -## API 契约与关键技术 - -API 契约通过 `dao.js` 桥为 Web UI 暴露，或为原生 UI 直接暴露，统一使用 **Protocol Buffers** 进行数据序列化。所有路径的核心技术保持一致。 +| 类别 | 技术 / 协议 | 用途 | +| :--- | :--- | :--- | +| **核心库** | Rust -> WASM / 原生库 | 为`元`创建一个单一的、安全的、高性能的核心逻辑。 | +| **Web集成** | `dao.js` SDK (JS/TS) | 任何Web应用成为`化身`的桥梁。 | +| **P2P网络** | `libp2p` | 模块化的节点发现、传输和安全通道。 | +| **数据同步** | 无冲突复制数据类型 (CRDTs) | 确保各`化身`间的最终一致性。 | +| **身份** | DID & VC | 主权身份与可互操作的、基于密码学的信任。 | +| **数据序列化** | Protocol Buffers (Protobuf) | 用于API的高效、语言无关的数据结构。 |