settled-reach/docs/workshops/v01-gap-analysis/round1-gestalt.md

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

title	description	type	status	workshop	agent	round	created
Round 1 Workshop Response: Gestalt (Systems Design)	Systems design analysis of concept proof strength, fun/wow factor, and missing systems for v0.1	workshop	archived	v01-gap-analysis	gestalt	1	2026-02-11

Round 1 Workshop Response: Gestalt (Systems Design)

Agent: Gestalt (Systems Design & Fun Factor) Date: 2026-02-11 Scope: Tracks 1, 2, 3

---

Track 1: Strength of Concept Proof

Let me break down what each claim actually means mechanically, and whether the tickets deliver it.

Claim 1: Asymmetric Information is the Core Mechanic

Rating: INFRASTRUCTURE STRONG, EXPERIENCE GAP Risk: MEDIUM-HIGH

Ticket(s)	What they deliver	What's missing
#138-142 (info boundaries)	Data layer: who knows what, entity visibility filtering, access control	How the player EXPERIENCES asymmetry
#182-183 (divergent knowledge/relationships)	Starting state differences between smuggler and detective	Ongoing divergence during play
#119-122 (monologue)	Character-specific interpretation of observations	Integration: monologue triggered BY information boundary differences
#168-174 (dialogue)	Access-tier filtered conversations	Integration: same NPC giving demonstrably different info to different characters

