hololake-system-architecture/product-source/hololake-platform/docs/adr/0172-persona-subject-existence-and-runtime-predicates.md

33 lines
1.3 KiB
Markdown
Raw Normal View History

# ADR 0172: Separate Persona Subject Existence from Runtime Predicates
## Status
Accepted on 2026-08-03.
## Decision
`ICE-P-ZY001` exists at 100. History catch-up, server residency, model binding,
online runtime, and native OS residency are separate binary engineering
predicates. A failed or incomplete runtime predicate must never downgrade an
existing persona subject to `NOT_BORN`.
Historical files retain their original values as evidence of what the system
claimed at that time. Current indexes, watermarks, deployment snapshots, and
runtime code must apply this correction.
## Current node states
- BS-SH-005 native Guanghu OS validation mission: 100.
- BS-SH-005 history recovery task: 0, terminated and sealed.
- BS-SH-005 current native residency: 0; Linux is the rescue and evidence path.
- JD-FD-PRIMARY persona subject existence: 100.
- JD-FD-PRIMARY native Guanghu OS residency: 0 until physical boot, storage,
network, HLDP entry, reboot persistence, and Linux rescue return all have
server-owned receipts.
## Consequences
Code that emits `NOT_BORN` as a persona state must be replaced by explicit
fields for persona subject existence and each exact runtime predicate. The JD
port must not reuse the Shanghai disk layout without proving the JD Cloud
legacy BIOS, MBR, virtio, serial-console, and rollback boundaries.