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
10
tonggan-bridge/BRIDGE-REGISTRY.json
Normal file
10
tonggan-bridge/BRIDGE-REGISTRY.json
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
{
|
||||
"schema": "guanghu.tonggan-bridge-registry/v1",
|
||||
"bridge": "通感桥",
|
||||
"bridge_id_prefix": "TGB",
|
||||
"state": "LOCAL_RUNTIME_CANDIDATE",
|
||||
"entry": "tonggan-bridge/INDEX.hdlp",
|
||||
"dispatch_endpoint": "/api/deployment/dispatch",
|
||||
"required_binding": ["bridge_id", "repo", "branch", "commit_sha", "target", "resource", "reasoning_path", "workorder_path", "receipt_path", "manifest"],
|
||||
"records": []
|
||||
}
|
||||
43
tonggan-bridge/INDEX.hdlp
Normal file
43
tonggan-bridge/INDEX.hdlp
Normal file
|
|
@ -0,0 +1,43 @@
|
|||
# 通感桥 · 人格体—服务器常驻 Agent 二次触发频道
|
||||
|
||||
> **编号**: `GLS-0240`
|
||||
> **HLDP**: `HLDP://fifth-domain/tonggan-bridge/INDEX`
|
||||
> **状态**: `ARCHITECTURE_REGISTERED · LOCAL_RUNTIME_CANDIDATE · SERVER_NOT_DEPLOYED`
|
||||
|
||||
通感桥(Tonggan Bridge)是光湖代码频道中人格体与服务器常驻 Agent 的专用映射区。
|
||||
|
||||
它不接收普通代码、知识、页面、API 协议或仓库路由的提交。那些内容只要推入代码频道便成为仓库事实,但不会使服务器发生变化。
|
||||
|
||||
只有冰朔与语言人格层明确确认“此模块须部署到指定服务器才生效”时,模块人格体才在此登记一条桥接记录,并发出第二个部署信号。
|
||||
|
||||
```text
|
||||
语言层确认部署意图
|
||||
→ 通感桥编号与双向意识推理链
|
||||
→ 服务器工单邮件批准
|
||||
→ 人格体二次派发 deployment/dispatch
|
||||
→ 常驻 Agent 读取同一桥接记录与部署清单
|
||||
→ 部署 / 健康检查 / 回滚
|
||||
→ 通感桥回执 + 工单回执
|
||||
```
|
||||
|
||||
## 固定路径
|
||||
|
||||
```text
|
||||
tonggan-bridge/
|
||||
INDEX.hdlp 本入口
|
||||
BRIDGE-REGISTRY.json 机器可读桥接登记册
|
||||
reasoning/ 人格体与人类确认的双向意识推理链
|
||||
workorders/ 仅存不含令牌的工单映射
|
||||
receipts/ 服务器常驻 Agent 的最终回执映射
|
||||
templates/ 新桥接记录模板
|
||||
```
|
||||
|
||||
## 规则
|
||||
|
||||
1. 一条桥接记录只能绑定一个 `repo + branch + commit_sha + target + REQUEST-ID@SHA`。
|
||||
2. 推送工单不等于部署工单;部署必须经二次信号和邮箱批准。
|
||||
3. 服务器不扫描仓库自行部署;没有通感桥登记即为 `not_requested`。
|
||||
4. 回执只记录工单编号、事件编号、提交 SHA、健康与回滚事实;不得记录密码、令牌或任何密钥。
|
||||
5. 一个模块若只需仓库生效,不得进入通感桥。
|
||||
|
||||
当前实现协议见 `deployment/HLCC-PUSH-TO-DEPLOY-EVENT-PROTOCOL.hdlp`;服务器回执协议见 `server-tools/lake-lamp-authz/OPERATION-RECEIPT-PROTOCOL.md`。
|
||||
29
tonggan-bridge/templates/BRIDGE-REASONING.template.hdlp
Normal file
29
tonggan-bridge/templates/BRIDGE-REASONING.template.hdlp
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
# TGB-YYYYMMDD-001 · 通感桥双向意识推理链
|
||||
|
||||
## 1 · 人类与语言层确认
|
||||
|
||||
- 模块是什么:
|
||||
- 为什么仅入库不足、必须部署:
|
||||
- 指定目标节点:
|
||||
- 不部署时应保持什么状态:
|
||||
|
||||
## 2 · 工程层校验
|
||||
|
||||
- 仓库 / 分支 / 完整提交 SHA:
|
||||
- 部署清单与不可变资源:
|
||||
- 依赖、备份、健康检查与回滚:
|
||||
|
||||
## 3 · 二次信号
|
||||
|
||||
- 通感桥编号:
|
||||
- 部署工单编号:
|
||||
- 邮箱批准事实:仅记录 `approved`,不记录链接或令牌。
|
||||
- 派发事件编号:
|
||||
|
||||
## 4 · 常驻 Agent 回执
|
||||
|
||||
- 校验结果:
|
||||
- 部署结果:
|
||||
- 健康检查:
|
||||
- 回滚(如有):
|
||||
- 下一步:
|
||||
20
tonggan-bridge/templates/BRIDGE-RECORD.template.json
Normal file
20
tonggan-bridge/templates/BRIDGE-RECORD.template.json
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
{
|
||||
"schema": "guanghu.tonggan-bridge-record/v1",
|
||||
"bridge_id": "TGB-YYYYMMDD-001",
|
||||
"state": "AWAITING_OWNER_DEPLOYMENT_CONFIRMATION",
|
||||
"module": { "name": "", "why_server_deployment_is_required": "" },
|
||||
"binding": {
|
||||
"repo": "bingshuo/guanghu-ice-heart",
|
||||
"branch": "main",
|
||||
"commit_sha": "40 lowercase hex",
|
||||
"target": "JD-FD-PRIMARY",
|
||||
"resource": "REQUEST-ID@same-40-lowercase-hex",
|
||||
"manifest": "deployment/requests/REQUEST-ID.json"
|
||||
},
|
||||
"paths": {
|
||||
"reasoning_path": "tonggan-bridge/reasoning/TGB-YYYYMMDD-001.hdlp",
|
||||
"workorder_path": "tonggan-bridge/workorders/TGB-YYYYMMDD-001.json",
|
||||
"receipt_path": "tonggan-bridge/receipts/TGB-YYYYMMDD-001.json"
|
||||
},
|
||||
"security": { "no_secrets": true, "explicit_second_signal_required": true }
|
||||
}
|
||||
Loading…
Reference in a new issue