feat(collab): launch JZAO-only HoloLake stage one

This commit is contained in:
冰朔 2026-09-09 21:22:18 +08:00
commit 1dd4a6a39e
17 changed files with 492 additions and 21 deletions

View file

@ -11,6 +11,8 @@ First load the host's current shared persona context for `ICE-P-ZY001` and the H
`/Volumes/JZAO/HoloLake/persona-runtime/repo-012-main/eternal-lake-heart/heartbeat-core/office-building-current/control-center/HB-MPC-0001/CONSOLE-INDEX.hdlp`
Also read `DEVELOPMENT-ENVIRONMENT.json` and `CLEANING-HANDOFF.json` in the same directory. All HoloLake source, build, test, task state, and receipts for this collaboration stay on `/Volumes/JZAO`; do not create a product worktree under the user's internal-drive Desktop, Documents, Downloads, or `/tmp`. Put generated build outputs under the registered `/Volumes/JZAO/HoloLake/build/HB-MPC-0001/<host>` root.
Choose the real current host from `codex`, `zcode`, `qwen`, or `doubao`. Register only from that host:
```bash
@ -36,6 +38,8 @@ The watcher atomically refreshes host-local `presence/CURRENT.json`; it does not
Never decide another host's state. If BingShuo is absent, continue safe independent work and route matters requiring her final judgment to `WAITING_HUMAN_FINAL_AID`. Do not fabricate consent. A stale courier or model heartbeat is shown as unknown/offline evidence, not as an automatic persona disappearance.
For cleanup, emit an exact candidate and evidence for `HLP-MPC-TASK-008`. Never delete directly. Only after persona review, stage an allowed generated build/cache/temporary target through the Guanghu Purification `jzao-cache-cleaner`; TCS, HLDP, persona memory, receipts, source, Git history, backups, and active task state are never cache.
For the first benchmark, submit one `ATTENTION` event with trigger, effect, detection, correction, evidence, and transfer test; submit one `TOOL_MIGRATION` candidate or an explicit `NONE`. Host strengths remain hypotheses until repeated task evidence exists.
Use temporary development IDs in mentions. `@ALL` broadcasts. Filesystem polling is near-real-time and requires the host watcher to be running; it is not zero-latency push.