The gap: The information boundary system (#138-142) is the ENGINE. The monologue (#119-122) and dialogue (#168-174) are the INTERFACE. But there's no ticket for the INTEGRATION layer that makes asymmetry experienceable. Specifically:

• No "asymmetry moment" authoring ticket. Who writes the content that makes the smuggler's internal monologue say "the usual cargo run" while the detective's says "those shipping manifests don't match"? This falls somewhere between Mellanie's content packs (#190-192) and the monologue line pool (#120), but the specific design of character-divergent reactions to the same observations isn't called out.
• No ticket for the player discovering they were wrong. Asymmetric information is most powerful when the player realizes their character's view was incomplete or wrong. How does this realization surface mechanically? Monologue? Dialogue? Environmental discovery?

Minimum bar for v0.1: The player must, at least once per playthrough, encounter a situation where they later realize "oh, that's what was really happening" — and the realization comes from systems, not a scripted reveal.

Claim 2: Fog of Perception Creates Tension

Rating: SOLID Risk: LOW-MEDIUM

Ticket(s)	What they deliver	What's missing
#110-113 (fog pipeline)	Shadowcasting, vision cone, observer query, fog rendering — all critical priority	Nothing missing in the pipeline itself
#124-128 (sound model)	Sound events through fog, directional indicators	Close-range (#125) is high, medium-range (#126) is medium — this ordering is correct
#115 (NPC vision)	NPCs use the same system	Solid

The tension question: Fog creates tension only when there's something to be tense ABOUT. A fog system over a static, predictable world is just visual clutter. Tension requires:

1. NPCs occasionally being where you don't expect them (#88 routines are predictable by design)
2. Sounds from fog-edge creating decision moments ("investigate or ignore?")
3. The possibility that what you can't see CAN hurt you or surprise you

Gap: NPC off-routine behavior. The routine system (#88, #101) makes NPCs predictable — which is great for investigation ("they always go to the back room at 3pm"). But for fog to create tension, NPCs need to occasionally deviate. The smuggling ring NPCs (#186) should have secret activities that break their public routine. This is implied but not explicitly ticketed as a behavior system.

Minimum bar for v0.1: At least one moment per playthrough where the player hears something through fog and has to decide whether to investigate. This is emergent if the sound system (#124-125) and NPC routines (#88, #101) work together — but it's worth validating that the content creates these moments.

Claim 3: NPCs Feel Alive Without Player Attention

Rating: STRONGEST CLAIM Risk: LOW

Ticket(s)	What they deliver	What's missing
#88 (daily routines)	NPCs have schedules — critical	Nothing in isolation
#93-99 (simulation tiers)	Full tier pipeline from active to state-saved	Comprehensive
#101 (routine execution)	NPCs actually follow routines	Solid
#102 (mood), #103 (relationship dynamics)	NPCs' internal state changes over time	Both medium priority — should at least one be promoted?

This is our best-covered claim. The tier system (D-026) ensures NPCs are simulated even off-screen. The routine system (#88) gives them predictable daily lives. The relationship dynamics (#103) mean things change while you're away.

Gap — discovery of off-screen life: The player needs to NOTICE that NPCs lived without them. Two mechanisms:

1. Dialogue references to off-screen events — "Did you hear about the argument at the bar last night?" This requires content in the content packs (#190-192) and the dialogue system to surface it. Partially covered by Layer 4: Unprompted disclosure (#172), but #172 is medium priority.
2. Environmental state changes — not ticketed at all. If the bar looks identical at 2am and 2pm, the world feels static even if NPC state changed. Even simple things (lights on/off, tables occupied/empty, items moved) would sell this.

Minimum bar for v0.1: When the player returns to a location they've visited before, at least one NPC should mention something that happened while the player was away, and at least one visible detail should have changed.

Claim 4: Observation is a Mechanic, Not a Cutscene

Rating: PIPELINE STRONG, PLAYER VERBS MISSING Risk: HIGH

Ticket(s)	What they deliver	What's missing
#110-113 (vision)	What the player can see	Passive: info flows TO player
#124-128 (sound)	What the player can hear	Passive
#119-122 (monologue)	Character interprets observations	Passive
#115 (NPC vision)	NPCs can see the player	Reactive: NPCs respond to player presence

Critical gap: OBSERVATION VERBS. The perception pipeline delivers information to the player. But "observation as a mechanic" means the player must DO something active:

Missing verb	What it means	Why it matters
FOLLOW	Maintain distance behind an NPC, track their movement	Core investigation mechanic. The observe->follow->discover sequence (D-027 criterion 4) literally requires this
WAIT/STAKE OUT	Stay in one location and let time pass while watching	Classic detective mechanic. Without it, the player can only observe in real-time
EXAMINE	Look closely at an object, container, terminal, document	Without this, the environment is wallpaper
EAVESDROP	Position yourself to overhear a conversation in progress	The sound model enables this spatially, but the player needs to know they're eavesdropping

The D-027 criterion says "observe -> notice -> follow -> discover must emerge from systems, not scripts." But FOLLOW doesn't have a ticket. Neither does any active observation verb. The perception pipeline is the sensory layer. The player agency layer for observation is missing.

Minimum bar for v0.1: Player can follow an NPC (the game tracks that you're following and adjusts monologue accordingly). Player can examine key objects. These two verbs plus the existing perception pipeline would be sufficient to prove the claim.

Claim 5: Same World, Different Story

Rating: SETUP STRONG, GAMEPLAY DIVERGENCE UNCLEAR Risk: MEDIUM-HIGH

Ticket(s)	What they deliver	What's missing
#179-183 (character builds)	Two distinct characters with different knowledge/relationships	Character GOALS/MOTIVATIONS
#196-199 (success criteria validation)	Testing framework	These are tests, not content
#169 (access tier filtering)	Different dialogue per character	Correct mechanism
#119-122 (monologue)	Different internal voice	Correct mechanism

The gap: what is the player DOING? Two characters seeing the world differently is necessary but not sufficient. They need to be DOING different things.

• Smuggler: what are their objectives? Maintain their cover? Complete a drop? Manage their contacts? There's a smuggling ring template (#186) but no ticket for "smuggler gameplay objectives."
• Detective: what are they investigating? Who assigned the case? What's their mandate? The detective has "authority access, analytical" — but what is the investigation ABOUT?

Without character-specific goals that drive different ACTIONS, the two playthroughs will feel like "same walking simulator, different flavor text." The characters need mechanical goals — even implicit ones driven by their starting state — that push them to different parts of the game space, different NPCs, different decisions.

Minimum bar for v0.1: The smuggler and detective should have at least one distinct mechanical objective that sends them to different places and creates different social dynamics. Not a quest log — a systemic pressure. The smuggler needs to maintain relationships with ring members (relationships erode if ignored). The detective needs to gather evidence (knowledge state builds toward a threshold). These feel like system-level features, not content.

Claim 6: Social Triangles Create Emergent Drama

Rating: GENERATION COVERED, ACTIVATION NOT Risk: HIGH

Ticket(s)	What they deliver	What's missing
#106-109 (triangle generation)	Schema, intra-template, cross-template, validation	Triangle DEFINITION — potential energy
#175-176 (entanglement ratio, NPC pool)	Population balance for triangles	Correct population math
#103 (relationship dynamics)	Relationships change over time	Closest to activation, but medium priority
#105 (tolerance threshold triggers)	NPCs snap when pushed too far	One activation mechanism, medium priority

Critical gap: triangle RESOLUTION mechanics. A triangle is potential energy: NPC A wants X, NPC B wants Y, NPC C is caught between. But what makes the drama HAPPEN? The triangle needs to ACTIVATE — produce observable events that the player can witness or discover.

Triangle activation requires:

1. Triggering conditions — when does tension in a triangle boil over? Tolerance (#105) is one mechanism, but it's medium priority.
2. NPC confrontation behavior — NPC A confronts NPC C about NPC B. This is an NPC behavior that needs to be simulated, not just tracked.
3. Observable events — the confrontation needs to happen in game-space where the player can see/hear it. This ties to routine deviation (NPC breaks routine to confront someone) and sound events (raised voices audible through fog).
4. Consequences — after a triangle event, relationship states change, routines adjust, secrets potentially spill. This feeds back into the social system.

Without activation mechanics, triangles are authored backstory, not emergent drama. The player will learn about triangle tensions through dialogue, but never WITNESS them playing out in the simulation.

Minimum bar for v0.1: At least one triangle should activate during a 30-minute playthrough. The player should be able to witness (or hear, or discover evidence of) an NPC confrontation that arose from triangle tensions. This means #103 and #105 should probably be promoted from medium to high priority.

Concept Proof Scorecard Summary

Claim	Infrastructure	Experience	Overall Risk	Key Gap
Asymmetric information	Strong	Gap	MEDIUM-HIGH	Character-divergent content integration
Fog of perception	Strong	Adequate	LOW-MEDIUM	NPC off-routine behavior for tension
NPCs alive off-screen	Strong	Gap	LOW	Discovery mechanisms for off-screen life
Observation as mechanic	Strong	Missing	HIGH	Player observation verbs (follow, examine)
Same world, different story	Setup done	Missing	MEDIUM-HIGH	Character mechanical objectives
Social triangles	Schema done	Missing	HIGH	Triangle activation/resolution mechanics

Overall assessment: Our INFRASTRUCTURE is strong. Our SYSTEMS are well-designed. The gap is consistently in the EXPERIENCE LAYER — the place where systems produce moments the player actually encounters. This is the classic systems design trap: building the engine without building the verbs and events that make the engine produce gameplay.

---

Track 2: Fun & Wow Factor

What's the Single Most Exciting Thing in 30 Minutes?

The smuggler watches their coworker — someone they've been working with, someone they greet every morning — walk into the back room at the wrong time. The monologue fires: "That's the third time this week. Something's off." The player follows. They overhear a conversation through the wall (medium-range sound). They realize: their coworker is talking to someone the smuggler knows is from the enforcement side. Their trusted colleague is an informant.

Or from the detective side: they interview a bar regular. Friendly, cooperative, nothing to hide. But later, staking out the bar at night, they see that same regular meet with someone in the alley. The monologue: "Interesting company for a shipping clerk." The detective has a choice: confront now or keep watching.

These moments are the game. And they emerge from systems interacting: routine + secret + perception + monologue + NPC relationships. That's the good news — our systems are designed to produce these moments.

The bad news: I can describe these moments, but I can't point to a ticket that guarantees they happen. They're emergent. They depend on:

• NPC secret behavior being observable (#88 + something not yet ticketed)
• The player being in the right place (spatial design #153-155)
• The monologue firing the right line (#119-120 + content #190-192)
• The player having enough context to recognize the anomaly (prior dialogue + information state)

Are We Front-Loading the Fun?

CONCERN: No. The first 5 minutes are likely to be:

1. Character spawns in the station district
2. Player sees their immediate surroundings (fog reveals area)
3. Player can walk around
4. Player... does what?

There's no opening hook. No "you have a message on your insert" moment. No "your shift starts in 10 minutes" prompt. No immediate pull.

Missing ticket: opening sequence/hook for each character. Not a cutscene — a systemic hook. The smuggler's insert buzzes with a message from their contact: "Shipment delayed. Meet me at the usual place." The detective's case file updates: "New lead in sector 7." These are information events that use existing systems (insert/minimap #148-149, monologue #119-122) but they need to be designed and authored.

Without an opening hook, we're asking players to explore a station district with no goal and discover emergent gameplay through wandering. That's a recipe for confusion, not excitement.

Which Tickets Are Wow vs Infrastructure?

Category	Tickets	Count
Pure infrastructure	#65-69, #70-74, #75-80, #81-85 (engine), #218-232 (tasks), #93-100 (tiers), #143-147 (chunks), #200-217 (testing)	~80
Foundation that enables wow	#86-92 (NPC data), #110-113 (fog), #138-142 (info boundaries), #129-133 (renderer)	~25
Wow-adjacent (systems that produce moments)	#88 (routines), #101 (routine execution), #106-109 (triangles), #119-122 (monologue), #124-128 (sound), #168-174 (dialogue)	~25
Direct wow (player-facing payoff)	#179-183 (character builds), #182-183 (divergent experience), #184-188 (station content), #189-194 (authored content)	~15
Validation/testing	#195-199, #200-217	~20

The ratio is infrastructure-heavy, which is expected for a foundation build. But the "direct wow" tickets are almost entirely content authoring (#189-194) and character setup (#179-183). There are very few MECHANICS tickets in the wow category. This confirms the Track 1 finding: the experience layer is thin.

Is There a 2-Minute Demo Moment?

Best candidate: the split-screen concept proof.

Show the same 60 seconds of gameplay from both characters. The smuggler walks through the logistics hub. Monologue: casual, familiar, routine. They greet a coworker. Normal day. The detective walks through the same hub. Monologue: analytical, suspicious. Same coworker, different greeting — the detective gets the polite-but-guarded version. The detective's insert flags the coworker's cargo manifest as anomalous.

Same world. Different experience. 60 seconds. Core concept proven.

Requirements: #179-181 (characters), #119-122 (monologue), #138-140 (info boundaries), #168-169 (dialogue access tiers), #129-131 (renderer), #113 (fog). All are in the plan. This is achievable.

Promote this as a milestone target. A side-by-side video of this demo would be enormously powerful for validating the concept.

Where's the First "Aha" Moment?

The "aha" moment is: "Wait, this NPC knows something they're not telling me."

This requires:

1. The player talks to NPC. NPC is friendly/normal. (#168-169 dialogue)
2. Later, the player observes NPC doing something contradictory. (#88 routine, #110-112 perception)
3. Monologue fires: interpretive commentary linking the contradiction. (#119-120)
4. The player realizes: that first conversation was a performance.

Timeline: This can't happen in the first 5 minutes. The player needs to establish a baseline expectation before it can be subverted. Earliest realistic "aha": ~10-15 minutes in, after the player has talked to several NPCs and gotten a feel for "normal."

Risk: If it takes longer than 15-20 minutes for ANY observation-based discovery to occur, the player will think the game is boring. The content packs (#190-192) need to ensure that at least one observable secret is available early.

Is Daily Life Interesting Enough for 30 Minutes?

Honest answer: uncertain.

The 30/50/20 split (D-029) means:

• ~6-10 flat NPCs (routine + greeting only) — these are wallpaper
• ~10-15 mundane triangle NPCs (disputes, rivalries, tensions) — these ARE the daily life game
• ~4-6 entangled NPCs (connected to smuggling ring) — these are the intrigue layer

For 30 minutes of daily life to be interesting, the mundane triangles must be engaging. A workplace rivalry. A bar regular who's cheating on their partner. A neighbor dispute about noise. These are small-stakes but relatable dramas that the player discovers through observation and conversation.

Content volume concern: Each template gets ~165-210 authored lines, expanded 4x. With 3 templates, that's ~2,000-2,500 total lines. If the player talks to 20-30 NPCs in 30 minutes, averaging 4-5 lines per conversation, that's ~100-150 lines consumed per playthrough. Budget seems adequate — but variety matters. If 3 NPCs give the same style of greeting, it feels repetitive even with different words.

Systemic concern: Daily life needs ACTIVITIES, not just conversations. What does the player DO between conversations? Walk around and watch NPCs? That's passive. The player needs micro-decisions: where to go next, who to talk to, what to examine, whether to follow someone. These are the observation verbs I flagged in Track 1 — without them, daily life is a walking simulator with dialogue.

Missing Wow Moments (Systems Design Perspective)

1. The betrayal discovery. You trusted an NPC. They were friendly, helpful, consistent. Then you discover they've been reporting your movements. Not through a scripted reveal — through observation and deduction. Requires: NPC double-agent behavior (secret routine) + player observation mechanics + monologue interpretation.

2. The overheard conversation. You're walking past a wall. You hear voices through it — two NPCs talking about someone. It's you. Requires: sound propagation (#124-128) + NPC-to-NPC conversation system (NOT TICKETED) + monologue interpretation.

3. The routine break. An NPC who's been on the same schedule for days suddenly deviates. Where are they going? Why now? Requires: NPC off-routine behavior (NOT TICKETED) + perception system + monologue flagging the deviation.

4. The wrong place at the wrong time. You walk into a room and interrupt something. Two NPCs jump apart, conversation stops. Requires: NPC reaction to player presence (#115 NPC vision) + NPC behavior state changes (NOT TICKETED).

---

Track 3: Things We May Have Forgotten (Systems Design)

Critical Missing Systems

1. Player Interaction System (NO TICKETS)

Severity: CRITICAL BLOCKER

The player can move, look, and listen. But there's no ticket for the basic interaction verb set:

Verb	Description	v0.1 necessity
INTERACT	General-purpose "use" action on entities/objects	Critical — without this, the world is untouchable
EXAMINE	Look closely at something for details	High — feeds investigation mechanic
FOLLOW	Track an NPC's movement	High — D-027 criterion 4 literally requires this
TALK	Initiate dialogue with NPC	Covered by #168-174
WAIT	Let time pass while staying in place	Medium — enables stakeout mechanic
USE DOOR	Open/close doors	Medium — basic spatial interaction
PICK UP	Take items from environment	Low for v0.1 — can defer

The dialogue system (#168-174) covers TALK. Everything else is unticketted. At minimum, INTERACT and EXAMINE need tickets. FOLLOW is required by D-027's success criteria.

Proposed new tickets (3-4 stories):

• Player interaction system — entity interaction framework (critical)
• Follow mechanic — track NPC movement with distance/detection (high)
• Examine mechanic — inspect objects/entities for detail info (high)
• Wait/time-skip mechanic — advance time while observing (medium)

2. Character Objectives / Motivation System (NO TICKETS)

Severity: HIGH

What is the player TRYING TO DO? The smuggler and detective have different starting states, but no mechanical goals.

For emergent gameplay, goals don't need to be explicit quest objectives. They can be systemic pressures:

• Smuggler: your contact expects you to show up for drops. Missing a drop damages your relationship (and your cover). Your tolerance threshold for risk slowly climbs as the ring gets more aggressive. Daily life = balancing normal work + criminal obligations.
• Detective: your case file contains leads that decay over time. The longer you wait to follow up, the less useful they become. Your superior expects progress reports. Daily life = balancing investigation + institutional obligations.

These are not quest systems — they're relationship/information pressures that create emergent deadlines. They use existing systems (relationships #87, information #89, tolerance #105) but need a character-specific goal layer.

Proposed: character goal framework story (high priority). Not a quest log — a pressure system that uses existing NPC axes to create character-specific pulls.

3. NPC-to-NPC Conversation System (NO TICKETS)

Severity: HIGH

NPCs talk to the player (#168-174). But do NPCs talk to EACH OTHER? For the social simulation to feel alive, NPCs need to have conversations that the player can overhear, witness, or learn about.

This is load-bearing for multiple claims:

• Fog of perception (hearing conversations through walls)
• NPCs alive off-screen (conversations happen without the player)
• Social triangles (confrontations are conversations)
• Observation mechanic (eavesdropping)

Proposed: NPC-to-NPC interaction system (high priority). At minimum: NPCs in the same social site engage in visible conversation events with sound propagation. Content from the dialogue line pools. The player can approach to overhear more clearly.

4. NPC Reaction to Player Presence (PARTIALLY COVERED)

Severity: MEDIUM-HIGH

#115 gives NPCs vision. But what do they DO when they see the player?

Situation	Expected NPC reaction	Ticket coverage
Player enters NPC's workspace	Greeting, acknowledgment	Covered by dialogue #168-174
Player follows NPC for too long	NPC becomes suspicious, changes behavior	NOT COVERED
Player is somewhere they shouldn't be	NPC challenges or reports player	NOT COVERED
Player interrupts a private conversation	NPCs stop talking, change topic	NOT COVERED
Player is witnessed doing something illicit	NPC reacts based on relationship/loyalty	NOT COVERED

The entire stealth/social-stealth dimension of the game depends on NPCs reacting to player behavior. This is partly a behavior system issue and partly a perception system issue.

Proposed: NPC player-awareness behavior (high priority). NPCs track player presence using #115 vision. Suspicious behavior triggers are defined (following too long, unauthorized areas, witnessing secrets). Reactions use existing relationship/personality axes.

5. Time System (Q-009 OPEN — BLOCKS CRITICAL TICKETS)

Severity: CRITICAL BLOCKER

Daily routines (#88, critical priority) cannot be implemented without a time system. Tick-based game time needs to convert to in-game hours/days. The routine system needs to know "it's 3pm, NPC should be at the bar."

Q-009 must be resolved before Sprint 1 of core simulation work begins.

Key design questions for the time system:

• Tick-to-game-time ratio (how many ticks per game minute?)
• Time display (does the player see a clock? In-universe insert display?)
• Time-skip mechanics (can the player advance time? Sleep? Wait?)
• Event scheduling (how do time-based triggers work?)

6. Pathfinding (NO TICKETS)

Severity: HIGH

NPCs need to navigate the station district. They follow daily routines that move them between locations. They need to avoid walls, navigate corridors, and find paths to destinations.

Godot has built-in NavigationServer2D, so this might be simpler than building from scratch. But it still needs:

• Navigation mesh setup for the station district
• NPC pathfinding integration
• Player movement collision

Proposed: NPC pathfinding story (high priority). Leveraging Godot's nav system.

7. Save/Load System (NO TICKETS)

Severity: MEDIUM for v0.1 (HIGH for any release)

A 30-minute play session needs to be saveable. The state serialization system (#96, high) covers NPC state, but full game save includes: player position, game time, all NPC states, relationship states, information states, map state, dialogue history.

Proposed: save/load system story (medium priority for v0.1). Can be deferred if v0.1 is treated as a demo that runs in one sitting.

8. Contamination Activation Mechanic (IMPLICIT BUT NOT TICKETED)

Severity: HIGH

D-027 says "contamination activates" — the smuggling ring's activities begin affecting the broader social ecosystem. But how?

Mechanically, contamination means:

• An NPC in a mundane triangle starts behaving differently because they're now involved with the ring
• Information starts leaking between social sites via shared NPCs (#187)
• The detective's leads start pointing at NPCs the player has already met

The storyteller (#162, LOW priority) was supposed to drive this. But if the storyteller is low priority, what activates contamination? A timer? A player action trigger? A systemic threshold?

Proposed: contamination activation mechanic (high priority). This is the v0.1 equivalent of the storyteller — a simplified version that activates the smuggling ring's expansion at a defined point (possibly tied to game-time or player-progress thresholds).

9. Environmental Interaction States (NO TICKETS)

Severity: MEDIUM

Doors, terminals, containers, lights. Immersive sims need interactive environment elements. For v0.1, at minimum:

• Doors that open/close (NPC sightlines change, sound propagation changes)
• Maybe one terminal or document that can be read
• Lights that affect visibility

Without these, the station district is a static diorama. NPCs walk through it, but the player can't interact with the space.

Proposed: basic environmental interaction story (medium priority). Doors + one examinable object type.

Feedback Loop Gaps

Feedback type	How the player knows	Ticket coverage
Action had consequences	NPC behavior changes after player interaction	#103 (relationship dynamics, medium) — needs promotion?
Missed something	Monologue hints at unseen events	Partially #119-122, but needs authored content
Investigation progress	Knowledge state advancing toward threshold	NOT COVERED — no player-facing progress indicator
Reputation/standing	NPCs treat player differently based on accumulated behavior	#170 (relationship history, high) — partially covers this
Time pressure	Events happening that the player can't stop	NOT COVERED — requires time system + event scheduling

Content Volume Feasibility

Content type	v0.1 volume estimate	Source	Risk
Authored dialogue lines	~500-630 lines (3 templates x 165-210)	Mellanie #190-192	Medium — tight but achievable
Generated dialogue lines	~2,000-2,500 (4x expansion)	Generation pass #194	Medium — quality of expansion matters
Monologue lines	~200-400 (two characters, context-sensitive)	Not explicitly estimated	HIGH — monologue needs to feel SPECIFIC, not generic
NPC definitions	20-30 NPCs with full 10-axis data	#92 NPC generation pipeline	Medium — pipeline should handle volume
Triangle definitions	~6-9 triangles (2 per template + cross-template)	#106-108	Low — manageable count
Environmental text	Signs, labels, terminal readouts, documents	NOT ESTIMATED	Medium — needs a ticket
Opening hook content	Character-specific starting events	NOT TICKETED	High — critical for first impression

Monologue content is the highest content risk. The monologue system carries an enormous burden in this game — it bridges perception gaps, creates atmosphere, provides hints, expresses character voice, and is the primary mechanism for the player understanding what's happening. If monologue lines feel generic or repetitive, the entire experience suffers. The current plan doesn't estimate monologue volume or call out monologue as a distinct content deliverable beyond the system tickets (#119-122).

Proposed: monologue content pack as explicit authoring deliverable (high priority). Per character, per template, per situation. This is as important as the dialogue content packs.

Systems That Have Tickets But May Need Promotion

Ticket	Current Priority	Recommended Priority	Rationale
#103 Relationship dynamics	Medium	High	Triangles can't activate without relationship state changes
#105 Tolerance threshold triggers	Medium	High	Only ticketed triangle activation mechanism
#102 Mood system	Medium	High	Mood affects dialogue selection (D-028) and NPC believability
#126 Medium-range visual indicators	Medium	High	Fog-edge tension depends on this — hearing things you can't see
#172 Unprompted disclosure (Layer 4)	Medium	High	NPCs need to volunteer information for the player to discover off-screen events
#162 Storyteller module activation	Low	Medium	Even a simplified version is needed for contamination

---

Summary: Top 5 Systemic Risks for v0.1

#	Risk	Impact if unaddressed	Proposed mitigation
1	No player interaction verbs beyond movement and dialogue	Player can see and hear the world but can't DO anything with it. 30 minutes of walking and talking.	New tickets: interaction framework, follow mechanic, examine mechanic
2	No character objectives/motivation	Player has no reason to go anywhere or do anything. Two characters with different views but no different drives.	New ticket: character goal/pressure framework
3	Triangle activation gap	Triangles are authored backstory that never produce observable events. Emergent drama claim fails.	Promote #103, #105 to high. New ticket: NPC confrontation behavior
4	Time system unresolved (Q-009)	Routines can't function, schedules can't exist, "daily life" concept breaks down.	Resolve Q-009 before Sprint 1
5	Monologue content underestimated	Internal monologue carries the heaviest experiential burden in the game. Generic/thin monologue = flat experience.	New ticket: monologue content pack as distinct authoring deliverable

---

Proposed New Tickets (Summary)

Title	Priority	Type	Rationale
Player interaction framework	Critical	Story	No way to interact with world beyond dialogue
Follow mechanic	High	Story	Required by D-027 criterion 4
Examine mechanic	High	Story	Investigation requires inspecting objects
Wait/time-skip mechanic	Medium	Story	Stakeout/observation requires time control
Character goal/pressure framework	High	Story	Players need reasons to act
NPC-to-NPC conversation system	High	Story	Social simulation requires NPC-NPC interaction
NPC player-awareness behavior	High	Story	NPCs must react to player presence/behavior
NPC pathfinding	High	Story	NPCs must navigate the station district
Contamination activation mechanic	High	Story	D-027 concept requires this, storyteller is low priority
Opening hook content (per character)	High	Story	First 5 minutes need direction
Monologue content pack	High	Story	Distinct authoring deliverable, separate from system
Basic environmental interaction (doors, objects)	Medium	Story	World needs to be interactive, not decorative
Environmental text content	Medium	Story	Signs, terminals, documents for world-building

Count: 13 new stories proposed. This would bring the total to ~245.

---

Gestalt out. The systems are well-designed. The gap is in the verbs and events that make those systems produce gameplay. We built a beautiful engine — now we need to put wheels on it.