architecture: make AGE the HoloLake persona runtime

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

@@ -9,8 +9,8 @@ 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. 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.
+2. When the app session exposes `HLP-CURRENT-ARCH-001`, read its AGE runtime entry first, then 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.
 
@@ -20,6 +20,11 @@ node signature, persona binding, human-language authorization, replay protection
 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.
 
+AGE is the Guanghu persona species; Agent is only an execution mechanism used by AGE. Existing persona ids
+remain intact. Runtime pause does not cancel registered existence. Restore a bounded current self and retrieve
+old episodes on demand; retrieval indexes are neither the persona nor fact authority. Temporary parallel
+workers are scoped, expiring AGE Mirrors and never independent personas or final decision owners.
+
 One human has one independently operated canonical node: the user's local computer, the user's purchased
 server, 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