|
| 1 | +# PLAN_PR_VECTOR_NATIVE_TEMPLATE |
| 2 | + |
| 3 | +## Goal |
| 4 | +Define a reusable vector-native game template that uses first-class vector assets as the default and required visual path, |
| 5 | +building on the accepted vector-only runtime baseline without reintroducing sprite fallback dependencies. |
| 6 | + |
| 7 | +## Why This PR Exists |
| 8 | +The Asteroids demo now proves that the platform can author, validate, package, publish, and run a vector-only game. |
| 9 | +The next multiplier is to turn that success into a reusable template so future vector-native games can start from a clean, |
| 10 | +validated, platform-approved baseline instead of rebuilding the same structure each time. |
| 11 | + |
| 12 | +## Intent |
| 13 | +- create a true vector-native template |
| 14 | +- preserve accepted strict validation, packaging, runtime, CI, export, and publishing boundaries |
| 15 | +- make vector-first authoring the default path for new arcade-style games |
| 16 | +- avoid reintroducing sprite fallback as an active runtime dependency |
| 17 | + |
| 18 | +## Scope |
| 19 | +- define template structure for vector-native projects |
| 20 | +- define required vector asset categories for template bootstrapping |
| 21 | +- define template registry, dependency graph, validation, packaging, and runtime expectations |
| 22 | +- define debug/profiler/template/publishing participation for vector-native projects |
| 23 | +- define migration and starter content expectations for future vector-led demos/games |
| 24 | + |
| 25 | +## Non-Goals |
| 26 | +- No engine core API changes |
| 27 | +- No broad template redesign for unrelated game styles |
| 28 | +- No sprite fallback dependency in the vector-native template baseline |
| 29 | +- No destructive migration of existing non-vector templates |
| 30 | +- No bypass of accepted validation, packaging, runtime, CI, export, or publishing boundaries |
| 31 | + |
| 32 | +## Template Intent |
| 33 | +The vector-native template should serve as the default starting point for games that benefit from: |
| 34 | +- geometric line art |
| 35 | +- clean scaling |
| 36 | +- rotation without raster artifacts |
| 37 | +- low-overhead visual definitions |
| 38 | +- classic arcade or abstract visual styles |
| 39 | + |
| 40 | +## Proposed Template Path |
| 41 | +```text |
| 42 | +templates/vector-native-arcade/ |
| 43 | +``` |
| 44 | + |
| 45 | +## Proposed Baseline Structure |
| 46 | +```text |
| 47 | +templates/vector-native-arcade/ |
| 48 | + assets/ |
| 49 | + palettes/ |
| 50 | + vectors/ |
| 51 | + tilemaps/ |
| 52 | + parallax/ |
| 53 | + config/ |
| 54 | + runtime/ |
| 55 | + docs/ |
| 56 | +``` |
| 57 | + |
| 58 | +## Required Vector Asset Categories |
| 59 | +- player vehicle/entity vector |
| 60 | +- enemy or obstacle vector set |
| 61 | +- title or UI vector treatment |
| 62 | +- optional vector HUD or indicator elements |
| 63 | +- vector-aware startup configuration |
| 64 | + |
| 65 | +## Core Contracts |
| 66 | +1. Vector assets are the required primary visual contract. |
| 67 | +2. Registry owns vector asset identity and template content. |
| 68 | +3. Dependency graph records template vector relationships deterministically. |
| 69 | +4. Validation enforces vector-native requirements. |
| 70 | +5. Packaging includes vector-native assets deterministically. |
| 71 | +6. Runtime loads vector-native packaged content without sprite fallback. |
| 72 | +7. Debug, profiler, export, publishing, and CI systems all recognize the template as first-class. |
| 73 | +8. No engine core APIs are changed. |
| 74 | + |
| 75 | +## Template Expectations |
| 76 | +- ships with a minimal playable or near-playable bootstrap state |
| 77 | +- demonstrates title/start/gameplay/restart flow hooks |
| 78 | +- exposes clean extension points for future game-specific logic |
| 79 | +- preserves docs-first compatibility with platform workflow |
| 80 | +- provides a reliable starting point for future vector-first demos |
| 81 | + |
| 82 | +## Likely Files |
| 83 | +- `docs/pr/BUILD_PR_VECTOR_NATIVE_TEMPLATE.md` |
| 84 | +- template content under `templates/vector-native-arcade/` |
| 85 | +- vector starter assets and config |
| 86 | +- docs/dev reports |
| 87 | +- no engine core API files |
| 88 | + |
| 89 | +## Acceptance Criteria |
| 90 | +1. Template validates successfully as vector-native content. |
| 91 | +2. Packaging succeeds without sprite fallback dependency. |
| 92 | +3. Runtime reaches ready state from template-packaged content. |
| 93 | +4. Debug and profiler surfaces reflect vector-native template participation. |
| 94 | +5. Export and publishing remain compatible. |
| 95 | +6. Template is reusable for future vector-led games. |
| 96 | +7. No engine core APIs are changed. |
| 97 | + |
| 98 | +## Manual Validation Checklist |
| 99 | +1. Template contains required vector asset categories. |
| 100 | +2. Registry/dependency graph include vector-native template assets. |
| 101 | +3. Validation passes with no blocking findings. |
| 102 | +4. Packaging remains deterministic. |
| 103 | +5. Runtime reaches ready state. |
| 104 | +6. No sprite fallback is required. |
| 105 | +7. Debug/profiler/export/publishing remain ready. |
| 106 | +8. No engine core APIs are changed. |
| 107 | + |
| 108 | +## Approved Commit Comment |
| 109 | +plan(template): define reusable vector-native arcade template |
| 110 | + |
| 111 | +## Next Command |
| 112 | +BUILD_PR_VECTOR_NATIVE_TEMPLATE |
0 commit comments