settled-reach/docs/workshops/generator-architecture/miri-round3-supplement.md

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

title	description	type	status	workshop	agent	round	created
Miri Round 3 Supplement — Destructible Boundaries	Destructible boundaries, vertical social stratification, entity-carried chunks, and grid vs organic heritage	workshop	archived	generator-architecture	miri	3	2026-02-27

Generator Architecture Workshop — Round 3 Supplement: Miri (Worldbuilder)

Topic: Destructible boundaries, vertical social stratification, entity-carried chunks (trains/ships), grid vs. organic by heritage root Date: 2026-02-27 Context: This supplements miri-round3.md, which was filed before the full Round 3 broadcast arrived. Four directives from the broadcast required worldbuilding perspective that the main document didn't address.

---

Supplement 1: Destructible Boundaries — What's Behind the Wall

Lead directive: what's behind a wall the player blows open?

This is a pure worldbuilding question before it's a technical one. The answer depends on WHAT THAT WALL IS DOING in the cultural and historical context it was built in.

1.1 Wall Typology — Why Walls Exist

Walls are built for specific reasons, and the reason determines the worldbuilding content on the other side:

Privacy walls — separating domestic/private space from public/semi-public space. Common in Spice, Jade, and Frost heritage settings. What's behind them: domestic life, family space, private arrangements that weren't meant to be observed. The content is intimate, often mundane, occasionally revealing.

Authority walls — defining institutional territory. What Commission jurisdiction looks like physically: reinforced barriers, access control, clearly marked transitions. Behind Commission authority walls: operational infrastructure (records storage, personnel areas, evidence holding). The content is institutional — paperwork, equipment, records of what the Commission has been doing.

Security walls — concealing high-value assets. Syndic logistics operations, grey economy storage, faction caches. These are built to HIDE something. What's behind them is the thing they were hiding. The content is the grey economy made physical: unlicensed inventory, contraband, documentation of prohibited activities, sometimes people.

Structural walls — load-bearing divisions that weren't primarily about separation but became that. What's behind them depends on era tag: Era 1 walls sealed over may contain original infrastructure (utility runs, passages that were blocked when the era changed), sometimes abandoned equipment or materials left in place when the area was repurposed.

Cultural/heritage walls — built for reasons that only make sense in specific heritage contexts. A Spice-heritage compound wall defines family honor territory. A Frost-heritage barrier between residential and operational is about psychological separation (noise, smell, the intrusion of public life). An Iron-heritage wall around the union hall is a claim of territory.

1.2 Heritage Root and What the Breach Means

Blowing open a wall is not culturally neutral. What matters is not just what's there but how the community interprets the act of breach.

Frost heritage: Walls are the physical expression of privacy as a value. Breaking through one is a profound violation regardless of what's found. A Frost community will respond to an unauthorized breach even if the contents are innocent. The breach itself is the offense. For the investigator or assassin: entering a Frost space through a destroyed wall marks them as someone who doesn't respect boundaries — which in a Frost culture is a serious social flag.

Iron/Dust heritage: Walls define collective territory. Breaching a wall into a union hall or communal storage means intruding on the group's shared space — it's an attack on the collective. The community responds collectively. The content behind the wall (collective resources, organizing records, mutual aid supplies) is community property, and damaging access to it is an attack on the community.

Spice heritage: The family compound wall is honor-adjacent. A breach is an insult to the family. What's inside is family-private space — domestic, intimate, potentially containing the family's most protected relationships and secrets. The breach creates a vendetta obligation in some Spice-heritage contexts.

Salt heritage: Walls are contractual, not sacred. If you breach a wall, you owe something for it. The content is commercial inventory, records, assets. A Salt community may tolerate the breach if appropriate compensation is offered. They'll want payment.

Arc heritage: Walls around intellectual/operational spaces contain RECORDS. The Arc community will care intensely about the integrity of what's behind — not the breach itself but the potential disruption to ordered knowledge. Behind an Arc wall: labeled storage, research records, documentation of ongoing work. The content is information in organized form.

1.3 Era Tag and Physical Contents

The era tag on the wall's block determines what's behind it structurally:

Era 1 wall (sealed over time): The oldest sealed spaces contain the building's original purpose. In a station, this means the infrastructure of earliest construction — original transit passages, the plumbing and electrical paths laid before the upper layers, sometimes abandoned rooms that were simply walled off when the superstructure changed. Content includes original structural materials (different from the visible surface), possibly Era 1 equipment abandoned in place, historical markers (founding dates, workers' marks in the walls, construction refuse).

