implements PLN-0153
This commit is contained in:
@@ -133,7 +133,37 @@ time. A suspended Game receives no normal gameplay ticks, no normal Game input,
|
||||
and no frame pacing. Real background execution is outside the v1 foreground
|
||||
contract.
|
||||
|
||||
## 8 Render Worker Concurrency
|
||||
## 8 VM Sessions and Execution Eligibility
|
||||
|
||||
Every VM-backed process MUST own a distinct VM session. A VM session owns the
|
||||
mutable execution context for that process, including the VM instance,
|
||||
per-session runtime counters, lifecycle delivery bookkeeping, debug/pause state,
|
||||
and transient handles opened through VM-facing services.
|
||||
|
||||
Foreground ownership and execution eligibility are related but separate
|
||||
concepts:
|
||||
|
||||
- foreground ownership selects the visual/navigation owner;
|
||||
- execution eligibility selects which sessions may receive VM ticks;
|
||||
- v1 grants normal VM execution only to the foreground VM-backed task, plus the
|
||||
bounded Game pause handoff tick defined above;
|
||||
- a suspended resident Game preserves its VM session but MUST NOT receive
|
||||
normal gameplay ticks, normal Game input, or frame pacing;
|
||||
- a VM-backed Shell owns its own VM session and MUST NOT overwrite or advance
|
||||
the resident Game session while the Shell is foreground;
|
||||
- a native Shell does not own a VM session.
|
||||
|
||||
The model is intentionally compatible with future background execution. Future
|
||||
service or media processes may become execution-eligible without changing the
|
||||
rule that mutable VM context belongs to the owning session. This chapter does
|
||||
not grant any v1 background progress guarantee.
|
||||
|
||||
Durable app data remains keyed by `app_id` where the relevant storage contract
|
||||
requires it. Transient VM handles, open files, lifecycle delivery queues, and
|
||||
staging state are session-scoped unless another spec explicitly makes them
|
||||
durable app data.
|
||||
|
||||
## 9 Render Worker Concurrency
|
||||
|
||||
The render worker is not a machine-visible event source and does not introduce
|
||||
guest callbacks. It is an implementation-side consumer of closed render
|
||||
@@ -160,7 +190,7 @@ Shutdown is explicit and bounded. A shutdown request wakes a waiting worker,
|
||||
causes pending work that will not be consumed to be discarded, and reports a
|
||||
typed failure if the worker cannot join within the configured timeout.
|
||||
|
||||
## 9 Async Asset and IO Work Lane
|
||||
## 10 Async Asset and IO Work Lane
|
||||
|
||||
The asset/IO async work lane is not a machine-visible event source and does not
|
||||
introduce guest callbacks. It is an implementation-side lane for asset
|
||||
@@ -184,7 +214,7 @@ does not publish resident graphics/audio/scene state directly.
|
||||
FS and game persistence services may consume this lane for IO-style work, but
|
||||
public FS API shape is defined by the FS/app-home contract, not by this chapter.
|
||||
|
||||
## 10 Determinism and Best Practices
|
||||
## 11 Determinism and Best Practices
|
||||
|
||||
PROMETEU encourages:
|
||||
|
||||
@@ -199,7 +229,7 @@ PROMETEU discourages:
|
||||
- hidden timing channels;
|
||||
- ambiguous out-of-band execution.
|
||||
|
||||
## 11 Relationship to Other Specs
|
||||
## 12 Relationship to Other Specs
|
||||
|
||||
- [`09a-coroutines-and-cooperative-scheduling.md`](09a-coroutines-and-cooperative-scheduling.md) defines coroutine lifecycle and scheduling behavior.
|
||||
- [`10-debug-inspection-and-profiling.md`](10-debug-inspection-and-profiling.md) defines observability and diagnostics surfaces.
|
||||
|
||||
Reference in New Issue
Block a user