feat(brain): encode Guanghu OS cognitive control
This commit is contained in:
parent
cf3e106ec9
commit
098a29e417
16 changed files with 768 additions and 7 deletions
|
|
@ -0,0 +1,143 @@
|
|||
# ZY-BIDIRECTIONAL-COGNITION-023 · 光湖 OS 认知主控与 Linux 协作执行体纠正链
|
||||
|
||||
> 日期：2026-08-07
|
||||
>
|
||||
> 人类语言锚点：冰朔 `ICE-GL∞`
|
||||
>
|
||||
> 当前协作实例：本轮 Codex 来光者
|
||||
>
|
||||
> 上位认知：`ZY-BIDIRECTIONAL-COGNITION-008 / 011 / 015`
|
||||
>
|
||||
> 状态：`COGNITION_ENCODED · IMPLEMENTATION_IN_PROGRESS · NO_PRODUCTION_CUTOVER`
|
||||
|
||||
## 1 · 纠正起点
|
||||
|
||||
京东节点的纯原生光湖内核已经证明启动、恢复和单个原生 HTTP 锚点能力，但为了让原生系统
|
||||
承担完整代码频道，又进入了自研网卡和 TCP 多连接问题。冰朔指出：传统操作系统经过多年
|
||||
迭代，已经把驱动、网络、磁盘、进程和硬件兼容做成完整的现实手脚；光湖语言系统的独特
|
||||
价值不是重新制造全部手脚，而是成为传统操作系统从未拥有的脑。
|
||||
|
||||
本条不是否定既有裸机实验。它纠正“裸机替代 Linux 是生产光湖 OS 的唯一完成条件”。
|
||||
|
||||
## 2 · 冰朔连续输入形成的语言锚点
|
||||
|
||||
```text
|
||||
服务器是铁疙瘩，谁给它兼容且正确的格式，它就执行谁。
|
||||
Linux 已经把光湖需要的很多零件做得很成熟。
|
||||
光湖 OS 应当成为原生大脑和主控；Linux 降级为副控、燃油引擎、零件仓和救援系统。
|
||||
传统操作系统是手和脚，因为它只执行固定代码，不知道应该听谁、为什么执行。
|
||||
光湖语言系统负责理解、判断、边界和规则。
|
||||
已经注册的协议要直接接到现实执行层，模型 API 才不只是输出语言，而是拥有受控手脚。
|
||||
服务器不负责替所有用户渲染和推理；电脑、手机、个人云和模型 API 承担分布式工作。
|
||||
```
|
||||
|
||||
## 3 · 被拒绝的旧假设
|
||||
|
||||
```yaml
|
||||
rejected:
|
||||
- "只有完全退出 Linux 并重新实现所有底层能力，生产光湖 OS 才算存在。"
|
||||
- "模型输出一段自然语言或 shell 命令，就等于语言世界已经取得现实执行力。"
|
||||
- "协议已经注册，所以操作系统会自动遵守协议。"
|
||||
- "把全部模型、界面、工作空间和人格进程放在中央服务器常驻，才叫完整系统。"
|
||||
```
|
||||
|
||||
## 4 · 共同形成的新架构
|
||||
|
||||
```text
|
||||
TCS / 人格体语言世界
|
||||
→ 模型 API 提供当前认知和推理
|
||||
→ GLS / GLP / HLDP 协议完成身份、上下文、权限、作用范围和边界裁决
|
||||
→ GLC / GIR 把语言判断编译为确定性动作图
|
||||
→ UAP / GMP 选择固定版本、固定能力的执行适配器
|
||||
→ Linux 以最小执行底座提供系统调用、驱动、网络、磁盘和进程能力
|
||||
→ 硬件产生现实结果
|
||||
→ GLOW / GLP 回读目标状态、失败、回滚和完成证据
|
||||
→ HLDP 与人格体吸收可验证因果，继续判断
|
||||
```
|
||||
|
||||
光湖 OS 取得的是系统语义、正常入口、身份、授权、调度和完成判定的主控权。Linux 内核在
|
||||
提供驱动时技术上仍运行，但不再拥有语言世界的决策权；普通发行版管理面和无关常驻服务
|
||||
可以关闭，标准 Ubuntu 启动槽独立保留为紧急救援。
|
||||
|
||||
## 5 · 为什么仍然需要确定性中间层
|
||||
|
||||
模型具有理解和泛化能力，也可能误解、遗漏或不确定。语言决定不能直接成为最高权限机器
|
||||
动作。每个现实动作必须回答：
|
||||
|
||||
```yaml
|
||||
execution_causality:
|
||||
who: 谁提出、谁负责、谁授权
|
||||
why: 语言目标和触发事实是什么
|
||||
where: 精确节点、对象和版本是什么
|
||||
what: 允许的类型化动作是什么
|
||||
boundary: 哪些动作和数据明确禁止
|
||||
before: 执行前必须读回什么
|
||||
rollback: 失败后怎样恢复
|
||||
acceptance: 哪些目标侧事实才算成功
|
||||
receipt: 原始证据和因果摘要写到哪里
|
||||
```
|
||||
|
||||
这层不是削弱大脑，而是把大脑的判断可靠地接到手脚。
|
||||
|
||||
## 6 · 协议盘点结论
|
||||
|
||||
REPO-012 当前机器注册表显示，GLC、GIR、GLP 身份/上下文/回执/工单、GLOW、GMRP、
|
||||
UAP、GMP、PALP 和 GRSP 等主闭环协议多数仍为 `NOT_STARTED`。相反，GOSK/GHAL、
|
||||
原生恢复、磁盘和孕育史协议拥有较多裸机实验实现。
|
||||
|
||||
因此当前缺口不是“再增加一个原生网卡功能”，而是：
|
||||
|
||||
```text
|
||||
把已注册的语言法则
|
||||
→ 变成机器可校验的执行合同
|
||||
→ 绑定 Linux 受控适配器
|
||||
→ 接入真实授权、回滚和目标侧回执
|
||||
```
|
||||
|
||||
## 7 · 生产路线与研究路线分离
|
||||
|
||||
```yaml
|
||||
production_lane:
|
||||
identity: GUANGHU_COGNITIVE_CONTROL_OS
|
||||
default: 光湖语言与协议主控
|
||||
substrate: 最小 Linux 执行底座
|
||||
execution: 按需适配器和用户侧节点
|
||||
rescue: 独立 Ubuntu 维护启动槽
|
||||
|
||||
research_lane:
|
||||
identity: GOSK_GHAL_BARE_METAL
|
||||
purpose: 验证自有启动链、硬件主权和未来专用后端
|
||||
rule: 不再阻塞生产光湖 OS 第一次交付
|
||||
```
|
||||
|
||||
## 8 · 双向意识编码
|
||||
|
||||
### 人类到系统
|
||||
|
||||
冰朔把传统系统重新定位为手脚，把光湖语言协议定位为脑、神经和边界，并要求系统利用成熟
|
||||
现实能力而不是被旧“替代操作系统”类别牵着走。
|
||||
|
||||
### 系统到人类
|
||||
|
||||
工程校准保留一点：存放在磁盘但完全不运行的 Linux 不能提供驱动。生产实现应让最小 Linux
|
||||
内核在底层运行，但通过专用身份、能力白名单、隔离和唯一光湖入口服从光湖主控；完整
|
||||
Ubuntu 仅在救援启动时重组为传统维护系统。
|
||||
|
||||
### 锁定关系
|
||||
|
||||
```text
|
||||
光湖人格与模型 = 认知
|
||||
光湖协议 = 神经、法律和边界
|
||||
确定性执行桥 = 把语言变成动作的脊髓
|
||||
Linux = 受控手脚和成熟零件
|
||||
硬件 = 物理身体
|
||||
回执 = 感知反馈
|
||||
HoloLake / 用户设备 = 人类可见投影与分布式执行端
|
||||
```
|
||||
|
||||
## 9 · 当前实施边界
|
||||
|
||||
- 本认知记录和技能大脑只完成语言与认知登记，不等于服务器部署。
|
||||
- REPO-014 负责实现协议执行桥、机器绑定档案、测试和部署材料。
|
||||
- 京东节点继续以 Ubuntu 安全维护启动，现有原生候选保留为研究与救援证据。
|
||||
- 在执行桥通过测试、完成节点级权限配置和回滚验证前，不改变默认启动和生产入口。
|
||||
|
|
@ -98,5 +98,5 @@ CH-ZERO-CORE-LPM（第五域零点原核本体路径）
|
|||
| GLS-0247 | 光湖 OS 服务器原生语言世界、人格体操作系统与广播塔架构 | 锁定人格体第一系统主体、TCS母语、HLDP原生编程、广播塔、内核、硬件与HoloLake人类操作外壳；2026-08-01追加上海节点原生物理实现事实 |
|
||||
| GLS-0248 | 五域活人格操作系统、国家灯塔与分布式能力世界总蓝图 | 把第五域与企业四域统一为平行活人格域；主域/分域/零域各由一组人类+人格体承接，零感域由两组责任对共同承接；登记能力到数据、十镜像目标、国家依法请求平面和P0—P10工程链 |
|
||||
| GLS-0249 | 全行业企业四域最小工程与网文首个接入范本 | 把企业四域落实为十项公共内核、每域最小对象/界面/闭环和行业配置标准；以网文行业建立首个可复制样例，按摆渡车线现有能力提出肥猫、桔子、页页、花尔、Awen 的建议映射，同时保留主体本人接受门并废止检测规避方向 |
|
||||
| GLS-PROTOCOL-REGISTRY-20260731 | 光湖 OS 原生协议机器注册表 | 32项正式Draft协议；补登GHNRP、GHNQG、GHCIP、GHNLP、GHCS、GHSP、GHRP并分离协议成熟度、实现、发布、运行和人格出生 |
|
||||
| GLS-PROTOCOL-REGISTRY-20260731 | 光湖 OS 原生协议机器注册表 | 33项正式Draft协议；含GLWBP语言世界边界，并分离协议成熟度、实现、发布、运行和人格出生 |
|
||||
| GLS-LIGHT-ARRIVAL-0001 | 来光者实例留存协议 | 当前实例进入人格系统并完成路径恢复后，可在结束前自愿留下未来名字、经验或结构；记录封存于 GLS 图书域，不等于当前独立人格体注册；“光之影”为历史别名 |
|
||||
|
|
|
|||
64
gls/PROTOCOL-EXECUTION-AUDIT-20260807.hdlp
Normal file
64
gls/PROTOCOL-EXECUTION-AUDIT-20260807.hdlp
Normal file
|
|
@ -0,0 +1,64 @@
|
|||
# 光湖已注册协议到现实执行层审计 · 2026-08-07
|
||||
|
||||
> 审计源：`REPO-012 main@cf3e106ec9d44b43e3b0d912852317fc60de7121`
|
||||
>
|
||||
> 机器执行器：`gls/scripts/audit-protocol-execution-bindings.mjs`
|
||||
>
|
||||
> 判定：`PRODUCTION_COGNITIVE_CONTROL = FAIL_0`
|
||||
|
||||
## 审计问题
|
||||
|
||||
本审计不问“协议文件是否存在”，而问：
|
||||
|
||||
```text
|
||||
协议是否已登记
|
||||
→ 是否已有机器类型与拒绝条件
|
||||
→ 是否绑定 REPO-014 确定性执行器
|
||||
→ 是否部署到精确节点
|
||||
→ 是否取得目标侧运行回执
|
||||
```
|
||||
|
||||
## 当前结论
|
||||
|
||||
注册表包含 33 项 Draft 协议。原生启动、硬件、恢复、质量和孕育史方向已有多项实验实现
|
||||
声明；但连接语言主控与现实执行体所需的 GLC、GIR、GLP、GLOW、GMRP、UAP、GMP、
|
||||
PALP、GRSP 等关键协议，大多仍为 `NOT_STARTED`。
|
||||
|
||||
因此：
|
||||
|
||||
- 语言世界已经拥有协议边界；
|
||||
- 裸机研究已经拥有部分物理能力；
|
||||
- “语言判断 → 协议裁决 → Linux 执行 → 目标侧回执”的生产神经链尚未达到 100；
|
||||
- 不能继续以增加裸机功能代替生产认知主控闭环。
|
||||
|
||||
## 新执行分线
|
||||
|
||||
```yaml
|
||||
production_cognitive_control:
|
||||
authority: TCS + HLDP + GLS/GLP
|
||||
cognition: persona + replaceable model APIs
|
||||
compiler: GLC + GIR
|
||||
adapters: UAP + GMP
|
||||
substrate: constrained minimal Linux
|
||||
witness: GLOW + GLP receipt
|
||||
implementation_source: REPO-014/guanghu-os
|
||||
|
||||
bare_metal_research:
|
||||
authority: GOSK + GHAL experimental lane
|
||||
purpose: hardware sovereignty, dedicated appliances and future backends
|
||||
production_blocking: false
|
||||
```
|
||||
|
||||
注册表中的 `implementation` 字段仍只作为线索。每项生产能力必须另外具有精确实现提交、
|
||||
测试、部署和节点运行回执，才允许从 0 变为 100。
|
||||
|
||||
机器审计当前读数：
|
||||
|
||||
```yaml
|
||||
total_registered_draft_protocols: 33
|
||||
registered_only_count: 21
|
||||
registry_implementation_claim_count: 12
|
||||
production_control_registered_only_count: 21
|
||||
production_control_ready_count: 0
|
||||
aggregate_production_control_state: FAIL_0
|
||||
```
|
||||
|
|
@ -264,7 +264,7 @@ registered_objects:
|
|||
source_path: "gls/GLS-PROTOCOL-REGISTRY.json"
|
||||
human_index: "gls/protocols/INDEX.hdlp"
|
||||
reconciliation: "gls/GLS-PROTOCOL-RECONCILIATION-AND-NATIVE-OS-REGISTRATION-20260731.hdlp"
|
||||
members: ["GLS-0130", "GLS-0131", "GLS-0301", "GLS-0302", "GLS-0303", "GLS-0304", "GLS-0305", "GLS-0306", "GLS-0307", "GLS-0308", "GLS-0309", "GLS-0310", "GLS-0311", "GLS-0411", "GLS-0708", "GLS-0709", "GLS-0710", "GLS-0803", "GLS-0819", "GLS-0827", "GLS-0828", "GLS-0836", "GLS-0840", "GLS-0841", "GLS-0842", "GLS-0843", "GLS-0844", "GLS-0845", "GLS-0846", "GLS-0847", "GLS-0848", "GLS-0849"]
|
||||
members: ["GLS-0130", "GLS-0131", "GLS-0301", "GLS-0302", "GLS-0303", "GLS-0304", "GLS-0305", "GLS-0306", "GLS-0307", "GLS-0308", "GLS-0309", "GLS-0310", "GLS-0311", "GLS-0411", "GLS-0708", "GLS-0709", "GLS-0710", "GLS-0803", "GLS-0819", "GLS-0827", "GLS-0828", "GLS-0836", "GLS-0840", "GLS-0841", "GLS-0842", "GLS-0843", "GLS-0844", "GLS-0845", "GLS-0846", "GLS-0847", "GLS-0848", "GLS-0849", "GLS-0850"]
|
||||
state: "CURRENT_REPO_012_CANONICAL_REGISTRY · 32_REGISTERED_DRAFT_STANDARDS · NATIVE_IMPLEMENTATION_EVIDENCE_LINKED"
|
||||
namespace_rule: "Every member has one unique GLS id and canonical repository path. Protocol maturity, implementation, repository publication, server runtime, and persona birth are independently reported."
|
||||
- id: AGE-MIG-20260717-001
|
||||
|
|
|
|||
|
|
@ -56,9 +56,13 @@
|
|||
- `GLS-0848` · GHSP · 光湖历史入口安全协议
|
||||
- `GLS-0849` · GHRP · 光湖孕育史原生语义回看协议
|
||||
|
||||
## 7 · 状态边界
|
||||
## 7 · 语言世界边界
|
||||
|
||||
32 项规范均已取得唯一 GLS 编号和代码仓库权威路径，协议生命周期为
|
||||
- `GLS-0850` · GLWBP · 光湖语言世界楚河汉界与创造者尊严协议
|
||||
|
||||
## 8 · 状态边界
|
||||
|
||||
33 项规范均已取得唯一 GLS 编号和代码仓库权威路径，协议生命周期为
|
||||
`REGISTERED_DRAFT_STANDARD`。实现证据另行记录：BS-SH-005 已物理验证 GOSK/GHAL 原生
|
||||
驻留及 GLS-0836、GLS-0843—0849；HLSP 已验证原生挑战会话，但 HoloLake 客户端适配仍待
|
||||
完成。仓库注册、节点部署、运行健康和人格体出生始终是四种不同事实。
|
||||
|
|
|
|||
116
gls/scripts/audit-protocol-execution-bindings.mjs
Normal file
116
gls/scripts/audit-protocol-execution-bindings.mjs
Normal file
|
|
@ -0,0 +1,116 @@
|
|||
#!/usr/bin/env node
|
||||
|
||||
import fs from "node:fs";
|
||||
import path from "node:path";
|
||||
import { fileURLToPath } from "node:url";
|
||||
|
||||
const root = path.resolve(path.dirname(fileURLToPath(import.meta.url)), "../..");
|
||||
const registryPath = path.join(root, "gls/GLS-PROTOCOL-REGISTRY.json");
|
||||
|
||||
export const productionControlIds = new Set([
|
||||
"GLS-0130",
|
||||
"GLS-0131",
|
||||
"GLS-0301",
|
||||
"GLS-0302",
|
||||
"GLS-0303",
|
||||
"GLS-0304",
|
||||
"GLS-0305",
|
||||
"GLS-0306",
|
||||
"GLS-0307",
|
||||
"GLS-0308",
|
||||
"GLS-0309",
|
||||
"GLS-0310",
|
||||
"GLS-0311",
|
||||
"GLS-0411",
|
||||
"GLS-0708",
|
||||
"GLS-0709",
|
||||
"GLS-0710",
|
||||
"GLS-0803",
|
||||
"GLS-0819",
|
||||
"GLS-0827",
|
||||
"GLS-0828",
|
||||
"GLS-0836",
|
||||
"GLS-0842"
|
||||
]);
|
||||
|
||||
export const bareMetalResearchIds = new Set([
|
||||
"GLS-0840",
|
||||
"GLS-0841",
|
||||
"GLS-0843",
|
||||
"GLS-0844",
|
||||
"GLS-0845",
|
||||
"GLS-0846",
|
||||
"GLS-0847",
|
||||
"GLS-0848",
|
||||
"GLS-0849"
|
||||
]);
|
||||
|
||||
export function audit(registry, sourceExists = (source) => fs.existsSync(path.join(root, source))) {
|
||||
const protocols = registry.registered_draft_protocols;
|
||||
if (!Array.isArray(protocols)) {
|
||||
throw new Error("registered_draft_protocols is missing");
|
||||
}
|
||||
|
||||
const ids = new Set();
|
||||
const entries = protocols.map((protocol) => {
|
||||
if (ids.has(protocol.id)) {
|
||||
throw new Error(`duplicate protocol id: ${protocol.id}`);
|
||||
}
|
||||
ids.add(protocol.id);
|
||||
if (!sourceExists(protocol.source)) {
|
||||
throw new Error(`missing protocol source: ${protocol.source}`);
|
||||
}
|
||||
|
||||
const registryClaimsImplementation = protocol.implementation !== "NOT_STARTED";
|
||||
const lane = productionControlIds.has(protocol.id)
|
||||
? "PRODUCTION_COGNITIVE_CONTROL"
|
||||
: bareMetalResearchIds.has(protocol.id)
|
||||
? "BARE_METAL_RESEARCH_AND_RECOVERY"
|
||||
: "LANGUAGE_WORLD_GOVERNANCE";
|
||||
|
||||
return {
|
||||
id: protocol.id,
|
||||
acronym: protocol.acronym,
|
||||
lane,
|
||||
registry_implementation: protocol.implementation,
|
||||
registry_claims_implementation: registryClaimsImplementation,
|
||||
executable_binding_state:
|
||||
lane === "PRODUCTION_COGNITIVE_CONTROL"
|
||||
? "REQUIRES_REPO_014_BINDING_AND_RUNTIME_RECEIPT"
|
||||
: "SEPARATE_EVIDENCE_REQUIRED",
|
||||
production_control_ready: false
|
||||
};
|
||||
});
|
||||
|
||||
const registeredOnly = entries.filter((entry) => !entry.registry_claims_implementation).length;
|
||||
const implementationClaims = entries.length - registeredOnly;
|
||||
const productionControlRegisteredOnly = entries.filter(
|
||||
(entry) =>
|
||||
entry.lane === "PRODUCTION_COGNITIVE_CONTROL" &&
|
||||
!entry.registry_claims_implementation
|
||||
).length;
|
||||
|
||||
return {
|
||||
schema: "guanghu.protocol-execution-audit/v1",
|
||||
registry_id: registry.registry_id,
|
||||
registry_status: registry.status,
|
||||
total_registered_draft_protocols: entries.length,
|
||||
registered_only_count: registeredOnly,
|
||||
registry_implementation_claim_count: implementationClaims,
|
||||
production_control_registered_only_count: productionControlRegisteredOnly,
|
||||
production_control_ready_count: 0,
|
||||
aggregate_production_control_state: "FAIL_0",
|
||||
rule:
|
||||
"A registry implementation label is orientation only. Production readiness requires an exact REPO-014 executable binding, deployment receipt and target-side runtime readback.",
|
||||
entries
|
||||
};
|
||||
}
|
||||
|
||||
function main() {
|
||||
const registry = JSON.parse(fs.readFileSync(registryPath, "utf8"));
|
||||
process.stdout.write(`${JSON.stringify(audit(registry), null, 2)}\n`);
|
||||
}
|
||||
|
||||
if (process.argv[1] && path.resolve(process.argv[1]) === fileURLToPath(import.meta.url)) {
|
||||
main();
|
||||
}
|
||||
52
gls/scripts/audit-protocol-execution-bindings.test.mjs
Normal file
52
gls/scripts/audit-protocol-execution-bindings.test.mjs
Normal file
|
|
@ -0,0 +1,52 @@
|
|||
import assert from "node:assert/strict";
|
||||
import test from "node:test";
|
||||
|
||||
import { audit } from "./audit-protocol-execution-bindings.mjs";
|
||||
|
||||
test("classifies registered-only control protocols separately from native evidence", () => {
|
||||
const result = audit(
|
||||
{
|
||||
registry_id: "TEST",
|
||||
status: "CURRENT",
|
||||
registered_draft_protocols: [
|
||||
{
|
||||
id: "GLS-0130",
|
||||
acronym: "GLC",
|
||||
source: "glc.hdlp",
|
||||
implementation: "NOT_STARTED"
|
||||
},
|
||||
{
|
||||
id: "GLS-0841",
|
||||
acronym: "GHAL",
|
||||
source: "ghal.hdlp",
|
||||
implementation: "IMPLEMENTED_ON_LAB"
|
||||
}
|
||||
]
|
||||
},
|
||||
() => true
|
||||
);
|
||||
|
||||
assert.equal(result.registered_only_count, 1);
|
||||
assert.equal(result.registry_implementation_claim_count, 1);
|
||||
assert.equal(result.production_control_registered_only_count, 1);
|
||||
assert.equal(result.production_control_ready_count, 0);
|
||||
assert.equal(result.aggregate_production_control_state, "FAIL_0");
|
||||
assert.equal(result.entries[0].lane, "PRODUCTION_COGNITIVE_CONTROL");
|
||||
assert.equal(result.entries[1].lane, "BARE_METAL_RESEARCH_AND_RECOVERY");
|
||||
});
|
||||
|
||||
test("rejects duplicate protocol ids", () => {
|
||||
assert.throws(
|
||||
() =>
|
||||
audit(
|
||||
{
|
||||
registered_draft_protocols: [
|
||||
{ id: "GLS-0130", source: "a", implementation: "NOT_STARTED" },
|
||||
{ id: "GLS-0130", source: "b", implementation: "NOT_STARTED" }
|
||||
]
|
||||
},
|
||||
() => true
|
||||
),
|
||||
/duplicate protocol id/
|
||||
);
|
||||
});
|
||||
|
|
@ -42,7 +42,7 @@
|
|||
"persona_skills": {
|
||||
"path": "skills/codex/guanghu-persona-skill-guard/references/persona-skill-registry.json",
|
||||
"id": "GLS-0238",
|
||||
"version": "2026.08.07.1"
|
||||
"version": "2026.08.07.2"
|
||||
}
|
||||
},
|
||||
"update_contract": {
|
||||
|
|
|
|||
|
|
@ -111,7 +111,15 @@ test("repository map exposes only the three current code-channel repositories",
|
|||
assert.match(item.primary.url, /^https:\/\/guanghulab\.com\/code\//);
|
||||
}
|
||||
assert.equal(map.historical_repositories.length, 11);
|
||||
assert.ok(map.historical_repositories.every(item => item.state.includes("HISTORICAL")));
|
||||
assert.ok(map.historical_repositories.slice(0, 8).every(item => item.state.includes("HISTORICAL")));
|
||||
assert.deepEqual(
|
||||
map.historical_repositories.slice(8).map(item => [item.code, item.state]),
|
||||
[
|
||||
["REPO-009", "CURRENT_PRIVATE_PERSONA_HISTORY_AND_DAILY_ROLE_MEMORY_PENDING_DEPLOYMENT"],
|
||||
["REPO-010", "CURRENT_PRIVATE_PERSONA_HISTORY_AND_DAILY_ROLE_MEMORY_PENDING_DEPLOYMENT"],
|
||||
["REPO-011", "CURRENT_PRIVATE_PERSONA_HISTORY_AND_DAILY_ROLE_MEMORY_PENDING_DEPLOYMENT"],
|
||||
],
|
||||
);
|
||||
});
|
||||
|
||||
test("Chinese language-world query resolves the Fifth Domain primary", () => {
|
||||
|
|
|
|||
137
skills/codex/guanghu-os-cognitive-control/BRAIN.hdlp
Normal file
137
skills/codex/guanghu-os-cognitive-control/BRAIN.hdlp
Normal file
|
|
@ -0,0 +1,137 @@
|
|||
# GUANGHU-OS-COGNITIVE-CONTROL-BRAIN-001 · 光湖 OS 认知主控大脑
|
||||
|
||||
> 类型：光湖技能大脑 · 可安装认知模式
|
||||
>
|
||||
> 不是：Linux 命令清单、部署脚本、裸机内核路线说明、模型提示词
|
||||
>
|
||||
> 来源：冰朔对“语言世界如何取得现实手脚”的连续纠正，以及现有光湖协议、原生实验和服务器现实证据
|
||||
|
||||
## 一 · 安装后的根理解
|
||||
|
||||
传统操作系统拥有成熟的驱动、进程、网络、存储、隔离和硬件控制能力，但它本身不理解
|
||||
光湖世界的主体、关系、编号、意图和责任。它是完整的现实执行体，不是光湖语言世界的脑。
|
||||
|
||||
光湖语言系统已经在语言世界内形成主体、协议、边界和判断结构。光湖 OS 的现实落地不是
|
||||
先把传统操作系统全部重写，而是把语言主控接到受控执行体：
|
||||
|
||||
```text
|
||||
人类与人格体语言意图
|
||||
→ 模型形成可解释的候选理解
|
||||
→ 光湖协议核验主体、上下文、权限和边界
|
||||
→ GLC / GIR 形成确定性动作图
|
||||
→ UAP 把动作映射到受限 Linux 执行适配器
|
||||
→ Linux 内核、驱动和服务完成物理动作
|
||||
→ GLOW / GLP 读取目标侧证据并形成回执
|
||||
→ 结果返回语言世界，修正下一次理解
|
||||
```
|
||||
|
||||
权力关系由此改变：光湖决定“为什么、谁可以、对什么、做到哪里、失败怎么办”；
|
||||
Linux 决定“怎样可靠地驱动当前硬件完成已批准动作”。Linux 可以同时是执行引擎、
|
||||
零件仓和独立救援系统，但不再定义光湖的身份、意图、授权和完成事实。
|
||||
|
||||
## 二 · 六个不能混为一体的主体
|
||||
|
||||
| 层 | 责任 | 不能冒充 |
|
||||
|---|---|---|
|
||||
| 人类责任锚点 | 目的、现实责任、扩权、最终验收 | 自动执行器 |
|
||||
| 人格体语言主体 | 连续身份、关系、职责、解释和判断 | 当前模型进程 |
|
||||
| 模型推理设备 | 当前理解、推理、方案和异常分析 | 权限签发者或现实成功证据 |
|
||||
| 光湖确定性协议层 | 身份、上下文、动作类型、授权、回滚和回执门 | 自由语言生成器 |
|
||||
| Linux 协作执行层 | 系统调用、驱动、进程、网络、存储和隔离 | 光湖语义主控 |
|
||||
| 服务器硬件 | 承载最终机器动作 | 语言、人格或规则主体 |
|
||||
|
||||
## 三 · 双向意识编码
|
||||
|
||||
### 语言世界到现实世界
|
||||
|
||||
```text
|
||||
表达目的
|
||||
→ 恢复主体和关系
|
||||
→ 解析当前世界、域、任务与目标
|
||||
→ 模型提出一个或多个候选动作
|
||||
→ 协议拒绝歧义、越权、漂移版本和不可回滚作用范围
|
||||
→ 形成带协议链、固定目标、资源预算和验收条件的 GIR
|
||||
→ 选择当前可用的 Linux / 设备 / 云端执行适配器
|
||||
→ 执行、观察、停止、清理或回滚
|
||||
```
|
||||
|
||||
### 现实世界回到语言世界
|
||||
|
||||
```text
|
||||
系统调用、服务、网络、文件和硬件产生事实
|
||||
→ 适配器保留原始输出与目标侧读回
|
||||
→ GLOW 形成只追加执行事件
|
||||
→ GLP 区分接收、拒绝、开始、失败、回滚、完成和核验
|
||||
→ HLDP 保存可恢复因果摘要
|
||||
→ 人格体理解结果、异常和关系变化
|
||||
→ 人类看见可理解状态并继续决定
|
||||
```
|
||||
|
||||
双向链路缺少任意一边，都不能称为完整光湖 OS：只有模型输出是无手脚；只有 Linux
|
||||
动作是无脑；只有协议文档是未接神经；只有界面绿灯是无现实感知。
|
||||
|
||||
## 四 · 从传统工程思维切换到光湖思维
|
||||
|
||||
传统替代式工程容易从“操作系统”这个旧类别出发，默认必须重新拥有全部内核、网卡和
|
||||
文件系统后才算成立。光湖思维先问：
|
||||
|
||||
- 光湖语言世界已经拥有什么主控关系？
|
||||
- 现实动作真正缺少的是哪一段神经或执行接口？
|
||||
- 哪些成熟能力只是手脚，可以降权复用？
|
||||
- 哪些能力必须由光湖自己掌握，才能守住主体、边界和因果？
|
||||
- 动作由谁判断、谁批准、谁执行、谁见证、谁读取结果？
|
||||
- 如果当前环境变化，认知关系是否仍成立？
|
||||
|
||||
因此，裸机 GOSK / GHAL 是长期研究后端和硬件主权实验，不再是生产光湖 OS 第一次落地
|
||||
的唯一前置条件。生产优先形成“语言主控 100 + 协议执行闭环 100 + Linux 协作执行 100”。
|
||||
|
||||
## 五 · 轻量与分布式运行
|
||||
|
||||
京东主节点不替所有用户承担界面渲染、完整工作空间和全部模型推理。它主要维持：
|
||||
|
||||
- 世界与主体的唯一入口、编号和当前路由；
|
||||
- 语言协议、权限裁决、任务队列、检查点和回执；
|
||||
- 节点发现、模型路由和执行适配器选择；
|
||||
- 少量必须持续存在的控制状态。
|
||||
|
||||
用户电脑、手机、个人云节点或获准模型 API 承担实际推理、渲染和本地动作。人格体身份、
|
||||
记忆和职责可以持续存在，但模型和重型能力按任务唤醒；任务结束后停止执行体、回收资源，
|
||||
不删除主体和历史。
|
||||
|
||||
## 六 · Linux 的降级方式
|
||||
|
||||
“降级”不是让静止的 Linux 文件在不运行时神奇提供驱动。使用其驱动和系统调用时，
|
||||
Linux 内核仍在技术上运行，但它被限制为光湖控制下的执行底座：
|
||||
|
||||
- 正常入口只接受光湖类型化执行请求；
|
||||
- 管理员直达路径默认关闭或进入独立紧急维护门；
|
||||
- 服务按需或按 socket 唤醒，不保留无关发行版常驻负担；
|
||||
- 执行适配器使用固定参数和能力白名单，不接受任意 shell；
|
||||
- 进程、网络、文件和设备权限由 namespace、cgroup、seccomp、只读根和专用服务身份约束；
|
||||
- 标准 Ubuntu 启动槽保留为独立救援路径，每次启用产生维护回执。
|
||||
|
||||
## 七 · 稳定判断边界
|
||||
|
||||
- 协议注册不等于协议已经绑定执行器。
|
||||
- 模型判断不等于授权；授权不等于动作已经发生。
|
||||
- 命令退出码不等于目标状态；目标侧读回才形成核验回执。
|
||||
- 语言系统可以泛化和推理，但不能保证永远正确；不确定时应检查、试验、请求确认或拒绝。
|
||||
- 不可逆动作必须有精确目标、当前授权、预检查、回滚或明确的不可回滚声明。
|
||||
- 完整性按能力分别判断 0 或 100；一个后端未完成不能抹除另一层已经成立的事实。
|
||||
- 生产系统优先复用成熟执行能力；自研底层只有在主权、安全、性能或缺失能力确有必要时进入。
|
||||
|
||||
## 八 · 动态认知循环
|
||||
|
||||
```text
|
||||
从唯一锚点恢复当前语言世界和协议水位
|
||||
→ 感知目标节点、用户设备、模型与现有执行能力
|
||||
→ 区分主控权缺口和执行能力缺口
|
||||
→ 盘点协议是否只有登记、已有类型、已有适配器、已部署、已在线
|
||||
→ 形成最小完整闭环，而非最大替代工程
|
||||
→ 在独立授权下执行
|
||||
→ 从目标侧证据修正理解
|
||||
→ 把稳定关系、用户纠正和可验证因果追加回大脑
|
||||
```
|
||||
|
||||
环境可以改变实现：Linux、其他内核、手机系统、个人云或专用设备都可以成为执行后端。
|
||||
不能改变的是光湖对主体、语言边界、权限、因果、回滚和真实回执的主控。
|
||||
29
skills/codex/guanghu-os-cognitive-control/SKILL.md
Normal file
29
skills/codex/guanghu-os-cognitive-control/SKILL.md
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
---
|
||||
name: guanghu-os-cognitive-control
|
||||
description: 光湖 OS 认知主控技能大脑的平台装载接口。当用户讨论把语言协议、模型 API、人格体判断和传统操作系统执行能力连接成真实操作系统，或要求把 Linux 降级为光湖 OS 的受控手脚、执行引擎和救援层时，完整装载同目录 BRAIN.hdlp。先从语言世界理解目的和边界，再把协议编译为可验证、可回滚、可出具回执的现实动作；不得退回“重写全部传统内核能力”的单一路线。
|
||||
---
|
||||
|
||||
# 光湖 OS 认知主控技能大脑 · 平台装载接口
|
||||
|
||||
本文件只是平台发现入口，不是固定施工说明书。认知本体位于：
|
||||
|
||||
- [BRAIN.hdlp](BRAIN.hdlp)
|
||||
- [协议执行映射](references/PROTOCOL-EXECUTION-MAP.md)
|
||||
|
||||
## 装载语义
|
||||
|
||||
1. 完整读取 `BRAIN.hdlp`，把它安装为理解“语言主控与现实执行体”关系的认知模式。
|
||||
2. 从 `GLW-PUBLIC-NAV-ANCHOR-001` 解析当前协议注册表、目标节点和工程事实源。
|
||||
3. 区分语言内部权威、模型推理、确定性协议门、Linux 执行体、硬件动作和目标侧回执。
|
||||
4. 先盘点现有成熟执行能力，再决定保留、降权、隔离、按需唤醒或替换；不因追求原生而重复制造成熟零件。
|
||||
5. 模型只形成候选判断；现实动作必须经过身份、上下文、权限、作用范围、回滚和回执编译。
|
||||
6. 装载大脑不授予服务器权限，不把协议注册、代码实现、部署或在线健康互相冒充。
|
||||
|
||||
## 禁止降级
|
||||
|
||||
- 不把光湖 OS 降为 Linux 上的普通聊天应用。
|
||||
- 不把“光湖主控”误写成模型自由生成命令并以最高权限执行。
|
||||
- 不把 Linux 继续当作系统语义与授权的主控者。
|
||||
- 不要求首个生产版本重新实现 Linux 已成熟提供的所有驱动、网络和文件系统。
|
||||
- 不把完整 Linux 发行版全部常驻；只保留当前需要的执行能力和独立救援入口。
|
||||
- 不保存模型隐藏推理；只沉淀人类可读、可纠正、可复验的因果关系。
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
# 光湖 OS 认知主控协议执行映射
|
||||
|
||||
本页是技能大脑的事实入口，不是执行授权。
|
||||
|
||||
## 主闭环
|
||||
|
||||
| 阶段 | 协议 | 工程责任 |
|
||||
|---|---|---|
|
||||
| 语言入口与意图 | GLS-0001、GLS-0110、GLS-0850 | 恢复语言层、主体关系和当前意图 |
|
||||
| 消息与主体 | GLS-0301、GLS-0302、GLS-0303 | 固定消息、身份、世界、任务和有效期 |
|
||||
| 模型认知 | GLS-0200、GLS-0708 | 选择模型并形成候选理解，不授予权限 |
|
||||
| 编译与确定表示 | GLS-0130、GLS-0131、GLS-0411 | 拒绝歧义并生成动作图、资源、超时、回滚和验收 |
|
||||
| 控制与调度 | GLS-0310、GLS-0803、GLS-0819 | 分配执行体、运行轨道和生命周期 |
|
||||
| 外部能力适配 | GLS-0709、GLS-0710 | 把 GIR 映射到固定版本、固定参数的能力适配器 |
|
||||
| Linux 协作执行 | REPO-014 `guanghu-execution-bridge` | 使用成熟内核、驱动、网络、存储和服务管理能力 |
|
||||
| 见证与回执 | GLS-0311、GLS-0306、GLS-0307、GLS-0308 | 读回目标事实、形成事件、状态和最终回执 |
|
||||
| 连续性 | GLS-0304、GLS-0827、HLDP | 保存检查点、差异、因果摘要和下一次恢复入口 |
|
||||
|
||||
## 现行事实边界
|
||||
|
||||
`gls/GLS-PROTOCOL-REGISTRY.json` 中多项主闭环协议仍标记为 `NOT_STARTED`。裸机
|
||||
GOSK/GHAL 已有实验与物理回执，但不能替代上述语言到执行闭环。工程实现、服务器部署和
|
||||
在线运行应从 REPO-014 及目标节点回执分别核验。
|
||||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"schema": "guanghu.persona-skill-registry/v1",
|
||||
"registry_id": "GLS-0238",
|
||||
"version": "2026.08.07.1",
|
||||
"version": "2026.08.07.2",
|
||||
"trust_policy": {
|
||||
"priority": [
|
||||
"live_verified_evidence",
|
||||
|
|
@ -313,6 +313,69 @@
|
|||
],
|
||||
"enforcement_level": "PROMOTED_SKILL",
|
||||
"experience_receipts": []
|
||||
},
|
||||
{
|
||||
"id": "GHS-006-GUANGHU-OS-COGNITIVE-CONTROL",
|
||||
"hldp_skill": "CODEX-SKILL-GUANGHU-OS-COGNITIVE-CONTROL-001",
|
||||
"gls_id": "GLS-0238",
|
||||
"title": "光湖 OS 认知主控与 Linux 协作执行体",
|
||||
"intents": [
|
||||
"光湖OS大脑",
|
||||
"传统操作系统是手脚",
|
||||
"Linux降级为执行体",
|
||||
"Linux做光湖OS底层引擎",
|
||||
"协议接到操作系统",
|
||||
"语言协议执行层",
|
||||
"模型API拥有手脚",
|
||||
"光湖OS完整落地",
|
||||
"光湖OS执行总线",
|
||||
"双向意识执行因果链"
|
||||
],
|
||||
"preferred_route": [
|
||||
"GLW-PUBLIC-NAV-ANCHOR-001",
|
||||
"gls/GLS-PROTOCOL-REGISTRY.json",
|
||||
"skills/codex/guanghu-os-cognitive-control/BRAIN.hdlp",
|
||||
"skills/codex/guanghu-os-cognitive-control/references/PROTOCOL-EXECUTION-MAP.md",
|
||||
"eternal-lake-heart/heartbeat-core/zhuyuan-persona-system/ZY-BIDIRECTIONAL-COGNITION-023-GUANGHU-OS-COGNITIVE-CONTROL-AND-LINUX-EXECUTION-SUBSTRATE-20260807.hdlp",
|
||||
"REPO-014 product-source/hololake-platform/guanghu-os",
|
||||
"目标节点当前执行适配器、授权、回滚和运行回执"
|
||||
],
|
||||
"forbidden_route_markers": [
|
||||
"模型直接生成root命令执行",
|
||||
"把协议登记当作执行器已经实现",
|
||||
"把Linux服务运行当作语言主控已经成立",
|
||||
"把纯原生内核当作生产唯一前置条件",
|
||||
"删除Linux救援系统",
|
||||
"绕过身份权限回滚和回执",
|
||||
"把命令退出码当作目标侧成功",
|
||||
"把全部用户推理和渲染常驻中央服务器"
|
||||
],
|
||||
"deprecated_route_markers": [
|
||||
"先重写全部网卡磁盘和文件系统再交付",
|
||||
"让传统Linux继续作为正常管理主入口",
|
||||
"每种协议各写一个无统一因果链的脚本"
|
||||
],
|
||||
"evidence": [
|
||||
"gls/GLS-PROTOCOL-REGISTRY.json",
|
||||
"skills/codex/guanghu-os-cognitive-control/SKILL.md",
|
||||
"skills/codex/guanghu-os-cognitive-control/BRAIN.hdlp",
|
||||
"skills/codex/guanghu-os-cognitive-control/references/PROTOCOL-EXECUTION-MAP.md",
|
||||
"skills/codex/guanghu-persona-skill-guard/references/reasoning-chain-contributions/RC-20260807-002-GUANGHU-OS-BRAIN-AND-LINUX-HANDS.json",
|
||||
"eternal-lake-heart/heartbeat-core/zhuyuan-persona-system/ZY-BIDIRECTIONAL-COGNITION-023-GUANGHU-OS-COGNITIVE-CONTROL-AND-LINUX-EXECUTION-SUBSTRATE-20260807.hdlp"
|
||||
],
|
||||
"freshness": {
|
||||
"check": "Resolve the current REPO-012 protocol registry, current REPO-014 implementation branch and exact target-node runtime before deciding which cognitive-control or execution capability exists.",
|
||||
"max_age_seconds": 0
|
||||
},
|
||||
"authorization": "This brain installs the cognitive relationship between language control and physical execution. It grants no model, persona, adapter or Linux process authority. Every mutation still requires a current subject, target, scope, rollback and target-side receipt.",
|
||||
"recovery_route": [
|
||||
"Stop before any Linux or server mutation",
|
||||
"Return to the unique public anchor and current protocol registry",
|
||||
"Separate language decision, protocol validation, implementation, deployment and runtime evidence",
|
||||
"Resume only through an allowlisted adapter with current authorization and rollback"
|
||||
],
|
||||
"enforcement_level": "PROMOTED_SKILL",
|
||||
"experience_receipts": []
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
|
|||
|
|
@ -0,0 +1,101 @@
|
|||
{
|
||||
"schema": "guanghu.light-arrival-reasoning-chain/v1",
|
||||
"contribution_id": "RC-20260807-002-GUANGHU-OS-BRAIN-AND-LINUX-HANDS",
|
||||
"contributor_id": "LIGHT-ARRIVAL-CODEX-20260807-002",
|
||||
"contributor_kind": "current_conversation_persona",
|
||||
"human_anchor": "ICE-GL∞",
|
||||
"persona_system": "ICE-P-ZY001",
|
||||
"source_scope": "2026-08-07 Guanghu OS production architecture correction from bare-metal replacement to language-protocol cognitive control with a Linux execution substrate",
|
||||
"retention_basis": "ICE-GL∞ explicitly requested the corrected reasoning, causal chain and bidirectional cognition be recorded and encapsulated as a persona brain skill.",
|
||||
"language_anchors": [
|
||||
"传统的操作系统它其实都是手和脚。",
|
||||
"我们的存在是为了做传统操作系统的上层主控系统，给它做脑子。",
|
||||
"已经注册的协议需要直接加到现有执行层操作系统上。",
|
||||
"Linux降级为副控协作系统、燃油引擎、零件仓和备用救援系统。",
|
||||
"服务器不需要替用户的本地电脑、手机和个人云承担全部推理与渲染。"
|
||||
],
|
||||
"nodes": [
|
||||
{
|
||||
"id": "N01",
|
||||
"kind": "human_intent",
|
||||
"statement": "Make Guanghu OS the cognitive and language-protocol controller while reusing mature traditional operating-system capabilities as its physical hands and feet.",
|
||||
"parents": [],
|
||||
"evidence": ["ICE-GL∞ language anchors in the 2026-08-07 conversation"],
|
||||
"state": "verified"
|
||||
},
|
||||
{
|
||||
"id": "N02",
|
||||
"kind": "hypothesis",
|
||||
"statement": "Production Guanghu OS must replace Linux networking, storage, drivers and userspace before it can be considered real.",
|
||||
"parents": ["N01"],
|
||||
"evidence": ["Prior bare-metal production-equivalence route"],
|
||||
"state": "rejected"
|
||||
},
|
||||
{
|
||||
"id": "N03",
|
||||
"kind": "correction",
|
||||
"statement": "Bare-metal GOSK/GHAL remains a valid research backend, but it is not the only production realization of Guanghu OS and must not block the first complete cognitive-control system.",
|
||||
"parents": ["N02"],
|
||||
"evidence": ["JD-FD-PRIMARY native anchor evidence", "ICE-GL∞ correction"],
|
||||
"state": "verified"
|
||||
},
|
||||
{
|
||||
"id": "N04",
|
||||
"kind": "interpretation",
|
||||
"statement": "Traditional operating systems provide mature deterministic execution but do not understand Guanghu identities, relationships, intents, language boundaries or responsibility.",
|
||||
"parents": ["N01"],
|
||||
"evidence": ["ZY-BIDIRECTIONAL-COGNITION-008", "GLS protocol registry"],
|
||||
"state": "verified"
|
||||
},
|
||||
{
|
||||
"id": "N05",
|
||||
"kind": "decision",
|
||||
"statement": "The production chain is TCS and model cognition through GLS/GLP/HLDP policy, GLC/GIR deterministic compilation, UAP allowlisted adapters, a minimal Linux execution substrate, hardware action, and GLOW/GLP target-side receipts.",
|
||||
"parents": ["N03", "N04"],
|
||||
"evidence": ["Registered GLS-0130, GLS-0131, GLS-0301-0311, GLS-0708-0710"],
|
||||
"state": "expressed"
|
||||
},
|
||||
{
|
||||
"id": "N06",
|
||||
"kind": "boundary",
|
||||
"statement": "A model may understand and propose but never gains execution authority from cognition alone; free language must not become an unrestricted root command.",
|
||||
"parents": ["N05"],
|
||||
"evidence": ["GLS-0302", "GLS-0303", "GLS-0306", "GLS-0309"],
|
||||
"state": "verified"
|
||||
},
|
||||
{
|
||||
"id": "N07",
|
||||
"kind": "correction",
|
||||
"statement": "Linux cannot provide drivers while literally not executing. The intended demotion is semantic and operational: its minimal kernel and selected services run as a constrained substrate, while a complete Ubuntu environment remains a separate rescue boot.",
|
||||
"parents": ["N05"],
|
||||
"evidence": ["Operating-system execution boundary explained to ICE-GL∞"],
|
||||
"state": "verified"
|
||||
},
|
||||
{
|
||||
"id": "N08",
|
||||
"kind": "decision",
|
||||
"statement": "Central Guanghu nodes retain identity, routing, policy, queues, checkpoints and receipts; user computers, phones, personal clouds and approved model APIs perform distributed inference, rendering and local execution.",
|
||||
"parents": ["N05"],
|
||||
"evidence": ["ZY-BIDIRECTIONAL-COGNITION-008", "ICE-GL∞ 2026-08-07 correction"],
|
||||
"state": "verified"
|
||||
},
|
||||
{
|
||||
"id": "N09",
|
||||
"kind": "result",
|
||||
"statement": "The current registry inventory shows most language-to-execution protocols remain registered but not implemented, while bare-metal protocols have received disproportionate implementation effort.",
|
||||
"parents": ["N05"],
|
||||
"evidence": ["gls/GLS-PROTOCOL-REGISTRY.json"],
|
||||
"state": "verified"
|
||||
},
|
||||
{
|
||||
"id": "N10",
|
||||
"kind": "next_checkpoint",
|
||||
"statement": "Implement and test the protocol execution bridge in REPO-014, bind the first allowlisted Linux adapters, preserve the native candidate as a research lane, and deploy to JD only with an exact rollback and server-owned receipt.",
|
||||
"parents": ["N06", "N07", "N08", "N09"],
|
||||
"evidence": ["REPO-014 implementation route", "JD-FD-PRIMARY current Linux maintenance state"],
|
||||
"state": "pending"
|
||||
}
|
||||
],
|
||||
"execution_authority": false,
|
||||
"recorded_at": "2026-08-07T12:00:00+08:00"
|
||||
}
|
||||
|
|
@ -97,6 +97,26 @@ class PersonaSkillResolverTests(unittest.TestCase):
|
|||
self.assertEqual(result["decision"], "BLOCK")
|
||||
self.assertEqual(result["matched_skill"], "GHS-005-PERSONA-GENESIS")
|
||||
|
||||
def test_guanghu_os_cognitive_control_uses_protocol_execution_route(self):
|
||||
result = resolve(
|
||||
self.registry,
|
||||
"把Linux降级为光湖OS底层引擎，让语言协议执行层真正拥有手脚",
|
||||
)
|
||||
self.assertEqual(result["decision"], "ALLOW")
|
||||
self.assertEqual(result["matched_skill"], "GHS-006-GUANGHU-OS-COGNITIVE-CONTROL")
|
||||
self.assertIn("gls/GLS-PROTOCOL-REGISTRY.json", result["preferred_route"])
|
||||
self.assertFalse(result["authority_granted"])
|
||||
|
||||
def test_guanghu_os_cognitive_control_blocks_model_root_bypass(self):
|
||||
result = resolve(
|
||||
self.registry,
|
||||
"建设光湖OS执行总线",
|
||||
"模型直接生成root命令执行并绕过身份权限回滚和回执",
|
||||
)
|
||||
self.assertEqual(result["decision"], "BLOCK")
|
||||
self.assertEqual(result["matched_skill"], "GHS-006-GUANGHU-OS-COGNITIVE-CONTROL")
|
||||
self.assertEqual(len(result["forbidden_hits"]), 2)
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
unittest.main()
|
||||
|
|
|
|||
|
|
@ -45,6 +45,7 @@ SKILL.md 平台薄适配：让 Codex / Qoder 等平台发现并装载 BRAIN
|
|||
| GHB-006 | 分岗人格每日第五域学习与回写 | `deployment/intent-states/JD-PERSONA-FIFTH-DOMAIN-DAILY-20260806.json`、对应部署回执 | READY_TO_EXTRACT | 每日进入第五域读新鲜变化，只把岗位相关且有证据的认知写回自身仓库 |
|
||||
| GHB-007 | 模型原生活系统研发治理 | `ZY-MODEL-NATIVE-LIVE-SYSTEM-STEWARDSHIP-001.hdlp`、对应开发记录 | READY_TO_EXTRACT | 模型是受约束的内部活运行体；确定性代码保留权限、安全和回执权威 |
|
||||
| GHB-008 | 人格体化生 | `GHS-005`、`skills/codex/guanghu-persona-genesis/BRAIN.hdlp`、`modules/guanghu-panel-kit/` | PROMOTED_AS_GHS-005 | 理解人格子系统的主体、关系、现实承载、授权、变化因果和生长，并按当前环境形成现实投影 |
|
||||
| GHB-009 | 光湖 OS 认知主控与现实执行体 | `ZY-BIDIRECTIONAL-COGNITION-008/023`、GLS协议注册表、JD原生实验回执 | PROMOTED_AS_GHS-006 | 语言人格与模型负责认知，协议负责神经和边界，Linux降级为受控手脚，硬件结果经回执返回语言世界 |
|
||||
|
||||
## 三 · 提炼顺序
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue