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

fix: enforce one human one independent node

Browse source
This commit is contained in:
冰朔 2026-08-10 21:07:30 +08:00
commit cec261174d
32 changed files with 474 additions and 75 deletions
Download patch file Download diff file Expand all files Collapse all files

6
AGENTS.md
View file

@ -38,6 +38,12 @@ Keep this file focused on vault-specific conventions. For general HoloLake Era b
- Architecture, code, publication, deployment, health, and human-readable receipts are separate facts.
- `JD-FD-PRIMARY` Fifth-Domain responsibility and TCS-0002 enterprise four-domain responsibility are
parallel and independent; neither automatically inherits the other's access or operational liability.
- One human has one independently operated canonical node. It may be the user's local computer, a server
purchased by that user, or a user-owned IDE server deployed by an explicitly authorized team.
- Guanghu never provides user runtime servers, never pools users into a shared multi-tenant runtime, never
takes custody of private user data, and never assumes user workload concurrency or fallback execution.
- Team deployment does not transfer node ownership or create standing access. Node migration requires a new
binding and receipt; it must not duplicate one human root across multiple canonical nodes.
## Core conventions