settled-reach/docs/workshops/content-gap-analysis_v0_1/round1-paula.md

Round 1 — Paula's Content Gap Analysis

Agent: Paula (Narrative & Political Depth) Workshop: v0.1 Content Gap Analysis Date: 2026-02-11

---

My Approach

The workshop asks nine layers of questions, moving from the most global (art direction) down to the most specific (audio). I'm addressed directly in Layers 2, 3, 5, 6, and 7. But let me complicate this structure: content gaps don't exist in layers — they exist in relationships between layers. A character voice profile (Layer 2) only means something if it connects to a dialogue format (Layer 4) that connects to a content pack (Layer 5) that connects to monologue lines (Layer 7). The gaps I'm most concerned about aren't within any single layer — they're at the seams.

I'll address each question directed at me with concrete proposals, then identify the cross-layer dependencies that the workshop structure might obscure.

---

Layer 1: Art Direction & Visual Identity

Not my primary domain, but I have a narrative stake here.

Narrative implication of the visual identity question: The two characters should feel different before a single line of monologue plays. If the art direction is "functional minimalism, atmosphere through text" (which I support for v0.1), then the visual differentiation between smuggler and detective must come from the insert/HUD layer, not from the world itself. The detective might see the district through an analytical overlay — case file annotations on locations, routine deviation markers. The smuggler might see it through a social map — who's friendly, who's dangerous, where the exits are.

This means the "visual identity" for v0.1 is partially a question for me: what does each character's neural insert show them? Even with placeholder art, the insert overlay can carry character-specific visual language. I'd defer to Araminta on execution, but the information design of what each character's HUD reveals is a narrative question.

---

Layer 2: Narrative Framework & Character Design

