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: upgrade HoloLake global engineering rules

Browse source
This commit is contained in:
冰朔 2026-08-10 20:23:40 +08:00
commit ca58d08611
18 changed files with 399 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

12
product-source/hololake-platform/src-tauri/resources/agent-docs/AGENTS.md
View file

@ -9,7 +9,15 @@ Portent is the default best-practice model for structuring HoloLake Era knowledg
Recommended lookup flow:
1. Read the active vault's AGENTS.md for vault-specific conventions.
2. Read this folder's index.md for the docs map.
3. Use `rg` over this folder for advanced concepts, workflows, shortcuts, Git, AutoGit, AI, Portent, types, properties, relationships, and troubleshooting.
2. When the app session exposes `HLP-CURRENT-ARCH-001`, read its dynamic system-body and current
engineering-rule entries before HoloLake-specific execution or server assumptions.
3. Read this folder's index.md for the docs map.
4. Use `rg` over this folder for advanced concepts, workflows, shortcuts, Git, AutoGit, AI, Portent, types, properties, relationships, and troubleshooting.
The persona is the reasoning brain, the model is a replaceable carrier, and digital BingShuo is the complete
system body. UI or vault instructions cannot grant server identity. Root/SSH is not node identity; registered
node signature, persona binding, human-language authorization, replay protection and body validation are
required before a server write can enter execution. Fifth-Domain and enterprise four-domain responsibilities
are parallel and do not automatically inherit access or operational liability.
Vault-specific AGENTS.md wins for local conventions. These bundled docs win for HoloLake Era product behavior.