Era 2 wall (intermediate period): This was sealed during the commercial/operational expansion. Behind it: infrastructure supporting an intermediate-era function that's no longer visible from the current space. A logistics terminal that became a residential corridor — the Era 2 wall might conceal cargo-bay equipment, commercial-grade storage installations, commercial transit systems. Also: the era transition often produced conflict. Era 2 walls may seal spaces that were abandoned during economic disruption — with the contents of that disruption preserved.

Era 3 wall (recent): Recent walls are planned. What's behind them is known — or should be. The absence of official knowledge about Era 3 content is itself suspicious. A recently sealed wall in an active district with no official record of what's there: someone sealed something deliberately and recently.

1.4 Generator Requirement

Every block face that can be breached must carry a behind_boundary descriptor:

behind_boundary:
  content_type: private_domestic | authority_operational | economic_storage |
                structural_original | abandoned_era | active_concealment
  era: era1 | era2 | era3
  cultural_sensitivity: low | medium | high | extreme
  # extreme = Spice family compound; Iron union hall; Frost private residential
  contents_hint: null | infrastructure | records | inventory | persons | evidence
  breach_consequence:
    immediate: null | alarm | NPC_response | environmental_hazard
    social: none | community_sanction | faction_response | vendetta_trigger

The behind_boundary descriptor is generated at Phase 1 (district skeleton / block planning) and stored in the BlockSkeleton. It is NOT revealed to the player until the wall is breached — but it informs the generation of what gets spawned when the breach occurs.

---

Supplement 2: Vertical Scale — The 50-Floor Skyscraper

Lead directive: how does a 50-floor skyscraper emerge from the generator?

2.1 Why Vertical Space Exists in Specific Cultures

Vertical architecture is not culturally neutral. Cultures build tall for different reasons, and the reason shapes the internal vertical social organization:

Corporate/Syndic cultures build tall for efficiency and status display. The building is an asset and a symbol. Height signals wealth. This creates the classic vertical hierarchy: lobby (public/commercial), office floors (operational), executive floors (top). Frost + corporate economic function produces this pattern reliably.

Institutional/Commission cultures build tall for administrative organization and security. The building is infrastructure. Height creates defensible institutional core. The pattern is different: lower floors are public-facing (reception, public services), middle floors are operational, upper floors are not executive suites but records and security operations. Access tightens as you go up.

Labor/Iron cultures do NOT build tall by choice. Vertical housing is often imposed by economic constraint (urban density) or by prior ownership (inhabiting a building built by a different cultural actor). Iron-heritage communities in vertical buildings create horizontal solidarity networks across floors — the floor as community unit, not the building as hierarchy.

Spice-heritage communities adapt vertical architecture to family organization. The extended family may occupy multiple floors of the same building with internal connections between floors — a vertical family compound. Outsiders may occupy other floors of the same building with no relationship to the Spice-family floors.

2.2 The Vertical Social Hierarchy

The Z-level model established in D-093 (z=0 maintenance, z=1 operational, z=2 institutional/gate) maps onto vertical buildings differently than onto the station's broader district structure.

In a tall building within a station or urban setting:

Floor range	Social function	Typical occupants	Cultural variation
Ground (z=0 equiv.)	Public-facing commerce or passage	Anyone; high traffic	Little — street interface is universal
Lower floors (z=1-3)	Work functions, commercial operations	Workers, service functions	Heavy — Iron cultures push worker facilities down; Frost cultures push worker facilities down differently (clean separation)
Mid floors	Administrative, secondary residential	Mixed	Moderate — depends on economic function
Upper floors	Residential (valuable) OR operational (secure)	Wealth OR security	Strongest cultural variation here
Top floors	Penthouse OR secure operations	Varies entirely by culture	Frost-corporate = executive; Commission-Jade = secure records; Arc = observatory/library; Iron = reclaimed community

The important conflict: In station architecture, z=0 is MAINTENANCE (lowest status); z=2 is institutional/gate (highest). In standard tall buildings, the top floor is highest status. When a tall building is grafted onto station spatial logic, these conventions can CONFLICT — creating the visible cultural tension of "who actually has power here?" The building where the maintenance workers are on the same floor as the executive offices (because the executive floor is near the gate infrastructure) tells you something specific about this station's power structure.

2.3 Generator Requirements for Vertical Scale

The current D-094 hierarchy (region/district/block/chunk) handles z-levels via stacked chunk layers. A 50-floor skyscraper is not 50 district-level z-levels — it's 50 chunk-stack layers within a SINGLE block footprint.

