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

feat: mount persona language planning entry

Browse source
This commit is contained in:
冰朔 2026-08-12 03:58:02 +08:00
commit 5d465115cb
11 changed files with 294 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

9
product-source/hololake-platform/docs/ABSTRACTIONS.md
View file

@ -17,7 +17,9 @@ it does not pretend that deterministic keyword matching can perform persona reas
utterance as a bounded `FACT_SENSE` partner-deliberation question, accepts only a completed and schema-valid
PNCC lifecycle receipt, maps the eleven-field snake-case gravity frame into `PartnerDeliberation`, and only
then calls `compileLanguageGoal`. A failed, malformed, non-fact, or purpose-less receipt never becomes a goal.
The adapter is not yet mounted to the desktop language entry and has no live-product acceptance claim.
`PersonaLanguageShellPanel` now mounts this adapter in the Fifth Domain desktop source. That source wiring is
still gated by a unique manifest-valid persona repository, the manifest-pinned configured model, and public
device identity; it has no installed-desktop or live-product acceptance claim.
`compilePersonaLanguageGoalBinding` builds the exact native wake envelope only after a single clean persona
repository, its B0 and organ contracts, a registered local device identity, and the manifest-pinned model all
@ -217,7 +219,10 @@ The source-level authority-order coordinator for one natural-language goal. It f
discovery yields one clean persona binding and the configured provider/model matches that repository manifest.
Only then may it read the public node identity, compile the exact PNCC wake binding, and request B0 partner
deliberation. The result contains a plan and evidence binding only; it exposes no execution callback and performs
no reality action. Source implementation is distinct from desktop mounting and native acceptance.
no reality action. `PersonaLanguageShellPanel` mounts it through the capability-limited `LanguageShellBridge`,
passes only already-mounted Git roots and configured provider metadata, and deliberately keeps persona authority
false until a desktop authorization receipt exists. The panel does not expose an approval control because this
slice has no durable confirmation consumer. Source mounting remains distinct from native acceptance.
Key abstractions and domain models in Tolaria.

7
product-source/hololake-platform/docs/ARCHITECTURE.md
View file

@ -172,8 +172,11 @@ boundary. It resolves exactly one manifest-valid persona repository before selec
configured model, reads the public device-identity receipt only after those gates pass, compiles the wake
binding, and finally invokes B0 partner deliberation. Unavailable, unbound, ambiguous, model-missing, identity,
binding, and cognition failures stop at their own boundary; later stages are not invoked. Its successful result
is still a language-goal projection, not permission to perform a reality action. This controller is not yet
mounted into the desktop language shell and therefore does not establish runtime integration or acceptance.
is still a language-goal projection, not permission to perform a reality action. `PersonaLanguageShellPanel`
is now mounted from the Fifth Domain desktop source and receives the app's already-mounted repository roots and
configured provider metadata. It keeps `personaAuthorized=false`, exposes no execution callback, and hides the
reality confirmation surface because no durable confirmation consumer is wired. This proves source integration,
not a real persona manifest binding, installed desktop runtime, or acceptance.
Tolaria is a personal knowledge and life management desktop app. It reads a vault of markdown files with YAML frontmatter and presents them in a four-panel UI inspired by Bear Notes.