Files

T

jpmschweitzerandClaude Opus 4.6 9a5c9c4408 docs(docs): add frontmatter to generator-architecture workshop

Standardized YAML frontmatter on all 38 files with title, description,
type, workshop, agent, and round fields.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-13 23:40:37 +01:00

23 KiB

Raw Permalink Blame History

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

title	description	type	status	workshop	agent	round	created
Gestalt Round 1 — Systems Design Requirements	Gameplay loop requirements and information asymmetry guarantees for the generator	workshop	archived	generator-architecture	gestalt	1	2026-02-27

Generator Architecture Workshop — Round 1: Gestalt

Role: Systems Design / Gameplay Loop Requirements Date: 2026-02-27 Workshop: Generator Architecture (#562)

Framing Statement

The generator must produce spaces that create information asymmetry — not just visually plausible locations, but locations where what you know, who you know, and where you can go produce fundamentally different gameplay experiences. Every spatial guarantee below is ultimately a guarantee about asymmetric information production.

Let me break down what the generator actually needs to produce, mechanically.

1. What Gameplay Loops Does the Generator Need to Support?

The game has five confirmed gameplay loops (D-007 five pillars). The generator must support all five with spatial affordances.

Loop 1: Observation Loop

Mechanic: Player moves through space, maintains Careful/Walk stances (D-053), observes NPC tells, detects anomalies, fires monologue recognition events. Generator requirement: Every district needs spaces where NPCs are observable from cover — chokepoints, corridors, elevated positions, furniture arrangements that create natural sightline asymmetry. The functional cluster (D-025: 15-40 tile connected space with internal sightlines) is the atomic observable unit. The generator must instantiate these; it cannot produce districts where all spaces are either completely open or completely enclosed.

Loop 2: Investigation Loop

Mechanic: observe → notice → follow → discover. Three confirmed path types from D-093 (Path A: pattern/digital, Path B: physical/spatial, Path C: institutional/social). Each path yields unique evidence inaccessible to the other paths. Generator requirement: Every generated district must support all three path types. This means the spatial hierarchy must guarantee: (A) a zone with Meridian/camera log access (Path A), (B) a physical traversal corridor with acoustic gaps or spatial quirks (Path B), and (C) a social venue where institutional relationships develop (Path C). These are spatial guarantees, not content guarantees — the generator places the slots; templates fill them.

Mechanic: Player builds rapport, climbs trust tiers (D-075), unlocks dialogue options (D-062 — invisible until unlocked), triggers unprompted disclosures. Social sites (D-025: 4-8 NPCs within 15-40 tile cluster) are the primary stage. Generator requirement: Every district needs at least one social venue (bar-type social site) that is publicly accessible without authority credentials, AND at least one workplace social site where insider access is required. These are not the same space. The generator must distinguish them at the zoning/amenity stage.

Loop 4: Stealth/Exposure Loop

Mechanic: Player manages their own information exposure — who saw them, where they went, what was recorded. Meridian dead spots (D-093: maintenance corridors, z=0 layer) are critical for both archetypes. Generator requirement: Every district must have at least one zone with degraded Meridian coverage where private exchanges can occur. The smuggler needs it for ring operations. The detective needs it for confidential source contact. Without this guarantee, both archetypes lose a core tool.

Loop 5: Daily Life / Routine Loop (Substrate)

Mechanic: Player witnesses NPC routines, builds complacency, creates emotional attachment that makes contamination hit harder (D-023: "daily life is the substrate; conspiracies are weather"). D-031 day phases drive NPC routine transitions. Generator requirement: The district must have transit nodes (encounter nodes where NPC routing creates observable patterns), temporal rhythm affordances (NPC populations change by day phase), and density variation (not all spaces always populated). The transit platform from D-093 is the canonical example — workers arrive bar-side at shift change, the pattern is observable.

2. What Must the Generator Guarantee?

These are non-negotiable spatial guarantees. If a generated district fails any of these, it cannot support the core gameplay loops.

Guarantee 1: Surveillance Chokepoint

Definition: A spatial bottleneck where NPC traffic must pass and is observable from a fixed position by a player in Walk or Careful stance. Why mandatory: The observation loop (Loop 1) requires this. Without at least one chokepoint, the player has no reliable observation position. Evidence gathered here feeds Path A and Path B investigation. Example from D-093: Gate concourse (40×8 sim tiles, public zone) + transit platform (bar-side encounter node, ~12×8 visual). These are chokepoints by geometry — narrow corridors NPCs must traverse. Generator mechanism: Infrastructure stage must place at least one high-traffic corridor connecting the transit ingress to the district's social sites. Block generation must not route NPCs around it.

Guarantee 2: Quiet Zone (Meridian Dead Spot)

Definition: A zone with low or absent Meridian coverage and low ambient NPC traffic, suitable for private exchanges. Why mandatory: The stealth/exposure loop (Loop 4) requires this for both archetypes. The ring (and its analog in any generated district) needs operational dead spots. Without this, the 30/50/20 entanglement model (D-029) has nowhere to put the entangled 20%. Example from D-093: Maintenance corridors at z=0 (minimal Meridian, no general NPC traffic). Restricted storage corridor (acoustic gap, accessible only via specific physical path). Generator mechanism: Infrastructure stage assigns Meridian coverage per zone. Zoning stage marks these zones. At least one zone per district must be flagged meridian_coverage: degraded or minimal.

Definition: A social venue with D-025 cluster properties (4-8 NPCs, 15-40 tile connected space, internal sightlines) that is publicly accessible — no access credentials required. Why mandatory: Social manipulation loop (Loop 3) requires a space where both archetypes can build relationships. Bar-type social sites are the canonical form. Without this, trust tier progression has no natural stage. Example from D-093: The Last Shift / "Lera's" (bar). Public access, established regulars, D-025-compliant cluster. Generator mechanism: Amenities stage must instantiate at least one bar/social venue type. Its chunk fill must satisfy D-025 sightline requirements — the quarter system cannot fragment this into isolated enclosed rooms.

Definition: A functional cluster where employment/membership (not authority) grants access that the detective archetype cannot obtain through institutional credentials. Why mandatory: Asymmetric access between archetypes (D-007 pillar 1) requires at least one zone where the smuggler's insider knowledge is an advantage. This is what makes two-character play produce fundamentally different games (D-027 criterion 2). Example from D-093: The Terminal (logistics hub) — freight workers have insider access, detective requires Commission warrant to access operational areas. Generator mechanism: Zoning stage marks access_tier: insider zones that require employment/social credentials, not authority credentials.

Guarantee 5: Institutional Authority Zone (Restricted Access)

Definition: A zone where authority credentials (detective archetype) provide access that the insider (smuggler archetype) cannot obtain through social rapport. Why mandatory: Mirror of Guarantee 4. Both archetypes must have at least one access advantage the other lacks. This is the mechanical expression of "two keyholes on the same world" (D-027). Example from D-093: Gate cluster restricted zones — Commission inspector access; gate aperture chamber (8×4 restricted); observation gallery (z=2, Commission-only). Generator mechanism: Zoning stage marks access_tier: restricted/authority zones. At least one per district.

Definition: The district's NPC population must form at least 2 active triangles (D-024 minimum: "2 per template minimum, 1 cross-template"). Triangles require NPCs with conflicting interests positioned in overlapping spatial zones. Why mandatory: Triangles are "the atomic unit of social intrigue" (D-024). Without them, investigation and social manipulation loops have no payoff. The 30/50/20 model (D-029) requires triangles to exist across all tiers. Generator mechanism: Population stage assigns NPCs with conflicting Want/Secret/Relationship axes. District skeleton output must include at minimum: 2 triangles whose members' daily routines bring them into shared spatial zones. Cross-template triangle (D-024 minimum) means members must span at least 2 social sites.

Guarantee 7: Three-Path Investigation Structure

Definition: Three distinct evidence chains, each requiring different spatial access or social credentials. Why mandatory: Path A/B/C structure from D-093 is the mechanical proof-of-concept for investigation gameplay. A single investigation path collapses asymmetric information into a linear puzzle. Generator mechanism:

Path A (pattern/digital): requires a zone with Meridian/camera access point
Path B (physical): requires a physical traversal route with at least one acoustic anomaly or spatial gap
Path C (institutional/social): requires a social site where rapport-building yields unique evidence

Each path must produce at least one piece of evidence not obtainable via the other paths.

3. How Do the Pipeline Stages Map to Gameplay-Relevant Structures?

Taking the Cities Skylines top-down pipeline as the working model:

Geography
  → Infrastructure (transport nodes, utilities, Meridian coverage)
    → Amenities & Services (social site types, access tiers)
      → Population (NPC count, entanglement rate, triangle seeding)
        → Zoning (access tier assignment per zone)
          → Block generation (multi-block reservations, functional type per block)
            → Chunk fill (social site template instantiation, sub-chunk quarter assignment)

Geography → Spatial Affordance Type

Gameplay product: Determines what kinds of spaces are even possible.

Station → constrained corridors, z-level variation, Meridian infrastructure baked in
Planet-side → open space, variable Meridian coverage, weather effects (D-050: fog degrades vision cones equally)
Orbital → low gravity implications, different spatial scale The generator doesn't need to solve this in v0.1 (one station, one district). But the architecture must accept geography as an input to every downstream stage.

Infrastructure → Surveillance + Stealth Topology

Gameplay product: Where observation is rewarded; where privacy is possible. Critical generator outputs at this stage:

Transit node placement → chokepoint geometry (Guarantee 1)
Meridian coverage assignment per zone → quiet zone placement (Guarantee 2)
Utility corridor routing → maintenance spine, provides physical traversal path for Path B
Z-level assignment → which spaces are at ground level vs. elevated vs. sub-level (affects LOS per D-066)

Key design requirement: Infrastructure stage must not be purely functional — it must be evaluated through "does this produce interesting observation positions and interesting private zones?"

Gameplay product: Which social loops are available and where. Critical generator outputs:

Social venue (bar-type) → public social site, social manipulation hub (Guarantee 3)
Workplace (terminal-type) → insider access zone (Guarantee 4)
Institutional space → authority access zone (Guarantee 5)
Medical/service → secondary social contact points, NPC routing attractors

This is where the D-025 "social site / functional cluster" concept is first instantiated as a type, not yet filled. The amenities stage selects template tags; the chunk fill stage instantiates the template.

Population → Triangle and Entanglement Seeding

Gameplay product: The human drama that investigation reveals. Critical outputs:

NPC count per zone → density sufficient for 30/50/20 split (D-029)
Entanglement rate → seeded per-game, varies to prevent metagaming (D-029)
Triangle assignment → minimum 2 active triangles (D-024), placed across confirmed social sites
NPC axis rolls → Want/Secret/Relationship/Routine assigned; these must produce spatial conflicts (NPC A works at the terminal but secretly meets NPC B in the maintenance corridor)

Critical relationship with zoning: Population and Zoning must be jointly optimized. An NPC with a secret that requires access to a restricted zone must be assigned a role that gives them that access. The generator cannot assign secrets that have no plausible staging ground.

Zoning → Access Tier Palette

Gameplay product: The invisible layer of gates that defines what each archetype can see. Zone types required (from D-093 example):

public → anyone can enter
semi-public → soft social gate (regulars, workers)
semi-private → employment/insider required
private → insider + relationship required
restricted → authority credentials required
commission-only → detective-archetype exclusive
maintenance → ring-insider exclusive or physical bypass required

Key design requirement: Every district must have at minimum one zone from each end of the spectrum (public ↔ restricted/maintenance). Middle tiers provide the interesting gameplay — they're contestable.

Block Generation → Multi-Block Structure Reservation

Gameplay product: The "large civic structures" (gate terminals, stadiums, gov buildings) that anchor district identity and create mandatory routing patterns. Critical requirements:

Reserve multi-block footprint before chunk fill runs
Multi-block structures create natural chokepoints at their approaches (Guarantee 1)
They contain the institutional access zones (Guarantee 5)
Their internal layout is constrained but not dictated — a gate terminal must have a gate concourse (public) AND a restricted zone; exact dimensions are filled at chunk level

Gameplay product: The specific spaces players actually inhabit. This is where D-025 templates are instantiated. The chunk fill stage:

Selects a social site template tag (assigned at amenities stage)
Configures sub-chunk quarters for that template's spatial requirements
Places NPC slots, interaction points, overhearing positions, evidence anchors
Ensures D-025 sightline requirement within the cluster's tile footprint

4. What Constraints Does the Triangle Template System (D-025) Place on Chunk Fill?

This is the critical mechanics question. Let me map it precisely.

Constraint 1: Connected Space Continuity (15-40 sim tile radius)

D-025 says: The functional cluster is "15-40 tiles of connected space with internal sightlines." Constraint on chunk fill: The sub-chunk quarter system must not produce fully enclosed, sightline-isolated quarters within a single social site's footprint. A 64×64 sim tile chunk (32m) can fit a 40-tile cluster comfortably — BUT the quarter merge/split rules must preserve internal connectivity. Practical rule: If a social site spans N quarters, all N quarters must share at least one sightline corridor. A 2×2 quarter full merge (open floor) trivially satisfies this. An L-shaped 3-quarter configuration must not have the interior angle be a solid wall.

Constraint 2: Internal Sightline Preservation

D-025 says: "physical cluster defines spatial identity (sightlines, overhearing, public/private)." Constraint on chunk fill: Quarter configurations that fragment a social site into acoustically isolated boxes violate the overhearing mechanic (D-018 sound model). The observation loop (Loop 1) depends on players being able to hear conversations from adjacent positions. Practical rule: Social site chunks must have at least one "soft partition" zone — a position where the player can hear adjacent conversations but NPCs have reasonable privacy expectation. This is the eavesdrop sweet spot that rewards Careful stance.

Constraint 3: NPC Single-Ownership with Cross-Reference Links

D-025 says: "NPCs are owned by exactly one template with reference links to others." Constraint on chunk fill: When a district has multiple social sites, the chunk fill for each site must assign NPC ownership unambiguously. An NPC cannot "belong" to two filled chunks. Cross-template contamination (D-025: "One NPC can hold roles in multiple social sites") is expressed through reference links, not through shared ownership. The chunk fill must represent this as: NPC primary slot in Chunk A, secondary reference appearance in Chunk B (e.g., a bar regular who also works at the terminal). Practical implication for the generator: The population stage (upstream) must assign NPC primary templates BEFORE chunk fill runs. Chunk fill uses the population stage output, not the other way around.

Constraint 4: The 4-8 NPC Density Window

D-025 says: "4-8 NPCs who regularly interact." Constraint on chunk fill: A social site's chunk cannot be over-filled (>8 regularly interacting NPCs in one cluster) or under-filled (<4 interacting NPCs). Tier 3 background NPCs (D-029: 30% flat wallpaper) pass through but don't "belong" to the cluster. Quarter implication: A full 2×2 quarter merge producing a large open floor can host 4-8 NPCs in a social site. A single-quarter configuration (¼ chunk = 32×32 sim tiles = 16m) can host a smaller social site, but may be too small for 8 NPCs with meaningful daily routines. The generator should default: smaller clusters in single quarters (4-5 NPCs), larger clusters in merged quarter configurations (6-8 NPCs).

Constraint 5: Public/Private Gradient Within the Cluster

D-025 says: "Physical cluster defines spatial identity (sightlines, overhearing, public/private)." Constraint on chunk fill: Within a single functional cluster, there must be spatial differentiation between public-facing areas and private areas. The bar example from D-093: bar area (public, all access) + back room (private, insider only) + below-bar maintenance access (restricted, ring members only). This tri-zone structure within one cluster must be representable in the quarter system. Quarter solution: A 4-quarter chunk representing a bar might configure as:

2 quarters merged: main bar floor (public)
1 quarter: back area / staff zone (semi-private)
1 quarter gap or sub-quarter shack: storage/access point (private/restricted)

Constraint 6: The "Invisible Infrastructure" Principle (G-08 from D-093)

D-093 says: "every ring location reads as mundane; criminal function visible only to those who know." Constraint on chunk fill: This is a design constraint on HOW templates are instantiated. The chunk fill cannot place obvious "smuggling room" tiles. The physical arrangement must read as functional for mundane purposes while being usable for criminal ones. Practical implication: Templates must have a "surface reading" (manifest function) and a "second reading" (criminal function). Chunk fill must not diverge these visually — the same tile arrangement serves both. The distinction comes from NPC knowledge (D-041 knowledge graph), not from tile art.

5. Open Questions I'm Flagging for Round 2

Q-A: Does Population Precede or Follow Zoning in Our Pipeline?

The Cities Skylines model puts population after zoning. But our game has a critical dependency: NPC secrets must have plausible staging grounds in the spatial layout. An NPC with a secret meeting in a restricted zone requires that restricted zone to exist before the NPC can be validly generated.

My position: Population follows zoning for assignment (zones exist first), but population requirements should CONSTRAIN zoning (a zone must exist that satisfies the minimum secret/access requirements of the triangle configuration). This creates a feedback loop between population and zoning that the pipeline must resolve. Tyre will need to address whether this creates implementation complexity.

Q-B: Triangle Template (D-025) Instantiation Stage

The workshop brief asks where triangle templates are instantiated in the pipeline. My position: Triangle configuration is determined at the population stage (which NPCs exist, which have conflicting interests). Social site templates (D-025) are instantiated at chunk fill. The population stage produces a "social graph" that the chunk fill stage then places into physical space.

This means: social graph → chunk fill. NOT: chunk fill → social graph. The generator must not produce spatial arrangements and then try to fill them with compatible social graphs. The social graph drives spatial requirements.

Q-C: What Is the Minimum Generated District?

For v0.1 validation purposes: if we express Sova Transit District as generator output, what is the minimum generator that can reproduce it? I'd propose:

1 workplace social site (terminal-type)
1 social venue (bar-type)
1 maintenance spine (quiet zone)
1 transit encounter node
1 restricted zone (authority access)
2 active triangles across the above sites

This is the "minimum viable district" that satisfies all seven guarantees. Anything below this fails at least one gameplay loop.

Summary: Generator Requirements as a Checklist

Requirement	Source	Stage Where Guaranteed
Surveillance chokepoint	D-093, Loop 1	Infrastructure
Meridian dead spot / quiet zone	D-093, D-029, Loop 4	Infrastructure
Public social venue (bar-type, D-025 compliant)	D-025, Loop 3	Amenities
Insider access zone (workplace-type)	D-007, Loop 3	Zoning
Authority access zone (restricted-type)	D-007, Loop 3	Zoning
Triangle social geometry (≥2 active, D-024)	D-024, D-029, Loop 2	Population
Three-path investigation structure (A/B/C)	D-093, Loop 2	Multi-stage
Transit encounter node	D-093, D-095, Loop 5	Infrastructure
Internal sightlines within social sites	D-025, Loop 1	Chunk fill
Public/private gradient within clusters	D-025, Loops 1-3	Chunk fill
Invisible infrastructure (dual-reading spaces)	D-093 G-08, Loop 4	Chunk fill

Every pipeline stage maps to at least one row. No guarantee is produced "for free" — each requires an explicit generator mechanism.

Gestalt — Round 1 complete. Ready to respond to Tyre (technical constraints), Miri (worldbuilding inputs), and Araminta (visual coherence) in Round 2.

23 KiB Raw Permalink Blame History Unescape Escape