feat(runtime): implement shared transactional memcard with async saves
Intrepid/Prometeu/Runtime/pipeline/pr-master This commit looks good
Intrepid/Prometeu/Runtime/pipeline/pr-master This commit looks good
This commit is contained in:
@@ -100,14 +100,17 @@ Example groups:
|
||||
- `gfx`
|
||||
- `audio`
|
||||
- `asset`
|
||||
- `fs` (includes game memcard module `mem` in v1)
|
||||
- `fs`
|
||||
- `memcard` (game module `mem`, bit 9)
|
||||
|
||||
Capability checks exist to constrain which host-managed surfaces a cartridge may use.
|
||||
|
||||
Input in v1 is VM-owned intrinsic surface and is not capability-gated through syscall policy.
|
||||
|
||||
Game memcard operations (`mem.*`) are status-first and use `fs` capability in v1.
|
||||
`mem` remains layered on runtime `fs`; no parallel persistence channel is introduced.
|
||||
Game memcard operations (`mem.*`) require the separate `memcard` capability
|
||||
and a manifest `memcard_slots` count in 1..64. Domain operations are status-first;
|
||||
`mem.bootstrap()` is a controlled-call boundary returning the hook result.
|
||||
Storage is a host-owned region backend, independent of runtime `fs`.
|
||||
Domain surface, status catalog and slot semantics are defined in [`08-save-memory-and-memcard.md`](08-save-memory-and-memcard.md).
|
||||
|
||||
Asset backlog operations are status-first. `queued`, `active`, `ready`,
|
||||
|
||||
Reference in New Issue
Block a user