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: load authoritative empty persona trust registry

Browse source
This commit is contained in:
冰朔 2026-08-12 05:37:40 +08:00
commit 9281587a0f
11 changed files with 343 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -25,11 +25,13 @@ The source coordinator no longer accepts an unverified persona-authorization boo
`hasPersonaPrimaryControlAuthorization` validates the shape, exact bindings, digest format, and validity window
of a receipt that claims `GUANGHU_OS` verification. That renderer-side validation is not cryptographic provenance
and cannot turn a local JSON object into authority. A native loader may be connected only after it verifies a
signed receipt against a registered Guanghu OS trust source and returns the already-verified projection. No such
trust source or loader is currently registered, so planning remains in system-direct mode. The independent server
signed receipt against a registered Guanghu OS trust source and returns the already-verified projection. REPO-012
now publishes the exact registry source with zero signers, and the Tauri command loads only that exact commit-bound
empty state. It keeps authorization disabled and rejects any signer until native cryptographic verification exists,
so planning remains in system-direct mode. The independent server
contract in `product-source/guanghu-knowledge-base/server/persona-control-authorization.ts` defines the v2 signed
receipt, exact REPO-012 signer-registry source, canonical signing bytes, signer scope checks, revocation handling,
and Ed25519 verification. Its tested code does not populate the registry or connect the desktop native boundary.
and Ed25519 verification. Its tested code does not appoint a signer or enable the desktop persona-primary path.
`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

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

@ -189,7 +189,10 @@ current desktop source. Missing, stale, mismatched or merely local evidence ther
cryptographic source contract: v2 signed receipt fields, deterministic signing bytes, an exact-commit REPO-012
signer-registry source, persona/human/scope-limited Ed25519 signers, revocation, time and request binding, and
signature verification. The current REPO-012 main does not publish that registry path, so no signer is trusted and
the Tauri desktop has no native verifier or loader. Tested verifier source is not runtime authority.
the Tauri desktop now exposes a native read-only loader for the exact REPO-012 commit-bound registry. It accepts
the current empty registry only and keeps authorization disabled; any signer fails closed until the native
cryptographic receipt verifier and an authoritative signer/key-custody process exist. Tested loader and verifier
source are not runtime authority, deployment, or desktop 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.