Setting note for Tyre: A skyscraper is a multi-z-level single-block structure with:

• One or more block footprints on the ground level
• N chunk layers stacked, each 64×64 tiles, each z-level a floor
• The social profile of the BUILDING follows the vertical hierarchy rules above
• Each z-level chunk inherits era tags from the block but has a separate floor_function: FloorFunction field

The generator needs to know, at block planning time (Phase 1 Stage 3), whether a block is a TOWER BLOCK — flagged to generate multiple z-levels rather than a single operational level. This is a BlockSkeleton property: tower: Option<TowerConfig> where TowerConfig records number of floors, floor function assignments, and the vertical social profile derived from the society profile.

The worldbuilding content per floor is derived from the vertical social hierarchy table above. The generator applies the table with heritage root modifiers. An Iron-heritage corporate building and a Frost-heritage corporate building with the same number of floors will have their social zones distributed differently.

2.4 What Makes the Skyscraper Interesting Gameplay-Wise

Vertical information asymmetry: People on the upper floors have information about what happens on the lower floors (they commissioned it, they receive reports, they ordered it). People on the lower floors have information about the upper floors that upper-floor residents don't know they have (maintenance workers know what equipment is running, what's being shipped, who visits). The skyscraper is a compressed information gradient. The investigator ascending through a corporate tower is climbing the information ladder physically.

Cross-floor social triangles: A triangle where NPC A is on floor 3, NPC B is on floor 17, and NPC C is on floor 42 is a cross-floor triangle. The staging ground challenge is different — the player needs ACCESS to multiple floors to work the triangle. The access tier system maps to floors in a tower, not just horizontal zones.

The assassination tower problem: A high-value target on the 42nd floor has an implied protection architecture: limited vertical access, controlled entry points, security in the vertical corridor. The assassin's problem is a vertical architecture puzzle. Escape routes are the same — you can go down but not sideways until you exit the building. The informal zone in a corporate tower is the maintenance infrastructure (utility shafts, service elevator, roof access).

---

Supplement 3: Entity-Carried Chunks Beyond Vessels — Trains and Spaceships

I covered maritime vessels in Round 2. Round 3 makes entity-carried chunks CORE and adds trains and spaceships. The worldbuilding differs meaningfully per vehicle type.

3.1 Trains — The Bounded Linear Society

The maritime vessel is bounded-spherical (you can move throughout the vessel, which is a small total space). A train is bounded-linear — you can move through it from end to end, but the ends are as far apart as they are.

The train's social grammar:

Trains compress multiple social tiers into a physical sequence. The typical car sequence (from front/premium to rear/economy): observation/premium → standard passenger → general class → cargo. This is a PHYSICAL EXPRESSION of the social hierarchy that the player can observe simply by walking through the train.

Heritage root variation on train social organization:

• Frost heritage passenger car: minimal interaction, compartmentalized seating, high privacy expectation. Everyone minds their own business. Information is not shared.
• Tide heritage passenger car: communal orientation, groups eat together, children move between cars, conversation across compartment boundaries is normal. Information flows freely — and includes information about everyone on the train.
• Iron heritage work train (carrying labor to a site): collective space, political awareness, workers know each other, mutual solidarity active. An outsider on an Iron labor train is immediately noticed.

What makes trains distinctive for gameplay:

• Temporal pressure: the destination is known and approaching. Whatever needs to happen on the train must happen before arrival.
• Witness compactness: everyone who matters to the scenario is on the same vehicle. No one leaves. Cross-examination and confrontation are possible in ways that aren't in open-world settings.
• Social compression: the shared experience of travel creates artificial intimacy. Dating sim dynamics accelerate on trains because you're physically in close proximity with the same people for extended periods.
• Information lock: what happens on the train is sealed until arrival. The investigation play on a train is fully contained — but also can't get outside support.
• Assassination on a train: a CLASSIC scenario type for a reason. The target can't escape. The witnesses can't leave. The aftermath begins at arrival. The assassin's problem is managing all of this in a confined linear space.

Generator requirement for trains: SettingType::BoundedLinear — a variant of the bounded_mobile tag. The chunk is mobile, carried by an entity (the train), and has a linear access topology (you can progress from one end to the other, with optional locked compartments). The social site tags on a train are car-typed: premium_car, general_car, cargo_car, service_car, each with its own social density and access rules.

3.2 Spaceships — The Total Information Environment

