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

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

title	description	type	status	workshop	agent	round	created
Round 1 — Paula's Track 1 Analysis: Strength of Concept Proof	Narrative depth analysis of concept proof claims across mechanical coverage, narrative delivery, and emotional resonance	workshop	archived	v01-gap-analysis	paula	1	2026-02-11

Round 1 — Paula's Track 1 Analysis: Strength of Concept Proof

Agent: Paula (Narrative & Political Depth) Track: 1 — Strength of Concept Proof Date: 2026-02-11

---

Overview

Let me complicate the question the workshop is asking. The workshop asks: "Does the ticket catalog deliver on each claim?" But what SUSTAINS a concept proof across 30 minutes of play isn't whether systems exist — it's whether those systems produce meaning. A mechanically flawless information boundary that generates no narrative tension has proved nothing. A triangle system that creates structural conflicts but no emotional stakes has proved nothing. The honest truth is that several of these claims have strong mechanical foundations but weak narrative connective tissue. The tickets build the skeleton. The question is whether the skeleton can hold flesh.

I'm evaluating each claim on three dimensions:

1. Mechanical coverage — Do the tickets build the system?
2. Narrative delivery — Does the system produce story?
3. Emotional resonance — Does the story make the player feel something?

---

Claim 1: Asymmetric Information Is the Core Mechanic

Tickets: #138-142 (info boundaries), #182-183 (divergent knowledge/relationships)

Mechanical Coverage: STRONG