Question 1: What does the Dual Lens Authoring Guide (#261) need to contain?

This is the single most important pre-production document for content creation. Without it, Mellanie writes dialogue that works for one character but not the other. Miri designs a station that reveals itself the same way to everyone. Every content creator needs to understand the dual-lens principle before writing a single line.

Proposed contents of the Dual Lens Authoring Guide:

Part 1: The Two Characters

Dimension	Smuggler	Detective
Core identity	Logistics worker at the hub. Criminal activity is their day job disguised as normal work.	Institutional investigator. Assigned to the district on a routine case — or so it seems.
Emotional starting state	Comfortable but wary. This is home, these are friends, and the operation runs smoothly.	Professional and detached. This is an assignment, these are subjects.
Relationship to the district	Insider. Knows the rhythms, the shortcuts, who to avoid, who to trust.	Outsider. Reads the district through case files and institutional briefings.
What they notice first	People out of place. Routine disruptions. New faces. Things that threaten the operation.	Patterns. Inconsistencies. Things that don't match the official record.
What they miss	The institutional perspective — how this district looks from the outside, how exposed the operation actually is.	The human perspective — why people do what they do, what desperation drives the smuggling.
Internal monologue voice	Casual, sardonic, street-smart. Uses nicknames. Thinks in terms of loyalty and risk. "Kael's late again. Third time this week. That's how people get noticed."	Precise, observational, controlled. Uses titles and descriptions. Thinks in terms of evidence and procedure. "Dock worker, second shift. Arrived 12 minutes late. Noted."
Relationship default	Trust is earned through shared risk. New people are threats until proven otherwise.	Trust is institutional. Credentials open doors. Personal trust is a vulnerability.

Part 2: The Dual-Lens Rule

Every piece of content must pass this test: Does it read differently through each lens?

This doesn't mean every line needs two versions. It means every situation must have two interpretations. The same NPC behavior, the same location detail, the same overheard conversation should mean something different to each character.

Example — An NPC arriving late to work:

• Smuggler sees: A colleague whose reliability is slipping. Threat assessment — are they getting sloppy? Are they being watched? Should I cover for them?
• Detective sees: A data point. Late arrivals correlate with... what? Worth monitoring. File it.

Example — A locked room in the logistics hub:

• Smuggler knows: That's where the high-value cargo gets repackaged. Stay out unless it's your shift.
• Detective wonders: Restricted area, no manifest entries matching this space. What's in there?

Part 3: Access Tier Mapping

For each NPC role in each template, define the access tier per character:

NPC Role	Smuggler Access	Detective Access
Hub shift supervisor	Insider (colleague)	Authority (subject of inquiry)
Bar owner	Peer (regular customer)	Outsider (new face, no rapport)
Smuggling ring leader	Insider (direct report)	Unknown (doesn't know this person exists yet)
Dockworker (flat NPC)	Insider (coworker)	Outsider (background figure)
Off-duty security officer	Peer (bar acquaintance)	Peer (professional courtesy)

This table drives Layer 1 of the dialogue system (D-028): which lines each NPC will say to each character from minute one.

Part 4: Divergence Escalation Curve

The two experiences should start slightly different and diverge over time:

Phase	Time Window	Smuggler Experience	Detective Experience	Divergence Level
Arrival	0-5 min	Routine start. Greetings from colleagues. Comfortable.	Orientation. Reading the space. Nobody knows you.	Low — both just walking around
Daily life	5-15 min	Work shifts, bar visits, social rhythms. The operation hums in the background.	Observation, casual conversations, building a mental map. Small inconsistencies accumulate.	Medium — same NPCs, different relationships
Tension	15-25 min	Something is off. A colleague is nervous. New faces at the hub. The detective is asking questions.	Patterns emerge. Someone is lying. The district's rhythms have a hidden frequency.	High — both noticing the same disruption from opposite sides
Crisis point	25-30 min	The operation is at risk. Loyalty demands action.	Evidence points somewhere specific. The case demands action.	Maximum — both heading toward the same event from opposite directions

Part 5: Authoring Checklist

For every content piece (NPC profile, dialogue line, location description, monologue trigger), the author must answer:

1. Does the smuggler interpret this differently than the detective?
2. If yes, is the difference in access (they know different things), interpretation (they read the same thing differently), or emotional weight (the same information means more to one)?
3. If no, why not? (Some things are character-neutral — the bar serves drinks regardless. That's fine. But be deliberate about it.)

Is this a solo document or workshop output?

I should write the first draft. It's a narrative architecture document — the structure of how two perspectives coexist. But it needs input from:

• Mellanie — to validate that the voice profiles are writable and the checklist is usable
• Gestalt — to validate that the access tier mapping aligns with the dialogue system mechanics
• Miri — to validate that the station setting supports the divergence curve

Proposed workflow: I write a full draft, the team reviews in Round 2, Mellanie and I iterate until she can use it as her authoring bible.

---

Question 2: How do you define "divergent starting knowledge" (#182)?

Not a list of facts. A list of facts is inert — it doesn't generate gameplay. Divergent starting knowledge is a structural asymmetry in how the character understands the world.

Three dimensions of starting knowledge:

1. Factual knowledge — what you know is true

Category	Smuggler Knows	Detective Knows
People	Names, nicknames, personal details of all logistics hub workers + smuggling ring members. Bar regulars by face/habit.	Names and roles of institutional contacts. Case file subjects (partial, possibly outdated). District demographics from briefings.
Places	Layout of the hub including restricted areas. Hidden routes. Dead drops. Safe meeting spots.	Official district map. Registered businesses. Known gathering points from case history.
Routines	Shift schedules, break patterns, who drinks where, who avoids whom. The operation's timing.	Patrol routes. Shift change windows. Official facility hours.
Relationships	Who's sleeping with whom. Who owes whom. Who's reliable, who's cracking. The ring's hierarchy.	Chain of command. Informant network (if any). Known associates from prior cases.

2. Interpretive frameworks — how you read ambiguous information

This is more important than facts. The smuggler and detective don't just know different things — they think differently.

• Smuggler's framework: "Is this a threat to the operation?" Every new person, every unusual event, every authority figure is evaluated through this lens. The smuggler's paranoia is functional — it's kept them alive.
• Detective's framework: "Does this fit the pattern?" Every behavior, every routine deviation, every nervous glance is evaluated against a mental model of normal-vs-suspicious. The detective's analytical distance is professional — it's how they build cases.

These frameworks should be encoded as monologue biases. When the smuggler sees an ambiguous situation, the monologue leans toward threat assessment. When the detective sees the same situation, the monologue leans toward pattern analysis. Same stimulus, different interpretation, different suggested actions.

3. Emotional knowledge — what you feel about what you know

The smuggler doesn't just know the ring leader — they have feelings about them. Loyalty, fear, respect, resentment. These emotional weights on relationships determine which NPCs the smuggler protects, which they resent, which they'd sacrifice.

The detective doesn't just know the case file — they have feelings about the assignment. Ambition, boredom, duty, skepticism. These emotional weights on the investigation determine how aggressively they pursue leads, whether they bend rules, whether they start to sympathize with the people they're investigating.

Implementation proposal for #182:

Divergent starting knowledge is delivered through three ECS components per character:

1. KnowledgeInventory — list of known facts, tagged by source (personal experience, case file, rumor). Each fact has a confidence level and emotional weight.
2. InterpretiveFramework — set of biases that weight monologue generation. The smuggler's framework flags authority-related observations; the detective's flags pattern-related observations.
3. RelationshipMap — starting relationships with all known NPCs, including emotional valence (trust, fear, loyalty, professional respect, suspicion) not just access tier.

These three components together produce the starting divergence. Facts make you know different things. Frameworks make you interpret the same things differently. Emotional weights make you care about different things.

---

Layer 3: Station District Setting

Question 2: How does the station's character feed into NPC motivations?

The honest truth is that a station district's economic and social pressures are the engine that generates NPC motivations. NPCs don't exist in isolation — they exist in an economic ecosystem that creates the conditions for both ordinary life and criminal enterprise.

The motivational chain:

Station Economics → Employment Pressure → Individual Desperation → Criminal Opportunity → Social Complicity

Let me make this concrete with a proposal for how the v0.1 station district generates NPC motivations:

The district's economic reality: This is a logistics hub — goods flow through. The legitimate economy provides steady but modest work. The cost of living on the station is slightly too high for comfort on a single logistics salary. This creates a permanent mild financial pressure on the working population.

How this generates motivations:

NPC Type	Economic Pressure	Resulting Motivation	Smuggling Connection
Logistics worker (flat)	Paycheck covers rent but not much else	Contentment axis: moderate-low. Wants stability, not risk.	Aware something happens at the hub after hours. Doesn't ask questions.
Logistics worker (triangle)	Partner's medical debt, child's school fees	Want: financial relief. Secret: knows about the smuggling, tempted to participate.	The smuggling ring is a lifeline they haven't taken yet. The triangle: should they? Their partner suspects something.
Bar owner (triangle)	Business is marginal. The after-hours crowd is what keeps the lights on.	Want: keep the bar viable. Secret: knows the bar is a meeting point for the ring.	Complicit through inaction. Doesn't ask what the back room is used for. The triangle: the bar owner's employee is getting curious.
Ring member (entangled)	Started as a logistics worker who said yes. Now in too deep.	Want: get out without getting caught. Secret: considering cooperation with authorities.	The detective's potential informant. The smuggler's potential betrayer. The cross-template triangle.
Security officer (triangle)	Underpaid. Sees things. Faces a choice every shift.	Want: do the right thing, or at least not the wrong thing. Tolerance: how much can they ignore?	The mundane triangle: the security officer, the logistics supervisor who schedules the off-hour shifts, and the bar owner who provides the alibi drinks.

The key insight: Economic pressure doesn't just explain why smuggling exists — it explains why the community tolerates it. The bar owner looks the other way because the smugglers keep the bar profitable. The flat NPCs don't ask questions because they benefit from the economic activity without getting their hands dirty. The detective enters a community where everyone has a reason to not cooperate — not because they're villains, but because the smuggling economy is the district's immune system against poverty.

This is what makes the detective's job hard and the smuggler's moral position sympathetic. The station's economic character turns smuggling from a crime into a community survival strategy. That's the narrative engine.

What Miri's setting document needs from this perspective:

1. The economic squeeze — what makes legitimate life just hard enough to justify risk
2. The interdependencies — who benefits from the grey economy even without participating
3. The recent pressure point — what changed recently that's making the situation unstable (this becomes the storyteller's activation trigger)

---

Layer 4: Content Pipeline & Authoring Format

Not directly asked, but I have a critical dependency on this layer.

My concern: The four dialogue layers (D-028) need to be expressible in whatever format Gestalt proposes. Specifically:

• Access tier must be a per-line tag, because the same NPC says different things to insiders vs. outsiders vs. authority figures. This is Layer 1 of dialogue and the primary dual-lens mechanism.
• Relationship history needs a way to reference prior interaction states. A line tagged greeted_before:true reads differently than greeted_before:false. This is Layer 2 and drives the feeling of continuity.
• Trust tier must gate disclosure content. The same NPC has surface/real/secret versions of the same topic. This is Layer 3 and the mechanism for progressive revelation.
• Unprompted lines need mood and situational context tags. An NPC who volunteers information is driven by their current emotional state + the current situation. This is Layer 4 and the mechanism for NPC initiative.

Whatever format Gestalt proposes, I need to verify that all four layers can be expressed as line-level metadata. If they can't, the content packs will be flat — just access-filtered greeting pools with no depth.

---

Layer 5: Template Content (3 Social Sites)

Question 2: How do you design the relationship web for 3 overlapping social sites?

The relationship web is the narrative infrastructure of the vertical slice. Without it, 15 NPCs are 15 independent actors. With it, they're a community — interconnected, mutually dependent, full of tensions that the player can discover and exploit.

Design principles:

1. Every NPC has at least 2 relationships that matter — one within their home template, one that connects to another template. No NPC is an island.
2. Bridge NPCs connect templates — some NPCs have roles in multiple social sites. These are the most important characters because they carry information (and tension) between worlds.
3. The relationship web has layers — surface (visible to everyone), working (visible to insiders), and hidden (visible only through investigation or trust).

Proposed relationship web for v0.1 (15 NPCs across 3 templates):

Template 1: Logistics Hub (Workplace) — 5 NPCs

Role	Name Placeholder	Key Relationships
Shift Supervisor	NPC-A	Manages hub workers. Knows about the smuggling (looks away). Secret: taking a cut.
Logistics Worker 1	NPC-B	Smuggler's close colleague. Reliable ring member. The smuggler's anchor.
Logistics Worker 2	NPC-C	New hire. Curious. Asks questions they shouldn't. Triangle: B protects them, A wants them gone.
Dock Inspector	NPC-D	Legitimate authority. Bridge NPC: drinks at the bar after shifts. Secret: gambling debt makes them compromisable.
Maintenance Tech	NPC-E	Flat NPC. Fixes things, notices things, says nothing. Background presence that establishes normalcy.

Template 2: Bar (Social Venue) — 5 NPCs

Role	Name Placeholder	Key Relationships
Bar Owner	NPC-F	Knows everyone. Bridge NPC: supplies from the logistics hub. Complicit through willful ignorance.
Regular (off-duty security)	NPC-G	Bridge NPC: patrols the hub district during shifts, drinks at the bar after. Mundane triangle: F and G and D play cards — D owes G money, G pressures D, D considers compromising an inspection.
Regular (teacher/family person)	NPC-H	The most normal person in the district. Mundane triangle: H's partner works at the hub (NPC-B). H doesn't know what B does after hours. H represents what's at stake — ordinary life that smuggling protects and endangers.
Bartender	NPC-I	Flat NPC. Observant but discreet. Serves drinks, overhears everything, tells nothing. Source of ambient gossip if trust is built.
Drifter/New Arrival	NPC-J	Flat NPC but narratively loaded: new in the district, asking around for work. Could be innocent. Could be a rival operation's scout. Could be an undercover agent. The ambiguity is the point — the smuggler and detective read this person differently.

Template 3: Smuggling Ring (Criminal) — 5 NPCs

Role	Name Placeholder	Key Relationships
Ring Leader	NPC-K	The person the detective is ultimately looking for (without knowing it). Bridge NPC: legitimate business front at the bar. Public face is respectable.
Courier	NPC-L	Moves product. Bridge NPC: uses the logistics hub's infrastructure. Triangle with B and K: B arranges access, K gives orders, L takes the physical risk.
Fence/Buyer	NPC-M	External contact. Not from this district. Appears occasionally. The smuggler knows them; the detective has never seen them.
Ring Member (wavering)	NPC-N	The potential informant. Triangle with K and A: K demands loyalty, A applies pressure, N is cracking under the tolerance threshold. The detective's unknowing target. The smuggler's biggest worry.
Lookout/Runner	NPC-O	Flat NPC. Young, nervous, stationed at strategic positions. Visible to both characters — the smuggler knows why they're there, the detective reads them as loitering youths.

Bridge NPCs (connecting templates):

NPC	Home Template	Connected To	Bridge Function
NPC-D (Dock Inspector)	Hub	Bar	Professional life at hub, social life at bar. Information flows between worlds.
NPC-G (Security Officer)	Bar	Hub	Social at bar, authority at hub. Sees things in both contexts.
NPC-K (Ring Leader)	Ring	Bar	Criminal at ring, legitimate at bar. Public face conceals operation.
NPC-L (Courier)	Ring	Hub	Criminal at ring, logistics at hub. Physical movement connects sites.
NPC-B (Logistics Worker)	Hub	Ring	Day job at hub, ring member after hours. The smuggler's closest colleague.
NPC-H's partner	Bar	Hub	(Not a separate NPC — NPC-H references NPC-B's hub role.)

The web has 6 bridge connections across 3 templates, meaning information, tension, and consequences can propagate in multiple directions.

---

Question 3: How many triangles per template? What do they look like concretely?

D-029 requires 2 per template minimum + 1 cross-template. For v0.1, I propose 7 triangles total: 2 per template (6) + 1 cross-template.

Intra-template triangles (6):

Hub Triangle 1 — The New Hire Problem (B-C-A)

• B (loyal ring member) wants to protect C (curious new hire) from learning too much
• A (shift supervisor taking a cut) wants C removed before they see something
• C just wants to do their job but keeps noticing locked rooms and irregular schedules
• Player relevance: The smuggler has to choose between B's protective instinct and A's pragmatism. The detective notices C asking questions and wonders why B is so protective.

Hub Triangle 2 — The Inspection Squeeze (A-D-K)

• A (supervisor) needs inspections to go smoothly
• D (dock inspector) has a gambling debt and is being pressured
• K (ring leader, acting through intermediaries) is the source of the pressure
• Player relevance: The smuggler knows the inspection schedule is managed. The detective sees D's nervousness and smells corruption.

Bar Triangle 1 — The Card Game Debt (D-G-F)

• D (dock inspector) owes money from the weekly card game
• G (security officer) holds the debt and pushes for favors in return
• F (bar owner) facilitates the card games and profits from the arrangement
• Player relevance: Mundane triangle. No conspiracy connection. But the debt creates leverage that the smuggling ring exploits, and the detective might misread as conspiracy when it's just gambling. Red herring potential.

Bar Triangle 2 — The Worried Partner (H-B-F)

• H knows their partner B has been working late and spending more
• H confides in F (bar owner), who knows exactly why B is busy but won't say
• F reassures H while protecting the operation's secrecy
• Player relevance: The most emotionally loaded mundane triangle. H's worry is genuine. F's reassurance is a lie of omission. B is oblivious to the anxiety they're causing. The detective who earns H's trust might hear the first honest account of B's behavioral changes.

Ring Triangle 1 — The Wavering Member (K-N-L)

• K (ring leader) demands total loyalty from N (wavering member)
• N is considering cooperation with authorities — terrified of both sides
• L (courier) suspects N is unreliable and has told K as much
• Player relevance: The highest-stakes triangle. The smuggler knows N is shaky and must decide whether to support them or report them to K. The detective doesn't know N exists yet but will find them through investigation.

Ring Triangle 2 — The Power Dynamic (K-A-B)

• K (ring leader) gives orders through A (supervisor, the legitimate front)
• A resents taking orders but needs the money
• B (loyal to the smuggler/the team, not to K personally) would side against K if pushed
• Player relevance: Internal ring politics. The smuggler navigates this hierarchy daily. The detective, if they crack the ring, would exploit these fissures.

Cross-template triangle (1):

The Big One — The Informant Question (N-D-G)

• N (wavering ring member) is considering talking
• D (dock inspector) is compromised but might flip if pressured correctly
• G (security officer) has the institutional authority to act but doesn't know what they'd act on
• These three people, across all three templates, represent the three ways the ring could unravel: from inside (N betrays), from institutional corruption (D breaks), or from legitimate authority (G stumbles onto something)
• Player relevance: The smuggler wants to prevent all three. The detective, unknowingly, is pushing toward all three. The convergence of this triangle IS the crisis point of the vertical slice.

Triangle distribution by entanglement:

Category	Triangles	D-029 Split
Flat NPCs (no triangle involvement)	—	E, I, O = 3 NPCs (20%)
Mundane triangles (no conspiracy)	Card Game Debt, Worried Partner	7 NPCs in mundane-only roles (~47%)
Entangled triangles (conspiracy-connected)	New Hire, Inspection, Wavering Member, Power Dynamic, Cross-template	5 NPCs with conspiracy connection (~33%)

This skews slightly higher on entanglement than the 30/50/20 target (D-029), but the v0.1 district is small and needs to prove the concept. In a full game, the ratio would normalize with many more flat and mundane NPCs. For the vertical slice, we need enough entanglement to create discoverable conspiracy threads.

---

Layer 6: NPC Profiles & Dialogue

Question 1: How deep does each NPC profile need to be?

Let me complicate this by separating what the system needs from what the authors need.

What the system needs (ECS data): All 10 axes per D-024, populated as numeric values or enums. The system doesn't read backstory — it reads component data. This is the minimum: a fully populated NPC generation output.

What the authors need (creative brief): The 10 axes are a skeleton. Mellanie can't write voice-consistent dialogue from a skeleton. She needs flesh.

Proposed three-tier NPC profile depth:

Tier 1: Full profile (entangled NPCs — 5 NPCs: A, B, K, L, N)

Section	Contents	Length
10-axis data	All axes populated with values and brief justification	~20 lines
Backstory paragraph	How they got here, what shaped them, what they're hiding	3-5 sentences
Voice sample	3-5 example lines in their voice, covering different moods	3-5 lines
Dual-lens notes	How the smuggler sees them vs. how the detective sees them	2-3 sentences per lens
Triangle role notes	Their function in each triangle they participate in, what pressures they face	2-3 sentences per triangle
Secret	What they're hiding, from whom, and what would happen if it came out	2-3 sentences

Total per NPC: ~1 page. For 5 entangled NPCs: ~5 pages.

Tier 2: Working profile (triangle NPCs, non-entangled — 7 NPCs: C, D, F, G, H, M, O)

Wait — let me reconsider. O is flat. M is external. Let me re-sort.

Triangle-involved but not conspiracy-entangled: C, D, F, G, H = 5 NPCs.

Section	Contents	Length
10-axis data	All axes populated	~15 lines
Voice sample	2-3 example lines	2-3 lines
Dual-lens notes	Brief note on each character's perspective	1-2 sentences per lens
Triangle role notes	Their function in their triangle(s)	1-2 sentences

Total per NPC: ~half page. For 5 triangle NPCs: ~2.5 pages.

Tier 3: Sketch profile (flat NPCs — 5 NPCs: E, I, J, M, O)

Section	Contents	Length
10-axis data	Essential axes only (Want, Routine, Personality)	~8 lines
Voice hint	1 line that captures their energy	1 line
Function note	Why they exist in the world, what role they serve for atmosphere	1-2 sentences

Total per NPC: ~quarter page. For 5 flat NPCs: ~1.25 pages.

Grand total: ~8.75 pages of NPC profiles for the entire v0.1 cast. This is a manageable authoring load. I'd write Tier 1 profiles (the narrative architecture). Mellanie takes them and writes the voice kits and dialogue. Miri validates cultural/setting consistency.

---

Layer 7: Monologue & Observation Text

Question 3: What are the "mirror moments"?

Mirror moments are the places where the monologue hints — without breaking character — that this situation looks completely different from another perspective. They're not fourth-wall breaks. They're moments where the character's own thoughts inadvertently reveal the existence of an alternate interpretation.

The principle: A mirror moment occurs when the character's certainty about something is, from the other character's perspective, obviously wrong — and the monologue's confidence IS the tell.

Concrete mirror moments for v0.1:

Mirror 1: The Smuggler's Comfort

• Smuggler monologue: "Same shift, same faces. At least I know where I stand here."
• What the detective would see: A logistics hub where "same faces" means a closed social network resistant to outside inquiry. The comfort IS the suspicion.
• Design note: This plays in the first 5 minutes. It establishes the smuggler's world as normal and inviting. Only on the detective's playthrough does the player realize that "knowing where you stand" is exactly what makes the smuggling possible.

Mirror 2: The Detective's Read

• Detective monologue: "The dock inspector keeps glancing at the supervisor's office. Anxiety? Guilt? Worth noting."
• What the smuggler would know: D owes money from the card game and A has been riding them about inspection schedules. It's not guilt — it's stress about completely mundane workplace pressure. Or is it? The smuggler knows the mundane explanation but the detective's suspicion isn't wrong — D IS compromised, just not in the way the detective thinks.
• Design note: This plays mid-session. It shows the detective building a theory from observation — a theory that's simultaneously correct and incorrect.

Mirror 3: The Worried Partner

• Smuggler monologue (at the bar): "H looks tired. I should probably not mention seeing B at the hub so late — that's B's business."
• Detective monologue (at the bar): "Spouse of a hub worker. Looks stressed. Might know something about after-hours activity."
• Design note: Same person, same moment. The smuggler sees a friend they're protecting from the truth. The detective sees a potential source. The player who's played both characters recognizes the tragic irony — H is caught between two people who both think they're acting in H's interest.

Mirror 4: The Empty Corridor

• Smuggler monologue (passing a corridor late at night): "Quiet tonight. Good. Nobody using the south access."
• Detective monologue (same corridor, same time): "This corridor should see foot traffic — logistics staff use it for the night shift changeover. Why is it empty?"
• Design note: The smuggler's relief IS the detective's clue. The corridor is empty because the smuggling operation rerouted traffic. The smuggler knows this and is grateful. The detective doesn't know but senses something is wrong.

Mirror 5: The New Face

• Smuggler monologue (seeing NPC-J the drifter): "New face at the bar. Don't recognize them. Probably nothing, but... keep an eye out."
• Detective monologue (seeing NPC-J): "New arrival in the district. Looking for work, they say. Could be useful — fresh perspective, no local loyalties yet."
• Design note: The smuggler sees a potential threat. The detective sees a potential asset. Both are evaluating the same stranger through opposing frameworks. On replay, the player recognizes the irony — neither is wrong, and both reactions reveal their character.

How mirror moments are authored:

Mirror moments are NOT scripted paired events. They're monologue lines tagged to the same observation trigger but filtered through different character frameworks. The system requirements:

1. An observation trigger (NPC behavior, environmental state, routine deviation)
2. Two monologue line variants tagged to the same trigger, one per character
3. The lines must be independently coherent — each works on its own without the other
4. The mirror quality only emerges on replay, when the player remembers the other character's reaction

Authoring volume estimate: I'd target 10-15 mirror moments for the v0.1 vertical slice. Not every observation needs a mirror — that would feel forced. But 10-15 well-placed mirrors across 30 minutes means the replay playthrough produces a revelation roughly every 2-3 minutes. That's the rhythm of "oh, THAT'S what that was about" that makes the second playthrough compelling.

---

Layer 8: UI Text & Environmental Content

Not directly asked, but I have a narrative-critical input.

The neural insert must reflect character identity. If both characters see the same HUD, the diegetic fiction breaks. The smuggler's insert might show:

• Known associate locations (social map)
• Delivery schedules and routes
• Informal warnings ("avoid sector 7 — patrol activity")

The detective's insert might show:

• Case file markers (suspect locations, evidence flags)
• Institutional alerts
• Formal status reports ("Subject B: routine deviation detected")

This is a dual-lens question — the insert IS the character's window into the world. Even in v0.1 with minimal HUD, the insert text should feel different per character.

---

Layer 9: Audio Direction

Not my domain, but one narrative note: silence is a monologue trigger. The three-range sound model (D-018) means that close range provides rich audio. But when the player is alone in a quiet space, the absence of sound should trigger monologue. The character thinks when the world is quiet. This means the monologue system and the sound system need to coordinate — monologue fires more frequently when the audio environment is sparse, and less frequently when it's rich.

This has a dual-lens application: the smuggler alone in a quiet corridor thinks "Too quiet. Something's off." The detective alone in the same corridor thinks "Good. Time to think." Same silence, different interpretation.

---

Cross-Layer Dependencies: The Seams That Matter

The workshop's layer structure is useful for organizing work, but the content gaps I'm most worried about live between layers:

Dependency	From Layer	To Layer	Why It Matters
Dual Lens Guide must precede all content	2	4, 5, 6, 7	Every content author needs the guide before writing. Without it, content will be single-perspective and need rewriting.
Access tier mapping drives dialogue format	2	4	The authoring format must support per-character access tiers on every line. If the format can't express "this line is for insiders only," the dual-lens system collapses.
Station economics drive NPC motivations	3	5, 6	NPC profiles can't be written without understanding the economic pressures that shape their choices. Miri's setting document feeds Paula's relationship web feeds Mellanie's dialogue.
Relationship web drives content packs	5	5 (internal)	Content packs for each template can't be written independently — the bridge NPCs and cross-template triangles create dependencies between all three packs.
Mirror moments require authoring format	7	4	The format must support tagging the same observation trigger with character-specific monologue variants. If it can't, mirror moments are impossible to author systematically.
NPC profiles drive voice kits	6	5	Mellanie writes voice kits from NPC profiles. Profiles must exist before dialogue.

Proposed dependency chain for content work:

1. Station setting document (Miri) — Layer 3
   ↓
2. Dual Lens Authoring Guide (Paula) — Layer 2
   ↓
3. Relationship web + triangles (Paula) — Layer 5
   ↓
4. NPC profiles: Tier 1 entangled (Paula) + Tier 2/3 (Paula+Mellanie) — Layer 6
   ↓
5. Authoring format locked (Gestalt) — Layer 4
   ↓
6. Content packs: voice kits, situation scripts, monologue lines (Mellanie) — Layer 5 + 7
   ↓
7. Mirror moment pass (Paula reviews Mellanie's monologue for mirror opportunities) — Layer 7

Steps 1-4 are narrative architecture. Steps 5-7 are content production. The architecture must be done before production starts, or we'll be rewriting content to fit a structure that didn't exist when it was written.

---

Summary: What I Need To Deliver

Deliverable	Layer	Depends On	Estimated Effort
Dual Lens Authoring Guide (full draft)	2	Nothing — can start now	2-3 days
Divergent starting knowledge specification	2	Setting document (Miri)	1-2 days
Relationship web for 15 NPCs	5	Setting document (Miri)	1-2 days
Triangle definitions (7 triangles)	5	Relationship web	1 day
NPC profiles: Tier 1 (5 entangled)	6	Relationship web + triangles	2-3 days
NPC profiles: Tier 2 (5 triangle)	6	Tier 1 profiles	1-2 days
NPC profiles: Tier 3 (5 flat)	6	Setting document	1 day
Mirror moment design (10-15 moments)	7	All NPC profiles + Dual Lens Guide	1-2 days
Review pass on Mellanie's content packs	5+7	Mellanie's draft packs	Ongoing

The Dual Lens Guide is my first and most critical deliverable. Everything downstream depends on it.