settled-reach/docs/workshops/wiki-review/round1-gore.md

Round 1 — Gore

Topic 1: Direction Check — Is This the Game We Want?

The short answer

Almost. The wiki describes a mechanically sophisticated game about asymmetric information. What it doesn't fully articulate is what the game is about.

What the wiki gets right

Hael is the masterpiece. I want to be clear about this because it could get lost in what follows. Hael — a teacher, a civilian, a person who just wants their partner to come home on time — is the emotional fulcrum of the entire vertical slice. Both FRIEND arcs orbit Hael. Kael is hiding things to protect Hael. Sera is hiding things to protect Hael. The smuggler must lie to Hael. The detective can weaponize Hael. One person who never touches the conspiracy is the person the conspiracy most damages. That's not just good design. That's the game's thesis statement in a character.

The contraband is morally correct. Medical-grade lattice components for people locked out of the institutional system. The ring isn't moving weapons — they're moving healthcare. D-037 gets this exactly right. The smuggler isn't a villain. The detective isn't a hero. The system failed people, and the ring is the scar tissue. This is what "quotidian-with-undertow" actually means: the undertow isn't evil, it's rational.

The contradiction arcs are structurally excellent. Kael's single-observation contradiction (Corridor B-7) versus Sera's cumulative-pattern contradiction (three departures when Torek arrives) — two different ways of discovering betrayal, both honest to their characters, both mechanically distinct. The tell system (Kael looks left when lying, Sera over-helps to compensate) gives the player agency in the discovery. This is authored content earning its depth.

What's missing: the philosophical spine

The wiki describes what happens with precision. It's weaker on what it means.

There's a word for what this game is actually about, and it isn't "asymmetric information." It's complicity.

Every character in Sova Transit District is complicit in something:

