adjustments over frame composer contract - agnostic tile size
This commit is contained in:
@@ -60,6 +60,12 @@ This also preserves future backend freedom:
|
||||
- hardware-assisted blit path later;
|
||||
- or a more PPU-like backend in bare-metal environments.
|
||||
|
||||
It also preserves the scene-model contract already accepted below the frame layer:
|
||||
|
||||
- tile size is a property of each scene layer;
|
||||
- the frame orchestrator must consume that contract, not redefine it;
|
||||
- `FrameComposer` must therefore remain tile-size agnostic rather than hard-coding `16x16` assumptions.
|
||||
|
||||
## Invariantes / Contrato
|
||||
|
||||
### 1. Frame Entry
|
||||
@@ -113,6 +119,15 @@ This also preserves future backend freedom:
|
||||
- `Gfx` MUST NOT own cache refresh policy.
|
||||
- `Gfx` MUST only consume already prepared render state.
|
||||
|
||||
### 5A. Tile Size Contract
|
||||
|
||||
- `FrameComposer` SHALL remain tile-size agnostic.
|
||||
- `FrameComposer` MUST accept scene layers whose canonical `tile_size` is `8x8`, `16x16`, or `32x32`.
|
||||
- `FrameComposer` MUST NOT impose `16x16` as a bind-time, cache-time, resolver-time, or render-time precondition.
|
||||
- Cache sizing, resolver math, and world-copy preparation SHALL derive from the `tile_size` declared by each bound scene layer.
|
||||
- Compatibility checks, when needed, MUST be derived from canonical scene-layer and glyph-bank metadata rather than from a hard-coded compositor default.
|
||||
- Any implementation path that only works for `16x16` tiles is NON-COMPLIANT with this decision.
|
||||
|
||||
### 6. Sprite Model
|
||||
|
||||
- `Sprite.active` MUST be removed from the canonical operational model.
|
||||
@@ -158,6 +173,7 @@ This also preserves future backend freedom:
|
||||
- `Hardware` will need to aggregate `FrameComposer` next to `Gfx`.
|
||||
- `Gfx` will need to lose ownership of scene/sprite operational state.
|
||||
- Sprite submission state will need to move into `SpriteController`.
|
||||
- `FrameComposer`, cache, and resolver integration must preserve per-layer `tile_size` semantics, including `8x8`.
|
||||
|
||||
### Runtime / VM
|
||||
|
||||
@@ -168,6 +184,7 @@ This also preserves future backend freedom:
|
||||
|
||||
- Scene activation will become explicit through bank-id binding.
|
||||
- Scene slot replacement will require explicit rebinding behavior from callers.
|
||||
- Scene-driven tile-size metadata must propagate unchanged into `FrameComposer` orchestration and backend copy preparation.
|
||||
|
||||
## Referencias
|
||||
|
||||
@@ -180,7 +197,9 @@ This also preserves future backend freedom:
|
||||
- `FrameComposer` and `SpriteController` need explicit planning and migration sequencing.
|
||||
- `Gfx.render_all()` retirement MUST be planned rather than removed ad hoc.
|
||||
- The frame service rename and integration path MUST be propagated through the frame loop callsites.
|
||||
- Plan steps and tests that cover world composition MUST explicitly include `8x8` tile-size coverage.
|
||||
|
||||
## Revision Log
|
||||
|
||||
- 2026-04-14: Initial accepted decision from `AGD-0026`.
|
||||
- 2026-04-15: Revision accepted to make `FrameComposer` explicitly tile-size agnostic and to require `8x8` support alongside `16x16` and `32x32`.
|
||||
|
||||
Reference in New Issue
Block a user