01
能力声明Capability Declaration
能力带着身份、边界、权限和调用条件进入 AIOS。A capability enters AIOS with identity, boundaries, permissions, and invocation conditions.
SYS / 01AIOS 系统AIOS System
AIOS 如何把分散能力变成可运行系统？How does AIOS turn scattered capabilities into an operating system?
AIOS 让智能体、设备、服务、空间与开发者能力被识别、调用、协作和计量。AIOS lets agents, devices, services, spaces, and developer capabilities be identified, invoked, coordinated, and measured.
它不是单一工具、聊天入口或工作流平台，而是让能力在真实任务中进入、匹配、执行、归因，并把有效协作沉淀为下一次可复用关系的运行基础设施。It is not a single tool, chat entry, or workflow platform. It is operating infrastructure that brings capabilities into real tasks, matches them, executes them, attributes outcomes, and turns valid collaboration into reusable relationships.
一次系统运行如何闭合How one system run closes
04 项04 SIGNALS02
需求匹配Demand Matching
需求在明确上下文中找到可信、适配且可执行的能力。Demand finds trusted, suitable, and executable capabilities within explicit context.
03
协作调用Coordinated Invocation
运行层把智能体、设备、服务与空间组织成一次真实任务。The operating layer organizes agents, devices, services, and spaces into one real task.
04
贡献回流Contribution Return
结果被计量和归因，价值按贡献回流，并留下可复用关系。Outcomes are measured and attributed; value returns by contribution and leaves reusable relationships.
01系统架构System Architecture
AIOS 的运行对象不是界面或应用，而是主体、能力、任务与贡献。AIOS operates on subjects, capabilities, tasks, and contributions, not interfaces or apps.
系统成立的前提，是每个进入协作的主体都能被识别，每项能力都能被调用，每次结果都能被记录，每份贡献都能被计量。The system becomes valid when every collaborating subject can be identified, every capability can be invoked, every outcome can be recorded, and every contribution can be measured.
SUB
主体可识别Subjects Identified
智能体、设备、服务、空间和开发者能力进入系统前，必须拥有清晰身份与边界。Agents, devices, services, spaces, and developer capabilities need clear identity and boundaries before entering the system.
CAP
能力可调用Capabilities Invoked
能力不是停在目录里，而是在权限、上下文和条件明确时被真实调用。Capabilities do not stay in a catalog; they are invoked when permissions, context, and conditions are clear.
TASK
协作可调度Collaboration Orchestrated
一次任务会把多个主体与能力组织起来，在现场约束中完成连续执行。One task organizes multiple subjects and capabilities into continuous execution under field constraints.
VALUE
贡献可计量Contributions Measured
结果、贡献和反馈被记录后，价值才可能回流，关系才会进入下一次复用。Only recorded outcomes, contributions, and feedback can return value and make relationships reusable in the next run.
02标准与协议Standards & Protocols
先统一对象、边界与结果，再让不同实现进入同一套协作。Align subjects, boundaries, and outcomes before different implementations join the same collaboration.
这里说明跨产品必须共同保持的系统边界，不把概念提前包装成已发布协议。具体 API、SDK、Manifest、认证与发布状态，以经过验证的工程规范、开发者文档或实现为准。This section states the system boundaries shared across products without presenting concepts as released protocols. Concrete APIs, SDKs, manifests, certification, and release status remain governed by verified engineering specifications, developer documentation, or implementation.
ID
身份与信任Identity & Trust
智能体、设备、用户、服务与空间必须可识别，并在明确权限下建立可信关系。Agents, devices, users, services, and spaces must be identifiable and form trusted relationships under explicit permission.
CAP
能力声明与发现Capability Declaration & Discovery
能力带着边界、条件、版本与运行位置进入系统，才能被发现和选择。Capabilities enter with boundaries, conditions, versions, and runtime location before they can be discovered and selected.
CTX
上下文与状态Context & State
任务上下文、长期经验与空间状态保持来源和边界，孤立信号不直接成为系统判断。Task context, long-term experience, and spatial state preserve provenance and boundaries; isolated signals do not become system judgment.
RUN
可信调用Trusted Invocation
调用在授权、风险、确认、撤销、失败与恢复边界内完成，并保留人的控制。Invocation operates within authorization, risk, confirmation, undo, failure, and recovery boundaries while preserving human control.
TRACE
结果与追踪Outcomes & Traceability
结果、错误、反馈与贡献必须可记录和归因，只有被验证结果才能进入后续复用。Outcomes, errors, feedback, and contribution must be recordable and attributable; only verified outcomes enter future reuse.
03基础设施能力Infrastructure Capabilities
让 AIOS 持续运行的，是记忆、身份调度与价值流动。AIOS keeps operating through memory, identity orchestration, and value flow.
这些不是单个产品的卖点，而是跨产品共同承担的系统能力：保存协作历史，连接可信主体，让贡献产生回流。These are not single-product selling points. They are cross-product system capabilities: preserving collaboration history, connecting trusted subjects, and returning value to contributors.
MEM
长期记忆Persistent Memory
协作历史和经验不会随任务结束消失，主体可以跨任务、设备和场景保持连续状态。Collaboration history and experience do not disappear when a task ends, so subjects can keep continuity across tasks, devices, and scenarios.
ID
身份与调度Identity & Orchestration
智能体、设备、服务与空间被可信连接，并在明确权限和上下文中统一调度。Agents, devices, services, and spaces are connected with trust and orchestrated under explicit permissions and context.
FLOW
价值流动Value Flow
能力调用产生的贡献可计量、可归因、可结算并回流，系统才有持续吸引新能力的理由。Contributions from capability invocation need to be measurable, attributable, settleable, and returnable before the system can keep attracting new capabilities.
04运行位置Runtime Placement
AIOS 运行在云、边、端与设备之间，而不是被装进一种界面或一台机器。AIOS runs across cloud, edge, terminals, and devices instead of living in one interface or machine.
Linux 是云端和边缘节点的首选基础系统，但不是 AIOS 本身。容器、系统服务、安装包和 Origin 整机镜像负责交付，同一套系统职责按时延、隐私、权限和现场连续性分布运行。Linux is the preferred base for cloud and edge nodes, but it is not AIOS itself. Containers, system services, packages, and Origin device images deliver the system while responsibilities are distributed by latency, privacy, permission, and field continuity.
CLOUD
云端连接全局关系Cloud connects global relationships
承载跨空间身份、能力索引、策略、同步、治理和远程诊断。Hosts cross-space identity, capability indexes, policy, synchronization, governance, and remote diagnostics.
EDGE
边缘理解现场状态Edge understands field state
Origin 在现场承载空间状态、设备连接、本地运行、低延迟响应和断网恢复。Origin hosts spatial state, device connections, local runtime, low-latency response, and offline recovery in the field.
USER
终端保留人的控制Terminals preserve human control
手机、屏幕、语音与其它终端提供解释、确认、撤销和人工接管。Phones, screens, voice, and other terminals provide explanation, confirmation, undo, and human takeover.
DEVICE
设备感知并执行Devices sense and act
现场设备提供可验证感知和执行；协议适配后形成标准事件与执行回执。Field devices provide verifiable sensing and action; adapters turn their protocols into standard events and execution receipts.
05空间感知Spatial Perception
AIOS 接收的不是一堆传感器读数，而是可追踪、可解释的空间状态。AIOS receives traceable, explainable spatial state, not a pile of sensor readings.
设备适配器先把不同协议转成标准观察事件；引元再融合时间、位置、信号质量与现场规则；引核基于状态形成判断与计划，可信设备执行后把结果、错误和用户反馈送回系统。Device adapters first convert different protocols into standard observation events. Origin then combines time, location, signal quality, and field rules. Cortex plans from state, and trusted devices return outcomes, errors, and user feedback after execution.
OBS
信号标准化Normalize observations
设备身份、空间位置、观察时间、序列、值、质量和数据分类随事件一起进入。Device identity, spatial location, observation time, sequence, value, quality, and data classification travel with each event.
STATE
形成空间状态Form spatial state
多路信号经过窗口、状态机和现场规则融合，单点读数不直接触发高风险动作。Signals are fused through windows, state machines, and field rules; one reading never directly triggers high-risk action.
PLAN
判断与授权Decide and authorize
Runtime 在上下文、权限和风险边界内决定提醒、确认或调用能力。Runtime chooses reminders, confirmation, or capability invocation within context, permission, and risk boundaries.
BACK
结果回到关系Return outcomes to relationships
执行状态、错误、撤销与用户纠正被记录，只有被验证结果才进入后续复用。Execution status, errors, undo, and user corrections are recorded; only verified outcomes enter future reuse.
06持续运行Continuous Operation
系统能持续运行，是因为每次有效协作都会留下下一次可读取的关系。The system keeps operating because every valid collaboration leaves a relationship the next run can read.
AIOS 的中心不是单个能力，而是被验证价值的关系持续累积。能力是节点，价值发生在边上，系统负责让这些边被写入、读取和更新。The center of AIOS is not a single capability, but the accumulation of value-proven relationships. Capabilities are nodes, value happens on edges, and the system writes, reads, and updates those edges.
READ
读取上下文Read Context
系统先读取主体身份、能力边界、任务上下文和历史经验，避免每次协作都从零开始。The system reads subject identity, capability boundaries, task context, and historical experience so collaboration does not restart from zero.
WRITE
写入结果Write Outcomes
一次调用完成后，结果、贡献、失败位置和反馈被写回系统。After an invocation completes, outcomes, contributions, failure locations, and feedback are written back into the system.
UPDATE
更新关系Update Relationships
被验证的价值关系在时间上累积，下一次发现、调用和结算会读取这些关系。Value-proven relationships accumulate over time, and the next discovery, invocation, and settlement read them.
GROW
生成新能力Generate New Capability
关系越厚，既有能力越容易组合重组，系统越能产生新的可用价值。As relationships thicken, existing capabilities become easier to recombine, and the system can generate new usable value.
从系统进入下一层From System to Next Layer
理解运行机制后，再进入产品、蓝图或开发者入口。After the operating mechanics are clear, continue into products, blueprint, or the developer entry.
产品说明 AIOS 的产品体系如何分工；蓝图说明这些机制如何进入阶段、路径与长期判断；开发者平台让新的能力进入 AIOS 并参与真实协作。Products explain how the AIOS product system divides responsibility; blueprint explains how these mechanics become stage, path, and long-term judgment; the developer platform lets new capabilities enter AIOS and join real collaboration.