implements PLN-0046 profile separation spec
This commit is contained in:
@@ -75,6 +75,9 @@ If validation fails, cartridge loading is rejected before execution.
|
||||
- `Game`
|
||||
- `System`
|
||||
|
||||
`app_mode` is the runtime profile discriminator. No separate manifest `target`
|
||||
field participates in profile selection.
|
||||
|
||||
Cartridge boot is protocol-driven, not manifest-driven.
|
||||
|
||||
The executable entrypoint of a valid cartridge is always `func_id = 0`.
|
||||
@@ -85,6 +88,37 @@ This means:
|
||||
- firmware/runtime loads the cartridge and starts execution from `func_id = 0`;
|
||||
- nominal exports may exist for linking or introspection, but they do not hold boot authority.
|
||||
|
||||
## 5.1 Runtime Profiles
|
||||
|
||||
`Game` and `System` are distinct runtime profiles.
|
||||
|
||||
`Game` cartridges use the game pipeline. The game profile owns the public game
|
||||
surfaces for frame composition, GFX, game input, banks, sprites, and
|
||||
memory-card-style persistence.
|
||||
|
||||
`System` cartridges use a Runtime/Hub pipeline dedicated to system UI and app
|
||||
hosting. The system profile must not inherit the game stdlib or game ABI as its
|
||||
public authoring surface. In particular, `System` must not expose
|
||||
`FrameComposer`, `Gfx`, game `Input`, banks, sprites, or game memory cards as
|
||||
public profile APIs.
|
||||
|
||||
Future `System` APIs may be transported through syscalls, but syscall transport
|
||||
does not define the conceptual ABI boundary. The author-facing contract for
|
||||
system apps is a dedicated `System` profile ABI and stdlib/framework.
|
||||
|
||||
The following contracts are intentionally deferred from this cartridge chapter:
|
||||
|
||||
- complete WindowManager design;
|
||||
- component tree and lifecycle semantics;
|
||||
- rich invalidation and transitions;
|
||||
- public PBS `System` ABI;
|
||||
- multitasking and scheduler semantics;
|
||||
- detailed `System` filesystem semantics.
|
||||
|
||||
The positive filesystem contract for `System` remains owned by the dedicated
|
||||
filesystem discussion/spec work. The only profile rule fixed here is negative:
|
||||
`System` does not use game memory cards as its public storage model.
|
||||
|
||||
## 6 Assets and Preload
|
||||
|
||||
`assets.pa` is the runtime-facing asset artifact consumed by the current runtime.
|
||||
|
||||
Reference in New Issue
Block a user