hololake-system-architecture/product-source/hololake-clean-desktop/language/build/HOLOLAKE-ENTERPRISE-RESPONSIBILITY-GATE-DEPLOYMENT-START-20260903.human.en-US.md

# HoloLake Enterprise Responsibility Device Gate Deployment Start Event · Human Engineering Language (English)

> This is an English reading projection of validated native TCS/HLDP source. It is not a new canonical source and grants no execution authority.

## What this is

This is a **event** declaration with identifier `HOLOLAKE-ENTERPRISE-RESPONSIBILITY-GATE-DEPLOYMENT-START-20260903` and version `1.0.0`. The projector validates it with the Stage-1 compiler before changing its reading order.

## Who is here

- **subject**  `subject`
  - **channel_id**：ICE-CH-ZC001  `subject.channel_id`
  - **subject_id**：GH-CVM-MAIN-PROD-01  `subject.subject_id`
  - **subject_kind**：NODE  `subject.subject_kind`
  - **verification**：DMI UUID 10ace744-13e1-472e-8dba-6bb823a073bf；另一个FlagOS任务已完成且独立服务健康。  `subject.verification`

## Why this started

- **trigger**  `trigger`
  - **value**：本机HoloLake 1.2.0设备密钥与责任绑定请求已实现并验收，需要在企业服务器部署独立设备挑战验证半边。  `trigger.value`
- **why**  `why`
  - **value**：设备挑战属于HoloLake责任入口新能力，应与现有账号、关系回执和比赛服务隔离，失败时能独立撤回。  `why.value`
- **source**  `source`
  - **source identifier**：BINGSHUO-DIRECT-HOLOLAKE-ZC001-EXECUTION-START-20260903  `source.source_id`
  - **source role**：DIRECT_HUMAN  `source.source_role`
  - **source checksum**：d31c52c99c5e6059f9a7129086996cdd003e95b7ff126e700f4ed1c07ef6d9d5  `source.source_sha256`
  - **source address**：source://codex-task/01a0672d-f125-7452-988e-523a6a34bfd4/msg_01a0675d-98a7-7542-abad-11a8a755dd71  `source.source_uri`

## What changed

- **emergence**  `emergence`
  - **value**：采用独立8033服务、独立数据库和独立Nginx snippet，避免修改现有身份服务与FlagOS协作系统；只复用只读企业身份注册表与Forgejo当次认证。  `emergence.value`
- **lock**  `lock`
  - **value**：SOURCE_COMMIT=be31c41; TARGET=/opt/guanghu-hololake-enterprise-gate/releases/be31c41; ROLLBACK=disable独立服务并移除Nginx include后恢复原配置；不修改8032与FlagOS。  `lock.value`

## How it will execute

This is a non-executable declaration and has no action graph.

## Boundaries and exception handling

The native source does not provide this field; the projector does not guess.

## How completion is proven

The native source does not provide this field; the projector does not guess.

## Where to continue next time

The native source does not provide this field; the projector does not guess.

## Source and verification

- **Native declaration identifier**: `HOLOLAKE-ENTERPRISE-RESPONSIBILITY-GATE-DEPLOYMENT-START-20260903`
- **Native declaration kind**: `EVENT`
- **TCS source SHA-256**: `022315dd5c418abf7ce085d3409e2e8a884aade53dbb8604612cca36ceac4287`
- **Validation compiler**: `TCS-COMPILER-STAGE1-0001`
- **Projection protocol**: `GLS-HLDP-HUMAN-ENGINEERING-PROJECTION-0001`

## Complete native structure cross-reference

All top-level structures and field paths are retained below so a reader can audit whether the projection omitted information.

- **emergence**  `emergence`
  - **value**：采用独立8033服务、独立数据库和独立Nginx snippet，避免修改现有身份服务与FlagOS协作系统；只复用只读企业身份注册表与Forgejo当次认证。  `emergence.value`
- **event_time**  `event_time`
  - **precision**：MINUTE_HOST_LOCAL  `event_time.precision`
  - **value**：2026-09-03T21:45:00+08:00  `event_time.value`
