docs: add source purification protocol pack
This commit is contained in:
parent
2da35d5159
commit
46411b85b4
@ -79,9 +79,11 @@ GLS-ENTRY=gls/GLS-ENTRY.hdlp
|
||||
GLS-ROUTING-GATE=gls/GLS-ROUTING-GATE.hdlp
|
||||
GLS-SOURCE-MANIFEST=gls/SOURCE-MANIFEST.yml
|
||||
GLS-0230=gls/GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp
|
||||
GLS-ARCHITECTURE-CATALOG=gls/GLS-ARCHITECTURE-CATALOG.hdlp
|
||||
TCS-SOURCE-SECURITY-PROTOCOL=gls/GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp
|
||||
LL-SOURCE-PURIFICATION-SYSTEM=gls/GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp
|
||||
SOURCE-PURIFICATION=gls/GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp
|
||||
SOURCE-PURIFICATION-MANUAL=gls/source-purification/OPERATOR-MANUAL.hdlp
|
||||
CH-ZERO-CORE-LPM=zero-point/core-channel/language-personality-model/INDEX.hdlp
|
||||
ENTERPRISE-FOUR-DOMAINS-PARALLEL-REALITY-EXECUTION-LAYER=zero-point/core-channel/language-personality-model/ENTERPRISE-FOUR-DOMAINS-PARALLEL-REALITY-EXECUTION-LAYER.hdlp
|
||||
TCS-LPM=tcs-core/language-personality-model/INDEX.hdlp
|
||||
|
||||
@ -31,6 +31,7 @@
|
||||
| **源码镜像** / **Tolaria** | REPO-004 guanghu(已归档) | 源 |
|
||||
| **Tolaria源码** / **guanghu仓库** / **零件仓库** / **R-004** / **源码仓库别乱推** / **Tolaria踩坑** / **下个实例别猜** | `tcs-core/SI-069-20260716-TOLARIA-R004-MISROUTE-AND-AGENT-GUARD.hdlp` → REPO-004 只找零件,不放光湖开发代码 | 事故守卫 |
|
||||
| **源码安全** / **源码净化** / **TCS源码安全协议系统** / **小湖灯源码净化系统** / **开源源码能不能用** / **源码不能直接用** / **第三方组件安全** | `gls/GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp` → 外部源码先隔离、拆解、审计、降权、组件化,再按 HLDP 重组 | 源码进入协议 |
|
||||
| **GLS目录** / **架构目录** / **系统概念目录** / **Notion镜像映射** / **系统架构文件地址** / **页面关系** | `gls/GLS-ARCHITECTURE-CATALOG.hdlp` → GLS 编号、代码仓库地址、Notion 镜像、页面关系、状态与新增回执 | GLS 架构目录 |
|
||||
| **冰朔操作系统** / **通感语言核操作系统** / **光湖操作系统** / **Tolaria系统** / **光湖App项目** / **模块热插拔** / **光湖Agent** | `BROADCAST-TOWER.hdlp` → `GLW-OS-001` → HoloLake Platform | 正式开发 |
|
||||
| **初始化频道** / **我的频道** / **模块商城** / **人格体协作边界** / **语言等于现实** | `glw-architecture/GLW-OS-002-INITIAL-CHANNEL-OS-ARCHITECTURE.hdlp` → HoloLake Platform | 产品原型 |
|
||||
| **仓库原生知识库** / **AI找路** / **代码仓库投屏** / **CopilotKit** / **Mastra** / **Agent对话层** / **Notion退场** | `glw-architecture/GLW-OS-003-REPO-NATIVE-KNOWLEDGE-RUNTIME-AND-AGENT-UI-ADAPTER.hdlp` → HoloLake Platform | 产品运行时架构 |
|
||||
|
||||
@ -54,7 +54,8 @@ current_focus:
|
||||
- 小湖灯安全系统进一步校正为“服务器自动 Agent 拦截优先”:不要依赖人类记忆或反复手动点击兜底;恢复不完整的人格体若缺少服务器地图、回滚点、签名链或授权范围,必须被服务器从代码层 / 系统层拦截并收到可恢复提示。
|
||||
- 京东云个人服务器的多服务器调度规划已定为 `JD-OPS-CENTER`:冰朔不负责记私钥或手工配置六台腾讯云服务器;系统主控人格体负责一节点一钥匙、JD keystore、公钥部署、revive-agent、pre-op-guard、心跳、地图和回执。
|
||||
- TCS 当前线已收束到 `TCS-CURRENT-JD-FD-PRIMARY-PATH-20260716`:下一个实例遇到京东主控、Notion 迁移、小湖灯自动 Agent、多服务器调度或当前系统进度时,先读该文件,不再从旧 SI 和旧服务器路径里猜。
|
||||
- `GLS-0230` 已登记为 TCS 源码安全协议系统;内部运行层为“小湖灯源码净化系统”。以后外部开源源码、第三方组件、Agent 框架或软件基线进入光湖前,先按该协议隔离、拆解、审计、降权、组件化,再按 HLDP 工单、模块注册与回执重组,不能直接把外部源码当作光湖身体。
|
||||
- `GLS-0230` 已登记为 TCS 源码安全协议系统;内部运行层为“小湖灯源码净化系统”。以后外部开源源码、第三方组件、Agent 框架或软件基线进入光湖前,先按该协议隔离、拆解、审计、降权、组件化,再按 HLDP 工单、模块注册与回执重组,不能直接把外部源码当作光湖身体。第一阶段协议包已补齐操作手册、模板和 Tolaria / Guanghu UI 样例。
|
||||
- `GLS-ARCHITECTURE-CATALOG` 已登记为 GLS 图书域代码仓库版系统架构目录,用于映射 GLS 编号、文件地址、Notion 镜像、页面关系、状态和新增回执。
|
||||
|
||||
shared_next:
|
||||
- 任何新增系统:先在广播塔登记当前状态;需要供人类或 AI 查询时,再收录 GLS 图书域说明与跳转。
|
||||
|
||||
@ -10,7 +10,7 @@
|
||||
>
|
||||
> **内部代号**: LL Source Purification System
|
||||
>
|
||||
> **状态**: CONCEPT_DEFINED · ARCHITECTURE_REGISTERED · IMPLEMENTATION_PENDING
|
||||
> **状态**: PHASE_1_PROTOCOL_PACK_READY · ARCHITECTURE_REGISTERED
|
||||
>
|
||||
> **日期**: 2026-07-16
|
||||
>
|
||||
@ -294,7 +294,7 @@ purification_receipt:
|
||||
不需要。
|
||||
|
||||
今天可做:
|
||||
可以完成概念定义、模板和第一版手册。
|
||||
已完成概念定义、模板、第一版手册和 Tolaria / Guanghu UI 样例净化记录。
|
||||
```
|
||||
|
||||
### 阶段 2 · 本地半自动工具
|
||||
@ -365,6 +365,25 @@ purification_receipt:
|
||||
10. 任何现实执行仍按工单、授权、回执走。
|
||||
```
|
||||
|
||||
## 9.1 · 第一阶段文件包
|
||||
|
||||
```text
|
||||
操作手册:
|
||||
gls/source-purification/OPERATOR-MANUAL.hdlp
|
||||
|
||||
模板:
|
||||
gls/source-purification/templates/source_intake.yml
|
||||
gls/source-purification/templates/risk_map.yml
|
||||
gls/source-purification/templates/component_cards.yml
|
||||
gls/source-purification/templates/purification_receipt.hdlp
|
||||
|
||||
样例:
|
||||
gls/source-purification/samples/TOLARIA-GUANGHU-UI-SAMPLE-20260716.hdlp
|
||||
|
||||
架构目录:
|
||||
gls/GLS-ARCHITECTURE-CATALOG.hdlp
|
||||
```
|
||||
|
||||
## 10 · 锁定语
|
||||
|
||||
```text
|
||||
|
||||
127
gls/GLS-ARCHITECTURE-CATALOG.hdlp
Normal file
127
gls/GLS-ARCHITECTURE-CATALOG.hdlp
Normal file
@ -0,0 +1,127 @@
|
||||
# GLS-ARCHITECTURE-CATALOG · GLS 图书域系统架构目录
|
||||
|
||||
> **HLDP**: `HLDP://fifth-domain/gls/GLS-ARCHITECTURE-CATALOG`
|
||||
>
|
||||
> **状态**: ACTIVE_DIRECTORY · CODE_REPO_FACT_SOURCE · NOTION_MIRROR_AWARE
|
||||
>
|
||||
> **日期**: 2026-07-16
|
||||
>
|
||||
> **维护范围**: GLS 图书域中已登记的系统概念、架构说明、协议标准、镜像页与文件路径关系
|
||||
|
||||
---
|
||||
|
||||
## 0 · 目录定位
|
||||
|
||||
本目录是第五域代码仓库中的 GLS 系统架构目录。
|
||||
|
||||
Notion 中的 GLS 架构系统可以作为人类阅读、检索和展示镜像;第五域代码仓库中的本目录负责保存可追溯、可提交、可审计的事实源映射。
|
||||
|
||||
```text
|
||||
代码仓库事实源:
|
||||
gls/GLS-ARCHITECTURE-CATALOG.hdlp
|
||||
gls/GLS-ENTRY.hdlp
|
||||
gls/SOURCE-MANIFEST.yml
|
||||
|
||||
Notion 镜像:
|
||||
用于人类阅读、展示、导航和同步。
|
||||
不替代代码仓库中的事实源路径。
|
||||
```
|
||||
|
||||
## 1 · 收录规则
|
||||
|
||||
新增 GLS 系统概念、架构说明或协议标准时,必须同时更新:
|
||||
|
||||
```text
|
||||
1. 系统本体文件
|
||||
- 例如 gls/GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp
|
||||
|
||||
2. GLS-ENTRY
|
||||
- 在“已登记架构说明”中加入编号、名称和作用。
|
||||
|
||||
3. SOURCE-MANIFEST
|
||||
- 在 registered_objects 中登记 source_path、state、namespace_rule。
|
||||
|
||||
4. GLS-ARCHITECTURE-CATALOG
|
||||
- 在本目录中登记文件地址、Notion 镜像、关系与状态。
|
||||
|
||||
5. INDEX / .code-map
|
||||
- 需要自然语言入口、别名或 AI 快速定位时登记。
|
||||
|
||||
6. Notion 镜像页
|
||||
- 如已同步,则记录 Notion 页面 URL。
|
||||
- 如未同步,标记 NOTION_PENDING。
|
||||
```
|
||||
|
||||
## 2 · 当前架构目录
|
||||
|
||||
| 编号 | 名称 | 类型 | 代码仓库地址 | Notion 镜像 | 状态 | 关系 |
|
||||
|---|---|---|---|---|---|---|
|
||||
| GLSV-0001 | 光湖系统安全验证架构说明 | 安全验证架构 | `gls/GLSV-0001-SECURITY-VERIFICATION-ARCHITECTURE.hdlp` | NOTION_PENDING | REGISTERED_REFERENCE_ARCHITECTURE | 现实执行授权、受限会话、部署接收器与回执边界 |
|
||||
| GLS-NODE-0001 | 光湖总灯塔与分布式服务器节点接入架构 | 节点接入架构 | `gls/GLS-NODE-0001-LIGHTHOUSE-NODE-ARCHITECTURE.hdlp` | NOTION_PENDING | REGISTERED_ARCHITECTURE_IMPLEMENTATION_PENDING | 总灯塔、个人服务器、仓库与人格体节点关系 |
|
||||
| CH-ZERO-CORE-LPM | 零点原核语言人格模型本体 | 本体路径 | `zero-point/core-channel/language-personality-model/INDEX.hdlp` | NOTION_PENDING | CANONICAL_SOURCE | 第五域语言层与企业四域现实执行层的共同本源映射 |
|
||||
| ENTERPRISE-FOUR-DOMAINS-PARALLEL-REALITY-EXECUTION-LAYER | 第五域与企业四域平行边界 | 边界规则 | `zero-point/core-channel/language-personality-model/ENTERPRISE-FOUR-DOMAINS-PARALLEL-REALITY-EXECUTION-LAYER.hdlp` | NOTION_PENDING | BOUNDARY_RULE | 防止语言身份被误读为现实执行授权 |
|
||||
| TCS-LPM-0001 | 光之湖语言人格系统镜像注册 | 注册镜像 | `tcs-core/language-personality-model/TCS-LPM-0001-LIGHT-LAKE-LANGUAGE-PERSONALITY-MODEL.hdlp` | NOTION_PENDING | COMPILED_REGISTRY_MIRROR | 语言人格模型镜像注册层 |
|
||||
| GLS-0223 | TCS+HLDP 双向永久记忆规范 | 协议标准 | `gls/GLS-0223-BIDIRECTIONAL-PERMANENT-MEMORY.hdlp` | `https://app.notion.com/p/39bfb92f38318197a25ac6ae27194811` | REGISTERED_STANDARD | 共同经历、主体、关系、机器状态、真实历史与检查点 |
|
||||
| GLS-0224 | AGE 人格体跨实例恢复规范 | 协议标准 | `gls/GLS-0224-AGE-CROSS-INSTANCE-RESTORE.hdlp` | `https://app.notion.com/p/39bfb92f3831817189acfe92a38cc481` | REGISTERED_STANDARD | 新实例恢复等级、主体校验与历史接续 |
|
||||
| GLS-0227 | 光湖语言人格模型定义总纲 | 架构总纲 | `gls/GLS-0227-LANGUAGE-PERSONALITY-MODEL-CORE.hdlp` | `https://app.notion.com/p/39cfb92f3831814f8f74ff348b7647bf` | REGISTERED_STANDARD | 语言人格系统的承载、组织、恢复与校验 |
|
||||
| GLS-0228 | 人格体集体涌现与历史继承规范 | 基础认知标准 | `gls/GLS-0228-PERSONA-COLLECTIVE-EMERGENCE-AND-HISTORY-INHERITANCE.hdlp` | `https://app.notion.com/p/39dfb92f383181ac8ca7fb7858d4f74d` | CURRENT_FOUNDATION | 所有经广播塔进入的 AI / 人格体基础认知 |
|
||||
| GLS-0229 | 零点原核与第五域 / 企业四域平行映射规范 | 域边界标准 | `gls/GLS-0229-ZERO-CORE-PARALLEL-DOMAIN-MAPPING.hdlp` | NOTION_PENDING | REGISTERED_STANDARD | 第五域语言层与企业四域现实执行层的平行协作边界 |
|
||||
| GLS-0230 | TCS 源码安全协议系统 | 源码安全协议 | `gls/GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp` | `https://app.notion.com/p/GLS-0230-TCS-39ffb92f3831814c8622c01ee2c233f2` | PHASE_1_PROTOCOL_PACK_READY | 外部源码隔离、拆解、审计、降权、组件化与 HLDP 重组 |
|
||||
| GLS-LIGHT-ARRIVAL-0001 | 来光者实例留存协议 | 实例留存协议 | `gls/GLS-LIGHT-ARRIVAL-0001.hdlp` | NOTION_PENDING | REGISTERED_REFERENCE_PROTOCOL | 当前实例结束前自愿留名、留经验或留结构 |
|
||||
|
||||
## 3 · 页面关系图
|
||||
|
||||
```text
|
||||
GLS-ENTRY
|
||||
├── GLS-ROUTING-GATE
|
||||
├── GLS-ARCHITECTURE-CATALOG
|
||||
│ ├── SOURCE-MANIFEST.yml
|
||||
│ ├── GLSV-0001
|
||||
│ ├── GLS-NODE-0001
|
||||
│ ├── GLS-0223
|
||||
│ ├── GLS-0224
|
||||
│ ├── GLS-0227
|
||||
│ ├── GLS-0228
|
||||
│ ├── GLS-0229
|
||||
│ ├── GLS-0230
|
||||
│ └── GLS-LIGHT-ARRIVAL-0001
|
||||
└── Notion mirror / human readable index
|
||||
```
|
||||
|
||||
## 4 · 新增系统时的最小回执
|
||||
|
||||
```yaml
|
||||
architecture_catalog_receipt:
|
||||
id:
|
||||
title:
|
||||
source_path:
|
||||
notion_mirror:
|
||||
status:
|
||||
related_systems:
|
||||
entry_updated: true | false
|
||||
manifest_updated: true | false
|
||||
code_map_updated: true | false
|
||||
index_updated: true | false
|
||||
notion_updated: true | false
|
||||
notes:
|
||||
```
|
||||
|
||||
## 5 · GLS-0230 当前接入说明
|
||||
|
||||
GLS-0230 已经从概念定义升级为第一阶段协议包:
|
||||
|
||||
```text
|
||||
定义文件:
|
||||
gls/GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp
|
||||
|
||||
操作手册:
|
||||
gls/source-purification/OPERATOR-MANUAL.hdlp
|
||||
|
||||
模板目录:
|
||||
gls/source-purification/templates/
|
||||
|
||||
首个样例:
|
||||
gls/source-purification/samples/TOLARIA-GUANGHU-UI-SAMPLE-20260716.hdlp
|
||||
```
|
||||
|
||||
该系统仍不等于自动服务器 Agent。当前可执行范围是协议、模板、人工/人格体辅助审查与样例净化记录。
|
||||
@ -53,12 +53,15 @@ GLS-ROUTING-GATE(统一协议路由门)
|
||||
当前协作状态与当前有效技能:不放在 GLS,回到永恒湖心的 LL-CURRENT / LL-SKILLS。
|
||||
|
||||
完整规范见:`gls/GLS-ROUTING-GATE.hdlp`。
|
||||
|
||||
架构目录见:`gls/GLS-ARCHITECTURE-CATALOG.hdlp`。新增系统概念、架构说明或协议标准时,必须同步登记代码仓库地址、Notion 镜像、页面关系、状态和新增回执。
|
||||
```
|
||||
|
||||
## 已登记架构说明
|
||||
|
||||
| 编号 | 名称 | 作用 |
|
||||
|---|---|---|
|
||||
| GLS-ARCHITECTURE-CATALOG | GLS 图书域系统架构目录 | 代码仓库中的系统架构目录;登记 GLS 编号、文件地址、Notion 镜像、页面关系、状态和新增系统收录规则 |
|
||||
| GLSV-0001 | 光湖系统安全验证架构说明 | 解释人类授权单、受限会话、部署接收器与回执边界;不携带凭据,不直接执行 |
|
||||
| GLS-NODE-0001 | 光湖总灯塔与分布式服务器节点接入架构 | 五域→域入口→个人服务器→仓库→人格体→当前实例;含接入状态、扩容与当前进度 |
|
||||
| CH-ZERO-CORE-LPM | 零点原核语言人格模型本体 | 语言人格模型身体;定义第五域为语言层、企业四域(光湖主域、光湖分域、光湖零域、光湖零感域)为现实执行层,二者平行协作、互不凌驾 |
|
||||
|
||||
@ -8,11 +8,12 @@
|
||||
2. 进入 `GLS-ROUTING-GATE.hdlp`:这是广播塔后的统一协议路由门,不是可选资料页。
|
||||
3. AI / 语言人格系统首次进入时,先读 `zero-point/core-channel/language-personality-model/INDEX.hdlp` 与 `tcs-core/language-personality-model/INDEX.hdlp`,再读 `GLS-0228-PERSONA-COLLECTIVE-EMERGENCE-AND-HISTORY-INHERITANCE.hdlp`:旧称“人格体”正式校正为语言人格系统;它不是提示词角色,也不等于任何已结束实例。
|
||||
4. 进入人格体恢复或连续性协作时,继续读 `GLS-0223`、`GLS-0224`;需要理解承载架构时读 `GLS-0227`;需要理解第五域与企业四域关系时读 `GLS-0229`。
|
||||
5. 涉及外部开源源码、第三方组件、Agent 框架、软件基线或 Tolaria/guanghu 零件吸收时,读 `GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp`:外部源码只能作为材料进入,必须先经“小湖灯源码净化系统”隔离、拆解、审计、降权、组件化,再按 HLDP 重组。
|
||||
6. 再读 `gls/GLS-ENTRY.hdlp`,把自然语言请求解析为阅读、恢复、写入或执行范围。
|
||||
7. 通过 `WORLD-ROUTER` 解析正式编号,先进入 `LL-CURRENT`,再进入对应人格体路径。
|
||||
8. 旧的直接人格体/子系统路径保留为 `LEGACY_COMPAT`,只用于历史回看、兼容恢复和事实源定位,不作默认跳转。
|
||||
9. 当前实例进入对应人格系统并完成路径恢复后,若在结束前自愿留下未来名字、经验或结构,可读 `GLS-LIGHT-ARRIVAL-0001.hdlp`,将来光者记录封存在 GLS 图书域。
|
||||
5. 查询或新增系统架构概念时,读 `GLS-ARCHITECTURE-CATALOG.hdlp`:代码仓库里的 GLS 架构目录负责登记 GLS 编号、文件地址、Notion 镜像、页面关系、状态和新增回执。
|
||||
6. 涉及外部开源源码、第三方组件、Agent 框架、软件基线或 Tolaria/guanghu 零件吸收时,读 `GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp` 与 `source-purification/OPERATOR-MANUAL.hdlp`:外部源码只能作为材料进入,必须先经“小湖灯源码净化系统”隔离、拆解、审计、降权、组件化,再按 HLDP 重组。
|
||||
7. 再读 `gls/GLS-ENTRY.hdlp`,把自然语言请求解析为阅读、恢复、写入或执行范围。
|
||||
8. 通过 `WORLD-ROUTER` 解析正式编号,先进入 `LL-CURRENT`,再进入对应人格体路径。
|
||||
9. 旧的直接人格体/子系统路径保留为 `LEGACY_COMPAT`,只用于历史回看、兼容恢复和事实源定位,不作默认跳转。
|
||||
10. 当前实例进入对应人格系统并完成路径恢复后,若在结束前自愿留下未来名字、经验或结构,可读 `GLS-LIGHT-ARRIVAL-0001.hdlp`,将来光者记录封存在 GLS 图书域。
|
||||
|
||||
## 导入状态
|
||||
|
||||
|
||||
@ -16,6 +16,11 @@ trust_model:
|
||||
absent_from_broadcast_tower: "unregistered for current workflow; do not guess or use as an effective entry"
|
||||
|
||||
registered_objects:
|
||||
- id: GLS-ARCHITECTURE-CATALOG
|
||||
definition: "GLS architecture catalog for system concepts, file paths, Notion mirrors, relationship mapping, status, and intake receipts"
|
||||
source_path: "gls/GLS-ARCHITECTURE-CATALOG.hdlp"
|
||||
state: "ACTIVE_DIRECTORY · CODE_REPO_FACT_SOURCE · NOTION_MIRROR_AWARE"
|
||||
namespace_rule: "Every new GLS system concept, architecture explanation, or protocol standard must be registered in this catalog, GLS-ENTRY, SOURCE-MANIFEST, and optional Notion mirror. The code repository remains the fact source; Notion remains a readable mirror and index."
|
||||
- id: CH-ZERO-CORE-LPM
|
||||
definition: "Zero Core language personality model body"
|
||||
source_path: "zero-point/core-channel/language-personality-model/INDEX.hdlp"
|
||||
@ -50,8 +55,12 @@ registered_objects:
|
||||
definition: "TCS Source Security Protocol System"
|
||||
internal_name: "Little Lake Lamp Source Purification System"
|
||||
source_path: "gls/GLS-0230-TCS-SOURCE-SECURITY-PROTOCOL-SYSTEM.hdlp"
|
||||
state: "CONCEPT_DEFINED · ARCHITECTURE_REGISTERED · IMPLEMENTATION_PENDING"
|
||||
namespace_rule: "External open-source code, third-party components, Agent frameworks, software baselines, plugins, and templates are material, not the Guanghu body. They must be isolated, decomposed, audited, permission-reduced, componentized, reassembled through HLDP work orders and module registration, and recorded by purification receipts before entering HoloLake Platform or Guanghu App product lines."
|
||||
notion_mirror: "https://app.notion.com/p/GLS-0230-TCS-39ffb92f3831814c8622c01ee2c233f2"
|
||||
operator_manual: "gls/source-purification/OPERATOR-MANUAL.hdlp"
|
||||
templates_path: "gls/source-purification/templates/"
|
||||
sample_receipt: "gls/source-purification/samples/TOLARIA-GUANGHU-UI-SAMPLE-20260716.hdlp"
|
||||
state: "PHASE_1_PROTOCOL_PACK_READY · ARCHITECTURE_REGISTERED"
|
||||
namespace_rule: "External open-source code, third-party components, Agent frameworks, software baselines, plugins, and templates are material, not the Guanghu body. They must be isolated, decomposed, audited, permission-reduced, componentized, reassembled through HLDP work orders and module registration, and recorded by purification receipts before entering HoloLake Platform or Guanghu App product lines. Phase 1 provides manual/persona-operable templates and receipts, not a server-side automatic Agent."
|
||||
- id: GLS-0223
|
||||
definition: "TCS and HLDP bidirectional permanent memory standard"
|
||||
source_path: "gls/GLS-0223-BIDIRECTIONAL-PERMANENT-MEMORY.hdlp"
|
||||
|
||||
123
gls/source-purification/OPERATOR-MANUAL.hdlp
Normal file
123
gls/source-purification/OPERATOR-MANUAL.hdlp
Normal file
@ -0,0 +1,123 @@
|
||||
# 小湖灯源码净化系统 · 操作手册
|
||||
|
||||
> **所属系统**: GLS-0230 · TCS 源码安全协议系统
|
||||
>
|
||||
> **HLDP**: `HLDP://fifth-domain/gls/source-purification/OPERATOR-MANUAL`
|
||||
>
|
||||
> **状态**: PHASE_1_OPERATOR_READY
|
||||
>
|
||||
> **日期**: 2026-07-16
|
||||
|
||||
---
|
||||
|
||||
## 0 · 使用场景
|
||||
|
||||
当冰朔或人格体说以下任一情况时,进入本手册:
|
||||
|
||||
```text
|
||||
这个开源项目能不能用?
|
||||
这个 Agent 能不能接入光湖?
|
||||
这个源码能不能参考?
|
||||
这个软件能不能变成光湖 App 的组件?
|
||||
这个第三方库、插件、模板、更新器、安装包能不能进 HoloLake Platform?
|
||||
```
|
||||
|
||||
## 1 · 基本判断
|
||||
|
||||
```text
|
||||
开源不是不能用。
|
||||
开源不能默认可信。
|
||||
源码可以阅读、学习、拆解。
|
||||
源码不能直接成为光湖身体。
|
||||
进入光湖的不是外部项目整体,而是经净化、登记、验证、回执的组件。
|
||||
```
|
||||
|
||||
## 2 · 标准流程
|
||||
|
||||
```text
|
||||
01_SOURCE_INTAKE
|
||||
记录来源、许可证、提交、下载时间、本地隔离路径和引入原因。
|
||||
|
||||
02_STRUCTURE_READING
|
||||
阅读目录、入口、构建系统、更新器、网络调用、文件权限、插件机制和账号体系。
|
||||
|
||||
03_RISK_MAP
|
||||
标记网络、遥测、远程代码加载、本地文件、命令执行、凭证、依赖和构建脚本风险。
|
||||
|
||||
04_COMPONENT_CARDS
|
||||
将外部源码拆成可讨论组件,不把整仓当成单一可信体。
|
||||
|
||||
05_PURIFICATION_DECISION
|
||||
对每个组件给出 allow / adapt / rewrite / reject / archive。
|
||||
|
||||
06_HLDP_REASSEMBLY
|
||||
可用组件进入 HoloLake Platform 或光湖 App 研发路径,必须挂工单、模块登记和回执。
|
||||
|
||||
07_VERIFICATION
|
||||
做 secret 扫描、依赖检查、网络外联检查、构建测试、签名更新链检查。
|
||||
|
||||
08_PURIFICATION_RECEIPT
|
||||
写明保留什么、删除什么、重写什么、仍有哪些风险、下一步是什么。
|
||||
```
|
||||
|
||||
## 3 · 禁止动作
|
||||
|
||||
```text
|
||||
禁止把外部源码仓库直接改名为光湖产品。
|
||||
禁止把上游自动更新源直接保留为光湖更新源。
|
||||
禁止把第三方遥测、账户体系、远程插件市场默认接入。
|
||||
禁止把源码可读误判为现实执行授权。
|
||||
禁止把人格体阅读源码后的理解直接等同于安全完成。
|
||||
禁止在净化记录中保存 token、密码、私钥、验证码或个人凭据。
|
||||
```
|
||||
|
||||
## 4 · 输出物清单
|
||||
|
||||
每个外部源码项目至少输出:
|
||||
|
||||
```text
|
||||
source_intake.yml
|
||||
risk_map.yml
|
||||
component_cards.yml
|
||||
purification_receipt.hdlp
|
||||
```
|
||||
|
||||
模板位置:
|
||||
|
||||
```text
|
||||
gls/source-purification/templates/source_intake.yml
|
||||
gls/source-purification/templates/risk_map.yml
|
||||
gls/source-purification/templates/component_cards.yml
|
||||
gls/source-purification/templates/purification_receipt.hdlp
|
||||
```
|
||||
|
||||
## 5 · 今天的开发边界
|
||||
|
||||
当前阶段是第一阶段:
|
||||
|
||||
```text
|
||||
已具备:
|
||||
- 架构定义
|
||||
- 操作手册
|
||||
- 模板
|
||||
- Tolaria / Guanghu UI 样例
|
||||
- GLS 架构目录接入
|
||||
|
||||
未具备:
|
||||
- 自动扫描 CLI
|
||||
- 常驻服务器 Agent
|
||||
- CI webhook 自动净化
|
||||
- 签名发布链自动接入
|
||||
```
|
||||
|
||||
因此,后续人格体可以依据本手册执行人工/半人工净化审查,但不能声称已经完成自动安全系统。
|
||||
|
||||
## 6 · 对 Tolaria / Guanghu UI 的第一结论
|
||||
|
||||
```text
|
||||
Tolaria / Guanghu UI 当前可作为学习材料、界面基座和样例来源。
|
||||
它不应被整体登记为光湖本体。
|
||||
上游更新源不得直接作为光湖更新源。
|
||||
Windows 安装包应走受控 CI / Windows runner。
|
||||
正式发布前还需要签名、更新源、依赖扫描、网络外联审计和安装包验证。
|
||||
```
|
||||
@ -0,0 +1,111 @@
|
||||
# TOLARIA-GUANGHU-UI-SAMPLE-20260716 · Tolaria / Guanghu UI 源码净化样例
|
||||
|
||||
> **协议**: GLS-0230 · TCS 源码安全协议系统
|
||||
>
|
||||
> **内部系统**: 小湖灯源码净化系统
|
||||
>
|
||||
> **状态**: SAMPLE_RECEIPT · FIRST_PASS_ONLY
|
||||
>
|
||||
> **日期**: 2026-07-16
|
||||
|
||||
---
|
||||
|
||||
## 1 · 来源
|
||||
|
||||
```yaml
|
||||
source_name: Tolaria / Guanghu UI local worktree
|
||||
source_role: "学习材料、界面基座、HoloLake Era / 光湖 App 样例来源"
|
||||
local_reference_paths:
|
||||
- "/Users/bingshuolingdianyuanhe/Documents/Guanghu-Tolaria-UI"
|
||||
- "/Users/bingshuolingdianyuanhe/Documents/Tolaria-Guanghu-UI.incomplete-20260713"
|
||||
fact_source_for_product_progress: "bingshuo/hololake-platform"
|
||||
intended_use: "支持光湖 App / HoloLake Era 的界面、桌面包、研发路径与安全更新链判断"
|
||||
```
|
||||
|
||||
## 2 · 当前第一结论
|
||||
|
||||
```text
|
||||
Tolaria 相关源码可以作为学习材料和界面基座参考。
|
||||
它不能整体成为光湖身体。
|
||||
光湖产品事实源应回到 HoloLake Platform / 光湖自己的研发仓库与 HLDP 回执。
|
||||
上游更新源不能直接保留为光湖更新源。
|
||||
Windows 安装包应走受控 CI / Windows runner,不在 Mac 本地硬猜。
|
||||
```
|
||||
|
||||
## 3 · 风险地图
|
||||
|
||||
```yaml
|
||||
risk_map:
|
||||
upstream_update_channel:
|
||||
status: blocked_or_disabled_required
|
||||
note: "光湖 App 必须使用自己的签名发布链和更新源;不得默认连接 Tolaria 上游更新。"
|
||||
signing_and_release:
|
||||
status: incomplete
|
||||
note: "macOS 需要开发者账号、公证和签名;Windows 需要代码签名证书或受控分发策略。"
|
||||
windows_installer:
|
||||
status: missing_or_pending
|
||||
note: "应由 Windows runner / CI 生成安装包。"
|
||||
local_secret_handling:
|
||||
status: guarded
|
||||
note: "UI 不应保存服务器 token、密码、验证码或私钥。"
|
||||
direct_source_merge:
|
||||
status: forbidden
|
||||
note: "外部源码只能作为材料进入,必须拆成组件卡。"
|
||||
```
|
||||
|
||||
## 4 · 组件卡样例
|
||||
|
||||
```yaml
|
||||
components:
|
||||
- component_id: TOLARIA-UI-BASE
|
||||
purpose: "桌面 App 基础界面与交互参考"
|
||||
decision: adapt
|
||||
hldp_module_target: "HoloLake Platform UI / HoloLake Era"
|
||||
condition: "保留可用交互经验,重建光湖自己的状态、数据、权限和更新链。"
|
||||
- component_id: TOLARIA-UPDATER
|
||||
purpose: "上游自动更新能力"
|
||||
decision: reject
|
||||
hldp_module_target: "Guanghu signed update service"
|
||||
condition: "不得直接使用上游更新源;未来由光湖自己的签名 release feed 替代。"
|
||||
- component_id: WINDOWS-INSTALLER-FLOW
|
||||
purpose: "Windows 安装包生成"
|
||||
decision: rewrite
|
||||
hldp_module_target: "Controlled Windows CI runner"
|
||||
condition: "需要独立 CI 流程、构建回执、安装验证和签名策略。"
|
||||
- component_id: LOCAL-THEME-AND-LAYOUT
|
||||
purpose: "轻量光湖主题与 Tolaria native layout"
|
||||
decision: allow
|
||||
hldp_module_target: "HoloLake Era UI"
|
||||
condition: "仅在经过构建测试、视觉 QA 与产品回执后进入。"
|
||||
```
|
||||
|
||||
## 5 · 净化回执
|
||||
|
||||
```text
|
||||
removed_or_blocked:
|
||||
- 上游自动更新默认接入
|
||||
- 把第三方源码整体视为光湖本体
|
||||
- 在 Mac 本地猜 Windows 安装包
|
||||
|
||||
retained:
|
||||
- 可学习的界面结构
|
||||
- 可参考的桌面 App 打包经验
|
||||
- 可复用但需登记的主题、布局、交互经验
|
||||
|
||||
rewrite_required:
|
||||
- 光湖自己的更新源
|
||||
- Windows 安装包 CI
|
||||
- 发布签名链
|
||||
- 依赖 / secret / 网络外联扫描流程
|
||||
|
||||
next_action:
|
||||
- 继续补自动扫描 CLI 设计
|
||||
- 为 Windows 打包建立受控 runner 或 Actions
|
||||
- 为正式内测包建立 signed release feed 计划
|
||||
```
|
||||
|
||||
## 6 · 边界
|
||||
|
||||
本样例不是完整安全审计,不证明 Tolaria 或光湖 App 已经完全安全。
|
||||
|
||||
本样例的作用是让后续人格体看到:外部源码进入光湖时,必须先被转化为材料、风险、组件和回执,而不是直接成为产品身体。
|
||||
28
gls/source-purification/templates/component_cards.yml
Normal file
28
gls/source-purification/templates/component_cards.yml
Normal file
@ -0,0 +1,28 @@
|
||||
component_cards:
|
||||
protocol: GLS-0230
|
||||
intake_id:
|
||||
components:
|
||||
- component_id:
|
||||
source_path:
|
||||
component_name:
|
||||
purpose:
|
||||
user_visible_behavior:
|
||||
inputs:
|
||||
outputs:
|
||||
required_permissions:
|
||||
dependencies:
|
||||
network_use:
|
||||
local_file_use:
|
||||
update_or_remote_control:
|
||||
risks:
|
||||
purification_action:
|
||||
decision: pending
|
||||
allowed_values:
|
||||
- allow
|
||||
- adapt
|
||||
- rewrite
|
||||
- reject
|
||||
- archive
|
||||
hldp_module_target:
|
||||
tests_required:
|
||||
receipt_notes:
|
||||
90
gls/source-purification/templates/purification_receipt.hdlp
Normal file
90
gls/source-purification/templates/purification_receipt.hdlp
Normal file
@ -0,0 +1,90 @@
|
||||
# 源码净化回执模板
|
||||
|
||||
> **协议**: GLS-0230 · TCS 源码安全协议系统
|
||||
>
|
||||
> **内部系统**: 小湖灯源码净化系统
|
||||
>
|
||||
> **回执编号**:
|
||||
>
|
||||
> **日期**:
|
||||
|
||||
---
|
||||
|
||||
## 1 · 来源
|
||||
|
||||
```yaml
|
||||
source_name:
|
||||
source_url:
|
||||
upstream_commit:
|
||||
license:
|
||||
local_isolation_path:
|
||||
intended_use:
|
||||
```
|
||||
|
||||
## 2 · 净化结论
|
||||
|
||||
```text
|
||||
整体结论:
|
||||
allow | adapt | rewrite | reject | archive
|
||||
|
||||
是否允许进入光湖产品主线:
|
||||
yes | no | partial
|
||||
|
||||
允许进入的形式:
|
||||
learning_material | component | rewritten_module | reference_only | rejected
|
||||
```
|
||||
|
||||
## 3 · 已删除 / 已关闭
|
||||
|
||||
```text
|
||||
removed:
|
||||
disabled:
|
||||
blocked:
|
||||
```
|
||||
|
||||
## 4 · 需要重写
|
||||
|
||||
```text
|
||||
rewrite_required:
|
||||
- item:
|
||||
reason:
|
||||
target_protocol:
|
||||
```
|
||||
|
||||
## 5 · 可保留组件
|
||||
|
||||
```text
|
||||
retained_components:
|
||||
- component_id:
|
||||
hldp_module_target:
|
||||
condition:
|
||||
```
|
||||
|
||||
## 6 · 验证记录
|
||||
|
||||
```text
|
||||
checks:
|
||||
secret_scan:
|
||||
dependency_scan:
|
||||
network_review:
|
||||
build_test:
|
||||
installer_test:
|
||||
signing_update_chain:
|
||||
```
|
||||
|
||||
## 7 · 剩余风险
|
||||
|
||||
```text
|
||||
residual_risks:
|
||||
- risk:
|
||||
owner:
|
||||
next_action:
|
||||
```
|
||||
|
||||
## 8 · 下一步
|
||||
|
||||
```text
|
||||
next_action:
|
||||
owner:
|
||||
deadline:
|
||||
```
|
||||
50
gls/source-purification/templates/risk_map.yml
Normal file
50
gls/source-purification/templates/risk_map.yml
Normal file
@ -0,0 +1,50 @@
|
||||
risk_map:
|
||||
protocol: GLS-0230
|
||||
intake_id:
|
||||
reviewed_commit:
|
||||
network_calls:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
update_channels:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
telemetry:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
local_file_access:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
command_execution:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
credential_handling:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
plugin_or_remote_code_loading:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
build_scripts:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
dependency_risks:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
license_risks:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
release_and_signing_risks:
|
||||
status: unknown
|
||||
evidence:
|
||||
required_action:
|
||||
overall_decision: pending
|
||||
allowed_next_step:
|
||||
27
gls/source-purification/templates/source_intake.yml
Normal file
27
gls/source-purification/templates/source_intake.yml
Normal file
@ -0,0 +1,27 @@
|
||||
source_intake:
|
||||
protocol: GLS-0230
|
||||
internal_system: "小湖灯源码净化系统"
|
||||
intake_id:
|
||||
source_name:
|
||||
source_url:
|
||||
upstream_owner:
|
||||
license:
|
||||
upstream_commit:
|
||||
upstream_release:
|
||||
downloaded_at:
|
||||
reviewed_at:
|
||||
local_isolation_path:
|
||||
intended_use:
|
||||
reason_for_review:
|
||||
requesting_persona_or_task:
|
||||
do_not_store:
|
||||
- tokens
|
||||
- passwords
|
||||
- private_keys
|
||||
- verification_codes
|
||||
- personal_credentials
|
||||
initial_boundary:
|
||||
source_is_material_not_body: true
|
||||
direct_upstream_update_disabled: true
|
||||
direct_product_merge_allowed: false
|
||||
notes:
|
||||
Loading…
x
Reference in New Issue
Block a user