implements PLN-0129
This commit is contained in:
@@ -62,6 +62,11 @@ Typical host-facing boot intents are:
|
||||
|
||||
The CLI is an entry surface for boot target selection; the firmware contract remains the same underneath.
|
||||
|
||||
Host CLI, debugger, and equivalent single-game launch flows are the supported
|
||||
direct cartridge boot surfaces. Direct boot is not requested by guest bytecode
|
||||
through a `system.run_cart` syscall or any other app-callable cartridge boot
|
||||
ABI.
|
||||
|
||||
## 5 Firmware State Relationship
|
||||
|
||||
Boot target selection feeds into firmware states such as:
|
||||
|
||||
@@ -52,6 +52,11 @@ This identity is:
|
||||
|
||||
Input queries are VM-owned intrinsic calls in v1 and are outside the syscall identity space.
|
||||
|
||||
Cartridge boot is also outside the guest syscall identity space. A cartridge,
|
||||
Shell app, or other userland guest must not declare or call `system.run_cart`.
|
||||
Direct cartridge boot is a host/system boot-profile entrypoint, not an
|
||||
app-callable syscall.
|
||||
|
||||
Syscall identity is transport, not the conceptual boundary for runtime
|
||||
profiles. `Game` and `System` may both use syscall transport internally or at
|
||||
their ABI edge, but that does not make their public authoring surfaces the same
|
||||
|
||||
Reference in New Issue
Block a user