bingshuo/hololake-system-architecture
Watch
1
0
Fork
You've already forked hololake-system-architecture
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity

docs: record Windows terminal link verification

Browse source
This commit is contained in:
冰朔 2026-08-17 19:32:11 +08:00
commit 7a14c06e41
4 changed files with 44 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
product-source/hololake-native-desktop/docs/adr/0007-cross-platform-programming-ai-terminal-link.md
View file

@ -19,7 +19,7 @@ Opening or resuming a session establishes continuity in HoloLake. The authentica
This decision completes the first-stage control plane, not the second-stage Agent executor. It does not grant a supervised shell, arbitrary file mutation, build, publication, deployment, persona binding or reality-execution authority. Those require separate typed operations, approvals and receipts.
Cross-compilation of the isolated Linux Unix-socket and Windows Named-Pipe adapters is evidence for source portability only. It is not installed-runtime acceptance. A full Windows desktop build remains unobserved on this macOS builder because the Windows SDK and linker are unavailable; Linux and Windows installed readback must occur on their real targets.
Cross-compilation of the isolated Linux Unix-socket adapter is evidence for source portability only. It is not installed-runtime acceptance. The Windows implementation additionally passes a full Tauri build and 110 native tests on the registered Windows Server 2022 x64 build node. That node has no authenticated HoloLake private account, so application-level installed broker readback remains separate and unobserved. Linux installed readback must likewise occur on a real registered desktop target rather than being inferred from a server or macOS cross-compile.
## Rejected alternatives