implements PLN-0109
This commit is contained in:
@@ -31,6 +31,13 @@ MUST contain a frame id, the active app mode, and one typed packet:
|
||||
immutable. The runtime backpressure policy is latest-complete-submission-wins;
|
||||
it MUST NOT accumulate an unbounded frame queue.
|
||||
|
||||
The platform layer is the runtime-facing implementation boundary for render
|
||||
handoff. Runtime and firmware code publish completed frames through typed
|
||||
platform services such as `RenderSubmissionSink`, and they access Game 2D
|
||||
composition through `Game2DFrameComposer`. They MUST NOT depend on a monolithic
|
||||
hardware bridge, mutable `Hardware`, mutable `Gfx`, or live `FrameComposer`
|
||||
reference as the render handoff contract.
|
||||
|
||||
The current 2D graphics model is based on:
|
||||
|
||||
- framebuffer
|
||||
@@ -127,6 +134,10 @@ to the logical/runtime side before handoff, or to an owning service. They MUST
|
||||
NOT require the render consumer to hold mutable VM, `Hardware`, `Gfx`, or
|
||||
`FrameComposer` references.
|
||||
|
||||
Local host implementations may keep a concrete hardware object internally as a
|
||||
platform implementation detail. That object is not part of the runtime-facing
|
||||
render boundary; the boundary is the typed platform service set.
|
||||
|
||||
The runtime does not guarantee visual integrity if a developer or framework
|
||||
replaces resources behind an in-flight submission in a way that violates asset
|
||||
discipline.
|
||||
|
||||
@@ -123,9 +123,13 @@ The graphics system:
|
||||
|
||||
The platform layer:
|
||||
|
||||
- exposes typed service facades for render submission, render backend
|
||||
execution, Game 2D composition, input, audio, assets, and telemetry
|
||||
- consumes closed render submissions through a render-surface implementation
|
||||
- transports published RGBA8888 output into a host presentation surface without
|
||||
injecting host-owned debug overlay pixels
|
||||
- is the runtime-facing portability boundary; runtime and firmware code must not
|
||||
depend on a monolithic hardware bridge or on a concrete hardware aggregate
|
||||
|
||||
The host presentation layer MUST treat RGBA8888 as the canonical logical
|
||||
framebuffer format. RGB565 conversion is not part of the normal host
|
||||
|
||||
@@ -50,6 +50,12 @@ Does not belong in `docs/runtime/specs/` as the primary canonical source:
|
||||
|
||||
Here, hardware is not a generic bucket for everything. In the current package, "hardware" means the machine's virtual peripherals: GFX, AUDIO, INPUT, TOUCH, and MEMCARD/save memory. VM, firmware, cartridge, and ABI sit in sibling categories rather than inside hardware.
|
||||
|
||||
The implementation boundary for host portability is the platform layer. Runtime,
|
||||
firmware, and host integration code use typed platform services for rendering,
|
||||
input, audio, assets, and telemetry. A concrete local hardware aggregate may
|
||||
exist inside a host or test platform, but it is not the normative runtime-facing
|
||||
contract.
|
||||
|
||||
## Document Functions
|
||||
|
||||
- `normative`: defines the technical contract, expected behavior, or implementation-facing surface.
|
||||
|
||||
Reference in New Issue
Block a user