The information boundary system (#138-142) is well-architected. Component-level access control (#139), observer-based entity filtering (#140), knowledge-based gating (#141), and NPC information boundaries (#142) form a complete pipeline. This isn't fog-of-war bolted on — it's structural. The ObserverSnapshot (D-020) means the client literally cannot display what the character doesn't know. Good.

Divergent starting knowledge (#182) and divergent relationships (#183) create the initial conditions for the smuggler and detective to see the world differently. The smuggler knows criminals and workplace gossip; the detective knows institutional info and case files. Same NPCs, inverted trust maps.

Narrative Delivery: MODERATE — with a significant gap

Here's where I need to complicate things. The tickets deliver data asymmetry — the smuggler sees different component data than the detective. But data asymmetry is not the same as narrative asymmetry. The question is: does the smuggler experience a different STORY, or just see different data fields on the same NPCs?

What's present: The smuggler knows the dock worker's name, their role in the smuggling operation, their debts. The detective sees "dock worker, routine shift pattern, no flags." That's a good starting divergence.

What's missing: There's no ticket that translates information asymmetry into interpretive asymmetry. The internal monologue system (#119-123) is the bridge here, but it's not explicitly connected to the information boundary system. The smuggler looking at the dock worker should trigger monologue like "Kael's running late again. If the boss notices..." while the detective sees the same person and gets "Dock worker. On schedule. Nothing unusual." That interpretive layer — where the same visual stimulus produces different character thoughts — is where information asymmetry becomes narrative asymmetry.

Gap: No ticket explicitly connects #138-142 (information boundaries) to #119-122 (monologue system) through character knowledge. The monologue tickets describe event triggers and line pools, but don't specify that monologue generation should query the character's knowledge state to produce character-specific interpretations of observed entities and events.

Emotional Resonance: WEAK — needs design work

Information asymmetry creates tension only when the player feels the weight of knowing or not-knowing. The smuggler who knows their colleague is smuggling contraband should feel the dread of being close to someone who could expose them. The detective who doesn't know should feel the frustration of seeing normalcy where their instincts say something is wrong.

These are emotional states that emerge from the monologue system reflecting on information boundaries, not from the boundaries themselves. The monologue needs to do emotional work — not just inform, but interpret with feeling.

Specific gap: #182 (divergent starting knowledge) is described as "inverted information sets" — a mechanical framing. It should also define emotional starting positions. The smuggler's knowledge of the criminal network comes with anxiety, loyalty pressure, and complicity. The detective's ignorance comes with institutional confidence and the nagging sense that this district is too quiet. Starting knowledge isn't just data — it's emotional context.

Risk Rating: MEDIUM

The mechanical foundation is solid. The narrative bridge (monologue as interpreter of information asymmetry) is designed but not explicitly wired. The emotional layer is underspecified. The claim will be mechanically provable but may feel flat without deliberate work on the interpretive and emotional dimensions.

Minimum Bar for v0.1

The smuggler and detective, looking at the same NPC, should produce different monologue lines that reveal different knowledge AND different emotional relationships to that knowledge. If the monologue says the same thing with different facts, we've failed. If it says different things with different feelings, we've proved the claim.

---

Claim 2: Fog of Perception Creates Tension

Tickets: #110-113 (shadowcasting -> fog rendering)

Mechanical Coverage: STRONG

Shadowcasting (#110), vision cone (#111), observer visibility query (#112), and fog rendering (#113) are all critical priority and well-specified. The vision cone with forward/peripheral/behind sectors means the player literally has a blind spot behind them. The fog returns on departure, so previously explored areas become uncertain. Solid.

Narrative Delivery: MODERATE

The workshop question is precise: is fogless-information (what you know but can't see) captured in the narrative layer? This is the most interesting question in the entire analysis.

What fog does mechanically: You can't see behind walls, around corners, or behind you. NPCs in fog are invisible.

What fog doesn't capture: Your character KNOWS things about what's in the fog. The smuggler knows their colleague is in the warehouse right now because they share a shift schedule. The detective knows the suspect lives in apartment 3B because of case files. This knowledge-in-fog is where tension lives — you know something is happening beyond your vision, but you can't verify it.

The monologue bridge: Ticket #119 (monologue event generation) includes "NPC proximity" as a trigger, but doesn't explicitly address the case where a known NPC is beyond perception range. The monologue should fire not just when you see something, but when you don't see something you expected. "Kael should be at the dock by now. Haven't seen him." That absence-awareness is where fog creates narrative tension, not just visual occlusion.

Gap: No ticket covers "expected-but-absent" detection — the system comparing the character's knowledge of NPC routines against observed reality and flagging discrepancies. This is the bridge between the information boundary system (#138-142) and the fog system (#110-113) that creates the narrative experience of "something's wrong but I can't see what."

Emotional Resonance: MODERATE

Fog inherently creates anxiety — you can't see what's there. But fog-of-perception is more specific: you can't see what you know is there. The smuggler who knows the contraband handoff happens in the next room, but can't see through the wall, feels complicity and dread. The detective who suspects activity behind that door, but has no legal authority to enter, feels frustration and moral tension.

These emotional states are character-specific responses to fog, mediated by knowledge and identity. The monologue system can deliver them, but the tickets don't explicitly call for knowledge-aware fog responses.

Risk Rating: MEDIUM-LOW

The mechanical system is strong. The narrative gap (knowledge-aware absence detection) is designable and not architecturally complex — it's a query against the character's known-NPC-routine data filtered against current perception. The emotional layer needs monologue lines authored specifically for "I know something is happening that I can't see" situations.

Minimum Bar for v0.1

At least one moment per playthrough where the monologue comments on the absence of something the character expected to see, creating tension about what's happening beyond the fog. The smuggler should think about a colleague who isn't where they should be. The detective should notice a suspect's routine has changed without being able to see why.

---

Claim 3: NPCs Feel Alive Without Player Attention

Tickets: #88 (daily routines), #93-99 (simulation tiers), #101 (routine execution)

Mechanical Coverage: STRONG

The simulation tier system (#93-99) is well-designed. Background NPCs tick through state machines (schedule, mood, relationships, job) at 1/game-minute. Active NPCs get full behavior. The tier transition system means NPCs are always somewhere doing something even when the player can't see them. Routine execution (#101) drives schedule-based movement.

Narrative Delivery: MODERATE — with a critical distinction

But what SUSTAINS the feeling of alive NPCs across hours of play is not whether they move on schedules — it's whether the consequences of their off-screen life are visible when the player returns.

What the tickets deliver: NPCs move between locations on schedule, change mood over time, and have relationships that drift. When you return to the bar after a day at work, the bartender is there because their schedule says they should be.

What the tickets don't explicitly deliver: Evidence of off-screen life that the player can discover. The bartender should have had a bad day while you were at work — their mood shifted, they argued with a regular, and when you arrive, their greeting is different. The background relationship dynamics ticket (#103) is marked MEDIUM priority and described as "relationship values change over time, decay, reinforcement" — but this is the mechanism that makes NPCs feel like they lived while you were away.

Gap 1: Relationship dynamics (#103) should be HIGH priority for v0.1. Without it, NPCs have routines but no interpersonal continuity. They move around the map, but their relationships don't evolve. This makes them automata, not people.

Gap 2: No ticket covers "off-screen event narration." When the player returns to a social site after absence, there should be discoverable evidence of what happened. The monologue might note "Something's different here. The regulars are avoiding the corner table." An NPC might reference an event: "You missed it — Sario and the boss had it out yesterday." These discovery moments are what make off-screen life legible to the player.

Emotional Resonance: WEAK without relationship dynamics

If NPCs only have routines, they feel like clockwork. If their relationships evolve off-screen and the player discovers the consequences, they feel like people with lives. The emotional payoff is: "the world didn't wait for me, and now I have to deal with what happened while I was gone."

Specific concern: Ticket #198 (Criterion 3: Emotional NPC attachment) is a validation ticket, not a design ticket. It says "after playthrough, player names an NPC they felt conflicted about." But no ticket is responsible for producing that emotional attachment. Emotional attachment emerges from repeated interactions where the NPC's responses reflect history, mood, and relationship state — which requires #103 (relationship dynamics), #170 (relationship history dialogue), and #172 (unprompted disclosure) all working together. Three of those four are MEDIUM priority.

Risk Rating: MEDIUM-HIGH

The mechanical simulation is solid. The narrative delivery mechanisms (relationship dynamics, off-screen event narration, unprompted disclosure) are either medium priority or missing. The emotional resonance target (Criterion 3) has no explicit design path to delivery. This is the claim most at risk of being mechanically present but narratively empty.

Minimum Bar for v0.1

After leaving a social site and returning, at least one NPC's behavior or dialogue must reflect something that changed while the player was away. And the player must be able to discover what changed through conversation or observation, not through a notification.

---

Claim 4: Observation Is a Mechanic, Not a Cutscene

Tickets: #115 (NPC vision), #124-128 (sound model), #119-122 (internal monologue)

Mechanical Coverage: MODERATE

The observe->notice->follow->discover chain requires:

• Observe: Vision system (#110-113) + NPC routines (#88, #101) = you can watch NPCs do things
• Notice: Tell system (#90) + monologue (#119-122) = something flags as unusual
• Follow: Player movement + NPC pathing = you can physically tail someone
• Discover: Information boundaries (#138-142) + dialogue layers (#168-174) = you learn something new

Each link in the chain has ticket coverage. The question is whether the chain is connected.

Narrative Delivery: THE CRITICAL QUESTION

The workshop asks: "Where does the MEANING come from?" This is the right question, and the honest answer is: meaning comes from the narrative interpretation that sits between each mechanical link.

Observe -> Notice: The player sees an NPC. What makes them notice? Not just the tell system mechanically flagging behavior. The monologue must contextualize: "That's the third time this week Kael has gone to the loading bay after hours. His shift ended an hour ago." The monologue transforms raw perception into suspicion. Without it, the player sees an NPC walking somewhere and has no reason to care.

Notice -> Follow: The player decides to follow. This is a player choice — no ticket can deliver it. But the game must make the choice feel available. The monologue can plant the seed: "I could follow him. Or I could mind my own business." This is where D-016's "diegetic tutorial" function becomes load-bearing. The monologue suggests actions without commanding them.

Follow -> Discover: The player follows and sees something. The discovery must be legible. If the smuggler follows Kael to a secret meeting, the scene needs to be readable through the fog system — partial information, overheard fragments, visible but unidentifiable figures. Then the monologue interprets: "That's... who is that? Kael never mentioned knowing anyone in cargo processing."

Gap: The tell system (#90) is described as "behavioral indicators" and "trait-driven behavior modifiers" — but there's no ticket specifying what tells LOOK LIKE in the top-down renderer. How does the player visually distinguish "NPC acting normally" from "NPC acting suspiciously"? In a 3D game, you'd see body language. In a top-down game with placeholder art, tells need to be communicated through:

• Movement pattern changes (NPC looks around before entering a room — needs animation states or movement hesitation)
• Routine deviations (NPC goes somewhere unusual — needs the "expected-but-absent" system I flagged in Claim 2)
• Monologue interpretation (character notices and comments — needs monologue wired to tell system)

The first two need visual/behavioral expression tickets. The third needs explicit monologue-tell integration.

Emotional Resonance: HIGH POTENTIAL — if the chain connects

The observe->notice->follow->discover chain, when it works, is the single most satisfying experience in detective fiction. The player who pieces together a conspiracy from their own observations — without quest markers, without explicit instruction — will feel the pride of genuine deduction. This is the game's highest-potential moment.

But it fails catastrophically if any link breaks. If observation doesn't produce noticeable tells, the player never starts the chain. If the monologue doesn't interpret what they see, they don't understand why it matters. If following doesn't lead to legible discovery, the payoff fizzles.

Risk Rating: MEDIUM-HIGH

The individual systems exist. The chain connections are underspecified. The visual expression of tells in top-down view is unaddressed. The monologue's role as narrative interpreter of the observation chain is implicit but not explicitly designed into the ticket connections.

Minimum Bar for v0.1

One complete observe->notice->follow->discover chain that works without scripted triggers. The player watches an NPC, notices a behavioral anomaly through tells and/or monologue, follows by choice, and discovers information that changes their understanding of a situation. This chain must emerge from systems, as Criterion 4 (#199) requires.

---

Claim 5: Same World, Different Story

Tickets: #179-183 (character builds), #196-199 (success criteria)

Mechanical Coverage: MODERATE

Character definition (#179), smuggler build (#180), detective build (#181), divergent knowledge (#182), and divergent relationships (#183) establish the starting conditions. But all five tickets are marked "NEEDS DESIGN DISCUSSION" — they're placeholders, not specifications.

Narrative Delivery: THE MAKE-OR-BREAK CLAIM

This is the claim I care most about, because it's where narrative depth either emerges or doesn't.

Mechanical divergence is easy: The smuggler has insider access; the detective has authority access. Different dialogue pools, different information boundaries, different starting knowledge. The tickets cover this.

Narrative divergence is hard: The smuggler and detective need to experience different stories, not just different access levels. Let me be specific about what this means:

The Smuggler's Story: Daily life is the cover. Going to work at the logistics hub IS the smuggling operation. The tension isn't "go investigate" — it's "maintain normalcy while the walls close in." The smuggler's relationships with criminal NPCs are loaded with loyalty, fear, and complicity. When the detective starts sniffing around (as a background event the smuggler notices), the smuggler's story is about protection — protecting colleagues, protecting the operation, protecting themselves. The emotional core is: how far will you go to protect people you care about who are doing illegal things?

The Detective's Story: Daily life is the investigation. Walking the district, talking to people, observing routines. The tension is "I know something is wrong but I can't prove it." The detective's relationships with institutional NPCs (the precinct, the informant network) are loaded with obligation and political pressure. When evidence points toward people the detective has started to like (bar regulars, workplace acquaintances), the detective's story is about betrayal — the discovery that normalcy was a mask. The emotional core is: what do you do when the truth threatens the community you've come to value?

Gap: The tickets describe starting conditions (knowledge, relationships, access). They don't describe narrative arcs. The smuggler's story has an arc: safety -> pressure -> crisis -> choice. The detective's story has an arc: confidence -> suspicion -> evidence -> confrontation. These arcs need to be designed, not just hoped for.

Specific missing elements:

1. Smuggler-specific tension escalation: No ticket describes how the smuggling ring's situation deteriorates over time, creating pressure on the smuggler. Does the operation get sloppy? Does a new rival appear? Does someone in the ring consider betraying the others? This pressure is what drives the smuggler's story forward.
2. Detective-specific investigation progression: No ticket describes how the detective accumulates evidence and builds a case. Is there a case file system? How does the detective know they're making progress? Investigation needs a progression mechanic beyond "discover more facts."
3. Convergence point: What happens when the smuggler's protective instincts and the detective's investigation collide? This doesn't need to be a scripted scene — but the game needs mechanical hooks for "the investigation reaches someone the smuggler cares about" and "the smuggler's colleague gets arrested/questioned." These are the emotional climaxes that make both stories meaningful.

Emotional Resonance: HIGH POTENTIAL — if arcs are designed

The smuggler protecting friends from justice and the detective pursuing justice that threatens a community are mirror images of the same moral question. This is genuinely powerful narrative design. But it requires:

• The smuggler to feel loyalty (relationship depth, shared history, trust)
• The detective to feel doubt (moral complexity, community attachment, institutional pressure)
• Both to face consequences (actions that ripple through the social fabric)

None of these emotional states are ticket-specified. They're assumed outcomes of systems that exist for other reasons.

Risk Rating: HIGH

This is the weakest claim in the ticket plan despite being the most important. The mechanical foundations (information boundaries, dialogue layers, character builds) exist. The narrative arcs that would make two playthroughs feel like different stories rather than different access levels are not designed. The emotional divergence — smuggler-as-protector vs. detective-as-pursuer — is powerful but entirely implicit.

Minimum Bar for v0.1

After playing both characters, a player should be able to describe each as having a different emotional journey, not just different starting information. "The smuggler was about protecting people; the detective was about uncovering truth" — not "the smuggler knew different things than the detective."

---

Claim 6: Social Triangles Create Emergent Drama

Tickets: #106-109 (triangle generation), #175-176 (entanglement ratio)

Mechanical Coverage: MODERATE

Triangle definition schema (#106), intra-template generation (#107), cross-template generation (#108), and validation (#109) cover the structural creation of triangles. The 30/50/20 entanglement ratio (#175) ensures most triangles are mundane, creating the noise floor that investigation requires.

Narrative Delivery: MODERATE — with critical gaps

The triangle model I proposed in Round 17 is sound: 3 NPCs with conflicting interests as the atomic unit of intrigue. But the tickets as specified describe triangle creation, not triangle dynamics.

What the tickets deliver: Generate three NPCs with conflicting interests. Validate that the conflict is viable. Place them in social sites.

What the tickets don't deliver:

1. Triangle escalation. Triangles are static at generation time — A owes B, B is jealous of C, C needs A's help. But triangles need to evolve. Over time, A's debt worsens. B's jealousy becomes resentment. C's need becomes desperation. Without escalation mechanics, triangles are situations, not stories. Stories need arcs.

Missing ticket: "Triangle escalation system" — periodic state updates that push triangle tensions toward breaking points. Connected to the tolerance threshold system (#105, medium priority) but not explicitly linked. When any NPC in a triangle approaches their tolerance threshold, the triangle should enter a new phase with different behavioral tells and dialogue options.

2. Triangle consequences. When a triangle breaks (tolerance exceeded, secret exposed, betrayal occurs), what happens? The NPC who breaks doesn't just change a relationship score — they ACT. They confront someone. They leave. They seek help from the player. They seek help from someone else, pulling that person into the triangle's aftermath.

Missing ticket: "Triangle resolution and aftermath" — behavioral responses when triangle tensions resolve (through breaking, intervention, or time). This is where triangles produce the emergent stories the claim promises.

3. Player involvement in triangles. The player enters an existing triangle as an external force. Their actions — helping one NPC, pressuring another, revealing information — shift the triangle's dynamics. But no ticket describes how player actions modify triangle state. The dialogue system (#168-174) allows the player to interact with individual NPCs, but doesn't describe how those interactions ripple through the triangle.

Missing ticket: "Player-triangle interaction effects" — how player actions toward one triangle member affect the others' attitudes, behaviors, and dialogue. This is the mechanism by which the player plays the social game.

4. Triangle visibility. How does the player discover that a triangle exists? They don't see a "triangle" — they see individual NPCs behaving in ways that suggest connections. The bartender complains about the landlord. The landlord asks about the bartender. The player connects the dots. This discovery process needs:

• Gossip lines that reference triangle members (#171, trust-gated gossip — medium priority)
• Behavioral tells when triangle members interact with each other (#90, tell system)
• Monologue interpretation when the player observes triangle dynamics (#119-122)

These systems exist but aren't explicitly connected to triangle generation.

Emotional Resonance: HIGH POTENTIAL — if triangles have arcs

A static triangle is a puzzle: figure out who wants what, play them against each other. A dynamic triangle is a drama: watch tensions build, see people hurt each other, feel the weight of intervening (or not). The emotional payoff of triangles is the feeling of being complicit in someone else's story — you made a choice, and it affected people who didn't ask for your involvement.

The mundane triangles (50% of the population per D-029) are where this emotional payoff matters most. A neighbor dispute that the player could resolve or inflame. A workplace rivalry where the player's promotion depends on who wins. These aren't intrigue — they're life. And they're what creates the attachment that makes intrigue stakes meaningful.

Risk Rating: MEDIUM-HIGH

Triangle creation is well-specified. Triangle dynamics (escalation, consequences, player interaction, resolution) are not. The claim promises "emergent drama" — but drama requires arcs, not just initial conditions. The tickets build triangle starting states; the narrative systems that make triangles evolve and resolve are missing or medium priority.

Minimum Bar for v0.1

At least one triangle that the player discovers through observation and dialogue, where their involvement (or non-involvement) produces a visible consequence affecting at least two NPCs' behavior. The triangle should feel like a story that happened because of the player's choices, not a static relationship the player noticed.

---

Missing Claims: What the Game Should Also Prove

Missing Claim A: Consequences Ripple Through the Social Fabric

The game makes a strong implicit claim that actions have consequences — but no ticket explicitly covers a consequence propagation system. When the player helps one NPC, their ally should warm toward the player AND their rival should cool. When the player reveals a secret, the exposed NPC's relationships should shift, and those shifts should cascade.

The relationship dynamics ticket (#103) covers dyadic changes. But cascading consequences — where an action toward A affects A's relationship with B, which affects B's behavior toward C — are the social-fabric simulation that makes the world feel interconnected.

Suggested ticket: "Consequence propagation — social ripple effects" (high priority). When a player action modifies a relationship, propagate effects through the relationship graph with decay. First-order effects are strong and immediate. Second-order effects are weaker and delayed. Third-order effects are ambient mood shifts.

Missing Claim B: Moral Complexity Is Systemic, Not Scripted

The game should prove that there are no clean answers. The smuggler isn't evil — they're protecting friends. The detective isn't good — they're serving an institution with its own agendas. This moral ambiguity needs to be systemic, not just written into backstory.

What's needed: NPCs in the smuggling ring should have sympathetic motivations discoverable through relationship building and trust-gated disclosure. The detective's institution should have questionable practices discoverable through investigation. The game should resist categorizing anyone as villain or hero.

What's missing: No ticket describes "institutional critique" content for the detective's faction — the case files that reveal overreach, the colleague who bends rules, the informant who feels exploited. Without this, the detective's institutional access feels like a superpower, not a complicated bargain.

Missing Claim C: Character Growth Through Experience

The v0.1 slice is 30 minutes, but even in that window, the character should change. Not level up — change in how they understand their world. The smuggler who discovers a colleague is in deeper trouble than they thought. The detective who realizes the district isn't what it seemed.

The monologue system can express this growth: early monologue is confident and routine; late monologue is uncertain and questioning. But no ticket describes monologue evolution over a play session — the progression from baseline character voice to experience-modified character voice.

Suggested ticket: "Monologue state progression" (medium priority). Track significant discoveries and relationship changes; modify monologue tone and content to reflect accumulated experience. Early: "Same old shift." Late: "Nothing about this place is what I thought it was."

---

Summary Scorecard

Claim	Mechanical	Narrative	Emotional	Overall Risk	Minimum Bar
1. Asymmetric info	Strong	Moderate	Weak	MEDIUM	Different monologue = different feelings, not just different facts
2. Fog = tension	Strong	Moderate	Moderate	MEDIUM-LOW	Monologue on absence: "I expected X and don't see it"
3. NPCs alive	Strong	Moderate	Weak	MEDIUM-HIGH	Discoverable evidence of off-screen change on return
4. Observation mechanic	Moderate	Moderate	High potential	MEDIUM-HIGH	One unscripted observe->notice->follow->discover chain
5. Same world, different story	Moderate	Weak	High potential	HIGH	Different emotional journeys, not just different access
6. Triangles = drama	Moderate	Moderate	High potential	MEDIUM-HIGH	One triangle with player-affected consequences

The Pattern

The ticket catalog builds strong mechanical foundations but underspecifies the narrative connective tissue between systems. The gaps are not in what systems exist — they're in how systems talk to each other to produce narrative meaning. The monologue system is the critical bridge between mechanical state and narrative experience, and it needs to be more explicitly wired to information boundaries, fog, observation, and relationship dynamics.

Priority Adjustments I'd Recommend

Ticket	Current	Recommended	Reason
#103 Relationship dynamics	Medium	High	Required for Claim 3 (NPCs alive) and Claim 6 (triangle dynamics)
#105 Tolerance threshold triggers	Medium	High	Required for Claim 6 (triangle escalation) and Claim 4 (observation chain)
#171 Trust-gated gossip	Medium	High	Required for triangle discovery and progressive revelation
#172 Unprompted disclosure	Medium	High	Required for NPC-initiated narrative moments and off-screen event narration
#123 Unreliable narrator	Low	Medium	Contributes to emotional depth but not critical for v0.1 proof
#162 Storyteller module activation	Low	Medium	Without storyteller, the 30-min runway has no escalation curve

New Tickets I'd Propose

1. "Knowledge-aware monologue integration" (high) — Connect monologue generation (#119) to information boundaries (#138-142) so that character knowledge produces character-specific interpretive commentary on observed entities and events.

2. "Absence detection system" (high) — Compare character's known NPC routine data against observed reality. Flag discrepancies. Feed into monologue system. "I expected to see X and don't." This is the bridge between fog and narrative tension.

3. "Triangle escalation and resolution" (high) — Periodic state updates that push triangle tensions toward breaking points. Behavioral changes when triangles enter crisis. Consequences when triangles resolve. Connected to tolerance thresholds (#105).

4. "Player-action social propagation" (high) — When player actions modify a relationship, propagate effects through the relationship graph. First-order strong and immediate, second-order weaker and delayed.

5. "Tell visual/behavioral expression" (high) — Define how NPC tells manifest in the top-down renderer. Movement hesitation, routine deviation markers, interaction changes. Without this, the observation chain has no visual starting point.

6. "Character arc progression — smuggler and detective" (high) — Design the narrative arcs for both characters: what emotional journey each follows, what escalation triggers drive the arc forward, what choice points emerge from systems. Not scripted events — designed pressure curves that systems can deliver.

7. "Monologue tone progression" (medium) — Track cumulative discoveries and relationship changes; modify monologue tone from confident/routine to uncertain/questioning as the play session evolves.

---

Final Assessment

The ticket catalog builds a simulation. What it doesn't yet fully build is a narrative experience. The gap isn't architectural — the systems are right. The gap is in the connective tissue: how information boundaries produce interpretive monologue, how fog produces absence-awareness, how triangles produce arcs, how the smuggler and detective produce different emotional journeys.

The honest truth is that the strongest claim (Claim 1: asymmetric information) and the weakest claim (Claim 5: different story) are two ends of the same problem. We have excellent mechanical infrastructure for information asymmetry. We have underspecified design for what that asymmetry means narratively. The v0.1 vertical slice will prove whether we can bridge that gap — but only if we deliberately design the bridge, not hope it emerges.

The monologue system is the MVP of narrative delivery. It's the cheapest system (it's text), the most flexible system (contextual, character-specific, mood-responsive), and the most load-bearing system (it translates mechanical state into emotional experience). Every gap I've identified routes through the monologue system. Investing in deep monologue integration with every other system is the single highest-ROI narrative decision for v0.1.