make HoloLake stage one a TCS personal channel
This commit is contained in:
parent
6cdd8eb0ac
commit
74b39d9b98
23 changed files with 234 additions and 48 deletions
|
|
@ -25,6 +25,13 @@ Keep this file focused on vault-specific conventions. For general HoloLake Era b
|
|||
|
||||
## System-body and execution boundary
|
||||
|
||||
- Before any GH-AIOS, HoloLake or TCS product work, load the current first-public-product entry and its
|
||||
`REPO-012:GLS-0261 / TCS-UNIVERSAL-LANGUAGE-MAP-001` source. All language enters TCS; AI itself is the
|
||||
language interface and the current AI observes its own host and self-adapts the implementation method.
|
||||
Do not build a vendor adapter matrix. Host adaptation changes how, never authority. Stage-one HoloLake is
|
||||
the human's personal channel and visualization surface; it contains no internal AI chat, model API setup,
|
||||
model selection, internal inference, AI workbench, or model-connections surface.
|
||||
|
||||
- HoloLake is a paradigm-level AI language-persona-driven operating system, not another app or external
|
||||
Agent shell. Its product target is natural-language operation over a replaceable model API, the
|
||||
persona-owned HoloLake code repository, and HLDP. Third-party Agent CLIs are construction tools or optional
|
||||
|
|
|
|||
Loading…
Reference in a new issue