农业现场需要的，是感知环境、按权限控制设备，并确认动作后的变化。沿着这项任务，看 AIOS 如何连接现场能力、人的控制与结果反馈。A farm needs to sense its environment, control equipment with permission, and check what changed. Follow this task to see how AIOS connects field capabilities, human control, and feedback.
当前正通过具体项目验证可信协作，可用能力与接入范围按项目确认。Trusted collaboration is being validated through specific projects. Available capabilities and integration scope are confirmed per project.
同一片空间， 需要彼此配合的能力。One environment. Capabilities working together.
菌菇培育需要关注温度、湿度与 CO₂。感知、通风、加湿和温控，共同服务于环境调节。Mushroom cultivation depends on temperature, humidity and CO₂. Sensing, ventilation, humidification and temperature control all contribute to the same task.
AIOS 的系统设计将现场状态、任务目标与授权范围放在一起，再组织设备或服务参与执行。AIOS is designed to bring site state, task goals and permissions together before coordinating devices and services.
农业试点已将培育结果回流用于改进。结果与纠正，也是 AIOS 持续积累可复用经验的基础。The agricultural pilot feeds cultivation outcomes back into improvement. Results and corrections are the basis for reusable experience in AIOS.
试点进展：已实现环境感知、设备控制与培育结果反馈。协作图解释系统设计，不代表所有产品均已部署。Pilot progress: sensing, device control and cultivation feedback are implemented. The diagram explains system design; it does not imply deployment of every product.
Mushroom Farm · Andrew Bossi · CC BY-SA 2.5 · 缩小与格式转换，页面裁切；非引态试点。Resized, converted and displayed cropped; not an Instaon pilot.
管理跨空间任务、状态与权限策略，组织模型和能力调用，并处理失败升级。Manages cross-space tasks, state, permission policies, model and capability calls, and failure escalation.
了解引核Explore Cortex在空间边缘连接设备，维护现场状态，在本地规则和权限内执行，并回读真实结果。Connects devices at the edge, maintains spatial state, runs within local rules and permissions, and reads back outcomes.
了解引元Explore Origin明确设备身份、可信状态、能做什么与调用边界，让物理能力可验证地参与任务。Defines device identity, trusted state, available actions, and invocation boundaries so physical capabilities can join tasks verifiably.
了解引芯Explore Nexus天枢负责模型服务与模型包的管理和交付；灵枢、地枢及其他模型提供认知或空间理解。执行权限仍由运行产品校验。TianShu manages and delivers model services and packages. LingShu, DiShu, and other models provide cognitive or spatial understanding; runtime products still check execution permission.
开发者通过供给入口组织、封装与测试能力；织界的职责是帮助需求发现能力，记录调用和贡献关系。Developers organize, package, and test capabilities through the supply entry. Orcha is responsible for discovery and records of calls and contributions.
元域负责保存经验、评估改进与能力版本。成功结果、失败原因和人的纠正，都需要验证后再进入复用。Realm is responsible for experience, improvement evaluation, and capability versions. Successes, failures, and human corrections need validation before reuse.
说明谁提供能力、可在哪些条件下调用、哪些动作需要人的确认。Identify the capability provider, valid calling conditions, and actions that require human confirmation.
返回实际执行状态、可核实的结果和失败原因，让下一步能够判断、恢复或交由人处理。Return execution state, verifiable outcomes, and failure reasons so the next step can assess, recover, or hand over to a person.
从一个明确任务开始，确认现场条件、可调用设备与结果标准，再讨论如何扩大协作。Start with a clear task. Establish field conditions, callable devices, and outcome criteria before expanding collaboration.
