This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
# Phase 1.0AF: offline BigApp lifecycle model
|
||||
|
||||
Status: `HOST_LIFECYCLE_MODEL_COMPLETE_TARGET_IMPLEMENTATION_BLOCKED`
|
||||
|
||||
Date: 2026-07-29
|
||||
|
||||
The host-only state machine implements the lifecycle selected in Phase 1.0AE
|
||||
using exact built-in fake events. It contains no PS5 headers, process calls,
|
||||
syscalls, socket, real clock, CLI or filesystem output.
|
||||
|
||||
The model refuses launch when a BigApp already exists. A successful synthetic
|
||||
attempt must attach and arm the parent, request only fixed title `PPSA01659`,
|
||||
observe one positive unique child identity, detach the parent, observe child
|
||||
exec, replace one exact payload, restore temporary mutations, detach the child
|
||||
and emit one result within 64 supplied ticks.
|
||||
|
||||
Failure injection proves the modeled unwind order. An acquired parent is
|
||||
detached. A newly observed child is the only process eligible for termination.
|
||||
If replacement began, restoration precedes termination. Cleanup failure is a
|
||||
hard error rather than a clean result. These are properties of the model, not
|
||||
firmware or runtime evidence.
|
||||
|
||||
Target implementation remains blocked. The next permitted work is a host-only
|
||||
bounded ELF contract and validator so malformed or oversized payloads can be
|
||||
rejected before any future launcher boundary.
|
||||
Reference in New Issue
Block a user