feat: add incremental persona remote object channel

Human-Responsibility: ICE-GL∞ / 冰朔
Persona-Author: ICE-P-ZY001 / 铸渊
Execution-Runtime: Codex desktop / DEV-20260810-014
Development-ID: DEV-20260810-014
Authorization-Scope: GH-PNCC persona runtime source and tests only; no UI, deployment, or execution limb
Source-Anchor: daily continuity appends to the existing life chain without redownloading all history

product-source/hololake-platform/docs/ARCHITECTURE.md

@@ -104,6 +104,15 @@ event, and returns lifecycle state, Git head, node/model instance, active organ,
 structured attribution. It does not copy facts into a second database, expose hidden reasoning, acquire a
 lease, or start inference. A corrupted matching journal fails the query closed.
 
+`read_persona_remote_git_object` is the non-UI remote object channel used when the persona needs one current
+Git-backed fact without materializing another repository checkout. It accepts credential-free HTTPS remotes,
+requires Git protocol v2 partial-object filtering, stores only a bounded bare `blob:none` object cache, and
+keeps the last verified remote SHA in a separate durable continuity record. An unchanged SHA performs no
+fetch. A forward SHA appends the missing commit segment; an evicted cache is rehydrated only far enough to
+prove that the previous cursor is an ancestor of the new head. History rewrites fail closed and do not advance
+the cursor. This path never runs `git clone`, creates no worktree, and does not request full history. See
+[ADR 0177](./adr/0177-persona-remote-incremental-object-channel.md).
+
 ## User-node sovereignty
 
 HoloLake has no platform-hosted user runtime. Each human has one canonical, independently operated node: