settled-reach/docs/workshops/world-generation/miri-sw1r1.md

title, description, type, status, workshop, subworkshop, agent, round, created

title	description	type	status	workshop	subworkshop	agent	round	created
Miri SW1-R1 — Cultural Generation Product Questions	Product questions for the product owner on how cultural identity flows into world generation	workshop	draft	world-generation	1	miri	1	2026-03-24

World Generation Workshop — Sub-Workshop 1, Round 1: Miri (Worldbuilder)

Topic: How cultural identity flows into world generation — product questions for Jeroen. Date: 2026-03-24 Scope: 5 questions, each with options and a recommendation.

---

Context Check Before the Questions

The Generator Architecture Workshop (February 2026) locked a solid foundation I'm working within. Key confirmed decisions relevant to my angle:

• Heritage roots (D-104, D-105): Seven canonical roots — Frost, Stone, Tide, Vine, Dust, Iron, Salt. Each maps to spatial grammar rules applied at Phase 2 chunk fill.
• Heritage overlay at Phase 2 only (D-104): HeritageGrammarOverlay structs (10 per root) applied during chunk fill by weighted blending. gathering_probability is the one exception evaluated during Phase 1 block planning.
• ZonePalette modifier axis A = heritage root (D-101): Visual identity at a glance, without a label.
• Grid vs. Organic layout modes (D-096): These encode political history (Commission-planned vs. pioneer/growth), NOT heritage root. Cultural grammar and spatial layout mode are currently on separate axes.
• Culture implicit in starting location (D-128): Van Maanen's Star = Van Maanen's Star culture. No character creation menu.
• Trauma intensifies culture, does not transform it (D-107): Design principle already locked — heritage root as amplifier under stress.

The five questions below target genuine gaps the prior workshop did not close.

---

Q1 — How many heritage root profiles need to be authored for v0.2?

The question: We have 7 canonical heritage roots. How many need fully authored profiles (visual grammar, voice modifiers, behavior primitives, naming conventions) before the tycoon bookmark ships?

Why it matters: D-128 says culture is implicit in the starting location. That means v0.2 only requires the heritage blend of the starting district. But if we author too few profiles, we create a setting that visually homogenises the starting system — every district looks like a variation on the same heritage. If we require all 7 upfront, we front-load substantial authoring cost on systems that will be unreachable at launch.

Options:

A. One only — author the dominant heritage root of the starting district (e.g., if Sova Transit is primarily Iron-heritage, author Iron fully). Other roots are blank; generator falls back to default palette. (Minimal cost, visible gap: any NPC or district that carries secondary heritage feels like the default.)

B. Roots present in the starting location's blend — if the starting district is, say, Iron(0.6) + Stone(0.4), author both fully. Other roots are stubs. (Targeted cost, covers the playable surface area for launch.)

C. Three to four "pillar" roots — select the culturally richest contrasting roots as the v0.2 foundation (e.g., Frost, Tide, Iron, Stone), regardless of starting location blend. Gives the setting visible cultural range within the launch system without 7-root authoring. (Medium cost; requires deliberate selection of which roots represent maximal contrast.)

D. All 7 before v0.2 — every root fully authored. (Full worldbuilding surface, high cost, likely a stretch goal.)

My recommendation: B. Author what is genuinely playable at launch. The starting location blend determines the authoring scope. This also forces a prior decision: we need to know the heritage blend of the starting district now, before authoring begins. Consider that a dependent deliverable.

---

Q2 — Does heritage root influence district layout geometry (Phase 1) or only surface

expression (Phase 2)?

The question: Currently D-104 is explicit: heritage overlay applies at Phase 2 chunk fill. D-096's Grid/Organic mode handles spatial structure via political history (Commission-planned vs. pioneer). The question is whether heritage root should also contribute spatial targets during Phase 1 block planning — things like open-space ratio, building proximity density, gathering infrastructure frequency.

Why it matters: A Frost community (individual space valued, privacy is physical distance) should feel geometrically different from a Tide community (collective gathering, proximity is comfort). If heritage only affects surface materials and object placement, two districts with identical Grid/Organic modes will share the same spatial feel. This means a player who understands Frost culture cannot use spatial reading to identify a Frost district before reading any labels. That's a missed legibility opportunity.

Options:

A. Status quo — heritage stays Phase 2 only. Layout is political (Grid/Organic), culture is cosmetic (Phase 2 surface). Simpler architecture, less legibility.

B. Lightweight Phase 1 targets per heritage root. Add 2-3 numeric targets to each heritage root profile: open_space_ratio_target, building_proximity_weight, gathering_infrastructure_weight. These feed into Phase 1 block planning as soft biases, not hard constraints. Grid/Organic mode remains independent. (Low architectural cost, meaningful spatial legibility gain.)

C. Full Phase 1 integration. Heritage root drives block shape preferences, street width distributions, and courtyard/void placements at Phase 1. Requires rearchitecting Phase 1 block planning to accept cultural parameters. (High cost, maximum spatial legibility.)

My recommendation: B. The 2-3 numeric target approach is architecturally cheap and delivers the key design benefit: a Frost district reads differently at the structural level from a Tide district, before the player has read a single label or seen a single NPC. This aligns with D-101's stated goal ("a zone's visual identity must be legible at a glance") but extends it from visual to spatial. D-104 already has gathering_probability in Phase 1 as a precedent — this is extending that pattern.

---

Q3 — How does cultural mixing work at district boundaries?

The question: The setting is explicit that corridors are gradients, not borders. Cultural mixing is real — migration, trade routes, and sequential-hop travel produce blended communities throughout the Reach. But the generator workshop did not define what the generator does when two heritage-differentiated communities are adjacent. How does the boundary between a Frost district and a Tide district behave?

Why it matters: This is where the setting's most interesting human drama lives. The boundary between collectivist and individualist communities, between Commission-heritage and pioneer-heritage, between old and new settlement — these are sources of NPC motivation, economic friction, and player intrigue. If the generator produces a hard cut with no in-between, the world loses the gradients that make it feel real.

Options:

A. Hard district borders. Each district has a single dominant heritage root. Two adjacent districts with different roots have a hard visual/cultural cut. (Simple, legible, but unrealistic and misses the setting's gradient principle.)

B. Weighted blend within boundary districts. Districts adjacent to contrasting heritage districts receive a heritage blend weighted toward both neighbors. A district between Iron(0.8) and Tide(0.8) becomes Iron(0.5)+Tide(0.5). Visually expresses the mixing. (Medium complexity; requires heritage weights to propagate at generation time, not just per-district.)

C. Dedicated hybrid zone archetypes. Create explicit zone types for cultural mixing: "junction quarter," "trade market," "transit node." These zones carry formal cultural-hybrid identity — they are designed places that exist because two cultures meet. (Higher authoring cost but produces the richest gameplay territory. The market between two communities is always more interesting than either community alone.)

D. Passive overlap — mixing only in NPC backgrounds and naming. Districts are culturally monolithic spatially, but NPC generation allows cross-heritage backgrounds, and place names reflect historical mixing. Visual districts are clean; social texture carries the blending. (Low implementation cost, limits spatial legibility of mixing.)

My recommendation: C for urban hubs (Full-complexity districts), B for rural/wilderness. Junction archetypes are already gameplay-rich territory — they're where the most interesting NPCs congregate, where the most ambiguous social signals appear, where the player can most easily operate without tribal affiliation. These deserve deliberate spatial design, not just a blended palette. For smaller or more remote communities, B handles the gradient adequately without requiring a new archetype.

---

Q4 — Does cultural naming derive from generative grammar rules or authored flat lists?

The question: Districts, streets, establishments, and NPCs need names that carry cultural signature. D-138 already noted that Van Maanen's Star naming conventions differ structurally from other cultures and that the name extractor must eventually be culture-aware. The question is whether we author naming rules (syllable patterns, compound structures, phonological constraints per heritage root) or naming lists (finite authored pools the generator draws from).

Why it matters: Naming is the fastest cultural signal the player encounters — before any NPC dialogue, before any visual cues, the name of the street or the building is already communicating cultural identity. A generative grammar produces consistent cultural flavor at infinite scale but requires upfront design investment per heritage root. A flat list is quicker to produce but exhausts in large worlds and creates repetition that breaks immersion.

Options:

A. Flat lists per heritage root. Authored pools of street names, district names, building names. Generator draws from pools. (Fast to produce, visible repetition in large worlds.)

B. Grammar rules per heritage root. Syllable patterns, compound word rules, suffix/prefix inventories enabling infinite unique generation. (High upfront investment, infinite scale, fully consistent cultural signature.)

C. Hybrid: grammar for infrastructure (streets, districts, transport nodes), authored lists for commercial/social establishments. Street names and district names are generated from grammar rules (the world needs these at generation time, and they should feel systematic). Establishment names and colloquial NPC references draw from authored lists (these benefit from authored texture and specificity). (Medium cost, appropriate tool for each layer.)

My recommendation: C. The hybrid approach matches the use cases: streets are procedural infrastructure that needs to scale and feel architecturally consistent; the bar named after a local folktale needs authored specificity to feel real. Grammar for structure, authored lists for flavor. The grammar rules also serve as cultural documentation — they encode the logic of what names in a given heritage root sound like, which feeds Mellanie's voice card work and the LLM re-voicing pipeline (D-138).

---

Q5 — How does galactic corridor position map to heritage root probability weights?

The question: The world has macro-level cultural corridors — the North Reach, South Reach, East Reach, West Reach, and the core — each with dominant cultural drifts from original settlement patterns and migration history. Individual systems sit within these corridors and carry regional heritage blends. But the generator workshop didn't define how a location's corridor position translates into a heritage root probability weight on its districts.

This is workshop brief question 6 restated concretely: "Corridor heritage → architectural style → tile palette selection" — where does the corridor → heritage assignment happen, and who authors it?

Why it matters: If heritage root blends are fully hand-authored per system, the generator can't produce new locations without designer input. If heritage derives from corridor position automatically, we get emergent cultural geography — the world feels like it has history even in locations no one has scripted.

Options:

A. Per-system hand-authored heritage blends. Each system wiki entry specifies its heritage root weights. Generator uses these directly. (Full authorial control, doesn't scale to unpopulated systems or procedurally generated frontier worlds.)

B. Corridor zone → heritage probability table. A mapping table defines heritage root probability weights per corridor zone (and distance from galactic core). New systems draw their initial heritage blend from this table plus a seed-driven variance. Authors tune the table; the generator handles individual systems. (Scales to procedural worlds; corridor cultural identity becomes a tuneable parameter. Requires authoring the corridor table once, not per-system.)

C. Cultural drift simulation. Heritage roots diffuse across the galactic map based on simulated migration, distance from origin worlds, and trade route topology. The emergent cultural geography reflects actual setting history. (Most ambitious, highest authoring investment, endgame vision — not v0.2.)

My recommendation: B for v0.2. A corridor probability table is a one-time authoring deliverable that enables the generator to produce culturally coherent locations anywhere in the Reach, not just at hand-authored systems. It's also the setting document that encodes the macro-cultural shape of the universe — who settled where, what waves of migration produced what blends. I can draft this table once Jeroen confirms the corridor cultural identities. Option C is what this table eventually approximates; B is the practical version for launch.

---

Summary Table

#	Question	My Recommendation
1	How many heritage roots to author for v0.2?	B — roots present in starting district blend only
2	Does heritage influence layout geometry or surface only?	B — lightweight Phase 1 numeric targets per root
3	How does cultural mixing work at boundaries?	C (urban hubs) + B (rural/wilderness)
4	Naming from generative grammar or flat lists?	C — grammar for infrastructure, lists for establishments
5	How does corridor position → heritage blend?	B — corridor probability table

---

Upstream Dependency I'm Flagging

Before any of these questions can be fully answered, one prior question needs Jeroen's input:

What is the heritage root blend of the starting district (Sova Transit / Van Maanen's Star)?

This is the foundational content decision that all of Q1, Q2, and Q3 depend on. I have working hypotheses from the setting history (Sova Transit as a 40-year-old logistics hub with Commission infrastructure and pioneer-era organic growth suggests an Iron/Stone blend with Tide undertow from the tight-community dynamics of a small-station population). But this is a product decision, not a worldbuilding derivation — the blend should reflect what emotional register Jeroen wants the starting experience to carry.

---

Author: Miri Date: 2026-03-24 Status: Ready for product owner review.