Studio scene pack contract for runtime SCENE binary payload
This commit is contained in:
@@ -97,6 +97,18 @@ Rules:
|
||||
- `output.pipeline` carries tooling/build metadata kept separate at authoring time;
|
||||
- codec must remain explicit and must not be hidden inside format naming.
|
||||
|
||||
### Scene Bank Contract Boundary
|
||||
|
||||
For `Scene Bank` assets, `output.format = SCENE/tilemap_v1` identifies the runtime-facing scene contract.
|
||||
|
||||
Rules:
|
||||
|
||||
- `SCENE/tilemap_v1` is a runtime/publication format, not an editor-file format;
|
||||
- `TMX`, `TSX`, and other editor-specific files may exist as tooling/editorial surfaces, but they are not the canonical publication contract;
|
||||
- the canonical packer input for `Scene Bank` publication is the editor-agnostic Scene Bank request emitted by Studio from canonical scene state;
|
||||
- packer must not reinterpret the presence of editorial files as authorization to bypass the request boundary;
|
||||
- packer must not assume any external scene file is canonical persistence, even when Studio supports that file as import/export compatibility.
|
||||
|
||||
### Explicit Index Collections
|
||||
|
||||
When `output.pipeline` carries ordered collections whose members need stable semantic identity, that identity must not depend on raw list position alone.
|
||||
|
||||
Reference in New Issue
Block a user