VoxelForge/Standalone/Research/WorldAssemblerM3/Research46/PROMPT.md

VoxelForge — research R46 (read-only): generator capability matrix

You are a researcher. Read only: do not edit, create or delete any file, and do not build, run or test anything. Read the code, reports and design docs. Be thorough: verify each claim by hand in the code, and mark each one [CODE] file:line, [MEASURED] report, or [INFERENCE]. Branch assembler/world (cbbfd46).

Why

The owner approved the next focus (from Standalone/Research/WorldAssemblerM3/Astra4/REVIEW.md #3): turn generator breadth into playable variety. First we need an honest picture of what each strate/generator family can do today.

Task

Find every generator family / strate type: surface world, floating islands, caves/cavern, tunnel network, vertical shafts, dreamcore/liminal, and any others in the code (Core native, legacy fallback, op stack, composer). For each, fill one row:

• Core path: native Core evaluator, legacy fallback, or not in Core at all? Where is it dispatched?
• Entrances/exits: arrival and departure mouths, and the primordial law (arrival → departure walkable).
• Interior connectivity: walkable, and audited by what?
• Edits: does digging (diff layer) work on it in the Core path?
• Materials/content: material IDs, decorations, foliage, lights, anything placeable.
• Far terrain: does it have far LOD/shells?
• Performance: latest measured near-ready, with the report.
• Identity: what makes it look and feel distinct today; is it recognisable without a label?
• Owner world: used in Standalone/data/owner_world.json? Which strate letter (SW/FI/TN/VS)?
• Gaps: what's missing for it to be a "place" with its own identity and a destination.

Then:

1. Which three families are closest to being distinct places (the owner's example: a grounded cave, an island environment, one liminal identity)? What is the smallest work to get each there?
2. What does the composer (VoxelSeasonManifest.cpp, COMPOSER-NOTES.md) already do for tagged content, and what's the smallest next step?
3. Risks: places where the Core path silently falls back, or where a family exists in docs but not in code.

Write plain Markdown: the matrix plus ≤ ~800 words of findings.