docs(guanghu-os): register JD pre-root QEMU proof

This commit is contained in:
冰朔 2026-08-15 23:35:22 +08:00
commit fed0c73b04
6 changed files with 110 additions and 15 deletions

View file

@ -0,0 +1,64 @@
schema: guanghu.jd-pre-root-qemu-receipt/v1
receipt_id: JD-FD-PRIMARY-pre-root-qemu-af84e42
issued_at: 2026-08-15T23:45:00+08:00
node_id: JD-FD-PRIMARY
node_dmi: f3d4b730-7f02-452f-975b-7091a4800431
source_commit: 29bb023455ce245dc44dbd5e61ced92cd647e071
source_tree: 4e158f7aaf8700afbf5cd859cbd8f00f30c32246
source_publication: PENDING_CODE_HOST_CREDENTIAL_RECOVERY
workorder_path: /guanghu/recovery/JD-FD-PRIMARY-pre-root-qemu-af84e42/WORKORDER.hldp
workorder_sha256: b97835f6a5678ac288f2572e0c4309c6f36a06dcb59f701282ade128b51abc25
candidate_initramfs_path: /guanghu/recovery/JD-FD-PRIMARY-pre-root-qemu-af84e42/guanghu-first-boot-initrd.img
candidate_initramfs_sha256: 55d8aafc8ff413c8976e017438372ec6bc45f4f7accfb3ff2e1e570e392b2dfa
candidate_initramfs_size: 109849987
member_manifest_sha256: c575728b4696b5805f74336426d4a43fc6e3488d365e1547a2e0ab3d2af58f48
trigger: Prove that Guanghu control can execute before the complete Ubuntu root system without changing the JD physical boot path.
emergence:
- The initial 512 MiB QEMU run stopped during initramfs decompression and is retained as bounded failure evidence.
- The first negative run exposed that initramfs-tools ignores an ordinary child-script exit, so emitting FAIL_0 alone did not stop root discovery.
lock:
- The local-premount adapter now invokes the initramfs panic path whenever supervisor validation fails.
- The final positive and negative runs use 2048 MiB software-emulated QEMU, the live JD kernel, exact JD DMI, and exact root UUID binding.
why: The gate must prove both early Guanghu execution and a real refusal to hand control to the root system when authority binding is absent.
rejected:
- Treating a printed validation error as fail-closed while initramfs continued toward the root system.
- Installing the candidate into /boot, changing GRUB, attaching a writable server disk, or rebooting JD-FD-PRIMARY.
positive_evidence:
serial_log: /guanghu/recovery/JD-FD-PRIMARY-pre-root-qemu-af84e42/qemu-positive.serial.log
serial_sha256: a0f56b15d6df414f0ee3c0a3dcadabc95db3f6533363437615c550d12fab0c81
observed: GUANGHU_FIRST_BOOT_SUPERVISOR_ACTIVE node=JD-FD-PRIMARY linux_userspace=DORMANT
negative_evidence:
serial_log: /guanghu/recovery/JD-FD-PRIMARY-pre-root-qemu-af84e42/qemu-negative-no-marker.serial.log
serial_sha256: 51c52db5602835253d7ecd25066cc74492adbeb03a0c287a6cb34c0a35f336f7
observed:
- GUANGHU_FIRST_BOOT_SUPERVISOR_FAIL_0: explicit first-boot marker is missing
- Guanghu pre-root authority validation failed; refusing root handoff
- Rebooting automatically due to panic= boot argument
root_discovery_after_failure: false
live_readback:
boot_id_before: 68d4a3c9-c866-4f4a-be2e-0aa5f41a61b1
boot_id_after: 68d4a3c9-c866-4f4a-be2e-0aa5f41a61b1
guanghu_supervisor_service: active_enabled
linux_code_bridge_service: active_enabled
linux_code_bridge_pid_before: 760
linux_code_bridge_pid_after: 760
residual_qemu_processes: 0
public_code_http: 200
public_anchor_http: 200
physical_boot_files_changed: false
physical_reboot_performed: false
claims:
guanghu_pre_root_supervisor_contract_source: 100
guanghu_first_boot_initramfs_builder_source: 100
jd_host_qemu_pre_root_supervisor: 100
negative_authority_binding_hard_fail: 100
cross_switch_root_persistent_supervisor: 0
independent_guanghu_first_boot_supervisor: 0
linux_on_demand_subcontrol: 0
final_guanghu_os_master: 0
next_gate: IMPLEMENT_AND_VERIFY_CROSS_SWITCH_ROOT_PERSISTENT_GUANGHU_SUPERVISOR_IN_ISOLATION
sources:
- /guanghu/recovery/JD-FD-PRIMARY-pre-root-qemu-af84e42/WORKORDER.hldp
- ADR-0176
- qemu-positive.serial.log
- qemu-negative-no-marker.serial.log