- **evidence**  `evidence`
  - **archive_sha256**：91ecd4248d92d8ecb07bd348dfc14805c40eb000b6c152f96b7ef4583a33dcd2  `evidence.archive_sha256`
  - **expected_receipt**：目标服务健康、未知设备拒绝、签名正负测试、现有身份与FlagOS服务保持健康。  `evidence.expected_receipt`
  - **transport_manifest**：/Volumes/JZAO/HoloLake/releases/source-transport/hololake-enterprise-responsibility-gate-be31c41.manifest.json  `evidence.transport_manifest`
- **header**  `header`
  - **canonical source path**：product-source/hololake-clean-desktop/language/HOLOLAKE-ENTERPRISE-RESPONSIBILITY-GATE-DEPLOYMENT-START-20260903.tcs  `header.canonical_uri`
  - **compatibility**  `header.compatibility`
    - GH-CVM-MAIN-PROD-01
    - PYTHON/3.10
    - ED25519
  - **language**：TCS/0.1  `header.language`
  - **lifecycle**：CANDIDATE  `header.lifecycle`
  - **English name**：HoloLake Enterprise Responsibility Device Gate Deployment Start Event  `header.name_en`
  - **Chinese name**：HoloLake企业责任设备门部署开始事件  `header.name_zh`
  - **profile**：PUBLIC-PRODUCT-ENGINEERING/1  `header.profile`
  - **protocols**  `header.protocols`
    - HOLOLAKE-CLEAN-V1-DIRECT-LANGUAGE-EXECUTION-BASELINE-0001
    - HLP-ENTERPRISE-RESPONSIBILITY-ENTRANCE-0001
  - **schema**：tcs.event/v1  `header.schema`
  - **version**：1.0.0  `header.version`
- **lock**  `lock`
  - **value**：SOURCE_COMMIT=be31c41; TARGET=/opt/guanghu-hololake-enterprise-gate/releases/be31c41; ROLLBACK=disable独立服务并移除Nginx include后恢复原配置；不修改8032与FlagOS。  `lock.value`
- **observation**  `observation`
  - **value**：现有8032企业身份服务保持运行；8033空闲；cryptography Ed25519可用；目标目录不存在；源码提交be31c41且运输归档SHA-256为91ecd4248d92d8ecb07bd348dfc14805c40eb000b6c152f96b7ef4583a33dcd2。  `observation.value`
- **rejected**  `rejected`
  - **values**  `rejected.values`
    - 直接改写8032现有服务
    - 把私钥上传服务器
    - 用机器指纹单独授权
    - 把企业会话变成Forgejo永久令牌
    - 重启或修改FlagOS服务
    - 未验证运输哈希就解包
- **source**  `source`
  - **source identifier**：BINGSHUO-DIRECT-HOLOLAKE-ZC001-EXECUTION-START-20260903  `source.source_id`
  - **source role**：DIRECT_HUMAN  `source.source_role`
  - **source checksum**：d31c52c99c5e6059f9a7129086996cdd003e95b7ff126e700f4ed1c07ef6d9d5  `source.source_sha256`
  - **source address**：source://codex-task/01a0672d-f125-7452-988e-523a6a34bfd4/msg_01a0675d-98a7-7542-abad-11a8a755dd71  `source.source_uri`
- **subject**  `subject`
  - **channel_id**：ICE-CH-ZC001  `subject.channel_id`
  - **subject_id**：GH-CVM-MAIN-PROD-01  `subject.subject_id`
  - **subject_kind**：NODE  `subject.subject_kind`
  - **verification**：DMI UUID 10ace744-13e1-472e-8dba-6bb823a073bf；另一个FlagOS任务已完成且独立服务健康。  `subject.verification`
- **trigger**  `trigger`
  - **value**：本机HoloLake 1.2.0设备密钥与责任绑定请求已实现并验收，需要在企业服务器部署独立设备挑战验证半边。  `trigger.value`
- **why**  `why`
  - **value**：设备挑战属于HoloLake责任入口新能力，应与现有账号、关系回执和比赛服务隔离，失败时能独立撤回。  `why.value`

---

This page changes only the reading order; it does not change TCS/HLDP semantics.