Skip to main content

Valenar Territory And Feature Generation

Valenar's production world generation pipeline is not locked here. The current live map is a stepping-in prototype fixture: a once-only SECS map system plus server-side Voronoi geometry, low Territory density, mostly-placeholder geography facts, and random inert Features. Keep prototype behavior clearly separated from future world-scale design: the current example map is not the final world extent, and later maps may be much larger with larger/variable Territories.

Before changing generation docs or related map/territory/feature code, read:

  • docs-site/content/valenar/generation/gd-world-generation-contract.md
  • docs-site/content/valenar/generation/gd-territory-generation-contract.md
  • docs-site/content/valenar/generation/gd-feature-generation-contract.md
  • docs-site/content/valenar/systems/gd-territories-features-sites.md
  • docs-site/content/valenar/ux/gd-territory-dossier.md
  • docs-site/content/valenar/systems/gd-world-pressure-nexus.md

Core Rules​

  • Future world data is the physical source of truth. Valenar imports generated facts through an explicit adapter contract; UI, renderer, and SECS systems do not infer missing geography.
  • Generated Territory facts are host-owned fields. SECS channels are resolved effective gameplay values. Stats are the player-facing labels for these channels. Do not write channel results directly from the host.
  • Territory classes and tags are derived summaries. Numeric facts are the truth.
  • Land and water Territories remain distinct. Large water bodies are water Territories; tiny water features inside land Territories are Territory facts or Features.
  • Features are real generated entities inside Territories. Feature existence is world state; discovery state controls UI visibility.
  • Do not place Features with flat per-Territory random rolls at production scale. Use suitability scoring, density budgets, spacing, conflicts, and story rules.
  • The starting Nexus is a constrained story Feature. Generic settlement suitability must never unlock founding by itself.
  • Generation without validation is incomplete.

Documentation Boundaries​

  • gd-world-generation-contract.md owns the top-level world-data import and validation boundary.
  • gd-territory-generation-contract.md owns Territory records, numeric facts, terrain composition, topology, knowledge, control, and settlement inputs.
  • gd-feature-generation-contract.md owns Feature placement, discovery, actions, causal rewards, site conversion, and Feature validation.
  • UX docs consume generated truth. They do not define spawning rules.