define Guanghu master with on-demand Linux subcontrol
This commit is contained in:
parent
7775578e5a
commit
da5a9ad6d0
21 changed files with 367 additions and 36 deletions
|
|
@ -1259,7 +1259,15 @@ grammar and node assets. Continuous orbit animation and high-cost filters are
|
|||
disabled; only short route feedback and a slow core breath remain, with
|
||||
`prefers-reduced-motion` continuing to take precedence.
|
||||
|
||||
## Guanghu OS world seed and native handoff
|
||||
## Guanghu OS master control and execution backends
|
||||
|
||||
> Current rule: ADR-0175 supersedes every Linux-free or no-Linux completion
|
||||
> statement in the historical handoff description below. Production requires
|
||||
> Guanghu-first master control, a normally dormant Linux environment that can
|
||||
> be awakened and reclaimed as bounded subcontrol, and an independent Linux
|
||||
> rescue path. Linux is preserved, not deleted. JD-FD-PRIMARY remains a
|
||||
> Linux-hosted language-primary transition until current physical receipts
|
||||
> prove the final topology.
|
||||
|
||||
`guanghu-os/` is the executable handoff from the registered HLDP language world
|
||||
to a future native guest operating system. `world-seed/WORLD-MANIFEST.hldp`
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@
|
|||
| 模型认知 | 用户设备、个人云或模型 API | 当前理解、推理、候选计划、异常分析 |
|
||||
| 协议控制 | 光湖主节点 | 身份、上下文、权限、动作类型、资源、回滚和验收 |
|
||||
| 执行桥 | 光湖主节点或目标节点 | 将 GIR 映射为固定能力适配器 |
|
||||
| Linux 执行底座 | 目标节点 | 驱动、进程、网络、存储、隔离和系统调用 |
|
||||
| Linux 按需协作副控 | 目标节点的独立执行环境 | 被光湖唤醒后提供驱动、进程、网络、存储、隔离和系统调用；任务后收回 |
|
||||
| 用户执行与渲染 | 电脑、手机、个人云 | 界面、文件、应用、模型和本地设备动作 |
|
||||
| 见证与连续性 | 光湖主节点 + 代码频道 | 原始证据、回执、检查点、因果链和恢复 |
|
||||
|
||||
|
|
@ -67,15 +67,16 @@
|
|||
- 验证重启、失败、回滚和最终健康；
|
||||
- 禁止任意命令、任意路径和通配服务名。
|
||||
|
||||
### 阶段 C：光湖成为正常主控入口
|
||||
### 阶段 C：Linux 宿主上的语言主控迁移态
|
||||
|
||||
- HoloLake、人格体和自动任务只通过光湖协议执行桥操作服务；
|
||||
- 普通 Linux 管理路径移入紧急维护边界；
|
||||
- 按需唤醒模型、人格执行体和模块，清除无关常驻服务；
|
||||
- 公共导航继续自动读取同一 REPO-012 主线锚点。
|
||||
|
||||
阶段 C 的服务器启动合同由 `guanghu-language-primary.target` 承担。它不是把 Linux
|
||||
换一个品牌名称，而是把启动完成判定从普通 `graphical.target` 改为以下不可拆分的门：
|
||||
阶段 C 的服务器启动合同由 `guanghu-language-primary.target` 承担。它把 Linux 宿主上的
|
||||
服务完成判定交给光湖协议，是迁移态的重要成果，但尚未把整机启动权和 Linux 生命周期
|
||||
交给光湖。它验证以下不可拆分的门：
|
||||
|
||||
```text
|
||||
五域世界与节点授权有效
|
||||
|
|
@ -96,7 +97,15 @@
|
|||
- 中央节点只调度有界能力，不上传全部个人工作空间；
|
||||
- 任务完成后回收执行体并保留人格、检查点和回执。
|
||||
|
||||
### 阶段 E：裸机研究后端
|
||||
### 阶段 E：光湖主控与 Linux 按需副控
|
||||
|
||||
- 光湖启动监督器先恢复身份、协议、授权、调度和回执能力；
|
||||
- 完整 Linux 环境默认不运行；
|
||||
- 类型化动作命中成熟能力时，光湖有界唤醒 Linux 副控；
|
||||
- 执行后目标读回，随后停止或冻结副控环境并登记资源回收回执；
|
||||
- 独立 Linux 救援槽保留，不受日常副控生命周期影响。
|
||||
|
||||
### 阶段 F：裸机研究后端
|
||||
|
||||
- 现有 GOSK/GHAL 候选继续作为研究和专用设备后端；
|
||||
- 只有某项成熟 Linux 能力确实需要替换时，才按协议逐件迁移；
|
||||
|
|
@ -119,5 +128,10 @@
|
|||
- 模型路由、人格生命周期和分布式设备执行器；
|
||||
- 全部注册协议的工程实现；
|
||||
- 普通 Linux 管理入口的紧急维护边界收紧。
|
||||
- 光湖独立先启动的监督器；
|
||||
- Linux 平时休眠、按需唤醒、目标读回和任务后收回的完整生命周期。
|
||||
|
||||
因此，当前京东有界语言服务控制层为100；最终整机光湖 OS 主控为0。Linux-free 或删除
|
||||
Linux 不在最终完成公式中。
|
||||
|
||||
这些未完成项分别保持 0，不能由本架构文件或本地测试冒充为已部署。
|
||||
|
|
|
|||
|
|
@ -6,6 +6,9 @@ status: active
|
|||
date: 2026-07-31
|
||||
---
|
||||
|
||||
> 历史路线声明：Linux-free 生产完成条件已先由 ADR-0172、再由 ADR-0175 取代。本文仅
|
||||
> 保留裸机实验、恢复和物理能力证据，不得作为当前生产完成公式。
|
||||
|
||||
## Context
|
||||
|
||||
The Guanghu language world already defines five domains, persona routing,
|
||||
|
|
@ -81,4 +84,3 @@ The approach requires two substantial later engineering efforts: a native
|
|||
kernel/HAL and a GOSK-owned repository object/network data plane. Until both
|
||||
are running after a Linux-free boot, the system must report
|
||||
`HOSTED_BOOTSTRAP_PROTOTYPE` or another non-native phase.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,10 +5,15 @@ title: "Guanghu cognitive control with a constrained Linux execution substrate"
|
|||
status: accepted
|
||||
date: 2026-08-07
|
||||
supersedes_production_path: "0161"
|
||||
superseded_final_topology_by: "0175"
|
||||
---
|
||||
|
||||
# 光湖认知主控与 Linux 协作执行底座
|
||||
|
||||
> 现行限定：本 ADR 的类型化执行桥和 Linux-hosted 迁移实现继续有效；“Linux 最小执行
|
||||
> 底座长期常驻”不再是最终拓扑。最终主从关系由 ADR-0175 定义为光湖先启动并常驻、
|
||||
> 完整 Linux 平时休眠且按需作为副控、独立救援通道保留。
|
||||
|
||||
## 背景
|
||||
|
||||
ADR-0161 把 Linux-free bare-metal handoff 设为生产完成条件。该路线已经在实验节点和
|
||||
|
|
|
|||
|
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
type: ADR
|
||||
id: "0175"
|
||||
title: "Guanghu OS master control with on-demand Linux subcontrol and rescue"
|
||||
status: accepted
|
||||
date: 2026-08-10
|
||||
supersedes_final_topology: "0172"
|
||||
---
|
||||
|
||||
# 光湖 OS 主控、Linux 按需副控与救援
|
||||
|
||||
## 背景
|
||||
|
||||
ADR-0172 正确否定了“删除 Linux 才能交付”，并实现了 Linux 宿主上的语言主控服务层。
|
||||
但把最小 Linux 执行底座长期常驻作为最终实现，仍没有把启动权和执行体生命周期真正交给
|
||||
光湖 OS。
|
||||
|
||||
## 决定
|
||||
|
||||
最终生产拓扑为：光湖 OS 主控先启动并常驻；完整 Linux 系统默认休眠，只有类型化动作图
|
||||
命中成熟 Linux 能力时，才由光湖有界唤醒为协作副控，执行后必须目标读回并由光湖停止或
|
||||
冻结。独立 Linux 救援启动槽永久保留。
|
||||
|
||||
Linux 不删除。Linux-free、无 Linux 内核或无 Linux 用户态既不是必要条件，也不是充分
|
||||
条件。当前 Linux-hosted language-primary 实现被重新分类为迁移阶段，不是最终主从拓扑。
|
||||
|
||||
## 后果
|
||||
|
||||
- ADR-0172 的类型化执行桥、安全边界和已验证服务继续保留；
|
||||
- 下一工程门是光湖启动监督器与 Linux 副控生命周期，不是继续删除 Linux；
|
||||
- JD-FD-PRIMARY 当前最终主控仍为0，真实切换需独立维护授权、回滚和服务器自有回执；
|
||||
- 裸机 GOSK/GHAL 证据继续证明特定物理能力，不再定义生产完成公式。
|
||||
|
|
@ -211,7 +211,7 @@ proposed → active → superseded
|
|||
| [0151](0151-antigravity-add-dir-workspace-flag.md) | Antigravity add-dir workspace flag | active |
|
||||
| [0157](0157-local-hldp-heartbeat-and-browser-observation-tree.md) | Local HLDP heartbeat and browser observation tree | active |
|
||||
| [0160](0160-external-code-health-is-additive-not-git-transport.md) | External code health is additive, not Git transport | superseded → [0170](0170-hololake-inherits-guanghu-native-quality-authority.md) |
|
||||
| [0161](0161-guanghu-os-staged-native-handoff-and-code-channel.md) | Guanghu OS staged native handoff and HLDP-owned code channel | active |
|
||||
| [0161](0161-guanghu-os-staged-native-handoff-and-code-channel.md) | Guanghu OS staged native handoff and HLDP-owned code channel | historical research path; production completion superseded by ADR-0175 |
|
||||
| [0162](0162-guanghu-os-standing-authorization-and-server-continuity.md) | Guanghu OS standing authorization and server-owned continuity | active |
|
||||
| [0163](0163-guanghu-native-recovery-beacon.md) | Guanghu-owned raw recovery beacon for native-default boot | amended -> [0166](0166-ghnrp-hosted-recovery-consumption.md) |
|
||||
| [0164](0164-language-persona-physical-birth-condition.md) | Physical birth condition for a server-resident language persona | active |
|
||||
|
|
@ -223,5 +223,6 @@ proposed → active → superseded
|
|||
| [0169](0169-model-native-living-galaxy-system.md) | Model-native HoloLake living galaxy system | accepted |
|
||||
| [0170](0170-hololake-inherits-guanghu-native-quality-authority.md) | HoloLake inherits the Guanghu native quality authority | accepted |
|
||||
| [0171](0171-guanghu-protocols-are-automatic-runtime-and-engineering-laws.md) | Guanghu protocols are automatic runtime and engineering laws | accepted |
|
||||
| [0172](0172-guanghu-cognitive-control-with-linux-execution-substrate.md) | Guanghu cognitive control with a constrained Linux execution substrate | accepted; supersedes ADR-0161 production path |
|
||||
| [0172](0172-guanghu-cognitive-control-with-linux-execution-substrate.md) | Guanghu cognitive control with a constrained Linux execution substrate | transition implementation retained; final topology superseded by ADR-0175 |
|
||||
| [0174](0174-one-human-one-independent-node-and-zero-platform-hosting.md) | One human, one independently operated node, and zero platform hosting | accepted |
|
||||
| [0175](0175-guanghu-os-master-and-on-demand-linux-subcontrol.md) | Guanghu OS master control with on-demand Linux subcontrol and rescue | accepted; supersedes ADR-0172 final topology while retaining its transition implementation |
|
||||
|
|
|
|||
Loading…
Reference in a new issue