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

evidence: verify JD repository bridge lifecycle

Browse source
This commit is contained in:
冰朔 2026-08-16 00:26:25 +08:00
commit 9d411a252a
6 changed files with 127 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

7
product-source/hololake-platform/guanghu-os/README.md
View file

@ -134,7 +134,12 @@ state and one allowlisted repository readback request. It wakes a registered
backend, verifies the pinned `main`, and reclaims the backend on both success
and failure. `scripts/forgejo-repository-shadow-backend.sh` provides a separate
loopback-only Forgejo data plane for physical-node isolation tests; it never
targets the public repository process. See ADR-0178.
targets the public repository process. JD request `REQ-JD-REPO-003` now proves
the real Forgejo shadow lifecycle from `DORMANT` through verified readback and
back to `DORMANT`, including fail-closed cleanup. This raises only the isolated
repository lifecycle predicate to `100`; physical Guanghu boot, full Linux
on-demand subcontrol, and final master control remain `0`. See ADR-0178 and
`deployments/JD-FD-PRIMARY/REPOSITORY-BRIDGE-LIFECYCLE-RECEIPT-20260816.hldp`.
## Language-primary boot target