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
hololake-system-architecture/product-source/hololake-native-desktop/server/release-broadcast
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
冰朔 aa3df05775 fix(hololake): harden immutable broadcast activation
2026-08-13 18:37:30 +08:00
..
hololake-release-broadcast.service feat(hololake): add fail-closed JD release broadcast origin 2026-08-13 18:32:38 +08:00
README.md feat(hololake): add fail-closed JD release broadcast origin 2026-08-13 18:32:38 +08:00
server.mjs fix(hololake): harden immutable broadcast activation 2026-08-13 18:37:30 +08:00

README.md

HoloLake release broadcast candidate

This is the HoloLake-owned, loopback-only origin for signed update broadcasts. It has no upstream software feed and never uploads or activates a release.

Without ACTIVE.json, /health reports EMPTY_FAIL_CLOSED and /latest.json returns HTTP 204, the updater protocol's explicit no-update result. An active release is accepted only when the human activation record, immutable broadcast, pipeline receipt, package bytes, Developer ID receipt, and Apple notarization receipt form one exact evidence chain. Invalid evidence locks the whole release endpoint until an operator fixes the evidence and explicitly restarts the service.

The service listens only on 127.0.0.1. Public HTTPS routing, updater trust-key provisioning, artifact upload, activation, and desktop rollout are independent deployment gates.