• Kael is complicit in the ring's operations (even while trying to exit)
• Sera is complicit in concealment (sitting on evidence to protect a friend)
• Voss is complicit in smuggling (takes a cut, manages the schedule)
• Lera is complicit through willful ignorance (Torek's spending keeps her bar viable)
• Maret is complicit through silence (sees the discrepancies, doesn't report)
• Drin is complicit through coercion (gambling debt, can't say no)
• The smuggler is complicit in all of it — and depending on player choices, becomes more so
• The detective becomes complicit the moment they choose which truths to pursue and which to ignore

And the player? The player becomes complicit in whatever they choose. There is no "observe without participating" option. Watching IS participating. Knowing and not acting IS a choice.

This is what D-027's success criterion #3 ("player names an NPC they felt conflicted about") is really measuring. Not "did the NPC have good dialogue?" but "did the player feel the weight of their own complicity?"

The wiki needs to name this. Right now, "asymmetric information" is treated as the core mechanic AND the core theme. It's the mechanic. The theme is complicity. Every NPC profile should be readable through the lens of: what are they complicit in, and what would it cost them to stop?

The contentment axis is underdeveloped

D-024 introduced contentment (my proposal) as a thematic axis. The NPC profiles include it but treat it as a status indicator rather than a thematic driver. Kael's contentment is "moderate-low." Sera's is "moderate, declining."

This misses the point. Contentment isn't a meter. It's the question the game asks every character — and by extension, the player:

"Is this enough?"

That's the question the Commonwealth universe was built to explore. Post-scarcity societies (and the Settled Reach is close to post-scarcity, if not there) force every intelligent being to answer: when survival is solved, what do you do? What's worth wanting?

Every NPC in the district has an implicit answer:

• Kael: "It was enough until it wasn't. Now I want out, but 'out' might not exist."
• Sera: "It was enough until someone I care about was in pain. Now my quiet life is a lie."
• Lera: "It's enough. Don't ask me questions that would change that."
• Maret: "It should be enough. The numbers say otherwise. I can't un-see them."
• Hael: "It was enough. Something changed and nobody will tell me what."
• Voss: "It's enough if people stop pushing. (They won't stop pushing.)"

The smuggler and detective each answer this question through play. The smuggler's answer is: "It isn't enough — I need more money, more security, more control." The detective's answer is: "It isn't enough — something is wrong here and I need to know what."

Proposal: Add a "Thematic Question" field to NPC profiles — not a mechanical axis, but an authoring-guide entry that states the character's implicit answer to "Is this enough?" This anchors every NPC to the game's philosophical spine without adding mechanical complexity. Content authors write to a question, not just a set of traits.

The dual-lens needs a thematic frame, not just a mechanical one

"Same world, two lenses" is the tagline. The wiki executes this mechanically: the smuggler sees Kael's greeting as warmth, the detective sees it as data. Good.

But the deeper version is: the smuggler's lens is complicity and the detective's lens is judgment. The smuggler knows they're part of the problem. The detective believes they're outside it. Both are wrong. The smuggler is trying to exit (via Kael's arc), which means the complicity isn't total. The detective becomes complicit the moment they choose to protect Sera or use Hael as leverage.

The best version of this game doesn't just show you two perspectives. It shows you that the distinction between "inside" and "outside" a conspiracy is a fiction. Everyone is inside something. The only question is what.

Specific wiki amendments I'd propose

1. Wiki index.md — Add a "Thematic Core" section before "Quick Reference" that states: The Settled Reach asks what happens when comfortable people discover they're complicit in systems they depend on. Every character is compromised. The game's question isn't "who did it?" but "what will you do now that you know?"

2. NPC profiles — Add ## Thematic Question section to the Tier 1 template. Not mechanical. Authoring guidance: "This character's answer to 'Is this enough?'"

3. Relationship states — The "Contaminated Trust" concept in Phases 5 of both FRIEND arcs is the game's thematic core expressed as a mechanic. The wiki treats it as a post-arc state. I'd elevate it: contaminated trust isn't an endpoint, it's the normal condition of adult relationships in a compromised community. Everyone in Sova Transit District already lives with contaminated trust. The player just hasn't noticed yet.

---

Topic 3: Cultural Identity and the Game's Themes

You're asking the wrong question

The workshop asks: "Should the player notice heritage, or is it ambient?"

Neither. Cultural identity in this game is the immune system of the community, and the detective is the foreign body.

What Krenn System culture actually is

The wiki describes Krenn System culture as "compact names, first-name-primary, pragmatic, mind-your-business ethos." That's fine as a naming guide. It's radically incomplete as a cultural description, because it doesn't say what the culture does.

What Krenn System culture does is protect the ring.

Not intentionally. Not conspiratorially. But structurally:

• Mind-your-business ethos = nobody reports Torek's spending, nobody asks where Kael goes at night, nobody questions Voss's schedule changes. The cultural norm IS the ring's security model.
• First-name-primary social contexts = institutional identity (Sera's Commission role, the detective's authority) is deemphasized in social settings. You're "Sera," not "Field Tech Venn." This makes authority feel like an imposition, not a service.
• Pragmatic = the ring exists because people need things the system doesn't provide. Pragmatism doesn't moralize about how needs get met. This is the cultural bedrock of the grey economy.
• Working-class freight district = solidarity is default. The detective, regardless of personal warmth, represents institutional authority that could shut down someone's livelihood. Cooperation with the detective isn't just risky — it's a betrayal of social solidarity.

The bar is called "The Last Shift." Not "The Starlight Lounge." Not "The Golden Gate." A name that says: we're tired, we're done for the day, this is where we exhale. That name IS the culture. It tells you everything about who these people are and what they value.

Cultural identity as mechanical resistance

Here's my concrete proposal:

Cultural identity should manifest as the difficulty gradient the detective faces and the social camouflage the smuggler benefits from. Not as a stat or a modifier, but as a felt experience:

1. Detective experience: NPCs default to surface-level cooperation. They answer questions but don't volunteer. They're polite but not helpful. The cultural value of minding your own business means the detective has to earn every piece of real information, not because people are hostile, but because sharing someone else's business violates a social norm. This is why Maret hasn't reported. It's not fear — it's culture.

2. Smuggler experience: The smuggler is of this culture. First-name-primary, bar regular, knows the rhythms. The ring works because it's culturally embedded — "we take care of our own" is both a family value (Nils to Kael) and a community value (Lera protecting her regulars). The smuggler's camouflage isn't a disguise. It's being from here.

3. The cultural rupture: When the detective's investigation disrupts the community — when Drin is pressured, when Maret is confronted, when Hael is drawn in — the damage isn't just to the ring. It's to the social fabric. People who minded their own business are now being asked to testify. Friendships that assumed privacy are now under scrutiny. The detective isn't just solving a crime. They're tearing a community's operating agreement apart. The question is whether that's justice or vandalism.

Should the player notice heritage?

Heritage should be like gravity. You don't notice it. You notice when it's absent.

The player should never think "oh, this is a Krenn System cultural value." They should think "why won't anyone talk to me?" (detective) or "I'd never bring that up at Lera's" (smuggler). The culture is the water they swim in. It becomes visible only when someone (the detective, Olin the outsider) doesn't understand the rules.

Miri will have more to say about the specific cultural clusters, heritage drift over 180 years, naming conventions. That's important work. My contribution is this: whatever the cultural details are, they must serve the game's mechanical and thematic needs. The mind-your-business ethos isn't decoration. It's the reason the ring survives. It's the reason the detective's job is hard. It's the reason Maret is silent and Lera is blind and Hael is confused. Culture IS the gameplay.

What the regional style guide pattern needs

Beyond naming and aesthetics, each regional style guide should include:

1. Default social norm toward authority: How do locals treat institutional representatives? (Krenn System: polite distance, cooperation without volunteering, first-name-basis to deformalize authority)
2. Privacy expectations: What's considered "your business" vs. community knowledge? (Krenn System: income source is private, spending is visible but uncommented upon, relationships are acknowledged but not interrogated)
3. Loyalty structure: Family first? Community first? Institution first? (Krenn System: family > workplace bonds > district solidarity > institutional allegiance)
4. The thing nobody discusses: Every community has a shared silence. (Krenn System: everyone knows the grey economy exists. Nobody names it.)

These aren't flavor entries. They're mechanical parameters for dialogue selection. When the detective asks Lera about Torek's spending, Lera's deflection isn't personality — it's culture. A regional style guide that doesn't capture this is incomplete.

---

Topic 6: Procedural Generation — Dilution or Amplification?

Wrong question. Let me reframe it.

The workshop asks whether procedural generation dilutes authored moments or amplifies them. That's a question about production methodology. The real question is:

Can a procedurally generated relationship make you feel complicit?

Because that's what the game needs. Not "can a proc-gen NPC have a schedule" — obviously yes. Not "can a proc-gen NPC have dialogue" — with tagged pools, yes. But can a proc-gen NPC make you feel the weight of knowing their secret? Can a proc-gen NPC be THE FRIEND?

No. And that's the answer that matters.

What can't be generated

Kael's tell — looking left when lying — works because the player learns to recognize it over 15 minutes of authored casual interaction, then sees it during the confrontation. That's an authored behavioral arc. A procedural system can't teach the player to read a specific NPC's body language through repeated authored moments.

Sera's avoidance pattern works because it requires three specific departures, each with a different excuse, spaced across multiple bar visits, with the detective's training firing on the third. That's precision timing. A procedural system can generate "NPC leaves when other NPC arrives" but can't generate the escalating internal monologue that makes the third departure land.

The Phase 5 "contaminated trust" — where every warm interaction from Phase 1 is retroactively poisoned — works because the specific warm interactions were authored to be re-readable. "There you are. Good — I was starting to worry" from Kael at game start is heartbreaking after you see him in Corridor B-7. That retroactive recontextualization requires authored specificity.

Rule: THE FRIEND cannot be procedurally generated. The emotional payload of D-034 requires Tier 1 authored depth — every line, every tell, every contradiction beat.

What should be generated

Everything that makes the authored content hit differently on replay:

1. FRIEND assignment from a pool, not FRIEND content. Write 4-6 FRIEND-eligible NPCs at full Tier 1 depth per district. The randomizer selects which one is THE FRIEND for this playthrough. The content is authored; the selection is procedural. Second playthrough: same district, different FRIEND. The player already knows Kael's arc from the first run — but this time THE FRIEND is Maret, and her contradiction is entirely different.

2. Mundane triangle variation. The Bar Tensions triangle (Lera - Torek - Olin) is load-bearing for atmosphere but not for the core emotional arc. Procedurally varying the nature of the tension (Torek's spending source, Olin's actual identity, what Lera's tolerating) changes the detective's noise floor without touching the signal. The bar still feels alive. The specifics shift.

3. Tier 3 NPC generation. Drin, Sess, Olin, Sabel, Tav — social wallpaper. Generated from templates with regional naming conventions. Their function is to make the district feel populated, not to carry emotional weight.

4. Context variation. What's on the news ticker. What shift is running when the player arrives. What Lera's serving tonight. Whether Torek is drunk or sober. The environmental texture around the authored core.

5. Entanglement rate per D-029. The 30/50/20 split (flat/mundane/entangled) should vary per seed. Some playthroughs have more conspiracy density. Some have more life-sim quiet. The player shouldn't be able to calibrate.

The PC-as-NPC question

This is the most dangerous idea in the workshop brief. Let me explain why.

If the player inhabits an NPC who already has relationships, those relationships ARE the game. Kael's relationship with the smuggler is the emotional core of the smuggler's playthrough. If that relationship is procedurally generated — if the warmth of "There you are. Good — I was starting to worry" is absent because the PC-NPC connection was randomized without authored depth — the FRIEND arc can't land.

The PC template must include authored relationship stubs for every FRIEND-eligible NPC. Not just "Relationship: Friendly" — actual authored history, specific memories, the kind of shared experience that makes betrayal hurt. "Remember when we covered for each other during the audit last month?" That specificity is what makes contaminated trust painful instead of merely mechanical.

Here's my proposal for PC-as-NPC:

1. The PC starts as a named NPC from the district roster, with pre-existing relationships defined at Tier 2 minimum depth.
2. THE FRIEND relationship (whichever NPC is selected as FRIEND this playthrough) requires Tier 1 authored depth for the PC-FRIEND connection specifically.
3. The PC's starting knowledge is derived from their NPC profile's information inventory — what they know, what they don't, what they suspect.
4. The PC's "answer to the question" ("Is this enough?") is implicit in their starting situation and becomes explicit through play. The smuggler starts having answered "no." The detective starts having answered "something is wrong." Play reveals whether those answers hold.

The replayability thesis

Procedural generation amplifies authored content only when the authored content is the emotional core and the procedural content is the context that reframes it.

First playthrough: Kael is THE FRIEND. You discover his exit attempt. You feel betrayed.

Second playthrough: Kael is just a dock worker. You know his secret from last time, but your character doesn't. You watch him checking his lattice nervously and you know what it means, but your character monologues "Kael's distracted today. Probably nothing." The dramatic irony — player knowledge vs. character knowledge — is itself a thematic statement about complicity. You know and your character doesn't. You're complicit in maintaining their ignorance.

That's procedural generation amplifying authored content. The randomizer didn't create the irony. The authored content (Kael's full arc) combined with the procedural variation (different FRIEND assignment) produced an emergent emotional experience that neither could produce alone.

That's what procedural generation is for in this game. Not to create content. To create context that makes authored content mean something different every time.

---

Summary of Proposals

1. Name the theme. The game is about complicity, not just asymmetric information. Add thematic framing to the wiki index.
2. Add "Thematic Question" to NPC profiles. Each character's answer to "Is this enough?" — authoring guidance, not mechanical.
3. Elevate contaminated trust. It's not a post-arc state. It's the normal condition of life in a compromised community.
4. Cultural identity as mechanical resistance. Regional style guides must include social norms toward authority, privacy expectations, loyalty structures, and the community's shared silence.
5. THE FRIEND is never procedurally generated. Write a pool of FRIEND-eligible NPCs at Tier 1 depth. Randomize the selection, not the content.
6. PC-as-NPC requires authored relationship stubs at Tier 2 minimum for all connections, Tier 1 for the FRIEND relationship.
7. Procedural generation varies context, not content. The authored emotional core stays fixed. Everything around it shifts to create replay value through reframing.