World Generate
Outcome
Create navigable, performant environments that serve the intended player flow.
Required inputs
- level intent and player metrics
- engine, platform, and art direction
- terrain, biome, traversal, encounter, lighting, and streaming budgets
Ask for missing information only when it changes the route materially. Otherwise
state conservative assumptions and proceed with read-only analysis.
Workflow
- Map critical path, optional paths, landmarks, gates, encounter beats, spawn rules, and accessibility constraints.
- Choose deterministic procedural or generative stages with saved seeds and parameters.
- Generate into a new scene or layer while preserving authored content.
- Bake or update navigation, collision, lighting, occlusion, and streaming data only after plan approval.
- Run reachability, spawn safety, sightline, readability, lighting, and performance checks in representative routes.
Expected artifacts
- world specification
- seed and parameter manifest
- generated scene copy
- navigation and lighting evidence
- playthrough captures
- provenance record
Workflow-specific gates
- Verify every required objective and exit is reachable from every valid spawn.
- Check geometry intersections, floating props, traversal metrics, dark dead ends, and repetition artifacts.
- Human review decides whether a generated world replaces or merges with authored work.
Production completion gate
Before recommending production use, complete and report all seven gates:
- Rights, consent, code/model/dataset/output license, and generation-provenance checks.
- Technical format, naming, scale, color, metadata, and target-import validation.
- Visual and temporal consistency review across representative views and states.
- Runtime memory, frame-time, draw-call, streaming, and asset-budget checks.
- Playability and interaction smoke tests in the target runtime.
- Screenshot, capture, diff, or artifact-regression evidence with reproducible settings.
- Human approval before replacing source assets or promoting generated output.
Unknown rights, missing consent, unsupported hardware, conflicting host adapters,
or failed quality gates block production promotion. Preserve originals and make
fallbacks explicit.
1---2name: world-generate3description: Generate reversible terrain, environments, procedural levels, lighting, navigation, and spawn layouts from validated design constraints.4---56# World Generate78## Outcome910Create navigable, performant environments that serve the intended player flow.1112## Required inputs1314- level intent and player metrics15- engine, platform, and art direction16- terrain, biome, traversal, encounter, lighting, and streaming budgets1718Ask for missing information only when it changes the route materially. Otherwise19state conservative assumptions and proceed with read-only analysis.2021## Workflow22231. Map critical path, optional paths, landmarks, gates, encounter beats, spawn rules, and accessibility constraints.242. Choose deterministic procedural or generative stages with saved seeds and parameters.253. Generate into a new scene or layer while preserving authored content.264. Bake or update navigation, collision, lighting, occlusion, and streaming data only after plan approval.275. Run reachability, spawn safety, sightline, readability, lighting, and performance checks in representative routes.2829## Expected artifacts3031- world specification32- seed and parameter manifest33- generated scene copy34- navigation and lighting evidence35- playthrough captures36- provenance record3738## Workflow-specific gates3940- Verify every required objective and exit is reachable from every valid spawn.41- Check geometry intersections, floating props, traversal metrics, dark dead ends, and repetition artifacts.42- Human review decides whether a generated world replaces or merges with authored work.4344## Production completion gate4546Before recommending production use, complete and report all seven gates:47481. Rights, consent, code/model/dataset/output license, and generation-provenance checks.492. Technical format, naming, scale, color, metadata, and target-import validation.503. Visual and temporal consistency review across representative views and states.514. Runtime memory, frame-time, draw-call, streaming, and asset-budget checks.525. Playability and interaction smoke tests in the target runtime.536. Screenshot, capture, diff, or artifact-regression evidence with reproducible settings.547. Human approval before replacing source assets or promoting generated output.5556Unknown rights, missing consent, unsupported hardware, conflicting host adapters,57or failed quality gates block production promotion. Preserve originals and make58fallbacks explicit.
frabcd