implements PLN-0046 profile separation spec
This commit is contained in:
@@ -40,11 +40,18 @@ When the boot target is `Cartridge`:
|
||||
|
||||
For a cartridge boot target:
|
||||
|
||||
- `Game` cartridges transition into game-running flow;
|
||||
- `System` cartridges are initialized and integrated into the Hub/window path.
|
||||
- `Game` cartridges transition into the game-running pipeline;
|
||||
- `System` cartridges transition into a Runtime/Hub pipeline dedicated to
|
||||
system UI and app hosting.
|
||||
|
||||
This preserves the distinction between machine firmware state and app execution mode.
|
||||
|
||||
The `System` route must not be treated as the game pipeline running inside a
|
||||
window. It is a separate runtime profile path oriented around Hub ownership and
|
||||
WindowManager integration. The initial implementation may be minimal, but the
|
||||
routing boundary is normative: `System` does not enter `GameRunning` as its
|
||||
profile pipeline.
|
||||
|
||||
## 4 Host CLI Relationship
|
||||
|
||||
Typical host-facing boot intents are:
|
||||
@@ -67,6 +74,10 @@ Boot target selection feeds into firmware states such as:
|
||||
- `GameRunning`
|
||||
- `AppCrashes`
|
||||
|
||||
Additional firmware states may represent dedicated `System` profile execution.
|
||||
Such states are part of the Runtime/Hub route and do not change the `Game`
|
||||
pipeline contract.
|
||||
|
||||
Boot target is not itself a firmware state. It is an input to the firmware state machine.
|
||||
|
||||
## 6 Debug Boot
|
||||
|
||||
Reference in New Issue
Block a user