feat(guanghu-os): add pre-root supervisor source slice
This commit is contained in:
parent
0a39761bed
commit
29bb023455
13 changed files with 403 additions and 3 deletions
|
|
@ -94,6 +94,24 @@ host. It cannot prove Guanghu-first boot control or the final topology. Those
|
|||
remain `0` until the same lifecycle is owned by an independently booted
|
||||
Guanghu supervisor and has a current JD server receipt.
|
||||
|
||||
## Pre-root Guanghu supervisor source slice
|
||||
|
||||
`scripts/guanghu-first-boot-supervisor.sh` and the matching initramfs-tools
|
||||
hook move the first deterministic Guanghu control state ahead of the complete
|
||||
Ubuntu root filesystem. The pre-root step binds the exact JD DMI instance,
|
||||
root UUID, boot ID, explicit `guanghu.first_boot=1` kernel marker, preserved
|
||||
Linux rescue entry, and repository bridge. It then writes one boot-scoped
|
||||
handoff under `/run/guanghu/first-boot` while the complete Linux userspace is
|
||||
still classified as dormant.
|
||||
|
||||
`scripts/build-guanghu-first-boot-initramfs.sh` builds a candidate without
|
||||
changing the installed initramfs, GRUB, disk, or boot default. Path overrides
|
||||
are accepted only inside the isolated test harness. The source contract and
|
||||
fixture test do not prove that a Guanghu supervisor remains alive across
|
||||
`switch_root`; independent first-boot control, physical deployment, and full
|
||||
on-demand Linux subcontrol therefore remain `0` until separate QEMU and JD
|
||||
receipts exist. See ADR-0176.
|
||||
|
||||
## Language-primary boot target
|
||||
|
||||
`guanghu-language-primary.target` makes the accepted cognitive-control model
|
||||
|
|
|
|||
Loading…
Reference in a new issue