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 Definition
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基础设施能力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.
03持续运行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.