implements PLN-0046 profile separation spec

This commit is contained in:
2026-05-14 13:24:09 +01:00
parent e3ac3dfd06
commit da908ffcb4
5 changed files with 61 additions and 4 deletions
@@ -52,6 +52,12 @@ This identity is:
Input queries are VM-owned intrinsic calls in v1 and are outside the syscall identity space.
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
ABI. `System` APIs, when exposed to PBS or other guest languages, belong to a
dedicated `System` profile ABI and stdlib/framework.
## 3 Syscall Resolution
The host maintains a registry:
@@ -173,6 +179,9 @@ Return shape must also follow the transversal status-first policy in [`16a-sysca
The game memcard profile uses module `mem` with status-first return shapes.
`mem` is a domain layer backed by runtime `fs` (it is not a separate storage backend).
The `mem` module is a game profile surface. It is not the public storage model
for `System` profile apps.
Canonical operations in v1 are:
- `mem.slot_count() -> (status, count)`
@@ -215,6 +224,9 @@ For `asset.load`:
The canonical frame-orchestration public ABI uses module `composer`.
The `composer` module is a game profile surface. It is not inherited by
`System` profile apps as their public UI/composition API.
Canonical operations in v1 are:
- `composer.bind_scene(bank_id) -> (status)`