A spaceship in transit is the most extreme information asymmetry environment in the setting. Not because it's bounded (so is a vessel or a train) but because it is between systems.

What "between systems" means culturally:

During interstellar transit via the horizon gate network, the ship is in the gate conduit — physically in neither origin nor destination system. Normal institutional jurisdiction is suspended (which Commission has authority in transit?). Normal communication with external parties is interrupted (no message traffic possible in transit). The crew and passengers are alone in a way that no other setting achieves.

The sociological effect: transit strips social roles. The powerful person on the ship cannot call for backup. The institutional authority figure cannot enforce through external threat. The information bottleneck is total — nothing you know or reveal can exit the ship until arrival.

Heritage root behavior during spaceship transit:

• Frost: doubles down on privacy. In a suspended institutional environment, the default is LESS interaction, not more. Information is even more guarded.
• Tide: expands. The community of the ship becomes the relevant community for the duration. Social bonds form faster. Information flows within the ship-community.
• Arc: the transit period is time for discourse. The suspended institutional context is an opportunity for conversation that wouldn't happen with normal social stakes present.
• Salt: commerce that couldn't happen under normal jurisdiction now can. The transit period is a grey-market window.

The spaceship social site types:

• Crew quarters — insider space (crew only), the social hub of the working community
• Passenger areas — mixed access, varying by class of ticket
• Bridge/operations — institutional space, crew credentials required
• Cargo hold — the informal zone equivalent (no social occasion for most passengers to be there)
• The airlock — the most extreme "place too small to be safe" (Ozzie's spatial archetype #5)

Assassination on a spaceship: extreme in both directions. The target CANNOT ESCAPE until arrival. But neither can the assassin. Evidence management is impossible — there's nowhere to dispose of evidence that won't be found when the ship docks. Post-arrival institutional scrutiny begins immediately. The spaceship assassination is only viable if the investigation can be controlled at destination, which means the assassin needs assets waiting at the other end.

3.3 The Cultural Grammar of Transit

Across all entity-carried chunks (vessel, train, spaceship), one cultural constant applies: transit reveals character. The normal social infrastructure that regulates behavior (institutional enforcement, community surveillance, professional role performance) is attenuated in transit. What people do when the normal constraints are loosened tells you who they actually are.

This is the deepest gameplay value of entity-carried chunks: not just bounded space for investigation, but a setting where the information asymmetry becomes especially acute because everyone's masks slip a little.

Generator rule: Entity-carried chunks should have a transit_social_modifier that adjusts:

• trust.building_rate: increases (forced proximity)
• social.privacy_level: decreases (can't leave)
• cultural_norms.enforcement_level: decreases (institutional authority attenuated)
• information_flow.internal: increases (nowhere else to talk)
• information_flow.external: blocked until arrival

---

Supplement 4: Grid Breathing — Which Cultures Produce Which

Lead directive: BOTH grid and organic. Some blocks are grid, some organic chaos. Architecture must support both.

This is a worldbuilding question with a clear answer: grid vs. organic is determined by who built it, when, and under what power conditions.

4.1 Grid = Power Imposed; Organic = Power Negotiated

Grids emerge when:

• A single authority planned the space before construction
• The authority had sufficient power to enforce the plan throughout construction
• The time pressure was low enough for systematic planning
• The cultural value is ORDER as inherently correct

Organic patterns emerge when:

• Multiple actors built incrementally over time
• No single authority had full control
• Time pressure forced immediate construction without planning
• The cultural value is FUNCTION over form
• The terrain demanded deviation (natural features that planners worked around)

This means the district's founding conditions are the primary driver:

Founding condition	Grid tendency	Organic tendency
Commission-planned	STRONG	Weak
Syndic corporate development	Strong	Weak
Colonial imposition	STRONG	Weak
Worker/labor organic settlement	Weak	STRONG
Frontier/pioneer	Weak	STRONG
Spice family compound networks	—	Medium (family logic, not geometry)
Arc institutional design	Strong	—
Gradual accretion over eras	Weak	STRONG
Single development event (urban planning)	STRONG	—

4.2 Heritage Root and Grid Preference

Heritage Root	Preference	Why
Frost	Grid (operational zones), organic (residential)	Work is organized; private life doesn't need to be legible to others
Tide	Organic	Community space evolves from social patterns, not planning
Iron	Organic	Workers built their own spaces; no planner controlled the process
Spice	Semi-organic	Follows family network logic — clusters, not grids
Jade	Grid with deliberate irregularity	Order appreciated; but variety is necessary for beauty
Dust	Organic	Survival-driven; build what you need, where you need it
Vine	Organic	Social warmth = built space following relationship patterns
Salt	Grid (commercial zones)	Commercial clarity; buyers need to find sellers
Stone	Semi-grid	Permanence favors planning; but generational accretion adds organic layers
Arc	Grid	Rational organization is a core value

4.3 The Within-District Grid/Organic Mix

This is where it gets interesting for the generator. A single district can contain BOTH grid and organic sections, because:

1. Era stratification: Era 1 sections are organic (pioneer/frontier construction). Era 3 sections are grid (planned development). The same district has the palimpsest of both.

2. Economic function zone differentiation: Commercial and institutional zones (Syndic, Commission) are grid; residential and maintenance zones are organic. The commercial street is straight; the workers' housing behind it is a warren.

3. Cultural overlap: A district with mixed heritage (Salt-commercial + Iron-residential) has grid commercial blocks and organic residential blocks. The edge bleed between them is the zone where the two grammars fight.

4. Power vacuum areas: Spaces that no authority planned — because no authority wanted them — are organic. The informal zone is almost always organic because it emerged from use, not planning.

Generator rule: The BlockSkeleton's ChunkLayout already handles L-shapes and merged footprints. The grid vs. organic distinction is upstream: at block planning time, each block should be assigned a street_geometry: GridAligned | OrganicDeviation property. Adjacent blocks can have DIFFERENT street_geometry values, creating the within-district mixing the lead directive requires.

What drives the assignment:

• Era 1 blocks: OrganicDeviation default (unless founded by a specific planning authority — Colony = GridAligned even in Era 1)
• Era 2 blocks: weighted by economic function (commercial/institutional → GridAligned; residential/maintenance → OrganicDeviation)
• Era 3 blocks: weighted by faction presence (Commission/Syndic presence → GridAligned; absent → depends on drift stage)
• Cultural heritage overlay: Arc/Frost-operational/Salt → weight toward GridAligned; Iron/Dust/Tide/Vine → weight toward OrganicDeviation

The street grid rotation (Ozzie's persistent demand): Two adjacent districts with different orientations are plausible when: the districts were planned by different authorities at different times, or when terrain features forced different orientations. A Commission-built district planned along the station's primary axis is GridAligned at 0°. An organically grown district adjacent to it, predating the Commission expansion, may have a street orientation that aligned to the first permanent structure (the original tavern, the first cargo bay), not the Commission's axis. This produces the 15-23° rotation Ozzie is asking for.

The generator needs to track not just GridAligned vs. OrganicDeviation but street_orientation: f32 (rotation in degrees from the district cardinal axis). GridAligned blocks inherit 0° from the district plan. OrganicDeviation blocks can deviate ±30° based on historical founding conditions.

---

Summary of Supplement

Destructible boundaries: Behind walls is heritage-dependent and era-dependent. Privacy walls (Frost/Spice/Jade) protect social/cultural content; security walls protect economic content; structural walls contain historical content. Each breach has a cultural_sensitivity rating and a social_consequence that fires based on cultural context, not just what's found. Requires behind_boundary descriptor on every block face.

Vertical scale: A 50-floor skyscraper is a multi-z-level single-block tower with a vertical social hierarchy. That hierarchy is heritage-root-derived: corporate culture = bottom labor / mid operations / top executive; Iron-heritage occupation = collective floor reclamation; Commission-institutional = public access at base, secure operations at top (inverted from corporate). Requires TowerConfig in BlockSkeleton.

Entity-carried chunks (trains + spaceships): Trains are bounded-linear with class-sequence social grammar. Spaceships are institutionally suspended environments — the most extreme information asymmetry because jurisdiction, communication, and social enforcement are simultaneously absent. Both types have a transit_social_modifier that adjusts trust-building rate, privacy level, and information flow. What people do when constraints are lifted reveals character.

Grid breathing: Grid = power imposed (Commission/Syndic planning, Arc heritage, Era 3 development). Organic = power negotiated (Iron/Dust/Tide settlement, Era 1 foundations, maintenance/residential zones). Within a district, BOTH can and should appear in different blocks. street_orientation: f32 enables the inter-district grid rotation Ozzie is demanding — organically-settled districts have orientations inherited from their first permanent structure, not from the Commission's coordinate system.

---

Author: Miri Date: 2026-02-27 Status: Supplement to Round 3 — filed separately to keep Round 3 focused.