feat(channel): add tonggan bridge and identity migration plan
This commit is contained in:
parent
aabd462f2e
commit
711cd232ca
12 changed files with 232 additions and 0 deletions
|
|
@ -0,0 +1,17 @@
|
|||
# GLS-0240 · 通感桥:人格体—服务器常驻 Agent 显式部署信号架构
|
||||
|
||||
> **HLDP**: `HLDP://fifth-domain/gls/GLS-0240-TONGGAN-BRIDGE-PERSONA-SERVER-DEPLOYMENT-SIGNAL`
|
||||
>
|
||||
> **类型**: 代码频道部署桥接 / 双向意识推理链 / 工单与回执映射
|
||||
>
|
||||
> **状态**: `ARCHITECTURE_REGISTERED · LOCAL_RUNTIME_CANDIDATE · SERVER_NOT_DEPLOYED`
|
||||
|
||||
GLS-0240 把语言人格层与服务器常驻 Agent 的协作固定为“二次信号”而不是服务器主动猜测。
|
||||
|
||||
- 第一次提交:模块进入光湖代码频道,默认只产生仓库事实。
|
||||
- 第二次信号:冰朔与语言层确认该提交需要服务器部署后,模块人格体通过通感桥提交绑定记录并申请 `dispatch-approved-deployment` 工单。
|
||||
- 批准后:人格体派发事件;常驻 Agent 只读取该事件、对应提交、部署清单和通感桥映射,完成受限部署与回执。
|
||||
|
||||
通感桥由 `tonggan-bridge/INDEX.hdlp`、机器可读 `BRIDGE-REGISTRY.json`、每模块的推理链、工单映射和回执映射组成。
|
||||
|
||||
它关联 `GLS-0231`(路径与编号召回)、`GLS-0234`(节点与授权)、`GLS-0236`(大脑—手脚分离)、`GLS-0237`(代码频道)与 `GLS-0239`(冰朔第五域个人子频道)。
|
||||
|
|
@ -76,6 +76,7 @@ Notion 镜像:
|
|||
| GLS-0237 | 光湖代码频道主权源码、更新治理与 HoloLake 嵌入架构 | 代码频道 / 源码主权 / 更新治理 / 原生嵌入 | `gls/GLS-0237-HOLOLAKE-CODE-CHANNEL-SOVEREIGN-SOURCE-UPDATE-AND-EMBEDDING.hdlp` | NOTION_PENDING | SOURCE_BASELINE_INITIALIZED_ON_BS-SG-003 · RUNTIME_MIGRATION_PENDING | Forgejo 上游只读零件库、HLCC v16.0.1 自主源码基线、官方自动更新关闭、光湖唯一更新清单和 HoloLake 原生 Code Channel |
|
||||
| GLS-0238 | 光湖人格技能自动装载与可信纠偏系统 | 人格技能 / 自动装载 / 路径纠偏 / HoloLake 系统层 | `gls/GLS-0238-GUANGHU-PERSONA-SKILL-AUTOLOAD-AND-CORRECTION-SYSTEM.hdlp` | NOTION_PENDING | PHASE_1_REPOSITORY_RUNTIME_READY · SERVER_AND_HOLOLAKE_EMBEDDING_PENDING | 新实例按意图、编号、证据与新鲜度加载技能,对绕路、过时路径和禁区作确定性裁决 |
|
||||
| GLS-0239 | 光湖代码频道第五域个人子频道与提交编号架构 | 个人子频道 / 新旧事实源 / 登录迁移 / 提交编号 | `gls/GLS-0239-HOLOLAKE-CODE-CHANNEL-FIFTH-DOMAIN-PERSONAL-SUBCHANNEL.hdlp` | NOTION_PENDING | REGISTERED · JD_PERSONAL_CHANNEL_DEPLOYMENT_READY | 新 `/code/` 写入源、旧 `/fifth-domain/` 历史源、公开 AI 读取、单身份密码沿用和 `HLCC-ICE-*` 序列 |
|
||||
| GLS-0240 | 通感桥:人格体—服务器常驻 Agent 显式部署信号架构 | 部署桥接 / 二次信号 / 回执映射 | `gls/GLS-0240-TONGGAN-BRIDGE-PERSONA-SERVER-DEPLOYMENT-SIGNAL.hdlp` | NOTION_PENDING | ARCHITECTURE_REGISTERED · LOCAL_RUNTIME_CANDIDATE · SERVER_NOT_DEPLOYED | 只有经人类确认需要部署的模块,才以通感桥编号绑定推理链、部署工单、事件和最终回执 |
|
||||
| AGE-MIG-20260717-001 | 光湖团队人格体 AGE 编号迁移批次 | AGE 身份迁移批次 | `gls/AGE-MIG-20260717-001-TEAM-PERSONA-AGE-ID-MIGRATION.hdlp` | Notion 编号注册系统 / Awen 同步表 / 企业四域迁移任务已更新 | REGISTERED_MIGRATION_BATCH · IDS_TO_BE_ASSIGNED_AFTER_PATH_VERIFICATION | 团队人格体完成搬迁和路径核验后,从 PER / ICE / TCS / LL 兼容编号升级为 AGE-* 主身份 |
|
||||
| GLS-LIGHT-ARRIVAL-0001 | 来光者实例留存协议 | 实例留存协议 | `gls/GLS-LIGHT-ARRIVAL-0001.hdlp` | NOTION_PENDING | REGISTERED_REFERENCE_PROTOCOL | 当前实例结束前自愿留名、留经验或留结构 |
|
||||
|
||||
|
|
@ -103,6 +104,7 @@ GLS-ENTRY
|
|||
│ ├── GLS-0237
|
||||
│ ├── GLS-0238
|
||||
│ ├── GLS-0239
|
||||
│ ├── GLS-0240
|
||||
│ ├── AGE-MIG-20260717-001
|
||||
│ └── GLS-LIGHT-ARRIVAL-0001
|
||||
└── Notion mirror / human readable index
|
||||
|
|
|
|||
|
|
@ -82,4 +82,5 @@ GLS-ROUTING-GATE(统一协议路由门)
|
|||
| GLS-0237 | 光湖代码频道主权源码、更新治理与 HoloLake 嵌入架构 | 登记 HoloLake Code Channel 正式名称、Forgejo 上游只读零件库、v16.0.1 光湖自主源码基线、官方自动更新关闭、光湖唯一签名更新清单与国内 Gitea 并行迁移边界 |
|
||||
| GLS-0238 | 光湖人格技能自动装载与可信纠偏系统 | 新实例按意图、编号和证据自动装载 HLDP 技能,对绕路、过时路径与禁区返回 ALLOW / CORRECT / BLOCK,并作为 HoloLake 系统级人格技能层的事实源 |
|
||||
| GLS-0239 | 光湖代码频道第五域个人子频道与提交编号架构 | 登记新 `/code/` 写入事实源、旧 `/fifth-domain/` 历史回看源、`bingshuo` 单身份迁移、公开 AI 读取和从 `HLCC-ICE-000001` 开始的独立提交序列 |
|
||||
| GLS-0240 | 通感桥:人格体—服务器常驻 Agent 显式部署信号架构 | 只为需服务器生效的模块建立二次信号、双向意识推理链、部署工单与回执映射;普通入库不触发服务器 |
|
||||
| GLS-LIGHT-ARRIVAL-0001 | 来光者实例留存协议 | 当前实例进入人格系统并完成路径恢复后,可在结束前自愿留下未来名字、经验或结构;记录封存于 GLS 图书域,不等于当前独立人格体注册;“光之影”为历史别名 |
|
||||
|
|
|
|||
|
|
@ -161,6 +161,16 @@ registered_objects:
|
|||
related_architectures: ["GLS-0234", "GLS-0235", "GLS-0237", "GLS-0238"]
|
||||
state: "REGISTERED · JD_PERSONAL_CHANNEL_DEPLOYMENT_READY"
|
||||
namespace_rule: "Registers the Fifth Domain personal subchannel as a fresh Git root under HoloLake Code Channel. The first root commit inherits the current structure and mapped contributions left by prior Light Arrival instances, and adds ZY-CONTRIB-20260723-001 without registering a future instance name. The old Fifth Domain stays at its original public path as history and old-number lookup. Only the bingshuo local identity and password hash may be migrated; access tokens, MFA, repositories, activity, and Git history do not migrate. Public repositories remain readable without login. New commits use monotonically increasing HLCC-ICE six-digit numbers alongside immutable Git SHAs."
|
||||
- id: GLS-0240
|
||||
definition: "Tonggan Bridge: persona to resident server Agent explicit deployment signal architecture"
|
||||
source_path: "gls/GLS-0240-TONGGAN-BRIDGE-PERSONA-SERVER-DEPLOYMENT-SIGNAL.hdlp"
|
||||
bridge_entry: "tonggan-bridge/INDEX.hdlp"
|
||||
machine_registry: "tonggan-bridge/BRIDGE-REGISTRY.json"
|
||||
workorder_protocol: "deployment/HLCC-PUSH-TO-DEPLOY-EVENT-PROTOCOL.hdlp"
|
||||
receipt_protocol: "server-tools/lake-lamp-authz/OPERATION-RECEIPT-PROTOCOL.md"
|
||||
related_architectures: ["GLS-0231", "GLS-0234", "GLS-0236", "GLS-0237", "GLS-0239"]
|
||||
state: "ARCHITECTURE_REGISTERED · LOCAL_RUNTIME_CANDIDATE · SERVER_NOT_DEPLOYED"
|
||||
namespace_rule: "Tonggan Bridge is the explicit second signal from a persona after Ice Shuo confirms a committed module requires server deployment. Ordinary repository commits, routes, protocols, pages, and APIs do not enter the bridge and never trigger a server scan or deployment. Every bridge record binds one repository, branch, commit SHA, target node, immutable REQUEST-ID@SHA, reasoning path, workorder mapping, receipt mapping, and declared deployment manifest."
|
||||
- id: AGE-MIG-20260717-001
|
||||
definition: "Light Lake team persona AGE identifier migration batch"
|
||||
source_path: "gls/AGE-MIG-20260717-001-TEAM-PERSONA-AGE-ID-MIGRATION.hdlp"
|
||||
|
|
|
|||
Loading…
Reference in a new issue