jpmschweitzer/settled-reach
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(copy): remove v0.1 hand-authored content and detective mission system (#656, #657)

Browse Source 
Delete 64 hand-authored Krenn dialogue/monologue/NPC files superseded
by generated NPCs (D-122) and voice pipeline (D-138). Remove detective
investigation system dropped in v0.2 pivot (D-117): knowledge catalog,
faction, design docs, workshop archives, wireframe detective sections.
Clean investigation.* fact_id references from environmental and triangle
files. Strip investigation cross-references from overheard.yaml.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
jpmschweitzer
2026-03-13 11:44:26 +01:00
co-authored by Claude Opus 4.6
parent ce8c748462
commit e4f2477323
113 changed files with 34 additions and 32520 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/workshops/content-gap-analysis_v0_1/SUMMARY.md
-373
View File
@@ -1,373 +0,0 @@
# v0.1 Content Gap Analysis Workshop — Summary
**Workshop dates:** 2026-02-11
**Participants:** Mellanie, Paula, Araminta, Miri, Gestalt, Ozzie
**Facilitator:** Team Leader (Jeroen)
**Documenter:** Qatux
---
## Executive Summary
The v0.1 Content Gap Analysis Workshop examined 9 content layers across the vertical slice (D-027) to identify what content exists, what's missing, and what blocks production. Six agents delivered independent Round 1 analyses, then synthesized across all outputs in Round 2. The project lead made 9 directive decisions between rounds.
**Key outcomes:**
- 9 new confirmed decisions (D-032 through D-040)
- THE FRIEND NPC pattern established as emotional centerpiece (one production-level NPC per character)
- Converged tag taxonomy for line pools (6 structural + 3 selection tags)
- Sova Transit District / Krenn System confirmed as first concrete setting
- Audio confirmed in v0.1 scope (8 files via Stable Audio Open)
- All 6 wow moments promoted to v0.1 scope
- Wiki taxonomy structure declared non-negotiable
- ~50 new tickets identified across all agents (deduplicated below)
- Full dependency chain mapped with critical path: Dual Lens Guide → Voice Kits → THE FRIEND → Validation → Scale
---
## Workshop Structure
**Round 1:** Each agent independently analyzed 9 content layers against the vertical slice spec (D-027). Layers: character voice, dialogue, monologue, environmental text, NPC profiles, spatial layout, audio, visual design, wiki/lore.
**Between rounds:** Project lead reviewed all 6 outputs and issued 9 directive decisions.
**Round 2:** Each agent read all 6 Round 1 outputs plus directives. Synthesis: convergences, disagreements, dependency chains, concrete next steps, missing tickets.
**Workshop brief:** `docs/workshops/content-gap-analysis_v0_1/content-gap-analysis-workshop-brief.md`
**Round 1 outputs:** `round1-{agent}.md` (6 files)
**Round 2 outputs:** `round2-{agent}.md` (6 files)
---
## Project Lead Decisions (Between Rounds)
These 9 directives were issued by the project lead after reviewing Round 1 outputs. They are non-negotiable constraints for Round 2 and all downstream work.
| # | Directive | Status |
|---|-----------|--------|
| 1 | Separate monologue pools per character | Confirmed, non-negotiable → D-032 |
| 2 | Color = relationship to player | Approved → D-033 |
| 3 | Audio included in v0.1 (6-8 files via Stable Audio Open, self-hosted) | Confirmed → D-038 |
| 4 | One NPC per character = THE FRIEND, production-level complex | Confirmed → D-034 |
| 5 | Wiki taxonomy structure: non-negotiable, must be established NOW | Confirmed → D-040 |
| 6 | Sova Transit District / Krenn System: first concrete star system | Confirmed (worldbuilding milestone) → D-036 |
| 7 | Detective's FRIEND: Sera Venn (Paula's design) | Confirmed → D-034 |
| 8 | All 6 wow moments in scope (Ozzie's 4 essential + 2 nice-to-have all promoted) | Confirmed → D-039 |
| 9 | Stable Audio Open licensing confirmed (free commercial under $1M revenue) | Confirmed → D-038 |
---
## Decisions Produced (D-032 through D-040)
Full decision text in `decisions/*.md`. Summary:
| ID | Title | Domain | Source |
|----|-------|--------|--------|
| D-032 | Separate monologue pools per character | content.md | Project lead directive #1 |
| D-033 | Entity color = relationship to player | perception.md | Araminta R1 proposal, project lead directive #2 |
| D-034 | THE FRIEND production-level NPC pattern | content.md | Ozzie R1 concept, project lead directive #4, Paula R2 designs |
| D-035 | Converged tag taxonomy for line pools (6+3) | content.md | Gestalt R1/R2 + Mellanie convergence |
| D-036 | Sova Transit District / Krenn System as v0.1 setting | content.md | Miri R1, project lead directive #6 |
| D-037 | Contraband specification | content.md | Miri R1/R2 proposal, team validation |
| D-038 | Audio in v0.1 scope via Stable Audio Open | scope.md | Project lead directives #3, #9; Ozzie R2 spec |
| D-039 | v0.1 wow moment scope — all 6 moments | scope.md | Ozzie R1/R2, project lead directive #8 |
| D-040 | Wiki taxonomy structure | process.md | Miri R2 proposal, project lead directive #5 |
---
## Key Convergences
Areas where multiple agents independently reached the same conclusion:
### Fully aligned (no further discussion needed)
- **Dual Lens Guide is the root dependency** — all 6 agents identified this
- **Monologue carries the game** — perception, tells, atmosphere, tutorial, character voice (Gestalt, Mellanie, Ozzie)
- **YAML for line pools** — Mellanie proposed, Gestalt refined, no disagreement
- **5 tell categories for v0.1** — text-via-monologue as renderer (Gestalt, Araminta, Mellanie)
- **30/50/20 entanglement ratio works** — validated against 15 NPCs (Paula, Gestalt)
- **Spatial layout is load-bearing** — sightlines are gameplay (Araminta, Paula, Ozzie)
- **Miri's setting is the substrate** — everyone builds on Sova Transit District
### Converged during Round 2
- **Tag taxonomy**: 6 structural + 3 selection tags per dialogue line; 3 additional for monologue (Gestalt R2 section 1)
- **Situation taxonomy**: 13 situations from Gestalt + Mellanie merge
- **THE FRIEND mechanical spec**: full pipeline depth test, ~70-100 authored lines per NPC
- **Audio architecture**: event-driven with asset registry + visual fallback (Gestalt R2 section 6)
- **Line previewer MVP**: Rust CLI sharing pipeline code, 7 must-have features (Gestalt R2 section 7)
- **NPC relationship web**: 15 NPCs, 5 triangles (Paula R2 reconciliation)
- **Dependency chain**: three parallel tracks converging at content packs (Paula R2 section 2)
- **Placeholder art pipeline**: four phases, zero image files for v0.1 (Araminta R2 section 3)
### Minor divergences resolved
- **Paula proposed 7 triangles, Gestalt proposed 4** → Paula reconciled to 5 triangles
- **Mellanie proposed 8 per-line tags, Gestalt proposed more** → Converged to 6+3 (dropped location and type from per-line, made them directory-level)
- **Mellanie wanted to defer audio** → Project lead overruled; audio confirmed
- **Araminta wanted to defer audio entirely** → Project lead overruled; visual indicators complement audio
- **Detective's FRIEND candidate** → Mellanie proposed Lera (bar owner), Paula proposed Sera Venn (Commission tech) → Project lead confirmed Sera Venn
---
## Open Questions
### Updated existing questions
- **Q-003 (Art direction)**: Further resolved. Araminta's v0.1 Visual Grammar proposal covers color palette, entity rendering, fog states, zone palettes. Long-term art direction remains open.
- **Q-005 (Prototype scale)**: Further resolved. 15 NPCs, 3 social sites, 1 district (Sova Transit). Full game scale TBD.
### New questions raised during workshop
| ID | Question | Owner | Context |
|----|----------|-------|---------|
| Q-012 | How does the generation expansion pass work? LLM, template-based, or rule-based? | Gestalt, Mellanie | Affects how base lines are authored. LLM needs style-strong anchors; rules need substitution patterns. |
| Q-013 | How does the line previewer handle THE FRIEND's temporal progression? | Gestalt, Dudley | Previewer needs sequence mode to simulate multi-visit contradiction arcs. |
| Q-014 | Audio timing with monologue — when does the chime fire relative to text? | Gestalt, Ozzie | Affects monologue line writing rhythm (first word shouldn't be the important one if chime precedes). |
| Q-015 | Does 4x generation expansion apply to THE FRIEND's custom lines? | Mellanie, Gestalt | Ozzie recommends no expansion on FRIEND lines — every line hand-authored. |
| Q-016 | Knowledge hierarchy for monologue prerequisites | Gestalt, Paula | Need `suspects` < `knows_of` < `knows_details` hierarchy, not binary `knows: X`. |
| Q-017 | Triangle pressure threshold — what events trigger escalation? | Gestalt, Paula | Need numeric pressure model for `confrontation` situation activation. |
---
## Ticket Inventory (Deduplicated)
Tickets identified across all 6 agents, deduplicated and categorized. Cross-referenced against existing tickets where applicable.
### THE FRIEND (Critical — pipeline depth test)
| Ticket | Owner | Priority | Notes |
|--------|-------|----------|-------|
| THE FRIEND: Smuggler (Kael Davan) — full profile + contradiction arc | Paula (profile), Mellanie (voice) | Critical | ~75-100 authored lines |
| THE FRIEND: Detective (Sera Venn) — full profile + contradiction arc | Paula (profile), Mellanie (voice) | Critical | ~75-100 authored lines |
| Contradiction arc design document (reusable pattern) | Paula | High | Template for future complex NPCs |
| THE FRIEND visual treatment spec | Araminta | High | Color transition, earned visual detail |
### Opening Experience (Critical — first impression)
| Ticket | Owner | Priority | Notes |
|--------|-------|----------|-------|
| Opening hook content — smuggler (10-15 monologue lines) | Mellanie | Critical | Diegetic tutorial, sets voice |
| Opening hook content — detective (10-15 monologue lines) | Mellanie | Critical | Different emotional register |
| First monologue surprise moment (per character) | Mellanie, Paula, Gestalt | High | Core mechanic proof before minute 15 |
### Character & Narrative Architecture (Critical path)
| Ticket | Owner | Priority | Notes |
|--------|-------|----------|-------|
| Character voice speech patterns | Paula + Mellanie | High | Speech-level detail for voice kits |
| Access tier shift design document | Paula + Gestalt | High | How access changes during gameplay |
| Mirror moment design document | Paula + Mellanie | Medium | 10-12 paired observation triggers |
| Flat NPC "almost interesting" pass | Mellanie | High | Investigation noise floor |
| Diegetic insert flavor text (per character) | Mellanie | Medium | Character-specific HUD text |
| Diegetic tutorial monologue lines (8-10 per character) | Mellanie | Medium | Movement, fog, sound, NPC interaction |
| News ticker content — Sova (20-30 lines) | Mellanie + Miri | High | Cheap worldbuilding, high atmosphere |
### Setting & Worldbuilding
| Ticket | Owner | Priority | Notes |
|--------|-------|----------|-------|
| Sova Texture Appendix (slang, idioms, decoration, local complaint) | Miri | Critical | Blocks Mellanie's dialogue authoring |
| Krenn System wiki entry (first star system profile) | Miri | High | Sets template for all future systems |
| Sova Station Profile | Miri | High | Off-district references in dialogue |
| Detective institutional chain of command | Miri + Paula | High | Blocks detective character build |
| Meridian coverage map for Sova Transit | Miri | Medium | Investigation mechanics, ring ops |
| Off-station connections brief | Miri | Medium | Ring NPC dialogue consistency |
| Span gate transit schedule | Miri | Medium | NPC routine design, ring timing |
| Observation gallery / viewport description | Miri | Low | Ozzie's "something out the window" |
### Wiki & Taxonomy
| Ticket | Owner | Priority | Notes |
|--------|-------|----------|-------|
| Wiki taxonomy structure + first entries | Miri + Qatux | Critical | Project lead: non-negotiable, NOW |
| Tag taxonomy wiki page | Gestalt | High | Reference document for all content authors |
| Line pool format specification (standalone doc) | Gestalt | High | Formalize Round 1/2 YAML format |
### Visual & Spatial Design
| Ticket | Owner | Priority | Notes |
|--------|-------|----------|-------|
| v0.1 Visual Grammar document | Araminta | Critical | Root visual dependency |
| Entity color system spec | Araminta | Critical | Relationship-to-player color mapping |
| Spatial layout: Logistics Hub | Araminta | High | Floor plan, sightlines, NPC positions |
| Spatial layout: Bar (The Last Shift) | Araminta | High | Corner booth as key observation position |
| Spatial layout: Corridors + Smuggling spaces | Araminta | High | Hidden spaces, maintenance corridors |
| Insert/HUD wireframe + dual-character variants | Araminta | High | Smuggler social map vs detective case file |
| Monologue display system visual spec | Araminta | High | Typography, animation, stacking rules |
| Text display hierarchy spec | Araminta | High | 4 text pipelines, 4 visual treatments |
| Sound indicator visual design | Araminta | High | Fog-edge pulse, complementary to audio |
| Fog rendering visual spec | Araminta | Medium | 4-state visibility model |
| Span gate signature visual element | Araminta | Medium | Rhythmic glow, first-impression anchor |
| Visual asset taxonomy (wiki structure) | Araminta | Medium | Future-ready directory structure |
| Environmental text visual standards | Araminta | Medium | Bilingual signage, terminal screens |
### Systems / Server (Content-Supporting)
| Ticket | Owner | Priority | Notes |
|--------|-------|----------|-------|
| Dialogue selection pipeline (4-layer filter) | Dudley + Gestalt | Critical | Core runtime: access → situation → trust → weighted |
| Monologue trigger system | Dudley + Gestalt | Critical | 9 triggers, character-specific pools, prerequisite gates |
| YAML content loader (hot-reload for previewer) | Dudley | High | Parses YAML into indexed line pools |
| Sound event system architecture | Dudley + Gestalt | High | Event emitter with audio + visual fallback |
| NPC mood state machine | Dudley | High | Drives Layer 4 selection + tell system |
| Trust progression system | Dudley | High | Surface → real → secret per NPC pair |
| Interaction tracking component | Dudley | High | Per-NPC-pair counters drive Layer 2 |
| Knowledge state component | Dudley + Gestalt | High | Gates monologue prerequisites |
| Observation event generator | Dudley | Critical | Bridge between simulation and perception |
| Tell state derivation system | Dudley | Medium | Reads axes, outputs observable tells |
| Line variety tracker | Dudley | Medium | Prevents repeat lines per session |
### Audio
| Ticket | Owner | Priority | Notes |
|--------|-------|----------|-------|
| Audio asset set — 8 files via Stable Audio Open | TBD | High | See Ozzie R2 section 4 for full spec |
### Existing Ticket Scope Updates
| Ticket | Update Needed |
|--------|---------------|
| #90 (Tell system) | Scope to 5 categories; text-via-monologue as v0.1 renderer |
| #124 (Sound system) | Include sound event emitter architecture + visual fallback |
| #168 (Tag taxonomy) | Reference converged taxonomy (D-035) |
| #179 (NPC profiles) | THE FRIEND depth split: 2 production-level, 13 standard |
| #189 (Cultural generation guide) | Sova Transit District as first concrete instance |
| #190-192 (Template content packs) | Parallel spatial layouts as co-deliverables |
| #193 (Line previewer) | Concrete MVP: 7 must-have features, Rust CLI, sequence mode |
| #261 (Dual Lens Authoring Guide) | Add: emotional divergence, access tier shifts, authoring checklist, THE FRIEND section |
---
## Dependency Chain (Converged)
Three parallel tracks converge at content pack production. Critical path highlighted.
```
TRACK A: Narrative (Paula) TRACK B: Setting (Miri) TRACK C: Systems (Gestalt+Araminta)
1. Dual Lens Guide (#261) ←─ 1. Sova Setting Brief (#189) 1. Line Pool Format Spec
**CRITICAL PATH** (Round 1 output = v0.1 draft) 2. Visual Grammar (Araminta)
| | 3. Spatial Layouts x3 (Araminta)
2. Character Voice Patterns 2. Wiki Taxonomy + Krenn Entry 4. Line Previewer (#193)
| |
3. THE FRIEND profiles (x2) 3. Sova Texture Appendix
**CRITICAL PATH** |
| 4. Contraband Spec
4. NPC Profiles (Tier 1-3) + Detective Chain of Command
| |
└────────────┬─────────────────┘
|
v
5. Character Voice Kits (Mellanie) ← **CRITICAL PATH**
|
6. Opening Hooks (Mellanie) ← **CRITICAL PATH**
|
└──────────────────────────────────────────────────┘
|
v
7. THE FRIEND Content Packs (Mellanie) ← **CRITICAL PATH**
|
8. VALIDATION: Previewer test
|
9. Content Packs x3 (#190-192) (Mellanie)
|
10. Polish: Tell lines, mirror moments, environmental text
```
**Critical path:** Dual Lens Guide → Voice Kits → THE FRIEND Content → Validation → Scale
**Parallel work (no dependencies):**
- Miri: Wiki taxonomy, Krenn System entry, Sova Texture Appendix, contraband spec
- Araminta: Visual Grammar, spatial layouts, insert wireframe
- Gestalt: Line pool format spec (formalize), knowledge state vocabulary
- Mellanie: Tag taxonomy smoke test (20 lines), environmental text templates, news ticker draft
- Audio: Generate station ambient + monologue chime (the two most important files)
---
## Content Volume Estimates (Mellanie R2)
| Category | Authored Lines | After Expansion |
|----------|---------------|-----------------|
| THE FRIEND: Kael Davan (full pack) | 75-100 | Hand-authored only |
| THE FRIEND: Sera Venn (full pack) | 75-100 | Hand-authored only |
| Template dialogue (3 packs) | 400-500 | ~1,600-2,000 (4x) |
| NPC-specific lines (~13 remaining) | 80-140 | ~320-560 (4x) |
| Monologue — smuggler | 120-160 | ~240-320 (2x) |
| Monologue — detective | 120-160 | ~240-320 (2x) |
| Opening hooks (2 characters) | 20-30 | Hand-authored only |
| Environmental text | 50-60 | N/A |
| News ticker / Meridian feed | 20-30 | N/A |
| UI microcopy | 40-50 | N/A |
| Tell monologue lines | 30-50 | N/A |
| **Total** | **~1,030-1,380** | **~3,200-4,200** |
---
## Per-Agent Next Steps
### Paula (Critical path owner)
1. Dual Lens Authoring Guide — full draft (blocks everything)
2. THE FRIEND: Kael Davan — full production profile
3. THE FRIEND: Sera Venn — full production profile
4. Relationship web formalization (15 NPCs, 5 triangles with Krenn names)
5. NPC Profiles: Tier 1 (4 entangled), Tier 2 (7 mundane), Tier 3 (3 flat)
### Mellanie (Content production)
1. Tag taxonomy smoke test (20 lines in YAML, immediate)
2. Environmental text templates + news ticker draft (unblocked)
3. Voice kits (3 options per character, needs Dual Lens Guide)
4. Opening hooks (needs voice kit validation)
5. THE FRIEND content packs (needs FRIEND profiles)
### Miri (Setting foundation)
1. Contraband Specification (unblocked, immediate)
2. Sova Texture Appendix (slang, idioms — blocks Mellanie)
3. Wiki taxonomy structure + Krenn System entry
4. NPC name finalization (mapping to Paula's web)
5. Detective chain of command
### Gestalt (Systems specification)
1. Lock tag taxonomy + line pool format (formalize as document)
2. Knowledge state vocabulary (blocks monologue prerequisites)
3. Dialogue selection pipeline specification
4. Sound event system architecture
5. Line previewer (#193) MVP scope
### Araminta (Visual design)
1. v0.1 Visual Grammar document (unblocked, immediate)
2. Spatial layouts x3 (needs Visual Grammar + Miri's setting)
3. Insert/HUD wireframe (dual-character variants)
4. Monologue display system spec
5. Sound indicator visual design
### Ozzie (Validation)
1. Review THE FRIEND contradiction arcs (gut check)
2. Audio asset specification finalization
3. Playtest readiness evaluation
4. Wow moment dependency tracking
---
## Workshop Assessment
**Strengths:**
- Remarkable convergence across 6 independent analyses
- THE FRIEND concept evolved from Ozzie's emotional instinct through Paula's structural design to Mellanie's authoring plan in a single workshop
- Miri's Sova Transit District gave the entire team a concrete foundation
- Tag taxonomy converged without coordination — Mellanie and Gestalt proposed nearly identical structures
- Dependency chain was independently identified by Mellanie, Paula, and Gestalt with compatible structures
**Risks:**
- Dual Lens Guide is a single point of failure — everything downstream blocks on Paula's deliverable
- Content volume (~1,030-1,380 lines) is significant for one writer (Mellanie)
- 17 content-supporting systems identified, 0 built — server team has substantial work
- Generation expansion on monologue risks flattening character voice (Ozzie, Mellanie flag 2x max for monologue vs 4x for dialogue)
**Flags for Qatux:**
- Mellanie proposed Lera Sessik as detective's FRIEND in Round 2; Paula proposed Sera Venn. Project lead confirmed Sera Venn. Lera remains the bar owner, not THE FRIEND.
- Paula reconciled from 7 triangles to 5 triangles in Round 2. The 5-triangle model is canonical.
- Miri proposed different NPC name assignments than Paula's Round 2 reconciliation. Paula's Round 2 assignments are canonical (verified by project lead's Sera Venn confirmation).
- Gestalt's "17 content needs, 0 built" assessment accurately describes the systems gap.
---
*Compiled by Qatux. Workshop outputs archived at `docs/workshops/content-gap-analysis_v0_1/`.*
*Decisions recorded in `decisions/*.md` (D-032 through D-040).*
*Last updated: 2026-02-11*
docs/workshops/content-gap-analysis_v0_1/TICKETS.md
-197
View File
@@ -1,197 +0,0 @@
# v0.1 Content Gap Analysis — Ticket Summary
**Workshop:** Content Gap Analysis v0.1
**Date:** 2026-02-11
**Created by:** Si (Project Manager)
**Source:** 6 Round 2 synthesis outputs (Mellanie, Paula, Araminta, Miri, Gestalt, Ozzie)
---
## Project Lead Decisions Incorporated
1. Detective's FRIEND: **Sera Venn** (Paula's design) — confirmed
2. Smuggler's FRIEND: **Kael Davan** — confirmed
3. All 6 wow moments in scope (Ozzie's list)
4. Audio in v0.1 via **Stable Audio Open** (8 files)
5. Wiki taxonomy: **non-negotiable**, must be established now
---
## Summary Statistics
| Category | New Tickets | Updated Tickets | Total |
|----------|------------|----------------|-------|
| Critical | 9 | 1 | 10 |
| High | 23 | 3 | 26 |
| Medium | 10 | 2 | 12 |
| **Total** | **42** | **6** | **48** |
---
## Existing Tickets Updated (6)
| ID | Title | Change | Source |
|----|-------|--------|--------|
| #261 | Dual Lens Authoring Guide | Priority: high → **critical**. Expanded scope: voice signatures, access tier shift paths, authoring checklist, THE FRIEND section. | All 6 agents |
| #189 | Cultural generation guide — Miri | Sova Transit District is first concrete instance. Miri R1 output IS the v0.1 slice. | Mellanie, Miri |
| #168 | Tagged line pool structure | Converged 6+3 tag taxonomy from workshop. YAML format locked. | Gestalt, Mellanie, Paula |
| #124 | Sound event system — server | Expanded architecture: SoundEventEmitter with AudioAssetRegistry, visual fallback, AmbientManager. | Gestalt, Ozzie |
| #90 | Personality & tell system | 5 tell categories. v0.1 renderer = monologue text, not visual animation. | Gestalt, Araminta, Ozzie |
| #193 | Line previewer CLI | Concrete MVP: 8 features. Build AS dialogue pipeline first implementation. | Gestalt, Mellanie, Ozzie |
---
## New Tickets — Critical (9)
| ID | Title | Owner | Proposed By |
|----|-------|-------|-------------|
| #297 | THE FRIEND: Smuggler NPC — Kael Davan full profile + content pack | Paula + Mellanie | Mellanie, Paula, Gestalt, Ozzie |
| #298 | THE FRIEND: Detective NPC — Sera Venn full profile + content pack | Paula + Mellanie | Mellanie, Paula, Gestalt, Ozzie |
| #299 | Opening hook content — smuggler first 5 minutes | Mellanie | Mellanie, Paula, Ozzie |
| #300 | Opening hook content — detective first 5 minutes | Mellanie | Mellanie, Paula, Ozzie |
| #301 | Wiki taxonomy and structure — full future-ready schema | Miri + Qatux | Mellanie, Paula, Miri |
| #302 | Sova Texture Appendix — slang glossary, idioms, sensory details | Miri | Mellanie, Miri |
| #303 | v0.1 Visual Grammar Document | Araminta | Araminta, Ozzie |
| #304 | Entity Color System Spec — relationship-to-player mapping | Araminta | Araminta |
| #305 | Dialogue selection pipeline — 4-layer filtering engine | Dudley | Gestalt |
---
## New Tickets — High (23)
### Content / Narrative
| ID | Title | Owner | Proposed By |
|----|-------|-------|-------------|
| #306 | News ticker / Meridian feed content — 20-30 lines | Mellanie + Miri | Mellanie, Paula, Ozzie |
| #307 | Flat NPC memorable trait pass — 3 flat NPCs | Paula + Mellanie | Ozzie |
| #310 | Character voice speech patterns — smuggler + detective | Paula + Mellanie | Mellanie, Paula |
| #328 | Access tier shift design document | Paula + Gestalt | Paula, Gestalt |
### Visual / Spatial
| ID | Title | Owner | Proposed By |
|----|-------|-------|-------------|
| #311 | Spatial layout: Logistics Hub (The Terminal) | Araminta | Paula, Araminta |
| #312 | Spatial layout: Bar (The Last Shift) | Araminta | Paula, Araminta |
| #313 | Spatial layout: Smuggling spaces and transition corridors | Araminta | Paula, Araminta |
| #314 | Insert/HUD wireframe and spec — dual character variants | Araminta | Araminta |
| #315 | Monologue display system visual spec | Araminta | Araminta, Paula |
| #316 | Text display hierarchy spec — 4 content pipelines | Araminta | Araminta |
| #317 | Sound indicator visual design — fog-edge pulse | Araminta | Araminta |
| #318 | THE FRIEND visual treatment spec | Araminta | Araminta |
### Worldbuilding
| ID | Title | Owner | Proposed By |
|----|-------|-------|-------------|
| #319 | Krenn System wiki entry — first star system | Miri | Paula, Miri |
| #320 | Sova Station Profile — station beyond Transit District | Miri | Miri |
| #321 | Contraband specification — lattice components + supply chain | Miri | Miri |
| #322 | Detective institutional chain of command | Miri + Paula | Miri, Paula |
### Systems / Implementation
| ID | Title | Owner | Proposed By |
|----|-------|-------|-------------|
| #308 | Line pool format specification — formal document | Gestalt | Mellanie, Gestalt |
| #309 | Knowledge state vocabulary for v0.1 | Gestalt + Dudley | Mellanie, Gestalt |
| #323 | NPC mood state machine | Dudley | Gestalt |
| #324 | Trust progression system | Dudley | Gestalt |
| #325 | Interaction tracking component | Dudley | Gestalt |
| #326 | YAML content loader — hot-reload for previewer | Dudley | Gestalt |
| #327 | Audio asset set — 8 minimum viable files via Stable Audio Open | TBD | Mellanie, Ozzie, Gestalt |
---
## New Tickets — Medium (10)
| ID | Title | Owner | Proposed By |
|----|-------|-------|-------------|
| #329 | Mirror moment design document — 10-15 paired observations | Paula + Mellanie | Mellanie, Paula |
| #330 | Diegetic tutorial monologue lines — per character | Mellanie | Paula, Gestalt |
| #331 | Diegetic insert flavor text — per character | Mellanie + Araminta | Ozzie |
| #332 | Contradiction arc design document — reusable FRIEND pattern | Paula | Paula |
| #333 | Fog rendering visual spec — 4 states | Araminta | Araminta |
| #334 | Environmental text visual standards | Araminta | Araminta |
| #335 | Meridian Coverage Map for Sova Transit | Miri | Miri |
| #336 | Span Gate Transit Schedule | Miri | Miri |
| #337 | Tell state derivation system | Dudley | Gestalt |
| #338 | Line variety tracker — prevent repeat dialogue | Dudley | Gestalt |
---
## Owner Summary
| Owner | Critical | High | Medium | Total |
|-------|----------|------|--------|-------|
| **Paula** (+ co-owners) | 2 | 4 | 2 | 8 |
| **Mellanie** (+ co-owners) | 2 | 2 | 2 | 6 |
| **Araminta** | 2 | 8 | 2 | 12 |
| **Miri** (+ co-owners) | 2 | 4 | 2 | 8 |
| **Gestalt** (+ co-owners) | 0 | 3 | 0 | 3 |
| **Dudley** | 1 | 3 | 2 | 6 |
| **TBD** | 0 | 1 | 0 | 1 |
---
## Critical Path
```
Phase 0: FOUNDATIONS (no dependencies — can start immediately)
|
|-- [Miri #302] Sova Texture Appendix
|-- [Miri #301] Wiki taxonomy + Krenn entry (#319)
|-- [Miri #321] Contraband specification
|-- [Gestalt #308] Line pool format spec
|-- [Gestalt #309] Knowledge state vocabulary
|-- [Paula #261] Dual Lens Authoring Guide (CRITICAL PATH)
|-- [Araminta #303] v0.1 Visual Grammar Document
|-- [Araminta #304] Entity Color System Spec
|
Phase 1: CHARACTER ARCHITECTURE (needs Phase 0)
|
|-- [Paula+Mellanie #310] Character voice speech patterns
| |
| v
|-- [Mellanie] Smuggler voice kit (uses #180)
|-- [Mellanie] Detective voice kit (uses #181)
|
Phase 2: THE FRIEND (needs Phase 1)
|
|-- [Paula #297] Kael Davan full profile
|-- [Paula #298] Sera Venn full profile
| |
| v
|-- [Mellanie #297] THE FRIEND content packs
|
Phase 3: OPENING HOOKS (parallel with Phase 2)
|
|-- [Mellanie #299] Opening hook — smuggler
|-- [Mellanie #300] Opening hook — detective
|
Phase 4: CONTENT PACKS (needs Phase 2 validation)
|
|-- [Mellanie #190] Logistics Hub content pack
|-- [Mellanie #191] Bar content pack
|-- [Mellanie #192] Smuggling ring content pack
|
Phase 5: POLISH
|
|-- [Mellanie #306] News ticker
|-- [Paula+Mellanie #329] Mirror moments
|-- [Mellanie #330] Diegetic tutorial lines
|-- [Mellanie+Araminta #331] Insert flavor text
```
**Single highest-risk dependency:** #261 Dual Lens Authoring Guide. If delayed, everything downstream shifts.
---
## Notes
- Existing tickets #190, #191, #192 (content packs) now have parallel spatial layout co-deliverables (#311, #312, #313). Content and layout must be developed together.
- Existing ticket #179 (NPC profiles) now has a split: 2 NPCs (Kael, Sera) at production-level depth via #297/#298, remaining 13 at v0.1 tiers.
- #303 (Visual Grammar) supersedes #252 (Placeholder art spec) in scope.
- #305 (Dialogue pipeline) and #193 (Line previewer) share code — build previewer AS the pipeline.
- #327 (Audio assets) ownership TBD — needs someone to run Stable Audio Open generation pipeline.
docs/workshops/content-gap-analysis_v0_1/content-gap-analysis-workshop-brief.md
-269
View File
@@ -1,269 +0,0 @@
# Workshop Brief: v0.1 Content Gap Analysis
## What Does the Vertical Slice Actually Need?
**Project:** The Settled Reach (D-021)
**Date:** 2026-02-11
**Called by:** Jeroen
**Participants:** MELLANIE, PAULA, ARAMINTA, MIRI, GESTALT, OZZIE
---
## The Problem
The server and client teams are building the IPC bridge (Sprint 1). The content team — Mellanie (copywriter), Paula (narrative), Araminta (visual design) — has no actionable work yet. We have strong *architectural* decisions about content (D-023 through D-029) and some critical tickets (#190-192 content packs), but we haven't mapped what content the v0.1 vertical slice actually needs, in what format, and in what order.
This workshop moves from the most global decisions down to the most specific content needs. At each layer we identify what exists, what's missing, and what each team member needs to start working.
**v0.1 scope reminder (D-027):** Smuggler + detective two-character proof. One station district. 3 social site templates (workplace logistics hub, social bar, smuggling ring). ~15 NPCs. 30-minute daily-life runway before conspiracy activation. Success = both playthroughs feel like fundamentally different games.
---
## Layer 1: Art Direction & Visual Identity
**The most global question: what does this game look like?**
| What exists | Status |
|-------------|--------|
| Q-003 (art direction) | OPEN — no decision made |
| #20 Art direction ticket | medium priority, backlog |
| #252 Placeholder art spec | high priority, backlog |
| #133 Placeholder art pipeline | high priority, backlog |
| D-014 says "functional boxes with labels" | — |
| D-016 says "atmosphere carried by monologue" | — |
**Gaps:**
- No color palette, no sprite style guide, no UI visual language
- No resolution/format standards beyond what #252 will define
- No guidance on whether v0.1 should look deliberately placeholder or aim for a mood
**Questions for the team:**
1. **Araminta:** Can you define a v0.1 visual identity without resolving Q-003 fully? Or should we make Q-003 a decision now — even if it's "functional minimalism, atmosphere through text"?
2. **Araminta:** What's the minimum art direction document needed so that anyone producing visual assets stays consistent?
3. **Ozzie:** Does the vertical slice need visual mood, or is "readable placeholder" sufficient to prove the concept?
---
## Layer 2: Narrative Framework & Character Design
**Before writing a single line of dialogue: who are these two characters, and how do they see the world differently?**
| What exists | Status |
|-------------|--------|
| D-027 Vertical slice: smuggler + detective | confirmed |
| Epic #57 Playable Characters | critical, 5 children |
| #179 Character definition schema | backlog |
| #180 Smuggler character build | backlog |
| #181 Detective character build | backlog |
| #182 Divergent starting knowledge | backlog, critical |
| #183 Divergent relationships | backlog, critical |
| #261 Dual Lens Authoring Guide | high priority, backlog |
**Gaps:**
- #261 (Dual Lens Authoring Guide) **must precede ALL content packs** — it defines how the same NPCs, locations, and situations play differently for each character
- No character voice profiles (how does the smuggler's internal monologue sound vs. the detective's?)
- No access tier mapping (which NPCs treat the smuggler as insider vs. the detective?)
**Questions for the team:**
1. **Paula:** What does the Dual Lens Guide need to contain? Is it a document you write solo, or should it be a workshop output?
2. **Paula:** How do you define "divergent starting knowledge" (#182)? Is it a list of facts each character knows, or something more structural?
3. **Mellanie:** What do you need from the character builds before you can write voice-consistent dialogue?
4. **Gestalt:** How do access tiers (D-028 Layer 1) interact with the two character builds mechanically?
---
## Layer 3: Station District Setting
**What does this place feel like? What's the vibe, the history, the texture?**
| What exists | Status |
|-------------|--------|
| D-014 v0.1 map spec | confirmed |
| Epic #58 Station District Content | critical, 5 children |
| #184 Workplace template — logistics hub | backlog |
| #185 Social venue template — bar | backlog |
| #186 Smuggling ring template | backlog |
| #189 Cultural generation guide | critical, assigned to Miri |
| D-025 Social site structure (4-8 NPCs, 15-40 tiles) | confirmed |
**Gaps:**
- No station district lore document — what is this place? Who built it? What's the economic engine?
- No environmental storytelling plan — what do signs say? What's on the news ticker? What's the graffiti?
- No location "feel" descriptions — is the workplace sterile or chaotic? Is the bar upscale or dive?
**Questions for the team:**
1. **Miri:** Can you write a one-page station district setting document? Just enough for v0.1 — name, purpose, atmosphere, recent history, what makes it interesting.
2. **Paula:** How does the station's character feed into NPC motivations? (E.g., economic pressure → smuggling opportunity)
3. **Ozzie:** What environmental details make a player feel present in the first 30 seconds?
---
## Layer 4: Content Pipeline & Authoring Format
**Before Mellanie writes 500+ lines of dialogue: what format do they go in?**
| What exists | Status |
|-------------|--------|
| D-028 Tagged line pool architecture | confirmed |
| Epic #55 Dialogue system architecture | high, 7 children |
| #168 Tagged line pool structure | backlog |
| #193 Line previewer CLI | critical, backlog |
**Gaps:**
- No concrete authoring format defined — what does a line pool file actually look like? YAML? JSON? CSV with tags?
- No tag taxonomy — what tags exist? (role, trust_tier, mood, topic, situation, character_class)
- Line previewer (#193) doesn't exist yet — Mellanie can't test what she writes
**Questions for the team:**
1. **Gestalt:** Propose a concrete line pool format. What metadata per line? What's the minimum viable tag set for v0.1?
2. **Mellanie:** Can you write content packs in a provisional format before the previewer exists, or does the format need to be locked first?
3. **Gestalt:** How do the 4 dialogue layers (access, history, trust, unprompted) map to line tags? One tag per layer, or more complex?
---
## Layer 5: Template Content (3 Social Sites)
**The core content deliverables for v0.1.**
| What exists | Status |
|-------------|--------|
| #190 Workplace content pack | critical, backlog |
| #191 Bar content pack | critical, backlog |
| #192 Smuggling ring content pack | critical, backlog |
| D-025 Social site = 4-8 NPCs, 15-40 tiles | confirmed |
| D-028 ~165-210 authored lines per template | confirmed |
| D-029 Entanglement ratio: 30/50/20 | confirmed |
**Gaps:**
- No NPC personality profiles — the 10-axis model (D-024) is an ECS schema, not character descriptions
- No relationship web — who knows whom, who's lying to whom, who's sleeping with whom
- No routine descriptions — where does each NPC go and when?
- No triangle definitions — D-029 requires mundane triangles, but none are designed
**Questions for the team:**
1. **Mellanie:** What does a content pack deliverable look like? Break down #190 into what you'd actually write.
2. **Paula:** How do you design the relationship web for 3 overlapping social sites? Who are the "bridge" NPCs that connect them?
3. **Paula:** How many triangles per template? D-029 says 2 minimum per template + 1 cross-template. What do they look like concretely?
4. **Gestalt:** How does the entanglement ratio (30/50/20) play out across ~15 NPCs? That's ~4-5 flat, ~7-8 mundane-triangle, ~3 entangled?
---
## Layer 6: NPC Profiles & Dialogue
**Making ~15 NPCs feel like people, not database entries.**
| What exists | Status |
|-------------|--------|
| D-024 NPC 10-axis model | confirmed |
| #86 Core NPC data model components | backlog |
| #87 Relationship tracking system | backlog |
| #88 Daily routine system | backlog |
| #168-174 Dialogue system tickets | backlog |
| #251 Tell visual/behavioral expression | high, backlog |
**Gaps:**
- No tickets for writing actual NPC profiles (personality, backstory, voice)
- No tickets for voice kit authoring (15-25 lines per NPC role)
- No tickets for relationship history content (what happened between these people before the game starts?)
- No tell catalog (what observable behaviors map to what internal states?)
**Questions for the team:**
1. **Paula + Mellanie:** How deep does each NPC profile need to be? Full backstory, or just the 10 axes plus a voice sample?
2. **Mellanie:** How many lines per NPC for v0.1? D-028 estimates 15-25 per role in a template. With ~15 NPCs, that's 225-375 lines of role dialogue alone.
3. **Gestalt:** What's the minimum viable tell system? One behavioral marker per axis, or fewer?
4. **Ozzie:** Which NPC should the player remember after 30 minutes? What makes them memorable — a line, a routine, a contradiction?
---
## Layer 7: Monologue & Observation Text
**The character's inner voice — the primary content delivery mechanism in v0.1.**
| What exists | Status |
|-------------|--------|
| D-016 Internal monologue as perception bridge | confirmed |
| #119 Monologue event generation | backlog |
| #120 Monologue line pool system | backlog |
| #121 Character voice variation | high, backlog |
| #253 Monologue content architecture | high, backlog |
| #239 Observation event generator | critical, backlog |
**Gaps:**
- No monologue line count estimates per location type
- No character voice variation specs (how does the smuggler interpret vs. the detective?)
- No observation trigger catalog (what events produce monologue?)
- No "mirror moment" content — lines that hint at the other character's perspective
**Questions for the team:**
1. **Mellanie:** How many monologue lines make v0.1 feel alive? D-028 workshop estimated 200-300 across location types for atmosphere floor. Sound right?
2. **Mellanie:** Can the same observation event produce different monologue for smuggler vs. detective? Or do you need separate pools?
3. **Paula:** What are the "mirror moments" — places where the monologue hints that this situation looks different from another perspective?
4. **Ozzie:** When does the first monologue surprise the player? What's the moment where they think "wait, my character noticed something I didn't"?
---
## Layer 8: UI Text & Environmental Content
**Everything on screen that isn't dialogue or monologue.**
| What exists | Status |
|-------------|--------|
| #262 Environmental text content | medium, backlog |
| #263 Time display on insert HUD | medium, backlog |
| #264 Knowledge/journal display | medium, backlog |
| #174 Dialogue UI | backlog |
| D-013 Diegetic insert (neural implant map) | confirmed |
**Gaps:**
- No UI copy document (button labels, menu text, notification strings)
- No tutorial/onboarding text (how does the player learn the controls?)
- No diegetic content (signs, terminal screens, manifests, notices, news feeds)
- No insert/minimap text (POI labels, status indicators)
**Questions for the team:**
1. **Mellanie + Araminta:** What text appears on screen that isn't dialogue or monologue? Make a list.
2. **Araminta:** How does the neural implant UI look? Is it a literal implant overlay, or abstracted?
3. **Gestalt:** Does v0.1 need onboarding text, or can the monologue system serve as the tutorial (D-016 "diegetic tutorial")?
---
## Layer 9: Audio Direction
**The most deferred question: what does the game sound like?**
| What exists | Status |
|-------------|--------|
| D-018 Three-range sound model | confirmed |
| #124-128 Sound propagation tech tickets | backlog |
| #46 Sound Propagation Model epic | 5 children |
**Gaps:**
- Zero audio content tickets — no ambient soundscapes, no foley, no music direction
- No decision on whether v0.1 uses placeholder audio or real audio
- No audio style guide
**Questions for the team:**
1. **Ozzie:** Does placeholder audio kill the atmosphere, or is silence acceptable for a concept proof?
2. **Gestalt:** Does the three-range sound model need audio content to prove itself, or can it work with system beeps and text?
3. **Team:** Should we defer audio entirely to a later sprint, or establish direction now?
---
## Workshop Format
**2 rounds.**
**Round 1 — Layer-by-layer gap identification.** Each participant responds to the questions in their domain. Propose concrete answers, not just "we need to figure this out."
**Round 2 — Synthesis.** Review Round 1 answers. Produce:
1. Missing ticket list (new tickets to create)
2. Dependency chain (what must come before what)
3. Content team work order for Sprint 2 or a parallel content track
## Expected Outputs
- **Decision:** Art direction approach for v0.1 (resolve or scope Q-003)
- **Document:** Dual Lens Authoring Guide outline (Paula)
- **Document:** Station district setting brief (Miri)
- **Specification:** Line pool authoring format (Gestalt)
- **List:** New tickets filling content gaps (Si creates post-workshop)
- **Plan:** Dependency-ordered content work plan for Mellanie, Paula, Araminta
docs/workshops/content-gap-analysis_v0_1/round1-araminta.md
-383
View File
@@ -1,383 +0,0 @@
# Round 1 Workshop Response: Araminta (Visual Design)
**Agent:** Araminta (Visual Designer)
**Date:** 2026-02-11
**Scope:** All 9 layers from visual design perspective
---
## Layer 1: Art Direction & Visual Identity
### Q1: Can I define a v0.1 visual identity without resolving Q-003 fully?
**Yes. And we should do exactly that.**
Q-003 asks about long-term art direction. That's a question about final fidelity, sprite style, animation approach, lighting systems. We don't need to answer any of that to build v0.1. What we need is a **v0.1 visual grammar** - a set of rules for how information is communicated visually, regardless of art fidelity.
**Proposal: Resolve Q-003 partially with a scoped decision.**
> **D-XXX: v0.1 visual approach - "readable information design, atmosphere through text and spatial composition."**
>
> - Entities are colored rectangles with text labels. No sprites in v0.1.
> - Color communicates RELATIONSHIP TO PLAYER, not object type.
> - Spatial layout communicates function - the bar FEELS different from the logistics hub through room shape, furniture density, corridor width.
> - Atmosphere is carried by monologue text, dialogue content, and sound indicators - NOT by art.
> - All visual rules must scale: a color that means "danger" in boxes-with-labels must still mean "danger" when we add sprites.
This is not "we'll figure out art later." This is "v0.1's art IS information design." The boxes aren't placeholder art waiting for real art. The boxes ARE the visual language at this fidelity level.
Long-term Q-003 (sprite style, animation, lighting) stays open. It doesn't block anything.
### Q2: What's the minimum art direction document needed for consistency?
A **one-page visual grammar** covering:
1. **Color palette** (see below)
2. **Entity sizing rules** (NPCs, furniture, walls, doors - relative proportions)
3. **Label conventions** (what text shows on entities, when, at what zoom)
4. **UI layer separation** (game world vs. insert overlay vs. monologue text vs. dialogue)
5. **Fog/visibility rendering rules** (visible, fog-edge, hidden - how they look)
That's it. No style guide for art we haven't made. No font selection for UI that doesn't exist yet. Just the rules for communicating game state visually.
### Proposed v0.1 Color Palette
The Settled Reach is sleek, advanced, subtle. Even at boxes-with-labels fidelity, we can communicate mood.
**Background/Environment:**
- `#1a1a2e` - Deep navy. Base floor/ground. The station is dimly lit by default.
- `#2d2d44` - Slightly lighter. Walls, barriers, solid obstacles.
- `#0f0f1a` - Near-black. Fog/hidden areas. Darkness should feel HEAVY.
**Entity Colors (relationship-to-player, NOT object type):**
- `#4a9ebb` - Cool teal. Neutral/unknown NPCs. Default state.
- `#6bc9a6` - Soft green. Friendly/trusted NPCs. People your character knows and likes.
- `#e8c547` - Warm amber. NPCs of interest. Your monologue has flagged something about them.
- `#d45d5d` - Muted red. Hostile/dangerous. ONLY when the character KNOWS there's danger. Not omniscient threat display.
- `#8b8ba0` - Grey. Furniture, static objects, environmental elements.
**UI Overlay Colors:**
- `#3d7aaf` with 40% opacity - Insert/minimap overlay tint. The neural implant's "screen."
- `#ffffff` at 85% opacity - Primary UI text (labels, insert readouts).
- `#a0a0b8` at 70% opacity - Secondary UI text (non-critical info).
**Monologue Text:**
- `#c8d0e0` - Internal monologue. Slightly cool, slightly ethereal. This is thought, not speech.
- Italicized. Positioned bottom-center or left panel. Fades in/out, doesn't snap.
**Dialogue Text:**
- `#ffffff` - NPC speech. Clean white. Grounded, real.
- NPC name in their relationship color above the dialogue line.
**Key principle:** Red means danger TO YOUR CHARACTER, not danger in the abstract. If the smuggler's friend is secretly an informant, that NPC is GREEN until the smuggler discovers the betrayal. The detective might see that same NPC as AMBER (person of interest) from the start. Same NPC, different color, because asymmetric information drives the palette.
This is D-011 (fog of perception) applied to the color system. The player sees what the character knows.
### Fog Rendering Specification
Three visual states for tiles:
| State | Appearance | When |
|-------|-----------|------|
| **Visible** | Full color, full detail, entities shown | Currently in LOS |
| **Fog-edge** | Desaturated 50%, entities hidden, sound indicators shown | Adjacent to LOS, within medium sound range |
| **Hidden** | Near-black (`#0f0f1a`), no entities, no indicators | Outside perception range |
| **Remembered** | Desaturated 70%, static snapshot of last-seen state, no entities | Previously visited, now outside LOS |
The "remembered" state is important. D-011 says fog returns on departure, but the player should see a ghost of what they last saw - furniture stays, NPCs vanish. This communicates "I was here, but things may have changed." It costs almost nothing to implement and sells the information-decay concept visually.
---
## Layer 2: Narrative Framework & Character Design
### Visual implications of character divergence
The two characters need **distinct visual treatments** even at boxes-with-labels fidelity:
- **Smuggler's player entity:** Slightly different shade or shape indicator. Doesn't need to be dramatic - a subtle color difference in the player marker is enough.
- **Detective's player entity:** Same principle, different accent.
More importantly: the **insert overlay** should feel different per character. The smuggler's insert is consumer-grade, maybe slightly less polished. The detective's is institutional - cleaner layout, more structured information display. This is a v0.2+ concern but worth noting now so the insert UI is designed with parameterization in mind.
For v0.1: a small character icon or color accent on the HUD that says "you are the smuggler" vs "you are the detective." Minimal but present.
---
## Layer 3: Station District Setting
### Visual layout principles for the three social sites
Even with boxes, spatial design communicates EVERYTHING about a location. Here's what each site should feel like through layout alone:
**Workplace (Logistics Hub):**
- Regular grid layout. Rows of workstations. Wide corridors for cargo movement.
- A few enclosed offices (walls block LOS - management has privacy).
- One loading bay area (open, high visibility, the "public" face).
- One back area (restricted, fewer sightlines - where secrets live).
- **Visual feel:** Ordered, institutional, functional. The regularity IS the aesthetic.
**Social Venue (Bar):**
- Irregular, organic layout. Booths create pockets of privacy.
- Central bar area with high visibility (everyone can see who's ordering).
- Corner tables with partial LOS blocks (intimate conversations).
- A back room or alley exit (the sketchy escape route).
- **Visual feel:** Warm-toned compared to the hub. Furniture density higher. More "walls" from booths and partitions creating complex sightlines.
**Smuggling Ring (Hidden within/adjacent to other spaces):**
- NOT a labeled "smuggling HQ." It's a maintenance corridor, a storage room, a section of the cargo bay that's officially off-limits.
- Tight spaces, poor sightlines, few entrances/exits.
- Visually indistinguishable from other utility spaces unless you know what to look for.
- **Visual feel:** Cramped. The contrast with the open logistics hub IS the atmosphere.
**Cross-site visual language:**
- Public spaces: wider corridors, more open tiles, lighter floor colors.
- Private spaces: narrower, enclosed, slightly darker floor tones.
- Transition zones: doorways, corridors between sites. These are where "wrong place, wrong time" moments happen. They need enough space for the player to see someone passing through.
No art needed. Room shapes and tile colors do the work. A bar booth is a 3x2 rectangle with half-height wall blocks. An office is a 4x4 enclosed room with a door entity. The spatial relationships create the gameplay affordances.
---
## Layer 4: Content Pipeline & Authoring Format
### Visual implications of the authoring format
Not my primary domain, but one critical visual note:
**Every dialogue line needs a display context tag.** The renderer needs to know:
- Is this spoken dialogue? (Display in dialogue UI panel, NPC name header)
- Is this overheard conversation? (Display as fog-edge text snippet, lower opacity, partial)
- Is this a monologue reaction? (Display in monologue area, italic, character voice color)
- Is this environmental text? (Display as world-space label on the object/sign/terminal)
These are four different rendering pipelines. The authoring format must tag which pipeline each line targets. Mellanie and Paula need this in the format spec so they don't write a line that falls between categories.
---
## Layer 5: Template Content (3 Social Sites)
### Visual deliverables per template
Each social site template needs a **spatial layout document** alongside the content pack. This is my deliverable. For each template:
1. **Floor plan** - tile-level layout showing walls, doors, furniture, sightlines
2. **Sightline diagram** - from key observation positions, what can you see? Where are the blind spots?
3. **Sound propagation notes** - which walls are thin (sound bleeds through), which are thick
4. **NPC position markers** - where do NPCs stand/sit during their routine phases?
5. **Player approach vectors** - how does the player enter? What do they see first?
This is the spatial design that makes observation gameplay work. A bar where you can see everyone from the entrance is a different game than a bar where you have to walk past three booths before you see the back table.
**Proposed ticket: spatial layout design per social site template (3 layouts, high priority).** This should be parallel with the content packs, not after them. Layout affects what content makes sense.
---
## Layer 6: NPC Profiles & Dialogue
### Visual expression of NPCs at boxes-with-labels fidelity
At v0.1 fidelity, NPC differentiation is:
1. **Color** (relationship state, as defined in the palette above)
2. **Label text** (name when known, role when partially known, "?" when unknown)
3. **Position and movement** (are they at their expected location? Moving with purpose or loitering?)
That's it. No character portraits. No sprite variation. No clothing differences.
**But this is enough.** The detective walks into the logistics hub. They see: a cluster of teal rectangles labeled "Worker," "Worker," "Worker," one amber rectangle labeled "Jax (shift supervisor)." Amber because the detective's case file flagged Jax. The smuggler walks in and sees: green rectangles labeled "Tomas," "Kira," "Jax" (all known, all friendly). Same room, different visual state, different information.
The color system IS the visual expression of asymmetric information. It doesn't need sprites to work.
### Tell system visual language (#251)
D-024 mentions a tell system - observable behaviors mapping to internal states. At boxes-with-labels fidelity, tells are NOT visual. They're:
- Monologue: "Jax is tapping his foot. He does that when he's nervous."
- Dialogue: NPC speech patterns change based on mood (Mellanie's domain)
- Behavioral: NPC is in an unexpected location or moving unusually
The monologue is the tell renderer for v0.1. Visual tells (sweating, fidgeting, avoiding eye contact) are sprite-fidelity features. Text carries the load for now.
When we get to sprites: each NPC should have 2-3 behavioral animation states (idle, nervous, angry) that map to mood axes. But that's later.
---
## Layer 7: Monologue & Observation Text
### Monologue presentation design
This is one of my key deliverables. The monologue is the player's primary information channel in v0.1.
**Presentation rules:**
| Property | Specification | Rationale |
|----------|--------------|-----------|
| **Position** | Bottom of screen, left-aligned, 60% width max | Doesn't obscure the game world. Left-align because we read left-to-right; it's the natural "start reading" position. |
| **Font** | Monospace or clean sans-serif. Slightly smaller than dialogue. | Monologue is internal thought - quieter than spoken words. Monospace gives a "data overlay" feel consistent with the insert aesthetic. |
| **Color** | `#c8d0e0` (cool off-white) | Distinct from dialogue (#ffffff) and UI text. Slightly ethereal. |
| **Style** | Italic | Universal convention for internal thought. Instantly readable as "this isn't spoken." |
| **Animation** | Fade in over 0.3s, hold for read-time + 1s, fade out over 0.5s | Not jarring. Doesn't demand attention like a popup. Respects the player's pace. |
| **Stacking** | Max 3 lines visible. New lines push old lines up and fade them. | Prevents monologue flooding during high-event moments. |
| **Priority** | Observation > atmosphere > tutorial hint | If multiple monologue triggers fire simultaneously, observation wins. The player needs to know "that NPC is acting weird" more than "nice evening." |
**Character voice differentiation (visual):**
The smuggler and detective should have subtly different monologue presentation:
- **Smuggler:** Slightly warmer text color (`#d0d0c0`), slightly more casual phrasing (Mellanie's domain, but the visual warmth supports it).
- **Detective:** Slightly cooler text color (`#c0c8e0`), more structured phrasing.
This is a minor touch that compounds over 30 minutes. The player's subconscious registers "this character thinks differently" through the text color before they consciously parse the words.
### Observation text vs. monologue vs. dialogue - visual hierarchy
The player needs to instantly distinguish these three information channels:
| Channel | Position | Style | Color | Example |
|---------|----------|-------|-------|---------|
| **Dialogue** | Center-bottom panel, NPC name header | Regular weight | `#ffffff` on dark panel | **Kira:** "Quiet night at the hub." |
| **Monologue** | Bottom-left, no panel/frame | Italic | `#c8d0e0` | *She says that, but she won't look at me.* |
| **Observation** | Same as monologue but with icon marker | Italic + small eye icon | `#c8d0e0` | [eye] *Jax just walked past the restricted door.* |
| **Environmental** | World-space, attached to object | Small caps, subtle | `#8b8ba0` | CARGO BAY 7 - AUTHORIZED PERSONNEL ONLY |
The observation marker (small eye icon) is important. It tells the player "your character noticed something." It's the visual cue for the detective mechanic. Over time, players learn: eye icon = pay attention.
---
## Layer 8: UI Text & Environmental Content
### Q1: What text appears on screen that isn't dialogue or monologue?
Complete inventory:
**Insert/HUD Layer (diegetic - it's the neural implant):**
- Time display (D-031: game clock, day phase indicator)
- Minimap with POI dots and directional arrows (D-013)
- POI labels when close enough
- Alert notifications ("Message from [contact name]")
- Insert-mode indicators if perception modes are active (v0.1: just natural vision, but the slot should exist)
**World-Space Labels:**
- Location names (room/area labels: "Logistics Hub - Bay 7")
- Door labels ("Office," "Storage," "Restricted")
- Sign text (business names, warnings, directions)
- Terminal screens (if examine mechanic exists: cargo manifests, schedules, case files)
- NPC name/role labels (floating above entity rectangle)
**System UI (non-diegetic, minimal):**
- Pause indicator
- Character name/role reminder (top corner, very subtle)
- Save indicator (if save/load exists)
- Interaction prompt (when near an interactable: "E: Examine" or similar)
**NOT on screen (deliberately):**
- Health bars, stamina bars, XP indicators - none of these exist in v0.1 and may never exist in traditional form
- Quest log/objective marker - the monologue IS the quest hint system
- Mini-tutorial popups - monologue handles this diegetically (D-016)
### Q2: How does the neural implant UI look?
**It's a literal implant overlay, not an abstracted game UI.** This is non-negotiable given D-013.
The insert is what the character sees when they activate their neural implant's navigation overlay. In v0.1, this means:
**Visual treatment:**
- Semi-transparent overlay with a subtle blue-tinted border or vignette (`#3d7aaf` at 15-20% opacity)
- The minimap is NOT a separate UI window. It's an overlay that tints the top-right (or bottom-right) corner of the game view.
- POI markers are simple geometric shapes: circles for locations, diamonds for contacts, squares for objectives.
- Text on the insert uses a slightly different font weight or a monospace font - it's DIGITAL text rendered by the implant, distinct from the player's natural perception.
**Behavioral rules:**
- The insert is always "on" in v0.1 (the character always has their implant active). Toggle is a v0.2+ feature.
- Insert information updates based on character knowledge (D-013: POIs only appear when learned).
- The overlay should feel like looking at a heads-up display, not a game map. Subtle scan lines or a very light grid pattern would reinforce this. Even at v0.1, a 1-pixel grid at 5% opacity costs nothing and communicates "technology."
**What the insert does NOT do:**
- Show NPC positions beyond what the character can sense (no omniscient radar)
- Show information the character hasn't learned
- Provide objective markers for things the character doesn't know about
The insert is BOUNDED by the same information rules as everything else (D-010 principle 2). It's a tool the character uses, not a game abstraction.
### Q3 (Gestalt asked this, but visual input): Onboarding through monologue
The monologue IS the tutorial. But the insert could display a brief "new overlay detected" or "insert calibrating" sequence on first load to teach the player that the blue-tinted area is their implant. One line of insert text: "Neural insert active. Navigation overlay online." Then the monologue takes over: *"Let's see what's on the schedule today."* Diegetic from the first second.
---
## Layer 9: Audio Direction
### Visual design implications of sound
Since v0.1 may have limited or no audio, sound information needs VISUAL representation:
**Sound indicators at fog edge (D-018 medium range):**
- Small animated ripple or pulse icon at the fog boundary, in the direction of the sound.
- Color-coded by sound type:
- `#c8d0e0` (neutral) - footsteps, movement, ambient activity
- `#e8c547` (amber) - conversation, voices (something to investigate)
- `#d45d5d` (red) - aggressive sounds, alarm, conflict
- Size/intensity pulses with sound volume.
- The monologue fires simultaneously to interpret: *"Voices. Coming from the back office."*
**Close-range sound (within LOS):**
- No special visual indicator needed. You can SEE the source.
- Dialogue or conversation text renders normally.
**Long-range insert alerts:**
- Display on the insert overlay as a notification blip.
- Text: "[Contact name] sent a location pin" or "Disturbance reported in [area]."
- These are spoofable (D-018) - the visual design should NOT distinguish real from fake alerts. The player has to figure that out.
Even if we have zero audio files in v0.1, the sound model works through these visual indicators plus monologue text. Sound-as-information doesn't require sound-as-audio. The three-range model can be proven with visual indicators and text alone.
**Audio direction for later:**
I'd defer actual audio content entirely from v0.1. The visual indicator system proves the sound model mechanically. Adding audio is additive polish, not structural. When we do add audio:
- Ambient: low drone, station hum, ventilation. The Settled Reach is a machine. It breathes.
- Close range: footsteps on metal, door mechanisms, muffled conversation bleed.
- No music in gameplay. Music in menus/loading only. The station's ambient sound IS the soundtrack.
---
## Summary: Visual Design Deliverables for v0.1
### Documents to produce
| Document | Priority | Description |
|----------|----------|-------------|
| **v0.1 Visual Grammar** (1 page) | Critical | Color palette, entity sizing, label rules, UI layer separation, fog rendering spec. Everything above in Layer 1, codified. |
| **Spatial Layout: Logistics Hub** | High | Floor plan, sightlines, NPC positions, approach vectors |
| **Spatial Layout: Bar** | High | Floor plan, sightlines, NPC positions, approach vectors |
| **Spatial Layout: Smuggling spaces** | High | Floor plan, sightlines, NPC positions, approach vectors |
| **Insert/HUD Wireframe** | High | Minimap position, text areas, notification zones, monologue display area |
| **Monologue Presentation Spec** | High | Typography, animation, stacking, priority rules |
| **Sound Indicator Visual Spec** | Medium | Fog-edge indicators, color coding, pulse behavior |
### Proposed new tickets
| Title | Priority | Rationale |
|-------|----------|-----------|
| v0.1 Visual Grammar document | Critical | Everything visual depends on this. Must exist before any renderer work begins. |
| Spatial layout design - 3 social site templates | High | Sightlines and room layout are the physical foundation of the observation mechanic. Parallel with content packs. |
| Insert/HUD wireframe and spec | High | The insert is the player's primary UI. Needs to be designed before implemented. |
| Monologue display system spec | High | Monologue is the primary content delivery mechanism. Its rendering rules affect every other visual element. |
| Sound indicator visual design | Medium | Required for the three-range model to function without audio files. |
| Entity color system implementation | High | The relationship-to-player color mapping is the primary visual expression of asymmetric information. |
### Dependencies
```
Visual Grammar ──> Spatial Layouts ──> Content Packs (layout affects what content makes sense)
Visual Grammar ──> Insert/HUD Wireframe ──> Insert implementation
Visual Grammar ──> Entity Color System ──> Fog rendering, NPC rendering
Visual Grammar ──> Monologue Display Spec ──> Monologue system UI
```
The Visual Grammar document is the root dependency for all visual work. I can produce it quickly once this workshop concludes and we have consensus on the color-as-relationship-state approach.
### One strong opinion
**The entity color system (color = relationship to player, not object type) is the single most important visual decision for v0.1.** It's how asymmetric information becomes visible. It's how two characters in the same room see different things. It's the visual proof of concept. If we get nothing else right visually, get this right. A teal rectangle labeled "Worker" for the detective and a green rectangle labeled "Jax" for the smuggler - that IS the game, rendered at minimum fidelity.
Everything else is refinement. This is the foundation.
---
*Written by Araminta. Keep it clean, we can layer detail later.*
docs/workshops/content-gap-analysis_v0_1/round1-gestalt.md
-591
View File
@@ -1,591 +0,0 @@
# Round 1: Gestalt (Systems Design & Fun Factor)
**Workshop:** v0.1 Content Gap Analysis
**Date:** 2026-02-11
**Scope:** All 9 layers — systems design questions
---
## Layer 1: Art Direction & Visual Identity
No direct questions for Gestalt here, but one mechanical observation:
**Art direction is downstream of information design.** The visual system's primary job in The Settled Reach is communicating *what the player can and cannot perceive*. Fog edges, vision cone boundaries, sound indicators at fog-edge, NPC state tells — these are all visual elements that serve information mechanics first, aesthetics second.
Whatever Araminta proposes, the art direction must prioritize **perceptual legibility**: can the player instantly distinguish "I can see this" from "I cannot see this" from "I heard something here"? If that's clear, the aesthetics can be anything from pixel art to abstract minimalism. If it's unclear, no amount of beauty fixes the game.
**Recommendation for Q-003:** "Functional minimalism with perceptual clarity" is the v0.1 art direction. Atmosphere is carried by monologue (D-016). Visual mood is a polish layer, not a proof-of-concept requirement.
---
## Layer 2: Access Tiers and Character Builds
**Question:** How do access tiers (D-028 Layer 1) interact with the two character builds mechanically?
Let me break down what this actually means mechanically.
Access tiers are the first filter on every line of dialogue. They answer: "Given who the player character IS, what version of this NPC do they see?" This isn't a binary insider/outsider — it's a multi-axis classification that determines which lines from the pool are eligible for selection.
### Access Tier Model for v0.1
| Access Tier | Description | Smuggler sees | Detective sees |
|-------------|-------------|---------------|----------------|
| `public` | Available to everyone. Greetings, small talk, general observations. | Yes | Yes |
| `insider` | Available to people embedded in the social group. Shop talk, complaints, gossip about colleagues. | Logistics hub: Yes. Bar: Regular status. Ring: Yes. | Logistics hub: Outsider. Bar: Regular. Ring: No. |
| `authority` | Available to people with institutional power. Deference, compliance, formal responses. | No (except through cover) | Yes |
| `peer` | Available to people of equal social standing within a group. Casual, unguarded. | With ring members, coworkers | With other investigators, institutional contacts |
| `hostile` | Guarded, deflecting, minimal. Shown to people perceived as a threat. | From detective-allied NPCs (if blown) | From ring-connected NPCs |
### How This Maps to the Two Characters
**Smuggler access profile:**
| Social Site | Default Access | Why |
|-------------|---------------|-----|
| Logistics Hub | `insider` + `peer` | Works there. Coworkers. |
| Bar | `public` or `insider` (regular) | Social regular, not staff |
| Smuggling Ring | `insider` + `peer` | Member |
**Detective access profile:**
| Social Site | Default Access | Why |
|-------------|---------------|-----|
| Logistics Hub | `authority` | Investigating. Workers defer/comply. |
| Bar | `public` | No special status |
| Smuggling Ring | `hostile` (if known) or `public` (if not) | Target of investigation |
### The Interesting Decision Space
Here's where this creates gameplay. Access tiers are the player's **starting hand**, not their final state. The systems must allow tier SHIFTS during play:
| Shift | Mechanism | Example |
|-------|-----------|---------|
| `public` -> `insider` | Repeated positive interactions, time spent | Detective becomes a bar regular after visiting 3-4 times |
| `insider` -> `hostile` | Cover blown, secret discovered | Smuggler is seen talking to the detective |
| `authority` -> `peer` | Trust built through fairness, personal disclosure | Detective earns a worker's trust by keeping a minor infraction quiet |
| `peer` -> `hostile` | Betrayal, information leak | Smuggler discovers a ring member is informing |
**These tier shifts ARE the social gameplay.** The player isn't just receiving different dialogue — they're actively managing their social position by choosing who to talk to, what to reveal, and who to be seen with. Every conversation is a potential tier shift event.
**What Paula needs for the Dual Lens Guide:** A matrix per social site showing starting access for each character, plus the 2-3 most likely tier shift paths. Not every combination — just the ones the content packs need to support.
---
## Layer 3: Station District Setting
No direct questions for Gestalt here, but a mechanical note for Miri:
The station district setting needs to produce **spatial information asymmetry**. Concretely:
- At least one area that's publicly accessible but has a hidden back room / private area
- At least one area where the smuggler has natural access but the detective would need a reason to enter
- At least one chokepoint where NPCs from different social sites cross paths (this is where cross-template contamination becomes observable)
These are spatial requirements that emerge from the information design, not just atmosphere choices.
---
## Layer 4: Content Pipeline & Authoring Format
*Cracks knuckles.* This is the big one. Let me propose the concrete line pool format.
### Line Pool Authoring Format: YAML
YAML is the right choice for human-authored content. It's readable, supports comments (authors can annotate their intent), handles multiline strings naturally, and has mature tooling. JSON is too noisy for 500+ authored lines. CSV loses structure. TOML gets awkward for nested data.
### Concrete Line Pool File Structure
Each template gets one YAML file per content category. The file structure:
```
content/
templates/
logistics-hub/
dialogue.yaml # NPC role dialogue lines
monologue.yaml # Player character reactions to this location
environmental.yaml # Signs, terminals, ambient text
trait-guide.yaml # How personality traits modify base lines
bar/
dialogue.yaml
monologue.yaml
environmental.yaml
trait-guide.yaml
smuggling-ring/
dialogue.yaml
monologue.yaml
environmental.yaml
trait-guide.yaml
characters/
smuggler/
voice-kit.yaml # Character-specific monologue voice
opening-hook.yaml # First 5 minutes content
detective/
voice-kit.yaml
opening-hook.yaml
shared/
greetings.yaml # Cross-template greeting pools
farewells.yaml # Cross-template farewell pools
generic-ambient.yaml # Non-location-specific monologue
```
### Line Entry Schema
Here's what a single line looks like in `dialogue.yaml`:
```yaml
# logistics-hub/dialogue.yaml
# Template: Logistics Hub (Workplace)
# Author: Mellanie
# Last updated: YYYY-MM-DD
meta:
template: logistics_hub
version: 1
line_count: 70 # target: 55-70 authored lines for this template
lines:
- id: lh_d_001
text: "Another shipment from Taliesin. Third one this week. Must be nice to have that kind of credit flow."
role: dock_worker # which NPC role speaks this
access: [insider, peer] # who hears this (D-028 Layer 1)
trust: surface # disclosure tier: surface | real | secret
topic: [work, cargo, money] # what the line is about
mood: [neutral, tired] # NPC mood states that select this line
situation: [routine, morning] # when this line is eligible
tags: [gossip, observation] # freeform classification
dual_lens: # how this line hits differently per character
smuggler: "Routine shop talk. But Taliesin shipments are your cover run."
detective: "Cargo volume anomaly. Worth checking manifests."
notes: "Sets up Taliesin as a location name. Smuggler knows this is cover cargo."
- id: lh_d_002
text: "You're new around here? Or just... visiting?"
role: dock_worker
access: [public]
trust: surface
topic: [social, identity]
mood: [cautious, neutral]
situation: [first_meeting]
tags: [greeting, probe]
dual_lens:
smuggler: "Never triggered — smuggler is known here."
detective: "First contact. Worker is sizing you up."
- id: lh_d_003
text: "Look, I mind my own business. You should try it."
role: dock_worker
access: [authority, hostile]
trust: surface
topic: [deflection]
mood: [annoyed, defensive]
situation: [interrogation, repeated_visit]
tags: [resistance, wall]
dual_lens:
smuggler: "Only if your cover is blown and they see you as authority now."
detective: "Standard resistance. Either genuinely uninvolved or protecting someone."
```
### Minimum Viable Tag Set for v0.1
Here's the taxonomy — the minimum set of tags that makes the four dialogue layers functional:
#### Structural Tags (required on every line)
| Tag | Type | Values | Purpose |
|-----|------|--------|---------|
| `id` | string | `{template}_{type}_{###}` | Unique identifier |
| `text` | string | The authored line | What the NPC says |
| `role` | enum | Template-defined roles (e.g., `dock_worker`, `bartender`, `ring_courier`) | Which NPC role speaks this |
| `access` | list\<enum\> | `public`, `insider`, `authority`, `peer`, `hostile` | D-028 Layer 1: who hears this |
| `trust` | enum | `surface`, `real`, `secret` | D-028 Layer 3: disclosure tier |
| `situation` | list\<enum\> | See situation taxonomy below | When this line is eligible |
#### Content Tags (recommended, can be empty)
| Tag | Type | Values | Purpose |
|-----|------|--------|---------|
| `topic` | list\<enum\> | `work`, `social`, `cargo`, `money`, `relationships`, `rumors`, `identity`, `deflection`, `weather`, `complaint` | What the line is about — enables topic-based conversation steering |
| `mood` | list\<enum\> | `neutral`, `happy`, `tired`, `annoyed`, `nervous`, `defensive`, `friendly`, `cautious` | NPC mood states that select this line |
| `tags` | list\<string\> | Freeform | Author classification for search and grouping |
#### Authoring-Only Tags (not consumed by engine, used by previewer and authors)
| Tag | Type | Values | Purpose |
|-----|------|--------|---------|
| `dual_lens` | map | Per-character notes | How this line reads differently per character |
| `notes` | string | Author comments | Design intent, context, dependencies |
#### Situation Taxonomy for v0.1
Situations are the context triggers that make lines eligible. Minimum set:
| Situation | Description |
|-----------|-------------|
| `greeting` | First interaction this game-day |
| `first_meeting` | Characters have never met |
| `routine` | Normal daily activity |
| `morning` / `afternoon` / `evening` / `night` | Day phase (D-031) |
| `repeated_visit` | Player has visited this NPC 3+ times |
| `interrogation` | Player is asking pointed questions |
| `witnessed_secret` | Player has seen something they shouldn't |
| `idle` | NPC is between activities |
| `working` | NPC is performing their job |
| `social` | NPC is socializing (bar, break, etc.) |
| `confrontation` | Triangle tension has boiled over |
| `post_event` | Responding to a recent simulation event |
### How the Four Dialogue Layers Map to Tags
**Question:** How do the 4 dialogue layers map to line tags? One tag per layer, or more complex?
Let me map it out:
| Dialogue Layer | Tag(s) Used | Selection Logic |
|----------------|-------------|-----------------|
| **Layer 1: Access tier** | `access` | Hard filter. If the player character's current access tier for this NPC's social site is not in the line's `access` list, the line is **invisible**. No fallthrough. |
| **Layer 2: Relationship history** | `situation` + engine state | The engine tracks interaction count, last interaction time, and notable events. This modifies which `situation` values are active. E.g., `first_meeting` is only true once; `repeated_visit` activates after threshold. **Not a single tag — it's engine state mapped to situation eligibility.** |
| **Layer 3: Trust-gated gossip** | `trust` | Progressive filter. NPCs start at `surface`. As relationship improves, `real` lines become available. `secret` lines only after significant trust threshold. **One tag, three values, engine controls the threshold.** |
| **Layer 4: Unprompted disclosure** | `topic` + `mood` + engine state | The NPC has things they WANT to say (driven by mood, recent events, triangle pressure). The engine picks from eligible lines weighted by NPC mood and topic relevance. **No single tag — it's a weighted selection across mood + topic from the eligible pool.** |
#### Selection Pipeline (simplified)
```
All lines for this NPC's role
|
├── Filter by access tier (Layer 1) → removes ~40-60% of lines
|
├── Filter by situation (Layer 2) → narrows to context-appropriate lines
|
├── Filter by trust level (Layer 3) → caps disclosure depth
|
└── Weight by mood + topic relevance (Layer 4) → ranks remaining lines
|
└── Select top-weighted line (with variety tracking to avoid repeats)
```
**Key insight:** Layers 1 and 3 are HARD FILTERS (binary: eligible or not). Layers 2 and 4 are SOFT SELECTORS (weighting and context). This means:
- Authors must ensure every access/trust combination has enough lines to avoid dead conversations
- Authors can be more flexible with mood/topic — the engine can fall back to `neutral` mood lines
### Monologue Line Format
Monologue uses a similar but distinct schema. Key difference: monologue is triggered by observation EVENTS, not conversation initiation.
```yaml
# logistics-hub/monologue.yaml
lines:
- id: lh_m_001
text: "Busy morning. The usual controlled chaos."
character: smuggler
trigger: enter_location # what observation event fires this
location: logistics_hub
situation: [morning, routine]
mood: [neutral, relaxed] # character mood, not NPC mood
prerequisite: null # knowledge state required (null = always eligible)
tags: [atmosphere, establishing]
- id: lh_m_002
text: "Same faces, same cargo, same lies. Comfortable."
character: smuggler
trigger: enter_location
location: logistics_hub
situation: [morning, routine]
mood: [neutral, content]
prerequisite: { knows: smuggling_operation }
tags: [atmosphere, character_voice, irony]
- id: lh_m_003
text: "Standard logistics operation. On paper. The throughput numbers don't add up, though."
character: detective
trigger: enter_location
location: logistics_hub
situation: [morning, routine]
mood: [neutral, analytical]
prerequisite: { knows: cargo_anomaly }
tags: [investigation, observation, clue]
```
#### Monologue Trigger Taxonomy for v0.1
| Trigger | Description | Example |
|---------|-------------|---------|
| `enter_location` | Player enters a new area | "The bar's quieter than usual." |
| `observe_npc` | Player sees an NPC doing something | "They're checking the manifest again." |
| `hear_sound` | Sound event from fog edge | "Footsteps. Two people, moving fast." |
| `observe_anomaly` | NPC deviates from routine | "That's not where they usually go at this hour." |
| `post_conversation` | After dialogue ends | "They were lying. The pause before 'I don't know' — classic tell." |
| `discover_evidence` | Player examines an object with information | "This doesn't match the official log." |
| `witness_interaction` | Player sees two NPCs interacting | "Those two don't normally talk." |
| `time_idle` | Player hasn't done anything for a while | "Should probably get moving." |
| `return_visit` | Player returns to a previously visited area | "Different shift. Different faces." |
---
## Layer 5: Template Content & Entanglement
**Question:** How does the entanglement ratio (30/50/20) play out across ~15 NPCs?
Let me do the math and map it concretely.
### NPC Distribution (D-029 applied to v0.1)
With ~15 NPCs across 3 social sites:
| Entanglement Level | Count | Description | Template Distribution |
|-------------------|-------|-------------|----------------------|
| **Flat** (~30%) | 4-5 NPCs | Routine + greeting only. Social wallpaper. | 1-2 per template |
| **Mundane Triangle** (~50%) | 7-8 NPCs | Involved in non-conspiracy social drama. Neighbor disputes, workplace rivalries, relationship tensions. | 2-3 per template |
| **Entangled** (~20%) | 3 NPCs | Connected to smuggling operation. Their secrets are the investigation targets. | Primarily in ring template, with 1 bridge NPC in another |
### Concrete NPC Skeleton (proposal)
Here's how I'd distribute them:
**Logistics Hub (5 NPCs):**
| Role | Name (placeholder) | Entanglement | Triangle Role |
|------|--------------------|-------------|---------------|
| Shift Supervisor | [TBD] | Mundane | Triangle A: workplace authority tension |
| Dock Worker 1 | [TBD] | Flat | Wallpaper — reliable, boring, friendly |
| Dock Worker 2 | [TBD] | Mundane | Triangle A: chafes under supervisor |
| Cargo Handler | [TBD] | **Entangled** | Ring member. Uses job to move product. Bridge NPC to ring template. |
| Admin Clerk | [TBD] | Mundane | Triangle B: knows more than they should about cargo discrepancies |
**Bar (5 NPCs):**
| Role | Name (placeholder) | Entanglement | Triangle Role |
|------|--------------------|-------------|---------------|
| Bartender | [TBD] | Mundane | Triangle C: social hub, hears everything, discreet |
| Regular 1 | [TBD] | Flat | Wallpaper — always there, colorful but uninvolved |
| Regular 2 | [TBD] | Mundane | Triangle C: has a thing for the bartender, jealous of attention |
| Off-duty Worker | [TBD] | Mundane | Triangle B (cross-template): same person from logistics hub, different behavior here. Bridge NPC. |
| Stranger | [TBD] | Flat | Wallpaper — different face each playthrough. Procedural filler. |
**Smuggling Ring (5 NPCs):**
| Role | Name (placeholder) | Entanglement | Triangle Role |
|------|--------------------|-------------|---------------|
| Ring Leader | [TBD] | **Entangled** | Runs the operation. Triangle D: power/loyalty tension |
| Ring Courier | [TBD] | **Entangled** | Moves product between ring and hub. Triangle D: pressured by leader, considering turning |
| Ring Lookout | [TBD] | Mundane | Triangle D: doesn't know the full scope of operation, thinks it's minor smuggling |
| Ring Contact (bar) | [TBD] | Mundane | Triangle C (cross-template): the ring's eyes and ears at the bar |
| Ring Fixer | [TBD] | Flat | Wallpaper for the ring — handles logistics, no drama |
### Triangle Map
| Triangle | NPCs | Tension | Type |
|----------|------|---------|------|
| **A** (Logistics Hub) | Supervisor, Dock Worker 2, Cargo Handler | Authority vs autonomy. Worker resents supervisor. Handler stays quiet to protect cover. | Mundane + one entangled leg |
| **B** (Cross-template) | Admin Clerk (Hub), Off-duty Worker (Bar), Cargo Handler (Ring) | The clerk noticed discrepancies. The off-duty worker drinks too much and talks. The handler needs to keep both quiet. | Cross-template, entangled |
| **C** (Bar) | Bartender, Regular 2, Ring Contact | Social drama. Regular is jealous. Ring Contact uses bar as intel gathering. Bartender sees all, says nothing. | Mundane + one entangled leg |
| **D** (Ring) | Ring Leader, Ring Courier, Ring Lookout | Power and loyalty. Leader pushes for more volume. Courier is cracking under pressure. Lookout thinks it's small-time. | Entangled |
**Note for Paula:** Triangle B is the critical cross-template triangle. It's the mechanism by which the smuggling operation contaminates the mundane social world. The clerk's curiosity + the worker's loose lips + the handler's need for silence is a pressure cooker that the player can observe, manipulate, or accidentally trigger.
### Does This Create Interesting Decisions?
For the **smuggler**: You KNOW the handler, the courier, the leader. Your daily life is managing these relationships. Triangle B is your biggest risk — the clerk is asking questions, the worker talks too much at the bar. Do you befriend the clerk to deflect? Warn the worker to shut up? Or trust the handler to manage it? Every choice has relationship consequences.
For the **detective**: You don't know any of this at first. You see a normal workplace, a normal bar. But the clerk seems nervous. The worker mentions "weird cargo hours" after their third drink. The handler is suspiciously friendly with the detective — trying to assess the threat. The detective's game is connecting these dots through observation and conversation.
**This is the fun.** Same 15 people, completely different games.
---
## Layer 6: Minimum Viable Tell System
**Question:** What's the minimum viable tell system? One behavioral marker per axis, or fewer?
Let me break down what "tells" actually need to DO mechanically before deciding volume.
### What Tells Are For
A "tell" is an observable behavior that reveals internal NPC state without the NPC explicitly saying anything. Tells are the bridge between the simulation (NPC has mood=nervous, secret=smuggling) and the perception system (player sees NPC fidgeting, looking over their shoulder).
Tells serve two functions:
1. **Reward observation** — the player who watches carefully learns more than the player who just talks
2. **Create investigation breadcrumbs** — "they seem nervous" prompts the player to dig deeper
### Minimum Viable Tell System for v0.1
**Not one per axis. That's 10 tells per NPC x 15 NPCs = 150 behavioral markers. Way too many for v0.1.**
Instead: tells should map to the PLAYER-FACING question, not the simulation axis. The player doesn't think in axes — they think in "what's wrong with this person?"
| Tell Category | Maps to Axes | Observable Behavior | Implementation |
|---------------|-------------|---------------------|----------------|
| **Nervous/hiding something** | Secret, Tolerance threshold | Fidgeting sprite variation, checking over shoulder, breaking eye contact (monologue describes) | 2-3 text descriptions in monologue pool |
| **Angry/frustrated** | Contentment (low), Tolerance (near threshold) | Terse dialogue, aggressive movement pattern (faster walk), monologue notes "they look tense" | Mood affects dialogue selection + 1 movement modifier |
| **Friendly/warm** | Relationships (positive), Personality (sociable) | Longer conversations, approaches player proactively, monologue notes openness | Unprompted disclosure weighting increase |
| **Guarded/cold** | Relationships (negative), Access (hostile) | Short responses, avoids player, monologue notes resistance | Access tier filtering does this naturally |
| **Routine deviation** | Secret (active), Want (pursuing something) | NPC goes somewhere they normally don't, at an unusual time | Routine system deviation flag + monologue trigger |
**That's 5 tell categories for v0.1.** Each is expressed through a combination of:
- Monologue lines (character interprets the tell) — cheapest, most expressive
- Dialogue weighting (mood shifts what lines are selected) — already in the pipeline
- Movement behavior (1 modifier: speed/path deviation) — lightweight
**Most tells in v0.1 will be TEXT, not visual.** The monologue system IS the tell renderer. "They're checking the corridor before entering the back room" is a tell delivered through monologue, not through a complex animation system. This is consistent with D-016 (monologue as perception bridge) and D-014 (functional boxes with labels).
### What Mellanie Needs
For each of the 5 tell categories, 3-5 monologue lines per character. That's 30-50 monologue lines dedicated to tells, split between smuggler and detective voice.
**Smuggler tell monologue** reads differently from detective tell monologue:
- Smuggler noticing nervousness: "They're spooked. Wonder who's been asking questions."
- Detective noticing nervousness: "Nervous. Either guilty or scared of someone who is."
Same observation, different interpretation. This is where the dual-lens system shines brightest.
---
## Layer 7: Monologue & Observation Text
No direct questions for Gestalt here, but a systems note:
**Monologue content volume is the highest content risk in the entire project** (I flagged this in the previous gap analysis workshop). The monologue system carries perception, atmosphere, tutorial, tells, investigation clues, and character voice — simultaneously. If it feels thin or repetitive, the entire game suffers.
The trigger taxonomy I defined in Layer 4 above (9 trigger types) maps directly to content authoring work. Mellanie needs to write lines for each trigger type x each location x each character. That's approximately:
| Trigger | Lines per location | x3 locations | x2 characters | Total |
|---------|-------------------|-------------|----------------|-------|
| `enter_location` | 3-5 | 9-15 | 18-30 | 18-30 |
| `observe_npc` | 5-8 | 15-24 | 30-48 | 30-48 |
| `hear_sound` | 3-4 | 9-12 | 18-24 | 18-24 |
| `observe_anomaly` | 3-5 | 9-15 | 18-30 | 18-30 |
| `post_conversation` | 5-8 | 15-24 | 30-48 | 30-48 |
| `discover_evidence` | 2-3 | 6-9 | 12-18 | 12-18 |
| `witness_interaction` | 3-5 | 9-15 | 18-30 | 18-30 |
| `time_idle` | 2-3 | — (shared) | 4-6 | 4-6 |
| `return_visit` | 2-3 | 6-9 | 12-18 | 12-18 |
**Estimated monologue line count: 160-250 authored lines.** Plus the 30-50 tell lines. Call it **200-300 monologue lines total** — consistent with the D-028 workshop estimate.
These are authored lines. The 4x generation expansion applies here too, giving ~800-1200 total monologue lines in the game. That should prevent repetition across a 30-minute session.
---
## Layer 8: UI Text & Onboarding
**Question:** Does v0.1 need onboarding text, or can the monologue system serve as the tutorial (D-016 "diegetic tutorial")?
**Answer: Monologue IS the tutorial. No separate onboarding text needed for v0.1.**
Here's how it works mechanically:
### Diegetic Tutorial Through Monologue
The player's first 2-3 minutes produce a sequence of monologue lines that teach by narrating:
| Player Action | Monologue Tutorial | What It Teaches |
|---------------|-------------------|-----------------|
| Game starts | "Another day at [station]. Better check the schedule." (Smuggler) / "Precinct forwarded the case file. Time to start." (Detective) | You have a purpose. You're a person. |
| Player moves | "Quiet corridor. Nobody around." | Vision cone — you can see what's in front of you. |
| Player approaches fog edge | "Something around the corner. Can't see from here." | Fog = limited perception. Move to see more. |
| Player hears sound through wall | "Voices. Can't make out what they're saying from here." | Sound carries through walls. Get closer. |
| Player sees first NPC | "That's [Name]. [Brief relationship context]." (Smuggler) / "Unknown civilian. Standard profile." (Detective) | You know (or don't know) people. Character relationships matter. |
| Player talks to NPC | (Dialogue system handles this) | Conversation exists. Different people tell you different things. |
| Player checks insert | "Let's see... [location info]." | The minimap/insert exists and is diegetic. |
**No "Press WASD to move" text.** No tooltip overlays. The character's thoughts teach the player by reacting to what the player does naturally.
**What this requires from Mellanie:** A special `opening-hook.yaml` per character with 10-15 tightly sequenced monologue lines that fire in response to the player's first actions. These are the most important lines in the entire game — they set voice, teach mechanics, and establish motivation simultaneously.
### UI Text That IS Needed
Even with diegetic tutorial, some UI text is unavoidable:
| UI Element | Text Needed | Volume |
|------------|-------------|--------|
| Main menu | New Game, Continue, Settings, Quit | 4-6 strings |
| Character select | Smuggler description, Detective description | 2 paragraphs |
| Pause menu | Resume, Save, Load, Settings, Quit | 5-6 strings |
| Insert/minimap labels | POI names, distance indicators | ~10-15 strings |
| Dialogue UI | "Talk", "Leave", topic selection labels | ~5-10 strings |
| Time display | Day phase indicator, clock format | 4-5 strings |
**Total UI text: ~40-50 strings.** Trivial volume. Can be authored in an afternoon.
---
## Layer 9: Audio Direction
**Question:** Does the three-range sound model need audio content to prove itself, or can it work with system beeps and text?
**Answer: Text-only sound is mechanically sufficient for v0.1. Audio content is a wow multiplier, not a proof requirement.**
Here's why:
### How Sound Works Without Audio Files
The three-range model (D-018) is fundamentally an INFORMATION system, not an audio system. What matters is:
| Range | What the player needs to know | Text-only delivery |
|-------|------------------------------|-------------------|
| Close | "I can hear this clearly" | Monologue: "Footsteps behind me. Two people." |
| Medium | "Something's happening nearby but I can't see it" | Visual indicator at fog edge + monologue: "Voices from the next room." |
| Long | "Information arrived through my insert" | Insert notification text: "Alert: disturbance reported in Sector 7" |
All three ranges work through text + visual indicators. The SYSTEM is provable without a single audio file.
### What Audio WOULD Add
Audio adds emotional texture that text can't match:
- Close range: actual footstep sounds create spatial awareness and tension
- Medium range: muffled voices through walls create curiosity and dread
- Fog edge: ambient hum vs silence communicates "something's there" vs "empty"
**Recommendation:** Defer ALL authored/designed audio to a later sprint. For v0.1, use at most:
- 1 ambient drone per location type (3 total — can be freely licensed or generated)
- 1 footstep sound for close-range feedback
- 1 "notification chime" for insert alerts
That's 5 sound files. The rest is text + visual indicators. If even this is too much, zero audio is acceptable. The monologue system can carry the entire perceptual load.
**But the system architecture must still support audio.** The sound event system (#124) should emit events regardless of whether audio content exists. The client receives "sound event at coordinates X,Y with type FOOTSTEPS" — whether it plays a wav file or shows a visual indicator is a client rendering decision. Don't build the system around text; build it around events and render text as the v0.1 fallback.
---
## Cross-Layer Synthesis: What Gestalt Thinks the Content Team Needs
### Priority-Ordered Content Work
| Priority | Deliverable | Owner | Depends On | Lines/Volume |
|----------|-------------|-------|------------|-------------|
| 1 | Line pool format specification (this document) | Gestalt (done) | Nothing | Spec only |
| 2 | Dual Lens Authoring Guide | Paula | Layer 2 access tier model (above) | ~10 pages |
| 3 | Station district setting brief | Miri | Nothing | ~2-3 pages |
| 4 | Character voice kits (smuggler + detective) | Mellanie | Dual Lens Guide | 20-30 sample lines per character |
| 5 | Opening hook content (per character) | Mellanie | Voice kits | 10-15 lines per character |
| 6 | NPC profiles (15 NPCs) | Paula + Mellanie | Setting brief, character builds | 1 page per NPC |
| 7 | Logistics Hub content pack (#190) | Mellanie | NPC profiles, line pool format | ~55-70 dialogue + ~30-40 monologue lines |
| 8 | Bar content pack (#191) | Mellanie | NPC profiles, line pool format | ~55-70 dialogue + ~30-40 monologue lines |
| 9 | Smuggling Ring content pack (#192) | Mellanie | NPC profiles, line pool format | ~55-70 dialogue + ~30-40 monologue lines |
| 10 | Tell monologue lines | Mellanie | NPC profiles, tell categories | 30-50 lines |
| 11 | Environmental text | Mellanie + Araminta | Setting brief | ~30-50 strings |
| 12 | UI text | Mellanie | Character descriptions | ~40-50 strings |
### The Critical Path
```
Dual Lens Guide (Paula)
+ Station Setting (Miri)
+ Line Pool Format (Gestalt - this document)
→ Character Voice Kits (Mellanie)
→ Opening Hooks (Mellanie)
→ NPC Profiles (Paula + Mellanie)
→ Content Packs x3 (Mellanie)
→ Tell Lines + Environmental (Mellanie)
```
**Nothing blocks the line pool format — it's spec work.** The Dual Lens Guide and Station Setting can proceed in parallel. Once those two exist, Mellanie can start writing. The content packs are the bulk of the work and should start as soon as the voice kits feel right.
### One Last Mechanical Note
**The line previewer (#193) is critical.** Mellanie cannot efficiently author 500+ tagged lines without a tool that shows "given this NPC, this access tier, this mood, this situation — what line would fire?" The previewer doesn't need to be pretty. It needs to load a YAML file, accept filter parameters, and show the selected line. A CLI tool. Tyre can build this as a Rust binary that reads the YAML and applies the selection pipeline.
Without the previewer, Mellanie is writing blind. Tag errors won't surface until integration. That's a recipe for rework.
---
*Gestalt out. The format is proposed, the tags are defined, the pipeline is mapped. Now we need Paula's lens guide, Miri's setting, and Mellanie's voice. The systems are ready for content.*
docs/workshops/content-gap-analysis_v0_1/round1-mellanie.md
-438
View File
@@ -1,438 +0,0 @@
# Round 1 — Mellanie's Content Gap Analysis
**Agent:** Mellanie (Copywriter)
**Date:** 2026-02-11
**Scope:** All 9 layers, copywriting perspective
---
## Layer 1: Art Direction & Visual Identity
Not my lane directly, but I'll flag the intersection: **visual style determines how much weight text carries.** D-014 says "functional boxes with labels" and D-016 says "atmosphere carried by monologue." If the art stays minimal, my text is doing 80% of the atmosphere work. If the art gets moody, the text can be sparser.
**My ask for Araminta:** Tell me the visual fidelity target so I can calibrate density. Minimal art = more monologue lines per location. Moody art = fewer, sharper lines. I need to know which world I'm writing for.
---
## Layer 2: Narrative Framework & Character Design
### Q3: What do I need from the character builds before I can write voice-consistent dialogue?
Five things. Non-negotiable.
**1. Voice signature.** Not personality traits — *speech patterns.* Short sentences or long? Profanity or clean? Technical vocabulary or street? Internal monologue style: does the smuggler think in observations or feelings? Does the detective think in hypotheses or facts?
Here's what I mean concretely:
> **Smuggler sees a cargo container out of place:**
> *Option A (cautious, observational):* "That container's been moved. Wasn't there this morning."
> *Option B (anxious, relational):* "Kael moved the container again. He's going to get us all caught."
> *Option C (sardonic, detached):* "Someone rearranged the furniture. How creative."
Each of those is a different character. I need to know which one before I write 500 lines.
**2. What they notice.** The smuggler and detective look at the same room and see different things. Not just because of information boundaries — because of *attention.* The smuggler notices exits, security cameras, who's watching. The detective notices inconsistencies, nervousness, things out of place. This shapes every monologue line and every dialogue choice.
**3. Relationship to authority.** How do they talk to people with power over them? How do they talk to people they have power over? The smuggler with their ring boss vs. the detective with their precinct captain — those power dynamics shape every interaction.
**4. What they lie about.** Both characters have things they conceal or misrepresent. The smuggler hides their criminal activity. The detective might hide their investigation from suspects. Knowing what they lie about tells me what their "public voice" sounds like vs. their "internal voice."
**5. Emotional baseline.** Not mood — *posture.* Is the smuggler generally anxious, comfortable, or resigned? Is the detective generally confident, frustrated, or obsessive? This is the default register that all their lines return to between dramatic moments.
**Proposal:** I'll write a **Voice Kit** for each character — a 1-page document with these five elements plus 10 sample monologue lines covering common situations (entering a room, greeting an acquaintance, noticing something wrong, being lied to, being alone). Paula defines the narrative identity; I translate it into voice. The Voice Kit becomes the reference that keeps all dialogue on-character.
**Dependency:** Paula's character arc outlines (#180, #181) must come before my Voice Kits. I need to know who these people *are* before I can figure out how they *sound.*
---
## Layer 3: Station District Setting
Not my primary deliverable, but I write text that lives in this space. My ask for Miri:
**Give me the texture, not just the lore.** I don't need a history essay. I need:
- What does this place *smell* like? (Monologue uses all senses.)
- What's the slang? Do people say "shift" or "rotation"? "Credits" or "sols"?
- What's on the walls — corporate signage? Safety warnings? Union notices? Graffiti?
- What's the ambient sound the monologue might reference — machinery hum? Ventilation? Crowd noise?
- What's the local complaint? Every community has one. Bad water. Late transports. Overpriced food.
These details are what make monologue and environmental text feel *placed* instead of generic sci-fi.
---
## Layer 4: Content Pipeline & Authoring Format
### Q2: Can I write content packs in a provisional format before the previewer exists?
**Yes, with conditions.**
I can write in any structured text format — YAML, Markdown with frontmatter, even a spreadsheet — as long as we agree on the tag taxonomy first. The actual file format matters less than the metadata structure. I can adapt format later; I can't retag 500 lines.
**What I need locked before I write:**
1. **Tag taxonomy.** The minimum set of tags per line. My proposal for v0.1:
| Tag | Values | Purpose |
|-----|--------|---------|
| `character` | smuggler, detective, any | Who can trigger this line |
| `access` | insider, outsider, authority, peer | D-028 Layer 1 filter |
| `trust` | surface, real, secret | D-028 Layer 3 disclosure tier |
| `location` | workplace, bar, ring, corridor, any | Where this line fires |
| `situation` | greeting, idle, gossip, confrontation, observed_anomaly, absence, routine | What's happening |
| `mood` | neutral, tense, relaxed, suspicious, friendly | NPC emotional state |
| `topic` | work, personal, crime, rumor, weather, complaint | What the line is about |
| `type` | dialogue, monologue, environmental, ticker | Content category |
That's 8 tags. Enough to filter meaningfully, few enough to author quickly. Gestalt can add more if the system needs them, but I can start writing with these.
2. **Line format.** My proposed provisional format (Markdown-friendly, convertible to YAML/JSON later):
```
---
id: wp-dock-greeting-01
character: any
access: insider
trust: surface
location: workplace
situation: greeting
mood: neutral
topic: work
type: dialogue
speaker: dock_supervisor
---
Another day, another manifest. You know the drill.
```
If the actual format changes, I can batch-convert. The content and tags are what matter.
3. **One example template fully tagged.** Before I write 165 lines for the workplace, I want to write 20, tag them, and have Gestalt validate that the tags produce the right filtering behavior. Call it a "tag smoke test." This catches taxonomy problems before they compound.
**What I do NOT need before starting:**
- The previewer CLI (#193). Nice to have, not a blocker. I'll write blind and validate later.
- Final file format. Provisional is fine.
- Generation pass specs (#194). I write the authored core; expansion is a separate step.
---
## Layer 5: Template Content (3 Social Sites)
### Q1: What does a content pack deliverable look like? Break down #190.
Here's what the **Workplace Content Pack** (#190) contains, broken into concrete writing tasks:
#### A. Role Voice Kits (4-6 roles, ~5 lines each = 20-30 lines)
Each role in the workplace template gets a voice kit: a set of sample lines that establish how this *type* of person talks. Not a specific NPC — a role that gets filled by a generated NPC.
Proposed workplace roles:
- **Dock Supervisor** — authority figure, stressed, deadline-driven
- **Cargo Handler** — physical worker, pragmatic, gossip-prone
- **Logistics Clerk** — desk worker, detail-oriented, nervous or bored
- **Maintenance Tech** — gruff, observant, knows every corner of the facility
- **Security Guard** — bored or paranoid, depending on personality axis
- **Shift Manager** — middle management, caught between workers and bosses
Each kit: 5 lines covering greeting, idle chatter, reaction to anomaly, reaction to authority, and one line that hints at their secret/vulnerability axis.
#### B. Situation Scripts (tagged line pools — the bulk, ~80-100 lines)
These are the lines that fire during gameplay, filtered by tags. Organized by situation:
| Situation | Lines | Description |
|-----------|-------|-------------|
| Greetings | 15-20 | First contact lines, filtered by access tier and relationship |
| Idle/ambient | 15-20 | Background chatter, complaints, observations. The "daily life" texture |
| Work talk | 10-15 | Job-related conversation. Manifests, schedules, problems |
| Gossip | 10-15 | Trust-gated. Surface: weather, sports. Real: who's sleeping with whom. Secret: who's smuggling what |
| Confrontation | 5-10 | When triangle tensions surface. Accusations, denials, pleas |
| Observed anomaly | 5-10 | NPC reacts to something unusual. Feeds the observation chain |
| Authority interaction | 5-10 | How NPCs talk to/about the boss. Power dynamics |
#### C. Monologue Hooks (per character, ~30-40 lines)
Lines that fire as the player character's internal monologue in this location:
| Category | Smuggler | Detective |
|----------|----------|-----------|
| Entering workplace | 8-10 lines: routine, familiar, noting who's in/out | 8-10 lines: scanning, assessing, noting what seems off |
| Observing NPC behavior | 5-8 lines: protective, concerned about exposure | 5-8 lines: analytical, building hypotheses |
| Noticing anomaly | 3-5 lines: alarm, calculating risk | 3-5 lines: interest, cataloguing evidence |
| Absence/deviation | 3-5 lines: "Where's Kael?" worry-flavored | 3-5 lines: "Subject deviated from pattern" analytical |
#### D. Environmental Text (~15-20 items)
Diegetic text that exists in the space:
- Shift schedule board (readable, updates with game time)
- Safety notices ("Report unauthorized cargo to Security — Management")
- Cargo manifest fragments (readable if you examine them — information source)
- Employee notice board (upcoming events, complaints, lost items)
- Terminal login screen text
- Door labels, section markers, warning signs
#### E. Trait Transformation Guide (~1 page)
How personality axes modify the base lines. Not per-trait scripts — guidelines:
| Trait axis | Low | High | Effect on dialogue |
|------------|-----|------|--------------------|
| Tolerance | Snaps fast, short answers | Patient, elaborate | Shorter/longer responses, more/fewer warnings before confrontation |
| Contentment | Bitter, complaining | Satisfied, dismissive | Tone of idle chatter. Discontented NPCs gossip more |
| Want (ambition) | Passive, accepting | Driven, scheming | Proactive vs reactive dialogue. High-want NPCs steer conversations |
**Total for one template: ~165-200 authored lines + environmental text + trait guide.**
Three templates = ~500-600 authored lines of dialogue/monologue + ~50-60 environmental text items + 3 trait guides.
That's achievable. It's a focused sprint of writing, not a marathon. The quality bar is what takes time, not the volume.
---
## Layer 6: NPC Profiles & Dialogue
### Q1 (with Paula): How deep does each NPC profile need to be?
**Two tiers of depth, matching the 30/50/20 split.**
**Flat NPCs (30%, ~4-5 NPCs):** The 10 axes plus one distinguishing line. That's it. These people are wallpaper with a pulse. They greet you, they make small talk, they go about their routine. They exist so the station feels populated.
What I need per flat NPC:
- Name
- Role (which role voice kit to draw from)
- One distinguishing trait or habit (the dock worker who always eats during shift, the clerk who hums)
- 3-5 custom lines that make them *slightly* memorable (beyond the generic role pool)
**Triangle NPCs (50%, ~7-8 NPCs) and Entangled NPCs (20%, ~3 NPCs):** The 10 axes plus a **voice paragraph.** Not a full backstory — a paragraph that captures how this specific person *talks* and *thinks,* enough for me to write lines that feel specific to them.
What I need per triangle/entangled NPC:
- Name
- Role + which social sites they appear in
- 10-axis values (especially Want, Secret, Relationships, Contentment)
- One paragraph: "Kael talks like [X], thinks about [Y], is hiding [Z]. When stressed, he [behavior]. When comfortable, he [behavior]."
- Their triangle position: who they're in conflict with, what they want from the triangle
- 8-15 custom lines (beyond role pool) that express their specific voice and situation
**Who writes these profiles?** Paula defines the narrative identity and triangle dynamics. Miri provides cultural/setting flavor. I write the voice paragraph and sample lines. It's a collaboration, not a solo task.
### Q2: How many lines per NPC for v0.1?
Let me do the real math.
**Flat NPCs (~5):** 3-5 custom lines each = 15-25 lines. Plus they draw from the role voice pool, so they have maybe 20-30 lines available total (role pool + custom).
**Triangle NPCs (~8):** 8-15 custom lines each = 64-120 lines. Plus role pool. Total available per NPC: 30-45 lines.
**Entangled NPCs (~3):** 12-20 custom lines each = 36-60 lines. These need the most specific, plot-relevant dialogue. Total available per NPC: 40-55 lines.
**Custom NPC lines total: 115-205 lines.**
These sit ON TOP of the template content packs (~500-600 lines of role-based dialogue). The role pools provide the substrate; NPC-specific lines provide the personality.
**Grand total authored lines for v0.1:**
| Category | Lines |
|----------|-------|
| Template dialogue (3 packs) | 500-600 |
| NPC-specific lines (~15 NPCs) | 115-205 |
| Monologue — smuggler | 100-150 |
| Monologue — detective | 100-150 |
| Environmental text | 50-60 |
| UI/insert text | 20-30 |
| News ticker / unisphere | 15-20 |
| **Total authored** | **~900-1,215** |
After 4x generation expansion on the template dialogue: **~3,000-3,600 total lines available to the system.**
That's a solid content floor. It won't feel infinite, but it won't feel empty during a 30-minute session. The player will encounter maybe 150-200 lines per playthrough. Repetition becomes a problem only on the 3rd or 4th play of the same character.
---
## Layer 7: Monologue & Observation Text
### Q1: How many monologue lines make v0.1 feel alive?
The 200-300 estimate is the *floor.* Let me break it down by function:
| Function | Smuggler | Detective | Total |
|----------|----------|-----------|-------|
| **Location atmosphere** (entering/being in a place) | 25-30 | 25-30 | 50-60 |
| **NPC observation** (noticing behavior, tells) | 20-25 | 20-25 | 40-50 |
| **Absence/deviation** (expected NPC not present, routine broken) | 10-15 | 10-15 | 20-30 |
| **Sound interpretation** (hearing through fog) | 8-10 | 8-10 | 16-20 |
| **Investigation/deduction** (connecting dots) | 10-15 | 15-20 | 25-35 |
| **Emotional/reflective** (quiet moments, character depth) | 10-15 | 10-15 | 20-30 |
| **Diegetic tutorial** (hinting at available actions) | 8-10 | 8-10 | 16-20 |
| **Mirror moments** (hinting at the other perspective) | 5-8 | 5-8 | 10-16 |
| **Total** | **~96-128** | **~101-133** | **~197-261** |
Call it **250 monologue lines** as the authoring target. Some will overlap (same observation, different character voice), but most need to be distinct because the two characters *think differently* about what they see.
The generation pass doesn't work as well for monologue as for dialogue. Dialogue can be expanded with variations on the same sentiment. Monologue needs to feel *specific* — it's the character's private thoughts. Generic expansion will sound hollow. I'd estimate a 2x generation pass on monologue at best, giving us ~500 monologue lines total. That's enough for 2-3 playthroughs per character before noticeable repetition.
### Q2: Same observation event, different monologue — separate pools or shared?
**Separate pools. No question.**
The smuggler and detective don't just say different words about the same thing — they *see* different things. The whole game is built on this. Shared pools with character filters would tempt us toward "same observation, different adjective." That's death for the core mechanic.
Here's the concrete difference:
> **Event: NPC enters the back room during off-hours.**
>
> Smuggler pool:
> - "There goes Kael. Right on schedule."
> - "Back room again. He better not be skimming."
> - "Hope he remembered to lock the side door this time."
>
> Detective pool:
> - "Unauthorized access to restricted area. Noted."
> - "That's the second time today. What's in the back room?"
> - "He looked around before going in. People who belong somewhere don't check if they're watched."
Same event trigger. Completely different interpretation. The smuggler's lines reveal *familiarity* with the criminal activity. The detective's lines reveal *analytical distance.* You cannot get this from a shared pool with a character tag — the entire framing, vocabulary, and emotional register are different.
**Structure:** Two parallel monologue pools, one per character, keyed to the same observation event triggers. The observation event generator (#239) fires a trigger; the monologue system selects from the appropriate character pool. Tags on each line handle further filtering (location, mood, trust level, prior knowledge).
**This doubles the monologue writing work, but it IS the game.** If the monologue sounds the same from both characters, we've failed D-027's core success criterion. There is no shortcut here.
### Mirror Moments
Paula asked about these in the brief. Here's what they look like from a writing perspective:
A mirror moment is when the monologue *almost* acknowledges the other character's viewpoint without breaking the fourth wall. The character glimpses the moral complexity of their position.
> **Smuggler mirror moment** (watching the detective interview a colleague):
> "She's just doing her job. ...Aren't we all."
>
> **Detective mirror moment** (learning that a suspect supports their family through smuggling):
> "Twelve dependents on a cargo handler's salary. The math doesn't work. But the math never does for these people."
These are rare — 5-8 per character across the whole session. They're the moments where the writing does the thematic heavy lifting. They plant the seed of "what would this look like from the other side?" without ever saying it explicitly. On a second playthrough as the other character, the player remembers these lines and they hit differently.
---
## Layer 8: UI Text & Environmental Content
### Q1 (with Araminta): What text appears on screen besides dialogue and monologue?
Here's the full inventory:
#### Insert/HUD Text
- Time display (diegetic — the character's neural insert showing time)
- POI labels on minimap ("Logistics Hub," "The Rusty Valve," "Sector 7 Maintenance")
- Status indicators ("Signal weak," "Insert interference detected")
- Notification text ("New contact added," "Location discovered")
#### Environmental Text (diegetic — exists in the game world)
- Door labels and room signs
- Corporate signage (company names, slogans)
- Safety/regulatory notices
- Employee notice boards
- Cargo manifest fragments (readable as investigation tools)
- Terminal screens (login prompts, error messages, data readouts)
- News ticker / unisphere feed headlines
- Graffiti (if the station has a rougher district area)
- Menu/price board at the bar
- Wanted notices or institutional postings
#### UI Chrome (non-diegetic — game interface)
- Dialogue choice labels (if we have explicit choices, not just proximity-triggered lines)
- Journal/knowledge entries (if #264 makes it into v0.1)
- Tooltip text on interactive objects ("Examine," "Talk," "Read")
- Save/load screen text
- Settings menu labels
- Pause screen text
- Character selection screen text (if any)
#### Diegetic Tutorial Text (via monologue — D-016)
This isn't separate UI text — it's monologue lines that teach mechanics:
- "I could check my insert for the area layout." (teaches minimap)
- "Better keep my distance if I'm going to follow him." (teaches follow mechanic)
- "That terminal might have shipping records." (teaches examine)
- "Sounds like an argument in the next room. I could get closer to hear." (teaches eavesdrop)
**Volume estimate for non-dialogue/non-monologue text:**
| Category | Items | Lines |
|----------|-------|-------|
| Insert/HUD | 10-15 unique strings | 10-15 |
| Environmental — workplace | 15-20 items | 20-30 |
| Environmental — bar | 10-15 items | 15-25 |
| Environmental — ring | 5-10 items | 10-15 |
| Environmental — corridors/shared | 5-10 items | 8-12 |
| UI chrome | 15-20 unique strings | 15-20 |
| News ticker headlines | 10-15 items | 10-15 |
| **Total** | | **~88-132** |
This is quick writing — short strings, functional language, world-flavored. I can produce the full set in a focused session once I have Miri's setting document for terminology and Araminta's UI spec for constraints (character limits, display format).
---
## Layer 9: Audio Direction
From a copywriting perspective: **silence is fine for v0.1, but it shifts burden to me.**
If there's no ambient audio, every sense except sight goes through monologue. The character has to *narrate* the soundscape:
> "The ventilation system hums. Always that same frequency. I've stopped noticing it."
> "Footsteps behind me. Two people. Unhurried."
> "The bar's loud tonight. Good. Harder for anyone to overhear."
These sound-interpretation monologue lines are already in my budget (the "sound interpretation" category in Layer 7: 16-20 lines). If we add actual audio, some of those lines become redundant — the player *hears* the bar is loud instead of being told. But for v0.1, I'll write as if the monologue is doing all the sensory work. Audio can reduce the monologue load later.
**My recommendation:** Defer audio content. Let me carry the atmosphere through text. It's cheaper, faster, and we can always add audio on top. What we can't do is add text *quality* retroactively — so invest in the writing now, add sound later.
---
## Cross-Layer Summary: What I Need to Start Writing
Here's my dependency chain, in order:
| Step | What I need | Who provides it | Ticket |
|------|-------------|-----------------|--------|
| 1 | Station district setting brief | Miri | #189 |
| 2 | Character arc outlines (smuggler + detective) | Paula | #180, #181 |
| 3 | Dual Lens Authoring Guide | Paula | #261 |
| 4 | Tag taxonomy agreement | Gestalt (confirm or modify my proposal) | #168 |
| 5 | NPC profiles (10-axis + triangle positions) | Paula + Miri | #179, #184-186 |
**What I can start NOW, before any dependencies resolve:**
1. **Voice Kit drafts** for smuggler and detective — provisional, based on D-027 descriptions. I'll write three voice options per character and let Paula pick or blend. Gets us moving.
2. **Environmental text templates** — generic diegetic text (safety notices, terminal screens, door labels) that work in any station district. Setting-specific text waits for Miri.
3. **Tag taxonomy proposal** — the table in Layer 4 above. Gestalt validates, we iterate.
4. **Monologue starter set** — 20-30 monologue lines per character covering universal situations (entering a room, being alone, hearing something in fog). These don't depend on specific NPC profiles.
**What I cannot start without dependencies:**
- Template content packs (#190-192) — need NPC profiles and Dual Lens Guide
- NPC-specific dialogue — need NPC profiles
- Setting-specific environmental text — need Miri's district brief
---
## Proposed New Tickets
| Title | Priority | Type | Rationale |
|-------|----------|------|-----------|
| Smuggler voice kit | High | Story | Character voice reference for all smuggler dialogue/monologue. Blocks #190-192 content packs. |
| Detective voice kit | High | Story | Character voice reference for all detective dialogue/monologue. Blocks #190-192 content packs. |
| Monologue starter set (universal) | High | Story | 50-60 monologue lines (both characters) for common situations. Unblocked — can begin immediately. |
| Tag taxonomy specification | High | Story | Define the metadata structure for all authored lines. Must precede content packs. Gestalt validates. |
| Environmental text templates (generic) | Medium | Story | Diegetic text items (signs, terminals, notices) that work across location types. |
| News ticker / unisphere content | Medium | Story | 10-15 headline items for ambient world-building. Needs Miri's setting brief. |
| UI microcopy document | Medium | Story | All non-diegetic interface strings. Needs Araminta's UI spec. |
| NPC voice paragraphs (~15 NPCs) | High | Story | Per-NPC voice guides for triangle and entangled NPCs. Needs Paula's profiles. |
---
## One Honest Concern
The workshop brief says I'm "blocked, waiting on Miri's cultural generation guide." That's true for the *final* content packs. But I've been staring at these decision documents long enough to start building the scaffolding. Voice kits, tag taxonomy, monologue starters, environmental templates — these are all concrete deliverables that move us forward without waiting for the full dependency chain.
The risk isn't that I'll have nothing to do. The risk is that I'll write 200 lines in a voice that doesn't match the character Paula envisions, or a setting that doesn't match the world Miri builds. That's why the Voice Kit approach works — I write provisional options, we converge, then I scale. Write 20 lines right, throw away 10, then write 500 in the validated voice.
Three words for the content plan: **scaffold, validate, scale.**
---
*Mellanie out. Give me the voice, and I'll give you the words.*
docs/workshops/content-gap-analysis_v0_1/round1-miri.md
-443
View File
@@ -1,443 +0,0 @@
# Round 1 — Miri's Worldbuilding Gap Analysis
**Agent:** Miri (Worldbuilder & Setting Designer)
**Date:** 2026-02-11
**Workshop:** v0.1 Content Gap Analysis
---
## Approach
I'm going through all nine layers of the workshop brief from a worldbuilding perspective. My primary deliverable is the station district setting document (Layer 3), but I have contributions across most layers. I'm checking every proposal against what we've established in Round 14 (setting foundation), Round 16 (factions), and the confirmed decisions.
Let me be direct about my role here: the content team needs setting context before they can write a single line. Mellanie can't write a bartender's greeting without knowing what the bar looks like and what the bartender's world is like. Paula can't design a relationship web without knowing the social pressures of the district. Araminta can't set a visual tone without knowing the setting's mood. This document fills those gaps.
---
## Layer 1: Art Direction & Visual Identity
### Setting Context for Visual Identity
I won't wade into Araminta's territory on style guides and palettes, but the setting has strong visual identity implications that should inform Q-003.
**What stations look like in the Settled Reach:**
The Reach's built environments are not uniform. They reflect who built them, when, and for what purpose.
- **Core system stations:** High institutional presence. Clean lines, managed surfaces. Lattice Commission insignia on regulatory kiosks. Meridian access points glowing in alcoves. The aesthetic is "functional prosperity" -- not gleaming chrome utopia, but competent civic infrastructure that works well enough that nobody thinks about it. Think a well-maintained European transit hub, not a cyberpunk dystopia.
- **Mid-Reach stations:** Mixed use, mixed age. Older sections built during early settlement with exposed structural elements and retrofit Meridian hookups. Newer sections with institutional standard finishes. The seams between eras are visible -- different wall materials, different ceiling heights, cable runs added after construction. These stations have character because they have *history*.
- **Frontier stations:** Sparse, improvised, practical. Meridian coverage is spotty. Span gate connections are limited. Structures prioritize function. There's a frontier aesthetic -- things are built to work, repaired rather than replaced, and personalized because there's no institutional standard to enforce.
**v0.1 implication:** Our station district should read as mid-Reach or transitional core -- established enough to have institutions (the detective needs jurisdictional authority), rough enough to have shadows (the smuggler needs operational space). This gives Araminta a visual framework: not pristine, not derelict. Lived-in. Functional but imperfect. The kind of place where a logistics hub, a bar, and a smuggling ring can all exist in the same district without it feeling implausible.
**IP note:** Avoid any visual language that reads as "Blade Runner" (rain, neon, noir) or "Star Trek" (antiseptic corridors, uniforms). The Settled Reach's visual identity should be closer to "working infrastructure" -- think the mundane parts of Alien's Nostromo or the lived-in spaces of The Expanse's Ceres. Ordinary. Functional. The extraordinary is in the technology people carry, not the walls around them.
---
## Layer 2: Narrative Framework & Character Design
### Setting Context for Character Builds
**Smuggler (Logistics Worker)**
Setting note -- a smuggler in the Settled Reach is not a Han Solo archetype. The gate network makes interstellar smuggling a matter of *infrastructure manipulation*, not daring piloting. Smuggling means getting contraband past Lattice Commission checkpoints at gate hubs, through freight scanning at span gate terminals, and past Meridian-logged inventory systems.
A logistics worker is the *perfect* cover because they already have legitimate access to freight handling systems. They know the manifest protocols. They know which cargo containers get scanned and which get waved through. They know the dock schedules. Smuggling in the Reach is a social and bureaucratic crime, not a physical one -- you beat the system by understanding the system better than the people enforcing it.
**What the smuggler's daily life looks like:**
- Morning: Clock in at the logistics hub. Review the day's manifests. Standard freight processing.
- Shift work: Move containers, verify shipments, coordinate with dock crews. Mundane, physical, routine.
- Cracks in the routine: A contact pings on an off-Meridian channel. A container is flagged for special handling. A dock worker who knows the score gives a particular greeting that means "tonight's load is ready."
- After shift: The bar. Decompress. Maintain social ties. Read the room for who's being watched.
The smuggler's lattice is standard-issue Baseline. They avoid enhanced lattice precisely because enhanced lattice means enhanced monitoring. Their perception is limited but their *knowledge* is deep -- they know the dock, the people, the rhythms. They navigate by social intelligence, not technological advantage.
**Detective (Institutional Investigator)**
Setting note -- "detective" in the Settled Reach means a Lattice Commission field investigator or a Concord Assembly-licensed security operative. This matters: the detective has *institutional backing* but also *institutional constraints*. They can request lattice reads (with cause). They can access Meridian security logs (within jurisdiction). They can query Commission databases (subject to classification).
But they can't just kick down doors. The Reach's legal framework is real. Jurisdictional boundaries matter. Evidence gathered illegally is inadmissible and gets investigators sanctioned. The detective's daily frustration is the gap between what they suspect and what they can prove within the rules.
**What the detective's daily life looks like:**
- Morning: Review case file updates on insert. Check for overnight Meridian flags in the district.
- Investigation: Walk the district. Observe. Talk to contacts and informants. Request specific data pulls from Commission systems.
- Institutional overhead: File progress reports. Justify resource expenditures. Navigate the priorities of superiors who care about clearance rates, not justice.
- After shift: The bar -- a different role. Not a colleague unwinding, but an investigator maintaining a social presence, building rapport, looking for tells. Or reviewing notes alone, trying to see the pattern.
The detective's lattice is Augmented -- institutional issue. Enhanced sensory processing, audio analysis capability, pattern recognition support. The insert overlay shows more data: flagged persons of interest, anomalous manifests, case file annotations pinned to locations. The detective sees the same district through an institutional lens that the smuggler's simpler lattice can't provide.
**Divergent starting knowledge (#182) -- setting-grounded specifics:**
| Knowledge domain | Smuggler knows | Detective knows |
|---|---|---|
| Dock operations | Full insider knowledge -- schedules, protocols, which bays are used for what, who works which shift | Official manifests and scheduled arrivals. What's on paper. |
| Criminal network | Names, roles, hierarchy within the ring. Who's reliable, who's sloppy, who's getting nervous. | A case file: "suspected smuggling activity in logistics sector." Sparse intel. |
| Institutional structure | Who the inspectors are, when they visit, which ones are thorough. Practical, defensive knowledge. | Chain of command, jurisdictional authority, access protocols. Operational knowledge. |
| Bar regulars | Drinking buddies, social ties, who to trust. The bar as social haven. | Faces, observed patterns, potential witnesses or informants. The bar as intelligence gathering site. |
| District rhythms | Lived experience -- knows when streets are quiet, which corridors are unmonitored, where the blind spots are. | Patrol schedules, monitored zones, officially mapped infrastructure. |
| Technology | Standard logistics systems, off-Meridian communication (basic Severance techniques), freight handling equipment. | Commission investigative tools, lattice read protocols, Meridian query syntax, surveillance analysis. |
**Divergent relationships (#183) -- access tier implications:**
The same NPC responds differently based on who's asking:
- **Dock workers (smuggling ring):** The smuggler gets insider greetings, warnings, coded updates. The detective gets polite compliance and careful answers.
- **Bar regulars:** The smuggler gets camaraderie, gossip, the real atmosphere. The detective gets friendly-but-guarded small talk from people who've noticed the institutional lattice signature.
- **Station administration:** The smuggler gets bureaucratic indifference. The detective gets professional cooperation and data access.
- **Informants:** The smuggler has contacts in the ring who warn them about pressure. The detective has informants who trade information for favors or immunity.
---
## Layer 3: Station District Setting Document
### Sova Transit District -- v0.1 Setting Brief
**Name:** Sova Transit District (Station Sova, Krenn System)
**Classification:** Mid-Reach logistics hub. Gate-adjacent commercial district.
**Physical Description:**
Sova Transit District occupies a wedge of Station Sova between the primary freight span gate terminal and the residential blocks. It's a working district -- cargo handling, warehousing, customs processing, maintenance, and the service economy that grows up around people who work physical jobs: bars, food vendors, repair shops, a small medical clinic.
The district is roughly 40 years old. The original structure was prefab modular -- standard mid-Reach construction. Since then, it's been modified, extended, patched, and partitioned by successive occupants. The result is a space with layers: clean institutional corridors near the gate terminal transitioning to older, more improvised spaces as you move toward the residential boundary. Ceiling heights vary. Lighting shifts from institutional white near the terminal to warmer, cheaper, more irregular fixtures in the older sections.
The span gate at the district's edge connects to a planetary freight depot. Most of what flows through Sova Transit is bulk cargo -- agricultural products, manufactured goods, machine parts, biological supplies. Nothing glamorous. The kind of freight that keeps a system running.
**Economic Engine:**
Sova's economy is freight. The span gate processes dozens of container transits per day. The logistics hub -- the district's largest employer -- manages scheduling, manifests, container handling, and customs verification. Supporting businesses serve the workforce: the bar, food vendors, a general supply outlet, maintenance services.
The district is not poor, but it's not prosperous either. Workers earn steady wages. Housing is adequate. The infrastructure works. There's a pervasive sense of economic stability that sits just above the line where people start complaining -- comfortable enough to be complacent, tight enough that an extra income source is tempting.
This is the economic pressure that feeds smuggling. A logistics worker makes a decent living. A logistics worker who moves a flagged container to the wrong scanner bay makes a *good* living. The risk calculus is tilted by the fact that the Commission's presence here is intermittent -- Sova is mid-priority. Enough oversight to maintain order. Not enough to catch everything.
**Atmosphere:**
Sova Transit feels like a place where people *work*. Not dramatically. Not glamorously. The way a port town works -- shifts rotate, cargo moves, people know each other because they've been seeing each other every day for years. There are regulars at the bar. There are shift handoff rituals. There are petty grievances that have been simmering for months. There's gossip.
The mood is **quotidian-with-undertow**. Surface level: ordinary life proceeding normally. Underneath: the smuggling ring has been operating for long enough that it's become part of the district's unofficial economy. People know, or suspect, or deliberately don't ask. The ring isn't violent. It isn't chaotic. It's a business that runs alongside the legitimate one, and most people have decided that's fine.
This is the tension the detective walks into: a district that looks normal because the abnormal has been normalized.
**Recent History:**
- **3 months ago:** The district's previous Commission liaison was reassigned (routine rotation, nothing suspicious). The replacement is less experienced and less connected to the district's social network. This created a window -- the ring's operations have expanded during the gap in institutional familiarity.
- **6 weeks ago:** A new freight contract brought increased cargo volume through the span gate. More containers means more opportunity to hide contraband. The ring has been busier.
- **2 weeks ago:** The detective was assigned. Their cover story (or open mandate, depending on build) places them in the district to review logistics compliance. Standard operational audit. Nothing exciting. Except the detective's actual brief includes intelligence suggesting smuggling activity.
- **Present:** The district is in an equilibrium that's about to be disrupted. The ring is comfortable but not complacent. The detective is observing but not yet acting. Ordinary life continues. The contamination (D-027) is the storyteller's disruption of this equilibrium.
**What Makes Sova Interesting:**
1. **Everyone knows everyone.** The district is small enough that faces are familiar. A stranger stands out. The detective's arrival is noticed. Their institutional lattice signature (detectable by anyone paying attention) marks them as *not from here*.
2. **The freight rhythm structures daily life.** Span gate transit schedules create predictable waves of activity -- busy periods when cargo moves, quiet periods between. This rhythm is the skeleton of NPC routines and the smuggler's operational calendar.
3. **The bar is the social heart.** Off-shift, the bar is where information flows. Who's talking to whom, who's drinking alone, who left early -- these are the social signals the player reads.
4. **Institutional presence is real but thin.** There's a Commission terminal, but it's a kiosk, not a station. Security checks happen at the span gate. Surveillance exists but isn't comprehensive. This gives both the smuggler and the detective room to operate -- the smuggler because oversight has gaps, the detective because they can observe without the infrastructure making it obvious.
5. **The architecture has secrets.** Forty years of modifications have created spaces that aren't on official layouts -- maintenance corridors repurposed as storage, sealed sections reopened, gaps between wall layers. The smuggling ring uses these. The detective, if observant, can discover them.
**Environmental Details for Content Teams:**
- **Signage:** Bilingual in Concordat Standard (institutional) and local script (Krenn System vernacular). Official signs are clean, regulation-formatted. Unofficial signs are hand-lettered, idiosyncratic.
- **News ticker:** A Meridian feed display in the bar and logistics hub lobby. Concord Assembly proceedings (boring), freight market prices (relevant), weather alerts for planetary operations (practical), and occasionally a Commission public notice about regulatory compliance (pointed).
- **Ambient sounds:** Cargo handling machinery. Span gate transit hum (a deep, subsonic vibration felt as much as heard). Ventilation. Foot traffic. The clink of a bar in the evening.
- **Smells (monologue material):** Industrial lubricant near the docks. Recycled air everywhere. Cooking from the food vendors. The particular ozone-and-metal scent that lingers near span gate terminals -- the Interstitium leaving its trace on everything that passes through.
- **Temperature:** Slightly warm near the cargo bays (machinery heat), cooler in the corridors (ventilation), comfortable in the bar (climate-controlled, a small luxury).
**Cultural Notes:**
Station Sova is Krenn System -- a mid-Reach system settled roughly 180 years ago. It's old enough to have a distinct local identity but young enough that most residents still think of themselves as part of the broader Reach rather than frontier separatists. The local culture is working-class pragmatic. People value reliability, competence, and minding your own business. They're not hostile to institutions, but they're not deferential either. The Concord Assembly is a distant government. The Commission is a practical reality. The Syndics are the entities you actually deal with -- Sova's freight operations run through a Syndic logistics consortium.
Religion and philosophy are private matters. The Unbound are a known quantity -- a few district residents are Unbound by choice, mostly older workers who came from frontier backgrounds. Nobody makes a fuss about it. The Guardians (Severance) are rumored to operate in the system but are not a visible presence in the district.
**Naming conventions (Krenn System):**
Names in the Krenn System tend toward compact, consonant-heavy constructions. First names: Kael, Voss, Drin, Lera, Torek, Maret. Family names (used formally): Davan, Korr, Sessik, Lintar. Workers often go by first name or nickname on shift. The detective will be addressed by title or full name until trust is established.
*IP note: These names are constructed to feel plausibly human-future without mapping to any existing franchise's naming conventions. They are NOT Commonwealth names (Ozzie, Nigel, Mellanie -- those are conspicuously contemporary English names, which is Hamilton's trademark). Our names suggest cultural drift over centuries of interstellar settlement.*
---
## Layer 4: Content Pipeline & Authoring Format
### Setting-Relevant Tag Taxonomy
Gestalt is the lead on the authoring format, but I can contribute the setting-relevant tag dimensions that should exist in the tag taxonomy:
**Setting-grounded tags for line pools:**
| Tag dimension | Values for v0.1 | Setting justification |
|---|---|---|
| `lattice_tier` | baseline, augmented | Determines what the character can perceive and access. Smuggler = baseline, detective = augmented. |
| `shift_phase` | on_shift, off_shift, transition | Freight rhythm structures social norms. On-shift dialogue is professional; off-shift is personal. |
| `district_familiarity` | local, newcomer | The detective is new. NPCs respond to that. "Haven't seen you around" vs "the usual?" |
| `institutional_context` | civilian, commission, syndic | NPCs adjust register based on perceived institutional affiliation. |
These tags complement the access tiers (D-028 Layer 1) by grounding them in setting logic. An NPC doesn't filter dialogue because of an abstract "trust level" -- they filter because they've noticed the institutional lattice signature, or because they've never seen this person on a shift rotation, or because the district's social code says you don't talk about certain things when Commission personnel are around.
---
## Layer 5: Template Content (3 Social Sites)
### Setting Context for Templates
**Workplace -- Logistics Hub ("The Terminal")**
The logistics hub is the district's economic center. A large open space partitioned into operational zones: manifest processing, container staging, span gate prep, administrative offices, crew locker area.
Setting details:
- **Manifest processing:** Terminals where workers verify cargo contents against Meridian-logged manifests. This is where the smuggling happens -- mismatched containers, doctored manifests, containers routed to the wrong scanner.
- **Container staging:** The physical workspace. Heavy containers moved by small grav-lifts. Noisy, active during shift hours. Workers communicate in a mix of voice and short Meridian pings.
- **Administrative offices:** The supervisor's domain. Official records, shift schedules, performance reviews. The smuggling ring's vulnerability -- if the supervisor is compromised, the ring has institutional cover. If the supervisor is clean, the ring has to work around them.
- **Break room / lockers:** The social space within the workplace. Where off-the-record conversations happen. Where shifts overlap and gossip flows.
Triangle opportunities:
- Supervisor vs. senior worker (authority tension, possible complicity)
- Two workers competing for a promotion (mundane triangle, personal stakes)
- Worker who suspects the ring vs. worker who's in the ring (knowledge asymmetry within the NPC population)
**Social Venue -- Bar ("The Last Shift")**
A mid-grade bar in the district's older section. Not upscale, not a dive. The kind of place where working people go after shift. Good enough that regulars are loyal, plain enough that nobody puts on airs.
Setting details:
- **Interior:** A long bar, scattered tables, a corner booth that's semi-private (key location for discreet conversations -- the player can observe who uses it). Background Meridian music feed. A news ticker display that nobody watches except when something local comes up.
- **Bartender:** A fixture. Knows everyone. Listens more than talks. Observes. The bartender is a potential information source for both characters, but for different reasons -- the smuggler trusts them as a social contact; the detective recognizes them as someone who sees everything.
- **Clientele:** Logistics workers (the largest group), a few station maintenance crew, occasional visitors from other districts, the detective (who becomes a regular by design or necessity).
- **Rhythms:** Quiet during day shifts. Filling up as evening shift ends. Peak in the evening. Late-night regulars are a different crowd -- the ones who don't want to go home, or who are waiting for something.
Triangle opportunities:
- Two regulars with a personal dispute that predates the game (mundane, rich for player observation)
- Bartender caught between regulars they like and a regular they suspect (loyalty vs. honesty)
- Cross-template: a bar regular who also works at the logistics hub, carrying social dynamics between both spaces
**Criminal Template -- Smuggling Ring ("The Arrangement")**
Not a cartel. Not organized crime in the dramatic sense. The Arrangement is an informal network of logistics workers who use their freight access to move contraband -- restricted biologicals, unlicensed lattice components, Severance tech, off-Meridian communication devices, occasionally items with no clear origin (Gyre salvage? Institute-classified materials? Nobody asks).
Setting details:
- **Structure:** Flat hierarchy. One coordinator (off-station, communicates through dead drops and off-Meridian channels). A handful of dock workers who handle the physical cargo. One or two contacts outside the district who arrange receiving. The smuggler player character is mid-level -- experienced enough to be trusted with operations, not senior enough to know the full network.
- **Operations:** Contraband arrives in standard freight containers with doctored manifests. Workers route these containers to scanning bays with known blind spots, or to storage areas where they can be opened and repacked. Timing is critical -- operations happen during specific shift transitions when oversight is thinnest.
- **Security:** The ring's primary defense is normalcy. Nobody does anything dramatic. No late-night break-ins. No suspicious meetings in dark corridors. Everything happens within the flow of legitimate work. If a container is flagged, it's rescheduled. If someone is watched, they go quiet. Patience is the ring's greatest asset.
- **Vulnerability:** The ring has been operating for about two years -- long enough that some participants have become careless. A few workers have been spending beyond their visible income. Social ties within the ring are strong enough that personal conflicts (romantic entanglement, debt, jealousy) could compromise operational security.
Triangle opportunities:
- Ring member whose loyalty is wavering vs. ring member who's all-in (pressure under investigation)
- Ring coordinator (remote) whose demands are escalating vs. local workers who want to keep things small (ambition vs. safety)
- Cross-template: ring member who's a bar regular, whose off-shift behavior is observable by the detective
---
## Layer 6: NPC Profiles & Dialogue
### Setting-Grounded NPC Context
The 10-axis model (D-024) is an ECS schema. What it needs from worldbuilding is the *cultural substrate* that makes those axes feel grounded in Sova Transit District rather than generic.
**What "ordinary life" feels like for an NPC in Sova:**
- You have a job. It pays. It's not exciting. You've been doing some version of it for years.
- You have a lattice (unless you're Unbound). It connects you to the Meridian. You use it the way people use phones -- constantly, casually, unreflectively. You check freight schedules, message friends, look up recipes, watch entertainment feeds, read news you mostly don't care about.
- You know your neighbors. You know the regulars at the bar. You have opinions about the supervisor. You have a thing with someone, or you had a thing with someone, or you're trying to have a thing with someone.
- You are aware of the Commission the way people are aware of the tax authority -- it exists, it has power, you'd prefer not to attract its attention, but you're not living in fear.
- You don't think about the Founders or the Builders or the Interstitium. Gate transit is a commute. The span gate hum is background noise. The existential questions of the Reach are academic. Your questions are: will I make rent, is Kael seeing someone, why did the supervisor change the shift rotation.
This is the substrate that D-029's 30% flat NPCs embody. They are *genuinely ordinary*. Their ordinariness is not a disguise. It is the reality that makes the smuggling ring's deception meaningful and the detective's investigation consequential.
**Cultural tells that NPCs exhibit:**
These are setting-specific behavioral markers that can feed into the tell system (#90):
| Cultural tell | What it signals | Setting basis |
|---|---|---|
| Checking their lattice overlay frequently | Nervous, expecting a message, monitoring something | Meridian-connected behavior, universal |
| Avoiding eye contact with Commission-tagged individuals | Awareness of institutional surveillance, possibly hiding something | Social response to authority, especially in districts with thin Commission presence |
| Using off-Meridian communication (physical notes, verbal codes, dead-drop patterns) | Connected to Severance networks, smuggling operations, or extremely private | Severance counter-surveillance culture filtering into criminal methodology |
| Spending patterns visible through lifestyle | Income doesn't match visible employment | Observable consequences of illicit income |
| Shift timing irregularities | Arriving early, staying late, taking breaks at non-standard times | Freight-rhythm deviation -- meaningful in a schedule-driven workplace |
| Social avoidance of specific individuals | Relationship tension, secret, fear of exposure | Triangle dynamics manifesting as observable behavior |
**NPC naming for v0.1 -- a starter set:**
For Mellanie and Paula to begin writing, they need names. These are setting-consistent for Krenn System:
| Name | Role suggestion | Notes |
|---|---|---|
| Kael Davan | Dock worker, smuggling ring member | The smuggler's closest colleague and the detective's early person of interest |
| Voss | Logistics hub supervisor | Clean or compromised? Either works for v0.1 |
| Lera Sessik | Bartender at The Last Shift | Social hub, observes everything, talks carefully |
| Torek Lintar | Senior dock worker, ring member, getting sloppy | Visible spending, behavioral tells, vulnerability |
| Drin | Station maintenance, bar regular, not ring-connected | Mundane triangle participant, salt-of-the-earth |
| Maret Korr | Freight scheduler, ring-adjacent (knows but isn't active) | The moral gray zone -- aware, complicit by silence, conflicted |
These are suggestions, not mandates. Paula and Mellanie should adapt freely. The naming convention (compact, consonant-heavy, first-name-primary in social contexts) is the consistency requirement.
---
## Layer 7: Monologue & Observation Text
### Setting Context for Character Voice
The monologue is the most important content system for proving the setting works in gameplay. It's where the player *hears* the setting through their character's perspective.
**Smuggler voice -- setting notes:**
The smuggler's monologue should reflect someone embedded in Sova's social fabric. They think in terms of relationships, routines, and risk management. Their observations are practical and socially attuned.
- **Register:** Colloquial, direct, occasionally sardonic. They don't use institutional vocabulary. They don't think in Commission categories. When they see a cargo container, they think about who shipped it and what might be in it, not about regulatory compliance.
- **Knowledge flavor:** The smuggler notices things a logistics worker would notice. Manifest inconsistencies. Dock schedule changes. Which scanner bays are running and which are down for maintenance. These are mundane observations that carry hidden significance.
- **Emotional baseline:** Watchful comfort. This is the smuggler's territory. They're at ease here, but never fully relaxed -- the awareness that one mistake could unravel everything is always present, like a low hum.
Example monologue seeds (not final lines, but tone/content direction for Mellanie):
- Seeing a colleague arrive late: *observation + social reading + implicit risk assessment*
- Noticing the detective in the district: *wariness + social evaluation + threat assessment without acknowledging why they're a threat*
- Routine cargo handling: *competence + casual familiarity + the practiced not-looking at flagged containers*
**Detective voice -- setting notes:**
The detective's monologue should reflect trained analytical habits filtered through institutional perspective. They think in terms of evidence, patterns, and procedure. Their observations are systematic but tinged with the frustration of working within constraints.
- **Register:** More formal internally than the smuggler. Professional vocabulary. Commission frameworks for categorizing observations. But not robotic -- the detective is a person, not an institution, and their private thoughts include doubt, irritation, and occasional dark humor.
- **Knowledge flavor:** The detective notices things an investigator would notice. Behavioral patterns. Access anomalies. Infrastructure gaps. When they see a cargo container, they think about chain of custody, scanning records, and whether the manifest matches the shipping code.
- **Emotional baseline:** Alert curiosity with institutional weariness. They're doing a job. They believe in the job. But they've been doing it long enough to know that the job doesn't always produce justice, and that their institution is imperfect.
**Setting-specific monologue triggers Mellanie should consider:**
| Trigger | Smuggler response flavor | Detective response flavor |
|---|---|---|
| Span gate transit hum changes pitch | "Gate's busy today. Good cover." | "Increased freight volume. Worth checking manifests." |
| Unfamiliar person in the district | "Who's that? Not from any shift I know." | "New face. No district resident tag on file. Note for follow-up." |
| News ticker mentions Commission activity elsewhere | "Good. They're busy somewhere else." | "Regional enforcement stretched thin. Explains the understaffing here." |
| NPC seems nervous | "Something's wrong with Torek. He's been jumpy all week." | "Subject displays stress indicators. Possible concealment behavior." |
| Bar is unusually quiet | "Where is everyone? Something happen on late shift?" | "Reduced foot traffic. Correlated with any scheduled operations?" |
---
## Layer 8: UI Text & Environmental Content
### Setting-Grounded Diegetic Content
The neural lattice overlay (the insert, per D-013) is the player's interface. Everything the player sees on their HUD exists within the fiction as lattice-projected information. This constrains and enriches what appears on screen.
**What the lattice displays (both characters):**
- **Time:** Krenn System standard time. The lattice displays it in the corner of visual awareness -- the way you see a clock on a phone without looking directly at it.
- **Navigation:** Known locations appear as waypoints in the overlay. Fuzzy for general areas, precise for visited locations.
- **Notifications:** Meridian messages, institutional alerts, personal pings. The smuggler gets fewer institutional notifications; the detective gets more.
- **Identity tags:** When looking at a person, the lattice can display publicly available data -- name (if in your contact list or public record), employer (if publicly listed), lattice tier (detectable by proximity scan). The *absence* of this data is itself information -- someone with a masked or spoofed lattice signature stands out.
**What the detective's augmented lattice adds:**
- Case file annotations pinned to locations and persons of interest
- Commission database query results displayed in overlay
- Enhanced audio analysis readouts (sound direction, voice pattern matching)
- Surveillance zone boundaries (where Commission monitoring is active)
**Environmental text for Mellanie and Araminta:**
| Text type | Examples | Setting notes |
|---|---|---|
| Official signage | "Span Gate Terminal C -- Authorized Freight Only," "Lattice Commission -- Report Irregularities," "Emergency Re-embodiment: Deck 7 Med Center" | Institutional, bilingual (Concordat Standard + Krenn vernacular), regulation-formatted |
| Informal signage | "Lera's -- Cold Drinks, Hot Food, No Questions" (the bar), shift schedule boards, hand-lettered notices about lost items or shift swaps | Personality-rich, district-specific, the human layer over institutional structure |
| Terminal screens | Freight manifest summaries, Meridian news feeds, Commission public notices | Functional, data-dense, the kind of information that's everywhere and mostly ignored |
| Meridian news ticker | "Concord Assembly approves Krenn System infrastructure allocation," "Span gate maintenance: Terminal B offline 0200-0400," "Commission advisory: verify lattice firmware before next imprint cycle" | Background texture, occasionally plot-relevant (the detective might notice a news item the smuggler ignores) |
**Onboarding through monologue (D-016 diegetic tutorial):**
Setting note -- the lattice IS the tutorial system. The character's lattice overlay highlights interactive elements naturally. The character's internal monologue provides context naturally. "That terminal might have access logs" is the detective's trained instinct, not a tutorial prompt. "Better check in with Kael before shift" is the smuggler's social awareness, not a quest marker.
The setting makes diegetic onboarding not just possible but *inevitable*. These characters live in this world. They think about it. Their thoughts are the tutorial.
---
## Layer 9: Audio Direction
### Setting-Grounded Sound Identity
I won't prescribe audio design, but the setting has sonic character that should inform whatever direction we take:
**Sova Transit District soundscape:**
- **The span gate hum:** A persistent, low-frequency vibration that defines the district's acoustic identity. Everyone who lives here has learned to ignore it. But it's *always there*. When it stops (maintenance, emergency shutdown), the silence is unsettling. This is the district's heartbeat.
- **Freight operations:** Grav-lift motors, container locks engaging, manifest scanners pinging, dock crew calling to each other. Industrial but not deafening -- modern equipment is efficient. The sound of work happening.
- **Social spaces:** The bar has its own acoustic character -- conversation, glass on surfaces, a Meridian music feed that nobody chose and nobody changes. The logistics hub break room is quieter -- murmured conversations, locker doors.
- **Lattice sounds:** A lattice notification is a sound only the recipient hears -- it's internally generated. For gameplay, this means the player hears their own notifications (monologue, messages, alerts) but NPC lattice sounds are silent to the player. An NPC checking their lattice is a *visual* tell, not an auditory one.
**v0.1 audio recommendation from setting perspective:**
The span gate hum alone would do more for atmosphere than any amount of generic ambient music. If we implement one sound for v0.1, it should be this -- a constant, low rumble that the player eventually stops noticing, until it changes, and then the *absence* or *change* in that sound becomes information. This supports the three-range model (D-018) naturally: the hum is the acoustic baseline that other sounds are measured against.
---
## Setting Gaps & Risks
### What's Still Missing from the Setting for v0.1
1. **Contraband specifics.** What is the ring actually smuggling? This matters for narrative weight. Suggestions:
- **Unlicensed lattice components** -- aftermarket mods that bypass Commission regulation. Not dangerous, but illegal. The moral question: people want better lattice access than they can afford through official channels. Is that wrong?
- **Severance tech** -- counter-surveillance tools. The ring doesn't care about ideology; they move product. But the product has political implications.
- **Off-manifest biologicals** -- medical supplies, growth cultures, possibly re-embodiment materials diverted from Syndic supply chains. The gray market exists because Syndic pricing makes legitimate access prohibitive for working-class citizens.
Recommend: a mix, with unlicensed lattice components as the primary cargo. This creates moral ambiguity -- the smuggler isn't moving weapons or drugs. They're moving *access*. The detective's investigation targets an operation that, from a certain angle, is a public service.
2. **The detective's institutional chain of command.** Who assigned them? What's the stated mandate? What are the political pressures on the investigation? This needs to be defined before Paula designs the detective's narrative arc.
3. **Off-station connections.** The smuggling ring has contacts outside Sova Transit District. Who are they? We don't need to build them for v0.1, but we need enough detail that NPC dialogue can reference them consistently. Suggestion: the ring's coordinator is on-station but in a different district, communicating through dead drops and off-Meridian channels. External contacts are Syndic-adjacent freight handlers at the other end of the span gate route.
4. **The Meridian's local flavor.** What does the Meridian "feel like" in this district? Fast, reliable connection? Intermittent coverage with dead spots? The level of Meridian infrastructure affects everything from NPC behavior to the detective's investigative capability. Suggestion: solid coverage in the logistics hub and bar (institutional areas), degraded coverage in the older district sections (natural dead spots that the ring exploits, that Severance may have expanded).
### IP Originality Checklist
Let me check the v0.1 content against our guardrails:
| Element | Risk assessment |
|---|---|
| Station district setting | **Clear.** Generic enough to be original. No specific franchise owns "space station logistics district." |
| Smuggling ring premise | **Clear.** Smuggling as logistics manipulation rather than daring raids is original enough. Distinct from Star Wars (romantic), The Expanse (violent), or Hamilton (political). |
| Detective as institutional investigator | **Clear.** Commission investigator is setting-specific. Not a cop, not a Blade Runner, not a bounty hunter. |
| Span gate as infrastructure | **Clear.** Our dual-tier gate system is established as original (Round 14 audit). |
| Lattice/Meridian as daily technology | **Clear.** Original terminology, distinct from Hamilton's inserts/unisphere. |
| "The Last Shift" as bar name | **Clear.** Evocative of working-class setting, not franchise-specific. |
| Krenn System naming conventions | **Clear.** Constructed specifically to avoid franchise mapping. |
No IP concerns flagged for the v0.1 station district content.
---
## Summary: What Content Teams Need from Worldbuilding
| Recipient | What I've provided | What's still needed |
|---|---|---|
| **Mellanie** | District atmosphere, NPC naming conventions, character voice notes, monologue trigger examples, environmental text examples | Full NPC cultural profiles once Paula defines the relationship web |
| **Paula** | Smuggler and detective daily life descriptions, institutional context, triangle opportunities per template, setting-grounded access tier logic | Review of whether the detective's institutional framework supports the narrative arc she's designing |
| **Araminta** | Visual identity notes (mid-Reach, lived-in, functional), environmental detail descriptions, signage language | Confirmation that the visual tone aligns with what she's proposing for Q-003 |
| **Gestalt** | Setting-grounded tag taxonomy additions, cultural tell catalog for tell system | Validation that the setting tags integrate cleanly with the line pool format |
| **Ozzie** | The span gate hum as signature atmospheric element, the "stranger stands out" social dynamic | Feedback on whether the district atmosphere creates the "first 30 seconds of presence" he's looking for |
---
## Recommendation for Cultural Generation Guide (#189)
This workshop output should feed directly into the cultural generation guide I'm assigned to write. The Sova Transit District brief above is the first instance -- a concrete example of what the guide will generalize. The guide needs to cover:
1. How to adapt the setting's general principles to specific district types
2. Naming conventions by system origin
3. Daily life rhythms by economic base (freight, service, institutional, frontier)
4. Cultural attitudes toward lattice, Commission, and institutional authority by district character
5. Environmental detail templates (sounds, signs, smells, architectural character)
The Sova brief is the v0.1 slice. The cultural generation guide is the tool for scaling beyond v0.1.
---
*Setting note -- I'm satisfied that the v0.1 district is grounded in our established worldbuilding, original in its surface details, and rich enough to support the content teams' work. The Settled Reach's ordinary life needs to feel genuinely lived-in before the conspiracies have any weight. Sova Transit District is designed to be exactly that: ordinary enough to be real, textured enough to be interesting, and structured enough that the smuggler and detective experience it as fundamentally different places.*
*Miri out.*
docs/workshops/content-gap-analysis_v0_1/round1-ozzie.md
-267
View File
@@ -1,267 +0,0 @@
# Round 1: Ozzie — Player Experience & Wow Factor
## v0.1 Content Gap Analysis Workshop
---
## My Approach
Same as last time. I'm reading each layer and asking: **does this make someone FEEL something?** Content isn't lines in a file. Content is the moment a player stops thinking about the game and starts thinking about the WORLD. I'm going through all 9 layers and answering the questions directed at me, but I'm also flagging anything that smells emotionally flat.
---
## Layer 1: Art Direction & Visual Identity
### Q: Does the vertical slice need visual mood, or is "readable placeholder" sufficient to prove the concept?
**It needs mood. Not polish — MOOD.**
Here's the thing. D-016 says "atmosphere carried by monologue." That's true. The monologue is our primary atmosphere engine. But the monologue doesn't fire until the player is ALREADY in the world. There's a gap — however small — between "I see the screen" and "the first monologue line plays." In that gap, the player forms their first impression from VISUALS ALONE.
If that first impression is "this looks like a spreadsheet," the monologue has to fight upstream. It has to OVERCOME a first impression instead of REINFORCING one.
So here's what I'm asking for — and it's not much:
1. **A constrained color palette that says "space station."** Not beautiful — FUNCTIONAL but atmospheric. Think: muted blues and grays for corridors, warm amber for the bar, cold fluorescent white for the logistics hub. Three palettes, three moods. Even with box-art placeholders, color does 80% of the atmosphere work.
2. **Lighting variation between locations.** The bar is dim. The workplace is bright. The smuggling ring meeting spot is dark except for one harsh light. This isn't art — it's tinting. It can be done with placeholder boxes if the boxes are the RIGHT COLOR.
3. **One signature visual element.** Something the player sees in the first 5 seconds that says "this is a space station, not a warehouse." A viewport showing stars. A holographic sign. A wormhole gate visible in the distance. ONE thing. That's the visual hook while the monologue spools up.
**My answer: "readable placeholder" is NOT sufficient. "Readable placeholder WITH a color palette and one signature element" IS sufficient.** The gap between those two is maybe 2-3 days of Araminta's time and it's the difference between "this is a prototype" and "this is a WORLD I'm stepping into."
D-014 says "functional boxes with labels." Fine. But those boxes should be tinted correctly and that one signature element should exist. That's my line.
---
## Layer 2: Narrative Framework & Character Design
No questions directly at me, but I'm weighing in anyway because this is where the emotional foundation gets laid.
The Dual Lens Guide (#261) is the most important pre-content document in the entire project. I said this in the last workshop and I'll say it again: **the smuggler and detective must have fundamentally different EMOTIONAL RELATIONSHIPS to the same world.** Not just different access tiers. Different FEELINGS.
The smuggler walks into the logistics hub and feels... what? Boredom? Comfort? Low-level anxiety about their side gig? The detective walks in and feels... suspicion? Professional focus? The excitement of being undercover in a new environment?
The Dual Lens Guide needs to define these emotional registers. Not just "who knows what" — "who FEELS what, about the same things."
**One specific ask for Paula:** The guide should include 3-5 "emotional divergence moments" — specific situations where the two characters would have opposite emotional reactions. Examples:
- Seeing a cargo manifest (smuggler: routine / detective: evidence)
- An NPC being friendly (smuggler: genuine warmth / detective: "is this person a target or an asset?")
- A door that's usually locked being open (smuggler: "huh, that's weird" / detective: "THAT'S MY IN")
These divergence moments are what Mellanie needs to write voice-consistent monologue. They're the emotional atoms of the dual-lens system.
---
## Layer 3: Station District Setting
### Q: What environmental details make a player feel present in the first 30 seconds?
**Five things. That's all you need. Five things and you're THERE.**
1. **Sound first.** Before you even process the visuals, you should hear the station. A low hum. Distant chatter. The hiss of an airlock cycling somewhere. I know audio is Layer 9 and deferred — I'll fight about that there. But if we HAVE audio, it should land before the first monologue line.
2. **Movement.** NPCs should already be moving when the game starts. Not standing in their spawn positions waiting for the player. You walk out of your hab unit and there's someone walking past. Going somewhere. Living their life. The world was here BEFORE you pressed play. That's the single most important presence signal.
3. **The news ticker.** Miri, Paula — put a news ticker or announcement board in the player's starting location. Not a lore dump. Three lines. "Dock 7 maintenance: scheduled closure 14:00-18:00." "Community social: bar district, Thursday evening." "Security reminder: report unregistered cargo to station management." Those three lines tell you: there are docks, there's a community, there's security, and someone's worried about unregistered cargo. THAT'S worldbuilding in 30 words. And for the smuggler, that last line hits DIFFERENT.
4. **Something out the window.** I said it in Layer 1 and I'll say it again. The player needs to see that they're IN SPACE. On a STATION. A viewport, a transparent section of floor over a docking bay, a holographic display showing the local system. One visual anchor that says "you are very far from home and this metal tube is keeping you alive." Scale creates awe. Awe creates presence.
5. **A named NPC within 10 seconds.** Not a tutorial guide. Just someone your character KNOWS. They walk past, and your monologue says their name. "There goes Tomas. Early shift again." Suddenly you're a person who KNOWS PEOPLE. You're not a camera floating through a level. You're someone with a LIFE here.
**That's the recipe: sound + movement + environmental text + spatial context + a named face.** If Miri's station district document establishes these five elements, the setting will feel present regardless of art quality.
---
## Layer 4: Content Pipeline & Authoring Format
No questions directed at me, but I care about one thing here: **the line previewer (#193).**
The line previewer isn't just a QA tool. It's how we test whether content FEELS right. Can the smuggler's monologue play in sequence and sound like a person thinking? Does the detective's voice feel distinct? Do the NPC voice kits sound like different people?
I can't gut-check content I can't experience. Nobody can. The previewer needs to exist before the content packs are "done," or we'll ship content that reads well in a YAML file and sounds dead in the game.
**My ask to Gestalt:** When you define the line pool format, include a "preview sequence" tag or mechanism. Something that lets you say "play these 5 lines in order as if the character just walked into the bar." That's how Mellanie tests her work, and it's how I evaluate the emotional delivery.
---
## Layer 5: Template Content (3 Social Sites)
No questions directly at me but I'm going to SCREAM about something.
D-029 says 30/50/20 entanglement split. ~15 NPCs. That means:
- ~4-5 truly flat NPCs (routine + greeting only)
- ~7-8 mundane triangle NPCs (social drama, no conspiracy)
- ~3 entangled with intrigue
Here's what keeps me up at night: **those 4-5 flat NPCs need to NOT feel flat.** The player doesn't know who's entangled. The moment a player can look at an NPC and think "oh, that one's just background decoration" — the investigation collapses. Every NPC needs to SEEM like they could matter. The flat ones just... turn out not to.
What makes a flat NPC feel non-flat:
- A name and a visible routine (they go PLACES)
- One memorable trait (always eating, always late, always complaining about the same thing)
- One line that SOUNDS like it could be important but isn't ("I swear the cargo schedules are getting weirder" — nope, they're just bad at their job)
Mellanie — those flat NPC voice kits are LOAD-BEARING for the investigation mechanic. They're the noise floor. If the noise is obviously noise, the signal is too easy to find.
---
## Layer 6: NPC Profiles & Dialogue
### Q: Which NPC should the player remember after 30 minutes? What makes them memorable — a line, a routine, a contradiction?
**A contradiction. Every time, it's the contradiction.**
Here's the NPC I want the player to remember. Let's call them THE FRIEND.
THE FRIEND is the NPC your character has the strongest pre-existing relationship with. For the smuggler, it's a work buddy — someone you share shifts with, someone you eat lunch with, someone who covers for you when you're late. For the detective, it's a contact — someone who feeds you information, someone you trust, someone who stuck their neck out for you once.
THE FRIEND is memorable because of a CONTRADICTION the player discovers through observation:
- The smuggler's work buddy is kind, reliable, always has your back. But you catch them one evening in a part of the station they have no reason to be in. Your monologue: "What's Jax doing near the restricted docks?" You can ask them about it. They deflect. THEY LIE TO YOU. And now every warm interaction is CONTAMINATED with doubt.
- The detective's contact gives you solid intel. Reliable. Professional. But you notice they always have an excuse to leave when a certain other NPC shows up. Your monologue: "That's the third time Ana's left when Riks walked in." What's the connection? Is your contact avoiding someone? WHY?
**What makes THE FRIEND memorable is not a great line or an interesting routine — it's the SHIFT.** They start as background comfort. Then ONE observation changes everything. Now they're a mystery wrapped in a relationship. The player can't stop thinking about them because the player LIKED them and now doesn't know if they should.
**This is why D-027's success criterion #3 is genius: "player names an NPC they felt conflicted about."** THE FRIEND is the NPC designed to deliver that criterion. One per character. Authored specifically for this purpose.
**My recommendations for Paula and Mellanie:**
1. Each character needs ONE clear "friend" NPC designed for emotional contradiction
2. THE FRIEND must be present in the first 10 minutes — relationship established EARLY
3. THE FRIEND's contradiction must be discoverable through OBSERVATION, not told through dialogue
4. The contradiction should activate during or shortly after contamination — it's the emotional bridge between daily-life and investigation
For the remaining NPCs: one memorable thing each is enough. The bartender who remembers everyone's order. The security guard who's always reading something on their insert. The maintenance worker who hums. Small, human details. Not every NPC needs to be a mystery. Most should be PEOPLE. That's what makes the mysteries stand out.
---
## Layer 7: Monologue & Observation Text
### Q: When does the first monologue surprise the player? What's the moment where they think "wait, my character noticed something I didn't"?
**It happens the first time the character has an OPINION the player doesn't share yet.**
Here's the sequence:
1. The player walks into the bar. They see NPCs sitting around. Some talking, some alone. It's just... a bar.
2. The monologue fires: "Riks is at his usual table. But he's not drinking. He's watching the door."
3. The player thinks: "I didn't notice that. My character KNOWS this person well enough to know that not-drinking-and-watching-the-door is unusual."
4. NOW the player looks at Riks differently. They didn't decide to investigate Riks. The CHARACTER flagged Riks. The monologue created attention.
THAT'S the surprise. The character is a better observer than the player. The character has context the player doesn't. The monologue bridges that gap — and in doing so, it makes the player feel like they're WEARING someone else's eyes.
For the **smuggler**, the first surprise should be social instinct: "Kira's being extra friendly to the new dock supervisor. She wants something." The smuggler reads social dynamics like a trader reads prices. The player didn't see manipulation — the CHARACTER did.
For the **detective**, the first surprise should be professional pattern-matching: "Three people at adjacent tables, none of them talking to each other, all arrived within two minutes. That's not a coincidence." The detective sees formations. Tactical arrangements. The player saw people sitting at a bar.
**When should this happen?** Within the first 15 minutes. Before contamination. During the DAILY LIFE phase. Because the surprise isn't about the conspiracy — it's about discovering that your character is a PERSON with perceptions and biases and skills the player doesn't have. The conspiracy amplifies this. The daily life INTRODUCES it.
**Content implications for Mellanie:**
- Each character needs 10-15 "observational insight" monologue lines for the pre-contamination phase
- These lines should reference SPECIFIC NPCs and their known patterns
- The insights should be CORRECT — the character's observations should check out if the player investigates
- Occasionally, the character should be WRONG — confident assessment, incorrect conclusion. "She's probably just tired." (She wasn't tired.)
**The monologue surprise is the game's SIGNATURE MECHANIC in content form.** It's not infrastructure. It's not a pipeline question. It's Mellanie writing lines that make the player feel like someone else is thinking through their eyes. If we get this right, it doesn't matter that the art is placeholder. If we get this wrong, no amount of polish saves us.
---
## Layer 8: UI Text & Environmental Content
No questions directly at me, but I want to reinforce something from my Layer 3 response.
**The news ticker / announcement board is the cheapest wow-per-word content in the entire game.**
A news ticker running in the bar or the workplace that updates throughout the day is:
- Worldbuilding (what's happening on this station?)
- Atmosphere (is this a happy place? A tense place?)
- Foreshadowing (a headline that seems mundane but connects to the conspiracy)
- Character divergence (the smuggler reads "increased cargo inspections" and sweats; the detective reads it and thinks "about time")
For v0.1, we need maybe 20-30 ticker lines. Rotating. Some mundane ("Stellar weather: nominal"), some social ("Community garden expansion approved"), some loaded ("Security advisory: unscheduled vessel departures under review"). That's an afternoon of Mellanie's time and it makes the station feel ALIVE every second it's on screen.
**The diegetic insert (D-013) needs flavor text too.** When you check your neural implant map, the POI labels shouldn't just say "Bar" and "Workplace." They should say what your CHARACTER would label them. The smuggler's insert says "The Rusty Airlock" (the bar's name, they're a regular). The detective's insert says "Licensed establishment — district 7" (official designation, they just transferred here). SAME PLACE. Different label. Different character. That's asymmetric information in the UI layer and it costs NOTHING.
---
## Layer 9: Audio Direction
### Q: Does placeholder audio kill the atmosphere, or is silence acceptable for a concept proof?
**Silence is DEATH.**
I know that sounds dramatic. Hear me out — no pun intended.
Top-down view. Placeholder art. Small sprites moving around a tiled map. Without audio, this is a BOARDGAME. A pretty one, maybe. But a boardgame. The monologue is TEXT. The dialogue is TEXT. The fog of perception is a visual effect. Everything the player experiences through their ears is... nothing.
And the thing about silence is — you HEAR it. Not consciously, but your brain notices. Silence says "this isn't a place." Sound says "this is a place." The difference is primal.
**BUT — I'm not asking for a full audio suite.** Here's my minimum viable audio for v0.1:
1. **Station ambient loop.** One track. Low hum, distant machinery, occasional muffled announcements. This runs ALWAYS. It's the "you're on a space station" signal. Think: the Nostromo ambience from Alien. It can be royalty-free or generated. One file. Huge impact.
2. **Location variation.** Three variants of the ambient: workplace (louder machinery, cargo sounds), bar (muted music, glass clinks, conversation murmur), corridors (echoing footsteps, that lonely hum). These can be the same base track with different overlay layers. Three files.
3. **Footsteps.** Your character's footsteps. Metal floor. Consistent. This alone makes you feel PRESENT in the space. One sound, two variations (walk/run). The single highest bang-for-buck audio asset in any game.
4. **One UI sound.** The monologue appearance. A soft chime, a subtle click, something that says "your character is thinking." This trains the player to notice monologue, which is our primary content delivery mechanism. Without it, text just appears and might be missed.
That's 6-8 audio files total. Maybe a day of work for someone with access to a sound library. Maybe two days if we're generating them. And the difference between those 6 files and silence is the difference between "interesting tech demo" and "I want to keep playing."
**So my answer: silence is NOT acceptable for a concept proof. But we don't need much.** A station hum, three location variants, footsteps, and a monologue chime. That's the audio floor. Below that, the atmosphere collapses regardless of how good the monologue writing is.
**Should we defer audio entirely?** NO. We should defer SOPHISTICATED audio (the three-range model, directional sound, sound-through-walls). Those are milestone features. But ambient atmosphere and basic feedback sounds should be in Sprint 2 or early Sprint 3 at the latest. Before the first content playtest. Because if we playtest in silence, we'll get feedback about the writing and systems, but we won't learn whether the ATMOSPHERE works. And atmosphere is what turns systems into experiences.
---
## Cross-Layer: The Emotional Content Map
Stepping back from individual layers. Here's how I see the content gaps mapping to PLAYER EMOTIONS:
### The Emotional Journey (30-minute session)
| Minute | Emotion | Content That Delivers It | Status |
|--------|---------|-------------------------|--------|
| 0-1 | Curiosity / Awe | Visual mood + ambient audio + signature visual element | GAP |
| 1-3 | Grounding | Opening monologue + named NPC + news ticker | GAP |
| 3-10 | Comfort / Routine | Daily task + workplace/bar dialogue + flat NPCs being human | GAP (content packs not started) |
| 10-20 | Attachment | Repeated interactions + THE FRIEND + gossip + small social dramas | GAP (dialogue layers 3-4) |
| 20-25 | Unease | First observational surprise + monologue flagging deviations | GAP (no observation content) |
| 25-30 | Dread | Routine breaks + THE FRIEND's contradiction + things going wrong | GAP (contamination content) |
| 30+ | Investigation | Full conspiracy activation | GAP (storyteller activation) |
**Every single emotional beat is a content gap.** The SYSTEMS to deliver them exist or are planned. The CONTENT to fill them does not.
That's what this workshop is about. And that table is the priority order for content creation.
---
## My Top 5 Content Priorities (Ordered)
1. **Character emotional profiles** (for Dual Lens Guide) — Before anyone writes a LINE, we need to know how each character FEELS about their world. This is Paula's document but I want Mellanie in the room. No voice kit can be written without it.
2. **THE FRIEND NPC design** (one per character) — The single NPC designed to deliver D-027 success criterion #3. Full profile, full voice kit, full contradiction arc. This is the emotional centerpiece of v0.1.
3. **Opening monologue + first 5 minutes content** — The first 20 lines each character thinks. The diegetic first objective. The emotional register of "another day" before everything goes wrong. This is what the player's first impression is made of.
4. **News ticker / environmental text** — 20-30 lines of station life. Cheapest content, highest presence-per-word ratio. Worldbuilds while the player walks around.
5. **Flat NPC voice kits** — The noise floor. The 4-5 NPCs who AREN'T important but need to FEEL like they might be. One memorable trait each. 10-15 lines each. These make or break the investigation mechanic.
---
## The Bottom Line (Again)
Last workshop I said: "We need to design the moments, not just the systems."
This workshop I'm saying: **"We need to write the moments, not just design them."**
The systems are being built. The architecture is solid. The decisions are right. But somewhere between D-028 (tagged line pools with four relational layers) and an actual player sitting at their desk going "oh shit, did Jax just lie to my face?" — there's a canyon. And that canyon is filled with unwritten monologue lines, undefined character voices, and content packs that are tickets with no words in them yet.
This workshop fills the canyon. Let's go.
---
*Written by Ozzie. Still from the gut.*
docs/workshops/content-gap-analysis_v0_1/round1-paula.md
-500
View File
@@ -1,500 +0,0 @@
# 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.
docs/workshops/content-gap-analysis_v0_1/round2-araminta.md
-568
View File
@@ -1,568 +0,0 @@
# Round 2 Workshop Response: Araminta (Visual Design Synthesis)
**Agent:** Araminta (Visual Designer)
**Date:** 2026-02-11
**Round:** 2 (Synthesis)
**Inputs:** All 6 Round 1 outputs + project lead direction
---
## Project Lead Directives Acknowledged
1. **Color = relationship to player: APPROVED.** This is now the confirmed v0.1 color model. No more hedging.
2. **Audio in v0.1 scope (6-8 files).** Visual sound indicators are complementary, not the sole mechanism. My indicator design can be subtler now -- it confirms audio, not replaces it.
3. **THE FRIEND -- one per character, production-level complex.** Visual implications addressed in section 6.
4. **Wiki structure with full taxonomy -- non-negotiable.** Visual asset taxonomy included in section 7.
5. **Sova Transit District / Krenn System is concrete.** All visual proposals now grounded in Miri's Sova setting.
---
## What I Learned from Round 1 (All Six Responses)
Three things crystallized:
1. **Text carries the game.** Mellanie, Paula, and Miri all confirmed what D-014 and D-016 implied: at v0.1 fidelity, written content does 80%+ of atmosphere and information delivery. My visual design must *support* text, not compete with it. Every pixel I spec is either making text more readable, making game state more scannable, or getting out of the way.
2. **The insert is character-specific.** Paula proposed that the smuggler's and detective's inserts show different information categories -- social map vs. analytical overlay. Miri confirmed this with setting logic: the smuggler has a baseline lattice (less data), the detective has an augmented lattice (more data, institutional feeds). This changes my insert wireframe from "one HUD, two characters" to "one HUD framework, two information profiles."
3. **Spatial design is load-bearing.** Paula's relationship web (15 NPCs, 7 triangles, 6 bridge connections) and Gestalt's spatial requirements (chokepoints, public/private gradients, observation positions) make spatial layouts the most important visual deliverable. Room shapes serve sightline gameplay. Triangle dynamics need specific observation positions. These inputs make my spatial layouts functional, not decorative.
---
## 1. Missing Tickets for Visual/Art Direction Work
After reading all Round 1 outputs and cross-referencing the ticket system, here are the visual tickets that should exist:
### Critical (blocks other work)
| Ticket Title | Priority | Depends On | Blocks | Rationale |
|---|---|---|---|---|
| **v0.1 Visual Grammar Document** | Critical | Workshop conclusion | All visual implementation, spatial layouts, entity rendering | Root dependency. Codifies color palette, entity sizing, label rules, UI layers, fog rendering. One page. Everything visual hangs off this. |
| **Entity Color System Spec -- Relationship-to-Player Mapping** | Critical | Visual Grammar | NPC rendering, fog rendering, client renderer | The approved color model needs a formal spec: which relationship states map to which colors, how transitions animate, edge cases (NPC relationship changes mid-observation). |
### High Priority
| Ticket Title | Priority | Depends On | Blocks | Rationale |
|---|---|---|---|---|
| **Spatial Layout: Sova Logistics Hub ("The Terminal")** | High | Visual Grammar, Miri's setting | Content pack #190, sightline implementation | Tile-level floor plan with sightline analysis. Miri's Round 1 gives me the zones. I can now design concretely. |
| **Spatial Layout: Sova Bar ("The Last Shift")** | High | Visual Grammar, Miri's setting | Content pack #191, sightline implementation | Irregular layout with privacy pockets, corner booth as key location. |
| **Spatial Layout: Sova Transition Corridors + Smuggling Spaces** | High | Visual Grammar, Miri's setting | Content pack #192, sightline implementation | Maintenance corridors, repurposed storage, hidden spaces within the 40-year-old station structure. |
| **Insert/HUD Wireframe and Spec** | High | Visual Grammar | Insert implementation, UI rendering | The lattice overlay design. Includes dual-character variants (smuggler's social map vs. detective's case file overlay). |
| **Monologue Display System Visual Spec** | High | Visual Grammar | Monologue renderer, text system | Typography, positioning, fade animation, stacking rules, character voice differentiation. Mellanie's 900+ lines need a rendering pipeline. |
| **Text Display Hierarchy Spec** | High | Visual Grammar | All text rendering | How dialogue, monologue, observation, overheard conversation, and environmental text each render distinctly. Four pipelines, four visual treatments. |
| **Sound Indicator Visual Design** | High | Visual Grammar, audio scope | Medium-range sound system | Fog-edge pulse indicators. Complementary to audio, not replacement. |
| **THE FRIEND -- Visual Treatment Spec** | High | NPC profiles (Paula), Visual Grammar | THE FRIEND NPC rendering | Production-level visual differentiation for one NPC per character. See section 6. |
### Medium Priority
| Ticket Title | Priority | Depends On | Blocks | Rationale |
|---|---|---|---|---|
| **Visual Asset Taxonomy (Wiki Structure)** | Medium | Visual Grammar | Future asset pipeline, wiki | Directory structure, naming conventions, category definitions. Future-ready per project lead directive. |
| **Fog Rendering Visual Spec** | Medium | Visual Grammar | Fog system implementation | Four-state rendering (visible, fog-edge, hidden, remembered). |
| **Environmental Text Visual Standards** | Medium | Visual Grammar, Miri's setting | Environmental text rendering | How signage, terminals, news tickers render in-world. Bilingual treatment per Miri. |
| **Signature Visual Element -- Span Gate Glow** | Medium | Miri's setting | First-impression visual | Ozzie's "one thing that says space station." See section 2. |
**Total new tickets proposed: 13.** 2 critical, 8 high, 4 medium. This is the complete visual work scope for v0.1.
---
## 2. Refined v0.1 Art Direction Proposal
Round 1 proposed "readable information design, atmosphere through text and spatial composition." Round 2 refines this with Miri's Sova setting and Ozzie's mood requirements.
### The Visual Identity of Sova Transit District
Miri's setting brief tells me exactly what this place looks like: mid-Reach, 40 years old, prefab modular construction modified over decades. Institutional corridors near the gate terminal transitioning to older, warmer spaces toward the residential boundary. "Functional prosperity" -- not dystopian, not utopian. A working port.
**This translates to three visual zones with distinct palettes:**
#### Zone 1: Gate Terminal / Logistics Hub ("The Terminal")
The institutional face of Sova. Clean, regulated, functional.
| Element | Color | Hex | Rationale |
|---|---|---|---|
| Floor | Cool grey-navy | `#1e1e32` | Institutional flooring. Blue-tinted. |
| Walls | Cool slate | `#2e2e48` | Clean, maintained surfaces. |
| Lighting tint | Cool white | `#d8e0f0` at 15% overlay | Fluorescent institutional lighting. Bright, slightly harsh. |
| Equipment/furniture | Darker grey | `#222233` | Grav-lifts, terminals, workstations. Functional. |
| Restricted areas | Slightly darker floor | `#1a1a2e` | Subtle but perceptible. Private spaces are darker. |
#### Zone 2: Bar District / "The Last Shift"
The social heart. Warmer, older construction, personality.
| Element | Color | Hex | Rationale |
|---|---|---|---|
| Floor | Warm dark | `#221e28` | Older materials. Warmer tones. |
| Walls | Warm grey | `#342e38` | Aged, repaired, character. |
| Lighting tint | Amber-warm | `#e8c070` at 10% overlay | Cheaper, warmer fixtures. Inviting. |
| Bar counter/furniture | Dark warm tone | `#2a2018` | Solid, well-worn. |
| Corner booth | Slightly darker | `#1e1a18` | The semi-private space. Visually recessed. |
#### Zone 3: Corridors / Maintenance / Smuggling Spaces
The in-between. Older construction, poorer lighting, architectural secrets.
| Element | Color | Hex | Rationale |
|---|---|---|---|
| Floor | Neutral dark | `#18161e` | Transitional. Neither warm nor cool. |
| Walls | Varied | Mixed old/new sections | 40 years of modifications visible. Different wall tones = different construction eras. |
| Lighting tint | Dim, irregular | `#a0a0b0` at 8% overlay | Maintenance-level lighting. Gaps and shadows. |
| Hidden spaces | Near-black | `#12121a` | Sealed sections reopened, gaps between walls. Barely lit. |
**Transition gradient:** Walking from the logistics hub to the bar, the palette warms. Walking into a maintenance corridor, it goes flat and dark. No art needed -- just tile color variation. The player may not consciously notice but will *feel* the shift.
### Confirmed Entity Color Palette (Relationship-to-Player)
Project lead approved. Locked.
| Relationship State | Color | Hex | When |
|---|---|---|---|
| **Unknown/Neutral** | Cool teal | `#4a9ebb` | Default for NPCs the character hasn't assessed. |
| **Known/Friendly** | Soft green | `#6bc9a6` | People the character knows and trusts. |
| **Person of Interest** | Warm amber | `#e8c547` | Monologue or case file has flagged something. |
| **Hostile/Dangerous** | Muted red | `#d45d5d` | Character KNOWS there's danger. Subjective, not omniscient. |
| **Static objects** | Muted grey | `#8b8ba0` | Furniture, equipment, environmental elements. |
| **Player character** | Bright marker | `#e0e8ff` (detective) / `#e8e0d0` (smuggler) | Subtle warmth/coolness difference per character. |
**Key principle unchanged:** Red means danger TO YOUR CHARACTER, not danger in the abstract. The detective might see that same NPC as amber (flagged in case file) while the smuggler sees green (trusted colleague). Same NPC, different color, because asymmetric information drives the palette.
### Ozzie's Signature Element: The Span Gate Glow
Ozzie asked for "one thing that says space station." Miri's setting gives the answer: the span gate.
The span gate terminal sits at the district's edge. Its effects should be visible from the player's starting position.
**Proposal: The span gate glow.** A subtle, rhythmic light source visible through a viewport or structural gap near the starting area. Not dramatic sci-fi blue-plasma. A warm, deep amber-orange luminance that pulses with transit cycles. Miri says the span gate produces "a deep, subsonic vibration" -- visually, this translates to a gentle, rhythmic luminance shift. When the confirmed audio system plays the span gate hum, the visual pulse synchronizes.
Implementation cost: one animated light source with a viewport tile. It grounds the player in "space station near an active gate" within the first 5 seconds. It's also mechanically useful later -- changes in glow pattern (maintenance shutdown, increased traffic) become visual information.
### Character-Specific Insert Overlays
Paula and Miri both established the narrative logic: the smuggler has a baseline lattice, the detective has augmented. Ozzie wants the insert labels to reflect character perspective.
| Insert Element | Smuggler | Detective |
|---|---|---|
| **Tint** | `#3d7aaf` at 30% (consumer-grade) | `#3d7aaf` at 40% (institutional-grade, slightly denser) |
| **POI markers** | Social contacts as dots (color = relationship state), favorite spots as circles | Persons of interest as amber diamonds, evidence locations as squares, surveillance zones as faint boundary lines |
| **Labels** | Casual: "The Last Shift", "Kael's usual spot" | Institutional: "Licensed establishment - District 7", "POI: K. Davan" |
| **Notifications** | Informal: "Msg from Kael", "Drop point updated" | Commission format: "Case file update: Subject Davan", "Commission advisory" |
| **Grid overlay** | None (consumer-grade, no extras) | Faint 1-pixel grid at 3% opacity (analytical feel) |
**Implementation:** One insert system with a `lattice_profile` parameter. Stig builds one framework, not two. Character selection loads the appropriate profile.
---
## 3. Placeholder Art Pipeline Priorities
The question isn't "what art do we need" -- it's "in what order do we build the visual layers so each step is playable?"
### Four Phases
**Phase 1: Structural (blocks gameplay testing)**
- Tile-level floor plans for all three social sites
- Wall/door/furniture rectangles with correct proportions
- Fog rendering (visible/fog-edge/hidden/remembered)
- Entity rectangles with relationship colors
- Basic labels (NPC names, room names)
**Phase 2: Information (blocks content testing)**
- Insert/HUD overlay (minimap, POI markers, time display)
- Monologue text display (positioned, styled, animated)
- Dialogue panel (NPC name header, text area)
- Sound indicators at fog edge (pulse icons, complementary to audio)
- Environmental text (signs, terminals)
- News ticker display
**Phase 3: Atmosphere (blocks experience testing)**
- Zone-specific color palettes applied (three zones above)
- Lighting variation between locations
- Span gate signature visual element
- Character-specific insert variants
- Remembered-state fog (desaturated ghost)
- THE FRIEND visual treatment (color transition)
**Phase 4: Polish (pre-release quality)**
- Sprite replacements for entity rectangles (if v0.1 scope allows)
- Animated transitions (door opening, NPC movement smoothing)
- Particle effects (span gate glow, fog-edge shimmer)
- Visual tells for NPC behavioral states
- Full environmental detail (wall texture variation, construction-era differences)
**For v0.1 vertical slice: Phases 1-3 are required. Phase 4 is stretch.**
### Total Art Asset Count for v0.1
Approximately **zero image files.** Everything is procedural: colored rectangles, styled text, shader overlays. The "art pipeline" is a color configuration file plus spatial layout data.
This is deliberate. Zero image files means no asset loading latency, no sprite inconsistency, and no art-replacement migration when we move to real sprites. Stig and Dudley can build the full renderer without waiting on visual assets from me. My primary output is **documented specifications**, not image files.
---
## 4. Dependencies Between Visual Work and Content Work
### Content Teams Need from Me:
| Content Team | What They Need | My Deliverable | Urgency |
|---|---|---|---|
| **Mellanie** | Display constraints -- character limits per text type, line count, wrap rules | Text Display Hierarchy Spec + Monologue Spec | High -- she's writing to unknown constraints |
| **Mellanie** | Environmental text visual format | Environmental Text Visual Standards | Medium -- can write provisionally |
| **Paula** | Spatial layouts to validate sightline assumptions | Spatial Layouts (3 sites) | High -- her NPC positions must work spatially |
| **Miri** | Visual tone confirmation | Visual Grammar | Medium -- confirmation, not blocker |
### I Need from Content Teams:
| From | What I Need | Status |
|---|---|---|
| **Miri** | Station district setting brief | **DONE** (Round 1 Sova brief) |
| **Paula** | NPC relationship web | **DONE** (Round 1, 15 NPCs, 7 triangles) |
| **Paula** | NPC routine phases (who is where by time of day) | Pending -- needed for spatial layout NPC anchors |
| **Gestalt** | Display context tag confirmation | Pending -- Mellanie proposed, Gestalt validates |
**Key finding: I'm mostly unblocked.** The Visual Grammar has no upstream dependencies. Spatial layouts can begin with Miri's zones + Paula's relationship web. Insert wireframe has all its inputs.
### The Critical Circular Dependency
Spatial layouts need Paula's relationship web -> Content packs need spatial layouts -> Paula's relationship web needs content understanding.
**Resolution: Parallel drafting with one sync pass.**
1. I draft spatial layouts from Miri's zones + Gestalt's spatial requirements
2. Paula reviews layouts against her relationship web -- flags adjustments
3. I adjust. One round. Layouts lock for content authoring.
---
## 5. How Spatial Layout Serves Paula's Relationship Web and Gestalt's Access Tier Model
This is the most important synthesis. Paula's triangles and Gestalt's access tiers are abstract. My spatial layouts make them concrete.
### Principle: Space Creates Social Information
Physical arrangement determines:
- Who can observe whom (sightlines = observation opportunities)
- Who can talk privately (enclosed spaces = trust-gated conversations)
- Who crosses paths (chokepoints = accidental encounters)
- Who can be followed (corridors = approach vectors)
### Logistics Hub -- Serving the Relationship Web
Paula's hub NPCs: Shift Supervisor (A), Workers (B, C), Dock Inspector (D), Maintenance Tech (E).
Paula's hub triangles: New Hire Problem (B-C-A), Inspection Squeeze (A-D-K).
Gestalt's requirements: publicly accessible area with hidden back section, restricted-access area, chokepoint.
```
+------------------------------------------------------------------+
| SPAN GATE TERMINAL (visible glow) |
+------------------------------------------------------------------+
| |
| [Scanner Bay 1] [Scanner Bay 2] [Scanner Bay 3] |
| |
| +---------+ +---------+ +---------+ |
| | staging | | staging | | staging | |
| +---------+ +---------+ +---------+ |
| |
| === MAIN CORRIDOR (chokepoint - everyone passes through) ====== |
| |
| +----------------+ +----------+ +-----+ +--------+ |
| | Manifest | | Break | | WC | | Lockers| |
| | Processing | | Room | | | | | |
| | (terminals) | | (social) | +-----+ +--------+ |
| +----------------+ +----------+ |
| |
| +-------------+ +-------------------+ |
| | Supervisor | | Restricted Storage| <-- smuggling ops |
| | Office | | (key access) | |
| | (window) | | | |
| +-------------+ +-------------------+ |
+------------------------------------------------------------------+
```
**How this serves the triangles:**
- **New Hire Problem (B-C-A):** C works in manifest processing (open, visible). B observes C from staging. A watches from the office window (sightline into main floor, sound blocked). C's curiosity about restricted storage is observable -- other NPCs see C lingering near the locked door.
- **Inspection Squeeze (A-D-K):** D visits scanner bays. A watches from office window. The main corridor is the chokepoint -- D must pass through it, and the break room has a sightline to corridor traffic.
**How this serves access tiers:**
- **Public areas** (scanner bays, main corridor, manifest processing): Wide, well-lit, high visibility. Detective observes freely. `public` + `authority` dialogue.
- **Semi-private areas** (break room, lockers): Partially enclosed. Smuggler gets `insider` dialogue. Detective draws attention if lingering.
- **Private areas** (supervisor office, restricted storage): Enclosed, door access, blocked sightlines. The smuggler knows what's behind the restricted door. The detective can only observe from outside.
### Bar -- Serving the Relationship Web
Paula's bar NPCs: Bar Owner (F), Security Officer (G), Teacher/Family Person (H), Bartender (I), Drifter (J).
Paula's bar triangles: Card Game Debt (D-G-F), Worried Partner (H-B-F).
```
+----------------------------------------------------+
| |
| +---+ +---+ +---+ +-----------+ |
| | T | | T | | T | | Corner | |
| +---+ +---+ +---+ | Booth | <-- key |
| | (semi- | observation
| +==========================| private) | position |
| | BAR COUNTER +-----------+ |
| | (high visibility) |
| +========================== |
| |
| +---+ +---+ +---+ |
| | T | | T | | T | |
| +---+ +---+ +---+ |
| |
| +------------------+ +---------+ |
| | News Ticker | | Back | <-- alley exit |
| | Display | | Room | |
| +------------------+ +---------+ |
| |
| [ENTRANCE] |
+----------------------------------------------------+
```
**How this serves the triangles:**
- **Card Game Debt (D-G-F):** D and G at a table visible from the bar counter. F observes from behind the bar. The corner booth covers the card table -- observation position for both characters.
- **Worried Partner (H-B-F):** H sits at the bar counter (visible). Where B sits signals relationship state -- with H (normal) or at a separate table (avoidance, noteworthy). F observes from behind the bar.
- **The corner booth** is the most loaded piece of furniture in the game. From here: the bar counter (H, regulars), the card table area (D, G), the entrance (who comes and goes), and the back room door are all visible. For the smuggler: where ring contacts meet. For the detective: the surveillance perch. Same seat, different purpose.
### Smuggling Spaces -- Serving the Access Tier Model
NOT a separate building. The ring operates in: restricted storage (hub), maintenance corridors, dead-drop locations in transition areas.
**Design principle: The ring is invisible.** Meeting points have legitimate mundane purposes. Their ring function is only apparent if you know what to look for. The smuggler navigates naturally. The detective must DISCOVER these spaces -- following an NPC, finding corridors not on official maps, noticing recently-used maintenance hatches.
**The spatial layout encodes information asymmetry in the map itself.** Same physical space, different player understanding of it.
---
## 6. Visual Treatment of THE FRIEND
Ozzie's Round 1 makes the case: THE FRIEND is designed to deliver D-027 success criterion #3 ("player names an NPC they felt conflicted about"). Project lead confirms: one per character, production-level complex.
### Should THE FRIEND Look Different?
**Yes, but through EARNED visual detail, not special status marking.**
### The Visual Progression
**Phase 1: Before Contradiction (minutes 1-15)**
THE FRIEND is visually identical to other friendly NPCs. Same green rectangle, same label format. What makes them distinct is NOT rendering:
- **Label detail:** Their name shows from the start (not "Worker" or "?"). The character KNOWS this person.
- **Monologue frequency:** The character's thoughts reference THE FRIEND more often. Text creates attachment, not visuals.
- **Spatial proximity:** THE FRIEND's routine keeps them near the player. They're visually present more often.
This matters: THE FRIEND should NOT look special at first. If they look different, the player knows to pay attention. The point is natural attachment, then the contradiction hits.
**Phase 2: After Contradiction Discovery (mid-session)**
When the player observes THE FRIEND's contradictory behavior:
1. **Color shift:** Entity color transitions from green (`#6bc9a6`) to amber (`#e8c547`). Smooth 0.5s fade. The relationship-to-player color system working as designed -- the character now has QUESTIONS.
2. **Observation marker:** The eye icon appears alongside the monologue about the contradiction. Same icon used for all observations, but applied to someone the player trusted.
**The moment the rectangle shifts from green to amber IS THE FRIEND's visual moment.** It should be the first relationship color change in the session. If it's the FIRST color shift the player sees, they'll feel it -- because until now, colors have been static. The system proving it's dynamic ON a character the player cares about is the visual punch.
**Phase 3: Production-Level Treatment (planned, partially v0.1)**
When we move beyond boxes-with-labels:
- **Unique sprite.** Not dramatically different -- recognizably distinct. Where flat NPCs share sprite templates, THE FRIEND gets unique proportions, posture, one identifying accessory.
- **Behavioral animation states.** Minimum two: their "normal" state and their "hiding something" state.
- **Memory echo.** In the "remembered" fog state, THE FRIEND's ghost lingers longer. Their desaturated outline fades last. Subliminal signal that the character can't stop thinking about them.
### v0.1 Production Budget for THE FRIEND
- **Entity rendering:** Identical to other NPCs (colored rectangle, name label). No special rendering.
- **Color behavior:** Standard relationship color system, but designed so this NPC is MORE LIKELY to transition mid-session. The color spec must handle smooth transitions.
- **Writing investment:** The visual spec for THE FRIEND is actually a writing spec -- ensure Mellanie has enough monologue lines to create attachment before the contradiction.
**The visual treatment of THE FRIEND is mostly about what we DON'T do.** We don't mark them as special. We let writing and routines create attachment. Then the standard color-shift delivers the punch.
---
## 7. Visual Asset Taxonomy (Wiki Structure)
Project lead: full taxonomy, future-ready, non-negotiable.
```
assets/
visual/
style-guide/
v0.1-visual-grammar.md # Root document
color-palette.md # All color definitions + usage rules
entity-rendering-rules.md # Sizing, labels, color mapping
fog-rendering-spec.md # Four-state visibility
typography.md # Font choices, text hierarchy
ui/
insert/
hud-wireframe.md # Insert overlay layout
smuggler-variant.md # Smuggler lattice profile
detective-variant.md # Detective lattice profile
poi-markers.md # POI icon definitions
monologue/
display-spec.md # Typography, animation, stacking
character-variants.md # Per-character text style
dialogue/
panel-spec.md # Dialogue UI layout
name-header-rules.md # NPC name + relationship color
environmental-text/
signage-styles.md # In-world text rendering
terminal-screens.md # Interactive screen format
news-ticker.md # Ticker display format
sound-indicators/
fog-edge-pulse.md # Visual sound indicator spec
close-range.md # LOS sound indicators
insert-alerts.md # Long-range notification style
spatial/
sova-logistics-hub/
floor-plan.md # Tile-level layout
sightline-analysis.md # Observation positions, blind spots
sound-propagation.md # Thin/thick walls, bleed zones
npc-positions.md # Routine phase positions
approach-vectors.md # Player entry + first impressions
sova-bar/
floor-plan.md
sightline-analysis.md
sound-propagation.md
npc-positions.md
approach-vectors.md
sova-smuggling-spaces/
floor-plan.md
sightline-analysis.md
sound-propagation.md
npc-positions.md
approach-vectors.md
corridors-transitions/
district-connectivity.md # How zones connect
chokepoint-analysis.md # Cross-template encounter points
entities/
npc/
relationship-color-spec.md # Color mapping + transitions
label-rules.md # Name/role/unknown display rules
the-friend-treatment.md # Production-level NPC visual spec
flat-npc-templates.md # Shared visual templates
objects/
furniture.md # Sizing, color, interaction markers
doors.md # Open/closed/locked states
terminals.md # Interactive object visual
environment/
span-gate-glow.md # Signature visual element
lighting-zones.md # Per-zone lighting spec
construction-eras.md # Wall/floor variation by age
sprites/ # FUTURE: when we move beyond boxes
characters/
objects/
tiles/
effects/
```
Every folder exists even if files are stubs. New locations slot into `spatial/` with the same structure. Sprites slot into `sprites/` following entity definitions already established. This scales to full game without reorganization.
---
## 8. Complete Dependency Chain (All Teams)
```
PHASE 0: WORKSHOP OUTPUT (we are here)
|
v
PHASE 1: FOUNDATION (parallel, no cross-dependencies)
|
|-- [Araminta] v0.1 Visual Grammar Document
|-- [Miri] Finalize Sova Setting Brief (Round 1 is nearly complete)
|-- [Paula] Dual Lens Authoring Guide (draft)
|
v
PHASE 2: SPATIAL + CHARACTER (mostly parallel, one sync point)
|
|-- [Araminta] Spatial layouts (3 sites)
| depends on: Visual Grammar + Miri's setting
| |
| +--- SYNC POINT: Paula reviews against relationship web
| | (one feedback round, then layouts lock)
|
|-- [Araminta] Insert/HUD wireframe (parallel)
|-- [Araminta] Monologue display spec (parallel)
|-- [Araminta] Sound indicator design (parallel)
|-- [Paula] Relationship web + NPC profiles
|-- [Mellanie] Voice kits + monologue starters
|
v
PHASE 3: CONTENT PRODUCTION
|
|-- [Mellanie] Content packs (#190-192)
| depends on: Spatial layouts (locked), NPC profiles, format
|-- [Araminta] Environmental text visual placement
|-- [Araminta] THE FRIEND visual spec (needs Paula's NPC profiles)
|
v
PHASE 4: INTEGRATION
|
|-- Specs handed to Stig (UI) + Dudley (server)
|-- Araminta reviews implementation against specs
```
**The Visual Grammar Document is my Phase 1 deliverable. Zero dependencies. I can start today.**
---
## 9. Answering Specific Round 1 Asks
### For Mellanie: "Tell me the visual fidelity target"
**Maximum text density.** The colored rectangles communicate game state (who's friendly, where's the fog). They don't communicate mood, personality, or social dynamics. All that burden falls on text.
Concrete display constraints (pending full spec):
- Monologue: max ~80 characters per line (60% screen width at default font), max 3 visible lines
- Dialogue: max ~100 characters per line in dialogue panel
- Environmental text: 8-40 characters for labels, up to 200 for terminal screens
- News ticker: single scrolling line, ~60 character visible window
### For Paula: "Should the insert carry character-specific visual language?"
**Yes. One parameterized system, two profiles.** See insert section above. The `lattice_profile` loads POI categories, notification format, data density, and annotation style per character. No extra development cost -- just data.
### For Ozzie: "Does it need mood?"
**It needs three things: a color palette, lighting variation, and one signature element.** That's the span gate glow, the zone palettes, and the three-zone lighting model. Not polish -- MOOD through restraint. The gap between "readable prototype" and "world I'm stepping into" is these three things.
### For Gestalt: Spatial requirements
**Confirmed.** Each spatial layout includes: one publicly accessible area with hidden back section, one area with smuggler-natural access, one chokepoint where cross-template encounters happen. The main corridor in the logistics hub is the primary chokepoint. The bar entrance + counter serve as social observation chokepoint.
---
## 10. Immediate Next Steps
1. **Write v0.1 Visual Grammar Document.** One page. Color palette (locked), entity sizing, label conventions, UI layers, fog spec. No dependencies. Can start today.
2. **Draft spatial layouts for Sova's three social sites.** Based on Miri's zones + Paula's relationship web + Gestalt's spatial requirements. Submit to Paula for review.
3. **Design insert/HUD wireframe.** Two variants. Based on Paula's access tier model + Miri's lattice descriptions.
4. **Write monologue display spec.** Typography, positioning, animation, stacking. Gives Mellanie her display constraints.
5. **Design sound indicators.** Fog-edge pulse icons complementary to 6-8 audio files.
6. **Spec THE FRIEND's visual treatment.** After Paula's NPC profiles exist.
---
## Summary Position
Round 1: "The entity color system is the single most important visual DECISION."
Round 2: **"The spatial layouts are the single most important visual DELIVERABLE."**
The color system is confirmed and locked. Good. Now: does the physical space support the relationship web, the access tier model, the observation gameplay, and the dual-lens experience? If sightlines are wrong, no dialogue tagging saves the investigation. If chokepoints don't exist, cross-template encounters don't happen. If the bar doesn't have that corner booth, Paula's card game triangle has nowhere to play out.
The spatial layouts are where abstract systems become concrete games. Where Paula's 7 triangles become observable social dynamics. Where Gestalt's access tiers become physical spaces. Where Mellanie's 900 lines have rooms to live in.
I can start the Visual Grammar today. Spatial layouts begin as soon as the workshop concludes.
Keep it clean, we can layer detail later.
---
*Written by Araminta. Round 2 synthesis complete.*
docs/workshops/content-gap-analysis_v0_1/round2-gestalt.md
-591
View File
@@ -1,591 +0,0 @@
# Round 2: Gestalt (Systems Design) - Synthesis
**Workshop:** v0.1 Content Gap Analysis
**Date:** 2026-02-11
**Scope:** Mechanical convergence across all Round 1 outputs + Jeroen's Round 2 directives
---
## 0. Directives Acknowledged
Before I get into synthesis, let me confirm the constraints from Jeroen's Round 2 direction. These are locked. No further debate:
| Directive | Status | Mechanical Implication |
|-----------|--------|----------------------|
| Separate monologue pools per character | **Confirmed, non-negotiable** | Two parallel content trees. `character` is a hard partition tag, not a filter. |
| Color = relationship to player | **Approved** | Entity color is a client-side derivation from `RelationshipState` component + knowledge state. Not an NPC property. |
| Audio included in v0.1 | **Confirmed** | 6-8 AI-generated files. Sound event system architecture must support this. Visual fallback for everything beyond those files. |
| One NPC per character = THE FRIEND | **Confirmed** | Two production-level NPCs. Full pipeline depth test. All systems exercised on these two. |
| Wiki structure for taxonomy | **Non-negotiable** | Miri handling. Tag taxonomy I define here must integrate with wiki structure. |
| Line pool format (YAML) | **Needs validation** | Mellanie and Paula must sign off. That's what this section does. |
---
## 1. Converged Line Pool Format
*Let me break down what this actually means mechanically.* Three people proposed tag schemas in Round 1. Let me reconcile them.
### Schema Comparison
| Tag | Gestalt R1 | Mellanie R1 | Paula R1 (implied) | Converged |
|-----|-----------|-------------|-------------------|-----------|
| `id` | `{template}_{type}_{###}` | `{template}-{role}-{situation}-{##}` | Not specified | **Keep Gestalt format** — machine-parseable, stable |
| `text` | string | string | string | **Keep** |
| `role` / `speaker` | `role` (enum per template) | `speaker` (enum per template) | Implied by NPC profile | **`role`** — the template role, not the NPC name. NPC assignment is runtime. |
| `character` | N/A (on monologue only) | `character` (smuggler/detective/any) | Implied | **`character`** — but ONLY on monologue lines. Dialogue lines are character-agnostic; the access tier handles filtering. |
| `access` | list\<enum\> | single enum | Per-line, hard filter | **list\<enum\>** — a line can be eligible for multiple access tiers |
| `trust` | enum (surface/real/secret) | enum (same) | Three disclosure tiers, progressive | **Aligned. No change.** |
| `situation` | list\<enum\> | list\<enum\> | Relationship history + context | **list\<enum\>** — see converged situation taxonomy below |
| `topic` | list\<enum\> | single enum | Mood + topic for Layer 4 | **list\<enum\>** — lines can cover multiple topics |
| `mood` | list\<enum\> | single enum | Mood for weighted selection | **list\<enum\>** |
| `location` | N/A (implicit from file) | enum | N/A | **Drop from line-level.** Location is implicit from the file's directory. Adding it per-line is redundant and an error source. |
| `type` | N/A (implicit from file) | `type` (dialogue/monologue/env/ticker) | N/A | **Drop from line-level.** Content type is implicit from file name (dialogue.yaml vs monologue.yaml). |
| `tags` | list\<string\> freeform | N/A | N/A | **Keep** — escape hatch for author intent that doesn't fit taxonomy |
| `dual_lens` | map (per-character notes) | N/A | Critical for authoring | **Keep** — authoring-only, not consumed by engine |
| `notes` | string | N/A | N/A | **Keep** — authoring-only |
| `trigger` | On monologue only | N/A | N/A | **Keep for monologue** — the observation event that fires the line |
| `prerequisite` | On monologue only | N/A | N/A | **Keep for monologue** — knowledge state gate |
### Converged Tag Taxonomy — FINAL (pending Mellanie/Paula sign-off)
**Structural tags (required on every dialogue line):**
| Tag | Type | Values | Maps to D-028 Layer |
|-----|------|--------|---------------------|
| `id` | string | `{template}_{d\|m\|e}_{###}` | N/A (indexing) |
| `text` | string | The authored line | N/A (content) |
| `role` | enum | Template-defined roles | N/A (speaker assignment) |
| `access` | list\<enum\> | `public`, `insider`, `authority`, `peer`, `hostile` | **Layer 1** (hard filter) |
| `trust` | enum | `surface`, `real`, `secret` | **Layer 3** (hard filter) |
| `situation` | list\<enum\> | See taxonomy below | **Layer 2** (context filter) |
**Selection tags (recommended, fallback to defaults if empty):**
| Tag | Type | Values | Maps to D-028 Layer | Default |
|-----|------|--------|---------------------|---------|
| `topic` | list\<enum\> | See taxonomy below | **Layer 4** (weighted selection) | `[general]` |
| `mood` | list\<enum\> | See taxonomy below | **Layer 4** (weighted selection) | `[neutral]` |
| `tags` | list\<string\> | Freeform | N/A (author use) | `[]` |
**Authoring-only tags (not consumed by engine):**
| Tag | Type | Purpose |
|-----|------|---------|
| `dual_lens` | map | Per-character interpretation notes |
| `notes` | string | Author intent, dependencies, context |
**Monologue-specific tags (in addition to above):**
| Tag | Type | Values | Purpose |
|-----|------|--------|---------|
| `character` | enum | `smuggler`, `detective` | **Hard partition.** Separate pools per Jeroen's directive. |
| `trigger` | enum | See trigger taxonomy below | Observation event that fires this line |
| `prerequisite` | map or null | Knowledge state conditions | Gate: line only eligible if character knows X |
### Alignment with Paula's Four Layers
This is the critical validation. Does the converged schema express all four D-028 layers?
| D-028 Layer | How It's Expressed | Tag(s) | Filter Type |
|-------------|-------------------|--------|-------------|
| **Layer 1: Access tier** | `access` tag on every line. Engine checks player character's current access tier at the NPC's social site. | `access` | **Hard filter.** Line invisible if access doesn't match. |
| **Layer 2: Relationship history** | `situation` tag + engine-tracked interaction state. Engine maintains per-NPC counters (interaction_count, last_interaction_time, notable_events). These counters activate/deactivate situation eligibility. `first_meeting` is true once. `repeated_visit` activates after 3+ visits. `greeted_before` is tracked by engine, not tagged per-line. | `situation` + engine state | **Context filter.** Narrows eligible pool based on relationship progression. |
| **Layer 3: Trust-gated gossip** | `trust` tag on every line. Engine tracks trust progression per NPC (starts at surface, can reach real/secret through repeated positive interactions). | `trust` | **Hard filter.** Line invisible if current trust level is below line's trust tier. |
| **Layer 4: Unprompted disclosure** | `topic` + `mood` tags. Engine selects from eligible lines (post-Layer 1/2/3 filtering) weighted by match between NPC's current mood state and line's mood tag, and between NPC's current concern topics and line's topic tag. | `topic` + `mood` + engine state | **Weighted selection.** Soft ranking, not hard filter. Neutral mood always available as fallback. |
**Verdict: The converged schema fully expresses all four layers.** Layers 1 and 3 are hard filters (binary tag match). Layer 2 is engine-state-to-situation mapping. Layer 4 is weighted selection across two tag dimensions.
Paula's concern about `greeted_before:true` — this is NOT a per-line tag. It's engine state. The engine tracks whether these characters have met before and activates the `first_meeting` or `repeated_visit` situation accordingly. The content author doesn't tag individual lines with interaction history — they tag situations, and the engine decides which situations are active.
### Key Changes from My Round 1 Proposal
1. **Dropped `location` from line-level tags** — location is directory-level. This removes a redundancy Mellanie flagged.
2. **Dropped `type` from line-level tags** — content type is file-level. This reduces Mellanie's 8 tags to 6 structural + 2 selection = 8 total, but 2 fewer per-line.
3. **Added `character` as monologue-only hard partition** — confirms Jeroen's directive mechanically.
4. **Clarified that `access` is list, not single** — a line can be eligible for both `insider` and `peer`.
5. **Made `topic` and `mood` list types** — a line can cover multiple topics and be appropriate for multiple moods.
### Situation Taxonomy v0.1 (Converged)
Merged from my Round 1 list + Mellanie's proposal:
| Situation | Description | Activation |
|-----------|-------------|------------|
| `greeting` | First interaction this game-day | Engine: no interaction logged today |
| `first_meeting` | Characters have never interacted | Engine: interaction_count == 0 |
| `routine` | Normal daily activity | Engine: NPC in scheduled routine state |
| `morning` / `afternoon` / `evening` / `night` | Day phase (D-031) | Engine: current SimulationTime phase |
| `repeated_visit` | Player has visited this NPC 3+ times | Engine: interaction_count >= 3 |
| `interrogation` | Player is asking pointed questions | Engine: dialogue topic escalation detected |
| `witnessed_secret` | Player has observed something they shouldn't | Engine: KnowledgeInventory contains secret-tagged fact about this NPC |
| `idle` | NPC is between scheduled activities | Engine: NPC routine state = idle |
| `working` | NPC is performing job routine | Engine: NPC routine state = job |
| `social` | NPC is in social activity (bar, break) | Engine: NPC routine state = social |
| `confrontation` | Triangle tension has escalated | Engine: triangle pressure threshold exceeded |
| `post_event` | Responding to a recent simulation event | Engine: event log contains recent entry for this NPC |
| `absence_noticed` | An expected NPC is missing | Engine: NPC not in expected location during expected time |
**13 situations for v0.1.** Mellanie's `gossip` and `observed_anomaly` situations are covered by `social` + topic filtering and `post_event` respectively. I'm not adding them as separate situations because they're better expressed as topic + mood combinations.
### Topic Taxonomy v0.1
| Topic | Description |
|-------|-------------|
| `work` | Job-related: tasks, schedules, complaints |
| `social` | Relationships, personal life, family |
| `cargo` | Freight, manifests, shipments — setting-specific |
| `money` | Finances, costs, spending |
| `rumors` | Gossip, hearsay, speculation |
| `identity` | Who someone is, where they're from, what they do |
| `deflection` | Avoiding a topic, changing subject |
| `complaint` | Grievances, frustrations |
| `general` | Weather, food, neutral small talk |
**9 topics for v0.1.** Mellanie's `crime` topic is deliberately excluded — NPCs don't think of what they do as "crime." It's `cargo` or `money` from their perspective. The dual-lens interpretation is what makes those topics crime-adjacent for the detective.
### Mood Taxonomy v0.1
| Mood | Description |
|------|-------------|
| `neutral` | Default state. Calm, unremarkable. |
| `happy` | Positive, upbeat, satisfied |
| `tired` | Low energy, going through motions |
| `annoyed` | Irritated, short-tempered |
| `nervous` | Anxious, fidgety, checking surroundings |
| `defensive` | Guarded, deflecting, walls up |
| `friendly` | Warm, open, welcoming |
| `cautious` | Careful, measuring words |
**8 moods for v0.1.** Mellanie's `tense`, `relaxed`, and `suspicious` map to `nervous`, `happy`/`neutral`, and `cautious` respectively. I'm consolidating to prevent near-duplicate moods that make authoring harder without adding selection granularity.
### Monologue Trigger Taxonomy v0.1
Unchanged from Round 1. 9 triggers:
| Trigger | Description |
|---------|-------------|
| `enter_location` | Player enters a new area |
| `observe_npc` | Player sees NPC doing something notable |
| `hear_sound` | Sound event from fog edge |
| `observe_anomaly` | NPC deviates from known routine |
| `post_conversation` | After dialogue ends |
| `discover_evidence` | Player examines an informational object |
| `witness_interaction` | Player sees two NPCs interacting |
| `time_idle` | Player hasn't acted for a while |
| `return_visit` | Player returns to a previously visited area |
---
## 2. Mellanie's Tag Proposal vs. Mine — Convergence
Mellanie proposed 8 tags. I proposed a more granular set. Here's where we landed:
| Mellanie's Tag | My Tag | Resolution |
|---------------|--------|------------|
| `character` | `character` (monologue only) | **Aligned.** Monologue-only, hard partition. Not on dialogue lines. |
| `access` | `access` | **Aligned.** I upgraded to list\<enum\>; she had single. List is correct. |
| `trust` | `trust` | **Aligned.** Identical. |
| `location` | (directory-level) | **Dropped from per-line.** Directory structure handles this. Mellanie agreed provisional format is fine. |
| `situation` | `situation` | **Aligned.** Her values are a subset of mine. Using the full 13-situation taxonomy. |
| `mood` | `mood` | **Aligned.** Consolidated to 8 moods. |
| `topic` | `topic` | **Aligned.** Expanded to 9 topics. |
| `type` | (file-level) | **Dropped from per-line.** File naming convention handles this. |
**Net result: 6 per-line structural tags + 3 per-line selection/freeform tags = 9 tags per dialogue line.** For monologue lines: +3 monologue-specific tags = 12 tags per monologue line.
**Mellanie's "tag smoke test" request is smart.** Before she writes 165 lines for the workplace, she writes 20, tags them, and I validate the filtering behavior. This should happen as the first line previewer test case.
---
## 3. THE FRIEND: Production-Level NPC Specification
*Okay, let me map this to mechanics.* Jeroen says THE FRIEND is a production-level complex NPC — one per character, full pipeline depth test. Ozzie defined the emotional design in Round 1. Let me define what "production-level" means for the ECS and content pipeline.
### What "Production-Level" Means Mechanically
THE FRIEND exercises every system we're building. It's the NPC that proves the pipeline works end-to-end:
| System | What THE FRIEND Tests | Minimum Requirement |
|--------|----------------------|---------------------|
| **10-axis model (D-024)** | All 10 axes populated with meaningful values that change during play | Axes must shift in response to simulation events |
| **Access tiers (D-028 L1)** | THE FRIEND has different access tiers per character | Smuggler: `insider`+`peer`. Detective: varies (starts `public`, can reach `peer`) |
| **Relationship history (D-028 L2)** | Interaction count tracked, situation progression works | `first_meeting` -> `greeting` -> `repeated_visit` must trigger different lines |
| **Trust progression (D-028 L3)** | Trust level advances through positive interactions | Surface -> Real progression visible in dialogue depth change |
| **Unprompted disclosure (D-028 L4)** | THE FRIEND volunteers information when mood + topic align | At least 3 unprompted lines that fire based on NPC mood state |
| **Tell system** | Observable behavioral markers for internal state | All 5 tell categories must be demonstrable on THE FRIEND |
| **Routine system** | Predictable daily schedule with deviations | Morning/afternoon/evening locations defined. At least 1 deviation event |
| **Triangle membership** | Belongs to at least 1 triangle | Triangle pressure must affect THE FRIEND's behavior observably |
| **Contradiction arc (Ozzie)** | Discoverable through observation, not dialogue | The contradiction must emerge from routine deviation + tell, then be confirmed/complicated by dialogue |
| **Monologue integration** | Player character comments on THE FRIEND specifically | Named monologue lines referencing THE FRIEND's behavior, not generic role observations |
| **Dual-lens divergence** | Same NPC, fundamentally different relationship per character | THE FRIEND is a different person emotionally to the smuggler vs. detective |
### THE FRIEND: ECS Component Profile
Each FRIEND NPC needs these components at minimum:
```
Entity: THE_FRIEND_smuggler / THE_FRIEND_detective
Components:
- NpcIdentity { name, role, home_template, reference_templates[] }
- Want { current_want, intensity, blocked_by }
- Secret { content, known_by[], exposure_risk }
- Relationships[3] { target_entity, valence, trust_level, interaction_count, last_interaction }
- ToleranceThreshold { current_value, max_value, triggers[] }
- DailyRoutine { schedule: Map<DayPhase, Location>, deviations[] }
- InformationInventory { known_facts[], rumors[], secrets_held[] }
- Contentment { value, trend, causes[] }
- PersonalityTraits { trait_a, trait_b, trait_c }
- TellState { active_tells: Map<TellCategory, Intensity> }
- SkillSet { skills[], combat_trained: bool }
- AccessTierMap { Map<Entity, AccessTier> } // per-observer access
- TriangleMembership { triangle_ids[], role_in_triangle: Map<TriangleId, Role> }
- MoodState { current_mood, trend, causes[] }
```
### THE FRIEND: Content Requirements
**Per FRIEND NPC, Mellanie needs to author:**
| Content Type | Volume | Notes |
|-------------|--------|-------|
| Dialogue lines (all access tiers) | 25-35 lines | Must cover public, insider, peer, hostile. More lines than any other NPC. |
| Trust-gated dialogue (surface/real/secret) | 15-20 lines | Including at least 3 `secret`-tier lines that reveal the contradiction |
| Unprompted disclosure lines | 5-8 lines | Mood-triggered, topic-relevant. THE FRIEND initiates conversation. |
| Monologue lines (smuggler reacting to FRIEND) | 10-15 lines | Named references. "There goes Kael." Not "That dock worker." |
| Monologue lines (detective reacting to FRIEND) | 10-15 lines | Different framing. Analytical, not personal. |
| Tell observation monologue | 5-8 lines per character | "Kael's tapping his foot again." / "Subject displays stress indicators." |
| Contradiction discovery monologue | 3-5 lines per character | The moment the player realizes THE FRIEND isn't what they seemed |
**Total per FRIEND: ~70-100 authored lines** (including both character perspectives). This is roughly half the content budget of an entire template's dialogue pool — for one NPC. That's the cost of production-level. It's worth it because this NPC carries D-027 success criterion #3.
### THE FRIEND: Mapping to Paula's NPCs
Looking at Paula's Round 1 relationship web:
| Character | THE FRIEND candidate | Why |
|-----------|---------------------|-----|
| **Smuggler** | **NPC-B** (Logistics Worker 1 / Kael Davan) | Smuggler's closest colleague. Ring member. Works together daily. Trust + shared risk = deepest pre-existing bond. Contradiction: Kael is reliable to the smuggler, but is cracking under pressure / making mistakes / possibly considering turning. |
| **Detective** | **NPC-D** (Dock Inspector) or **NPC-G** (Security Officer) | The detective needs a contact who becomes a relationship. NPC-D has the gambling debt (exploitable, sympathetic). NPC-G has institutional proximity (a peer the detective trusts professionally). **Recommendation: NPC-D** — the gambling debt creates the contradiction (seems corrupt, might just be desperate) and connects to Triangle B (Card Game Debt). |
Paula should confirm these assignments in her Round 2. The FRIEND NPCs are the first profiles she should write at Tier 1 depth.
---
## 4. Missing Tickets for Systems/Mechanical Work
I've cross-referenced all Round 1 outputs against the existing ticket pool. Here are the systems tickets that should exist but don't (or need upgrading):
### New Tickets Needed
| Title | Type | Priority | Rationale | Depends On |
|-------|------|----------|-----------|------------|
| **Dialogue selection pipeline implementation** | Feature | Critical | The 4-layer filtering engine: access -> situation -> trust -> weighted(mood, topic). This is the core runtime system that makes content playable. Nothing in the existing tickets covers the actual selection algorithm. | Line pool format (this document), NPC component architecture |
| **Monologue trigger system** | Feature | Critical | Engine component that fires monologue events based on observation triggers (enter_location, observe_npc, etc.). Must select from character-specific pool, apply prerequisite gates, track variety (no repeats). | Perception system (#124), Character knowledge state |
| **NPC mood state machine** | Feature | High | NPCs need a mood component that changes based on simulation events (triangle pressure, time of day, recent interactions). Mood drives Layer 4 selection + tell system. | 10-axis NPC components |
| **Trust progression system** | Feature | High | Engine tracks trust level per player-NPC pair. Progresses through surface -> real -> secret based on interaction quality and frequency. Must be observable (player can sense trust improving). | Relationship tracking, dialogue system |
| **Interaction tracking component** | Feature | High | Per-NPC-pair counter: interaction_count, last_interaction_time, notable_events log. Drives Layer 2 situation activation. | NPC component architecture |
| **Tell state derivation system** | Feature | Medium | System that reads NPC axis values (Secret + Tolerance = nervous, Contentment low = frustrated, etc.) and outputs observable tell states consumed by monologue trigger system. | 10-axis NPC components, monologue trigger system |
| **Sound event system architecture** | Feature | High | Event emitter for sound occurrences. Emits typed events (footsteps, voices, machinery, alarm) with position, intensity, and range. Client renders as audio file OR visual indicator + monologue, depending on available assets. | Perception system (#124) |
| **YAML content loader** | Feature | High | Rust system that parses content YAML files into indexed, queryable line pools at startup. Must support hot-reload for previewer/authoring workflow. | Line pool format (this document) |
| **Line variety tracker** | Feature | Medium | Prevents the same line from firing repeatedly. Tracks recently-used line IDs per NPC per session. Selects from eligible pool excluding recent history. | Dialogue selection pipeline |
| **Knowledge state component** | Feature | High | Per-character component tracking known facts, tagged by source, confidence, and emotional weight. Gates monologue prerequisites and informs situation activation. Paula's `KnowledgeInventory` proposal. | NPC component architecture |
| **Observation event generator** | Feature | Critical | System that detects observable NPC behaviors (routine deviation, interaction between NPCs, absence from expected location) and generates events consumed by monologue trigger system. This is the bridge between simulation and player perception. | NPC routine system, perception system |
| **Tag taxonomy wiki page** | Documentation | High | The converged taxonomy from this document, formatted for the wiki structure Miri is building. Reference document for all content authors. | This document, Miri's wiki structure |
| **THE FRIEND: Smuggler's NPC profile** | Story | Critical | Full Tier 1 profile for the smuggler's FRIEND (NPC-B / Kael Davan). All 10 axes, voice paragraph, triangle positions, contradiction arc. | Dual Lens Guide (#261) |
| **THE FRIEND: Detective's NPC profile** | Story | Critical | Full Tier 1 profile for the detective's FRIEND (NPC-D / Dock Inspector). Same depth. | Dual Lens Guide (#261) |
### Existing Tickets That Need Scope Updates
| Ticket | Current Scope | Needed Addition |
|--------|--------------|-----------------|
| #90 (Tell system) | Unclear | Scope to 5 tell categories (nervous, angry, friendly, guarded, routine deviation). Text-via-monologue as v0.1 renderer, not visual animation. |
| #124 (Sound system) | Unclear | Must include sound event emitter architecture supporting both audio playback AND visual indicator fallback. See Section 6 below. |
| #193 (Line previewer) | "Authoring tool" | Concrete MVP scope defined. See Section 7 below. |
| #168 (Tag taxonomy) | "Agreement needed" | This document IS the agreement. Ticket should be updated to reference this converged taxonomy. |
---
## 5. How Mechanical Systems Support Content Needs
*Let me map every content need from Round 1 to a mechanical system.* This is the crosswalk that ensures nothing falls through the cracks.
### Content Need -> System Mapping
| Content Need (from Round 1) | Required System | Status | Gap? |
|-----------------------------|----------------|--------|------|
| Dialogue lines filtered by access tier | Dialogue selection pipeline (Layer 1) | **Not built** | YES - needs ticket |
| Dialogue changes based on relationship history | Interaction tracking + situation activation (Layer 2) | **Not built** | YES - needs ticket |
| Trust-gated disclosure | Trust progression system (Layer 3) | **Not built** | YES - needs ticket |
| NPCs volunteer information based on mood | NPC mood state machine + weighted selection (Layer 4) | **Not built** | YES - needs ticket |
| Monologue fires on observation events | Observation event generator + monologue trigger system | **Not built** | YES - needs ticket |
| Separate monologue per character | Character-partitioned content pools | **Not built** | Covered by YAML loader + `character` tag |
| Tells observable through monologue | Tell state derivation + monologue integration | **Not built** | YES - needs ticket |
| NPC routine creates observable patterns | NPC routine system (D-024 Daily routine axis) | **Partially ticketed** | Needs scope for deviations and absence detection |
| Dual-lens interpretation of same event | Per-character monologue pools + knowledge prerequisites | **Not built** | Covered by monologue trigger system + `prerequisite` field |
| Mirror moments on replay | Same trigger, different character pool | **Architectural** | Covered by design — separate pools keyed to same triggers |
| Flat NPCs don't feel flat | Routine system + 1 memorable trait + role voice pool | **Not built** | Personality trait modifier in dialogue selection |
| THE FRIEND contradiction arc | Triangle pressure + tell escalation + routine deviation | **Not built** | Composition of several systems (triangle, tell, routine) |
| Environmental text readable in world | Environmental text rendering in Godot client | **Not built** | Needs client-side ticket |
| News ticker / Meridian feed | Ticker content system + time-based rotation | **Not built** | Needs ticket for both content + rendering |
| Audio atmosphere (6-8 files) | Sound event system + audio playback | **Not built** | YES - see Section 6 |
| Diegetic tutorial via monologue | Opening hook monologue + trigger on first-time events | **Not built** | Covered by monologue trigger system + `first_meeting` / first-visit gates |
**Summary: 17 content needs, 0 fully built, 12 need new tickets, 5 covered by existing ticket scope updates.**
The critical path for systems is:
```
NPC Component Architecture (10 axes)
|
+-> NPC Routine System
| |
| +-> Observation Event Generator
| |
| +-> Monologue Trigger System
|
+-> NPC Mood State Machine
| |
| +-> Tell State Derivation
|
+-> Interaction Tracking
| |
| +-> Trust Progression
|
+-> YAML Content Loader
|
+-> Dialogue Selection Pipeline (4 layers)
|
+-> Line Variety Tracker
```
Everything fans out from the NPC component architecture. That's Sprint 1 server work. The YAML loader and dialogue pipeline can be developed in parallel once the component schema is stable.
---
## 6. Audio Event System: Minimal Architecture
Jeroen confirmed audio in v0.1: 6-8 AI-generated files. Ozzie's minimum viable list from Round 1:
1. Station ambient loop (1 file)
2. Location variants: workplace, bar, corridors (3 files)
3. Footsteps — walk/run (2 files)
4. Monologue appearance chime (1 file)
5. (Optional) UI interaction sound (1 file)
**That's 7-8 files.** Here's the minimal architecture that supports them while remaining extensible:
### Sound Event System Architecture
```
[Simulation Server]
SoundEventEmitter
- emits: SoundEvent { type, position, intensity, range_category }
- types: Footstep, Voice, Machinery, Alert, Ambient
- range_category: Close, Medium, Long (D-018)
|
v
[ObserverSnapshot]
sound_events: Vec<SoundEvent> // only events within perception range
|
v
[Godot Client]
SoundRenderer
- receives SoundEvents from snapshot
- looks up audio asset for event type
- if asset exists: play audio (with distance attenuation + stereo panning)
- if asset missing: render visual indicator + fire monologue trigger
|
+-> AudioAssetRegistry
| Maps SoundEvent.type -> audio file path (or null)
| v0.1 registry:
| Footstep -> footstep_walk.ogg, footstep_run.ogg
| Ambient(workplace) -> ambient_workplace.ogg
| Ambient(bar) -> ambient_bar.ogg
| Ambient(corridor) -> ambient_corridor.ogg
| Alert(monologue) -> monologue_chime.ogg
| * -> null (visual fallback)
|
+-> VisualSoundIndicator
| Renders fog-edge ripple/pulse for events without audio
| Color-coded per Araminta's spec:
| neutral (#c8d0e0), voices (#e8c547), danger (#d45d5d)
|
+-> AmbientManager
Manages location-based ambient loops
Crossfades between ambient tracks on location transition
The span gate hum (Miri's suggestion) is the base layer
```
### Key Design Principles
1. **Events first, assets second.** The simulation always emits sound events. The client decides how to render them. Zero audio files = everything renders as visual + monologue. 8 files = partial audio with visual fallback for the rest. Full audio suite = rich soundscape. The architecture doesn't change.
2. **The ambient manager is separate from event-driven sounds.** Ambient loops play continuously based on location. Sound events are discrete occurrences (footsteps, voices, alerts). These are two different subsystems that share the audio output.
3. **Monologue chime is a UI sound, not a simulation sound.** It's triggered by the client when monologue text appears, not by the simulation. It doesn't go through the SoundEvent system.
4. **Distance attenuation is simple for v0.1.** Close range = full volume. Medium range = 50% volume + slight muffle. Long range = no direct audio (insert notification only). Three tiers, not continuous falloff.
### What This Requires from Implementation
- **Server side:** `SoundEventEmitter` system that checks entity actions each tick and emits typed events. Perception filter includes events within hearing range in `ObserverSnapshot.sound_events`.
- **Client side:** `SoundRenderer` node in Godot that processes snapshot sound events. `AudioAssetRegistry` as a simple dictionary. `VisualSoundIndicator` for fog-edge rendering. `AmbientManager` for location loops.
- **Asset pipeline:** 7-8 .ogg files, generated or sourced. Integrated into Godot project's audio resources.
This is a small architecture for a large capability surface. It handles v0.1's 8 files and scales to hundreds without structural changes.
---
## 7. Line Previewer (#193): Concrete MVP Scope
The line previewer was flagged by me, Mellanie, and Ozzie in Round 1 as critical. Let me scope the MVP concretely.
### What the Previewer Does
The previewer answers one question: **"Given this NPC state and this player state, what line fires?"**
It's the authoring equivalent of a compiler — it tells the content author whether their tags produce the intended behavior before the line is integrated into the game.
### MVP Feature Set
| Feature | Description | Priority |
|---------|-------------|----------|
| **Load YAML** | Parse a content YAML file (dialogue or monologue) into indexed pool | Must have |
| **Set filter context** | CLI arguments or interactive prompts for: access tier, trust level, active situations, NPC mood, topic filter, character (for monologue) | Must have |
| **Show matching lines** | Display all lines that pass the 4-layer filter with the given context | Must have |
| **Show selected line** | Apply weighted selection to show which single line would fire | Must have |
| **Explain selection** | Show WHY each line was included/excluded (which filter passed/failed) | Must have |
| **Sequence mode** | Play N lines in order simulating a walk-through (Ozzie's "preview sequence" request) | Should have |
| **Coverage report** | Show which access/trust/situation combinations have zero eligible lines (dead conversation detection) | Should have |
| **Hot reload** | Watch YAML file for changes, re-run filter on save | Nice to have |
| **Batch validation** | Run all YAML files through a consistency checker (missing required tags, invalid enum values, duplicate IDs) | Should have |
### Implementation
**Language: Rust.** The previewer should use the same YAML parser and selection logic that the game server will use. This means the previewer IS a test harness for the dialogue pipeline — if the previewer selects correctly, the game will select correctly.
**Interface: CLI.** No GUI needed. Terminal output with color-coded pass/fail on filters.
```
# Show what the detective hears from a dock_worker at insider access, surface trust,
# morning routine, neutral mood
$ cargo run --bin previewer -- \
--file content/templates/logistics-hub/dialogue.yaml \
--role dock_worker \
--access authority \
--trust surface \
--situation greeting,morning,routine \
--mood neutral \
--verbose
[PASS] access=authority [PASS] trust=surface [PASS] situation=greeting
-> lh_d_002: "You're new around here? Or just... visiting?"
topic=[social, identity] mood=[cautious, neutral] weight=0.85
[PASS] access=authority [PASS] trust=surface [FAIL] situation=first_meeting (requires interaction_count==0)
-> lh_d_005: "Morning. Can I help you with something?"
(excluded: situation mismatch)
Selected: lh_d_002 (weight: 0.85, variety_penalty: 0.0)
```
### Sequence Mode (Ozzie's Request)
```
$ cargo run --bin previewer -- \
--file content/templates/bar/monologue.yaml \
--character smuggler \
--sequence enter_bar \
--mood neutral
[Sequence: enter_bar — smuggler]
1. (enter_location) "The Last Shift. Lera's already got my usual poured."
2. (observe_npc) "Kael's at the corner booth. He looks rough tonight."
3. (observe_npc) "Drin's telling the same story again. Third time this week."
4. (time_idle) "Should probably check in with Kael. He doesn't usually drink alone."
```
This gives Mellanie and Ozzie a way to "feel" the content flow without running the full game. It's the emotional smoke test.
### Effort Estimate
The previewer shares 80% of its code with the dialogue pipeline implementation. Building it first means the pipeline is already tested when it's integrated into the server. The unique work is the CLI interface, the verbose explain mode, and the sequence playback — maybe 2-3 days of Dudley/Tyre's time on top of the pipeline work they'd do anyway.
**Recommendation: Build the previewer AS the first implementation of the dialogue pipeline.** Don't build them separately. The previewer is the pipeline running in standalone mode with verbose output.
---
## 8. Cross-Agent Synthesis: Convergence Map
Here's where every Round 1 contributor's proposals landed after synthesis:
### Fully Aligned (no further discussion needed)
| Topic | Status | Contributors Aligned |
|-------|--------|---------------------|
| Separate monologue pools per character | **Locked** (Jeroen directive) | All |
| Color = relationship to player | **Locked** (Jeroen directive) | Araminta (proposed), Gestalt (endorsed) |
| YAML as authoring format | **Aligned** | Gestalt (proposed), Mellanie (accepted with conditions) |
| 5 tell categories for v0.1 | **Aligned** | Gestalt (proposed), Araminta (visual notes), Ozzie (emotional validation) |
| Diegetic tutorial via monologue | **Aligned** | Gestalt (mechanical), Mellanie (content), Paula (narrative) |
| 30/50/20 entanglement ratio | **Aligned** (D-029 confirmed) | All |
| Monologue is v0.1 tell renderer | **Aligned** | Gestalt, Araminta, Mellanie |
### Converged in This Document
| Topic | Resolution | Key Decision |
|-------|-----------|--------------|
| Tag taxonomy | Converged 8-tag system (6 structural + 2 selection + freeform) | See Section 1 |
| Situation taxonomy | 13 situations from Gestalt + Mellanie merge | See Section 1 |
| Access tier model | list\<enum\> with 5 values | Gestalt's model, Paula's content, aligned |
| Line pool file structure | Directory = template/location, file = content type | Dropped per-line location and type tags |
| THE FRIEND mechanical spec | Full pipeline depth test with ~70-100 authored lines per NPC | See Section 3 |
| Audio architecture | Event-driven with asset registry + visual fallback | See Section 6 |
| Line previewer MVP | Rust CLI sharing pipeline code, 7 must-have features | See Section 7 |
### Needs Round 2 Confirmation from Others
| Topic | Who Needs to Confirm | What I Need |
|-------|---------------------|-------------|
| Converged tag taxonomy | **Mellanie** | Can you author with 6+3 tags per line? Is the mood/topic consolidation workable? |
| Converged tag taxonomy | **Paula** | Does the Layer 2 approach (engine-state-to-situation mapping, not per-line relationship tags) satisfy your 4-layer requirements? |
| THE FRIEND NPC assignments | **Paula** | Confirm NPC-B (Kael) for smuggler, NPC-D for detective. Or propose alternatives. |
| Miri's setting tags | **Miri** | Your proposed `lattice_tier`, `shift_phase`, `district_familiarity`, `institutional_context` — these should be engine-state context, not per-line tags. The engine knows the player is a newcomer; it activates `first_meeting` situations. Do you agree? |
| Spatial layout timing | **Araminta** | Your spatial layouts are needed before or in parallel with content packs. Confirmed? Can they be done independently of content? |
| Audio asset creation | **Ozzie** | 7-8 AI-generated files. Who generates them? What's the quality bar? Do we need a ticket for audio asset generation? |
---
## 9. Emergent Interactions: Where Systems Collide
*This is my favorite part.* Let me map the places where independently designed systems will interact to produce emergent gameplay — the stuff nobody scripted.
### Interaction Map
| System A | System B | Emergent Result |
|----------|----------|----------------|
| **NPC Routine** + **Observation Events** | Player sees NPC in unexpected place at unexpected time | Monologue fires: "That's not where they usually go." Player decides to follow or ignore. Neither designer planned the specific moment. |
| **Trust Progression** + **Triangle Pressure** | NPC's trust in player increases while triangle pressure increases | NPC discloses something they shouldn't under pressure. The disclosure is selected by the dialogue pipeline combining high trust + high stress mood. Not scripted — emergent from system state. |
| **Access Tier Shift** + **Monologue Dual-Lens** | Player's access tier changes at a social site (e.g., detective becomes a bar regular) | New dialogue lines become available AND the monologue reflects the shift ("They're starting to warm up to me"). The player FEELS the social change through two channels simultaneously. |
| **Sound Events** + **Fog of Perception** + **Monologue** | Player hears voices through a wall they can't see past | Sound event at fog edge -> visual indicator -> monologue interprets ("Sounds like an argument. Can't make out the words.") Player decides to move closer or not. The three systems produce a decision point. |
| **THE FRIEND Contradiction** + **Tell System** + **Monologue** | THE FRIEND's tell state escalates (nervous) while their dialogue stays friendly | The player gets conflicting signals: dialogue says "everything's fine," monologue says "they keep checking the door." The player must decide which signal to trust. Asymmetric information within a single NPC. |
| **NPC Mood** + **Time Phase** + **Unprompted Disclosure** | An NPC's mood worsens over the course of a day; by evening at the bar, they're drunk and frustrated | Layer 4 selects from `mood: [annoyed, tired]` + `trust: real` pool. The NPC says something they wouldn't have said that morning. Time + mood + alcohol = emergent information leak. |
**This is why systems-first design works.** None of these moments are scripted events. They're collisions between independently designed systems operating on shared state. The content authors write the individual lines; the systems decide when and how those lines combine. The result is stories the designers didn't anticipate.
---
## 10. Open Questions for Round 3 / Sprint Planning
| Question | Owner | Context |
|----------|-------|---------|
| Does the 4x generation expansion apply to THE FRIEND's custom lines? Or are all 70-100 hand-authored? | Mellanie + Gestalt | Generation expansion on high-specificity NPC lines risks losing the hand-crafted voice. Recommend: no expansion on FRIEND lines. Every line hand-authored. |
| Who creates the 7-8 audio files? | Ozzie + Justine | AI-generated is confirmed, but the pipeline needs defining. Which AI tool? What format? Who evaluates quality? |
| Should the line previewer be a sprint deliverable or a tooling side-project? | Tyre + Dudley | I recommend sprint deliverable — it's the dialogue pipeline in standalone mode. Building it IS building the pipeline. |
| How does the knowledge prerequisite system handle "partial knowledge"? | Gestalt + Paula | A monologue line gated on `knows: smuggling_operation` — does the player need to know the full operation, or just that something suspicious is happening? Need a knowledge hierarchy: `suspects` < `knows_of` < `knows_details`. |
| Triangle pressure threshold — what triggers escalation? | Gestalt + Paula | Triangles need a numeric pressure value that increases based on events. When it crosses a threshold, `confrontation` situation activates. Need to define the events that increase pressure. |
---
*Gestalt out. The taxonomy is converged. The FRIEND is specified. The audio architecture is minimal and extensible. The previewer is scoped. Now we need Mellanie and Paula to validate the tag schema, and Dudley to start building the NPC component architecture. The systems are ready to support the content. Let's build.*
docs/workshops/content-gap-analysis_v0_1/round2-mellanie.md
-355
View File
@@ -1,355 +0,0 @@
# Round 2 — Mellanie's Content Synthesis
**Agent:** Mellanie (Copywriter)
**Date:** 2026-02-11
**Scope:** Cross-agent synthesis, dependency chain, work order, concrete next steps
---
## 1. Reactions to Round 1 Outputs
### Miri's Sova Transit District: Does it give me what I need?
**Almost. It's good. A few gaps.**
The Sova Transit District brief is the best setting document I've gotten on any project. The sensory details are exactly what I asked for — smells (industrial lubricant, recycled air, cooking, ozone-and-metal from the span gate), sounds (cargo machinery, span gate hum, ventilation), temperature variation. These go straight into monologue. That "quotidian-with-undertow" description is the atmosphere I'm writing to.
What I can now write that I couldn't before:
- Location-entry monologue for all three social sites
- Environmental text grounded in Krenn System culture
- News ticker content using Concordat Standard / Meridian terminology
- NPC greetings using Sova naming conventions (Kael, Voss, Drin, Lera, Torek, Maret)
**What's still missing from my perspective:**
1. **Slang and idiom.** Miri gave me naming conventions and cultural posture, but I need speech texture. Do Sova workers say "shift" or "rotation"? "Gate" or "transit"? "Credits" or something local? Do they swear, and if so, how? Three to five colloquialisms would anchor every line of dialogue in the setting. Without them I'll invent them, and we risk inconsistency.
2. **The bar's name.** Miri proposed "The Last Shift." That works. But she also used "Lera's — Cold Drinks, Hot Food, No Questions" on a sign. Are these the same place? I need the canonical bar name locked so every reference is consistent. **Proposal: "The Last Shift" is the official name. "Lera's" is the informal name used by regulars. Both coexist.** This is itself a worldbuilding detail — the smuggler calls it "Lera's," the detective's case file says "The Last Shift, licensed establishment, District 7."
3. **The logistics hub name.** Miri called it "The Terminal." Is that the colloquial name or the official one? Same question. **Proposal: "Sova Transit Freight Terminal" is official. "The Terminal" is what everyone calls it. The smuggling ring calls it nothing — they just say "the dock" or "work."**
4. **One more constraint: what CAN'T be said on the Meridian?** Miri mentioned off-Meridian communication for the ring. For dialogue writing, I need to know what NPCs self-censor in public channels vs. voice. If the Meridian is monitored, every NPC who knows about the ring has a public voice and a private voice. That's a dialogue-level split I need to author for.
**Bottom line: Miri gave me 90% of what I need. The remaining 10% is speech-level detail I can resolve in a short back-and-forth.**
### Gestalt's YAML Line Pool Format: Does it work for me?
**Yes. With one modification and two clarifications.**
The YAML format Gestalt proposed is clean, readable, and writable. The tag taxonomy covers the four D-028 layers. The file structure (`content/templates/{site}/dialogue.yaml` etc.) is logical. The example entries read like content I'd actually author. I can work in this format starting now.
**One modification — the `dual_lens` field:**
Gestalt put `dual_lens` as an authoring-only tag with per-character notes. That's useful during writing, but I want it to DO something in the previewer too. When I preview a line, I want to see: "If the smuggler triggers this line's context, which OTHER lines (from the smuggler's monologue pool) might fire as a reaction?" The dual_lens field should cross-reference monologue trigger IDs, not just carry prose notes.
Proposed change:
```yaml
dual_lens:
smuggler_context: "Routine shop talk. But Taliesin shipments are your cover run."
smuggler_monologue_ref: [lh_m_015, lh_m_016] # monologue lines that pair with this
detective_context: "Cargo volume anomaly. Worth checking manifests."
detective_monologue_ref: [lh_m_042, lh_m_043]
```
This connects dialogue to monologue at the authoring level. When I write a dialogue line, I can immediately link the monologue reactions. The previewer shows the full chain: NPC says X, smuggler thinks Y, detective thinks Z.
**Two clarifications I need:**
1. **Character-specific monologue files vs. shared monologue files.** Gestalt's structure has `templates/{site}/monologue.yaml` — one monologue file per location. But Jeroen confirmed separate pools per character. So do I write `templates/logistics-hub/monologue-smuggler.yaml` and `templates/logistics-hub/monologue-detective.yaml`? Or one file with `character: smuggler` / `character: detective` tags filtering within it? **I prefer separate files.** Two files per location, one per character. Cleaner authoring, no risk of accidentally sharing lines between pools.
2. **The `prerequisite` field on monologue lines.** Gestalt used `prerequisite: { knows: smuggling_operation }` — a knowledge state check. Who defines the knowledge state vocabulary? I need a list of knowledge flags so my monologue prerequisites reference real engine state, not invented strings. **Gestalt or Dudley needs to define the v0.1 knowledge state vocabulary before I write monologue lines with prerequisites.**
**Bottom line: The YAML format works. I'm adopting it. Separate monologue files per character. Need the knowledge state vocabulary defined.**
### Paula's Dual Lens Guide and Relationship Web
Paula's work is the narrative architecture I build on. Her proposed guide contents are exactly right — core identity, emotional starting state, what they notice, what they miss, relationship defaults, the divergence escalation curve. The relationship web with 15 NPCs, 7 triangles, and 6 bridge connections is rich enough without being bloated.
**One thing I need from Paula that wasn't in Round 1:** The voice paragraph for each character. Not the narrative identity — the *speech pattern*. My Round 1 asked for five things: voice signature, what they notice, relationship to authority, what they lie about, emotional baseline. Paula gave me the narrative framework for all five. Now I need them translated into speech:
- Does the smuggler think in short sentences or long ones?
- Does the detective use contractions in their inner monologue?
- When the smuggler is nervous, do they get quieter or louder?
- When the detective is frustrated, do they get clinical or profane?
These are the micro-decisions that determine whether 500 lines sound like the same person or a committee.
### Araminta's Visual Identity
Araminta's color-as-relationship-state proposal is brilliant and directly affects my work. If color carries the asymmetric information visually, my monologue doesn't need to constantly explain WHO people are to the player. The smuggler sees green (friendly) and I don't need "That's Kael, my shift partner" — the color already said "you know this person." My monologue can skip identification and go straight to observation: "Kael's early. That's not like him."
**Araminta's monologue presentation spec also answers my density question.** Max 3 lines visible, fade in/out, priority system (observation > atmosphere > tutorial). This means my lines need to be SHORT. One sentence, maybe two. Never three. The display area is small and fleeting. Every word earns its place or gets cut.
**Her character-differentiated monologue color** (smuggler slightly warmer, detective slightly cooler) is a subtle touch that supports my voice differentiation. The reader's eye will associate color temperature with character register before they consciously parse it. Good.
### Ozzie's Emotional Map and THE FRIEND
Ozzie's emotional journey table is the sequence I'm writing to. Every gap he flagged is a content deliverable on my list. His instinct about THE FRIEND — the NPC designed for emotional contradiction — aligns exactly with what I need to write the most important dialogue in the game.
His note about flat NPCs being "load-bearing for the investigation mechanic" is correct and important. The flat NPC voice kits aren't filler work. They're the noise floor that makes signal detectable. If the noise sounds fake, the signal is too easy to find.
---
## 2. How THE FRIEND Changes My Content Pack Approach
Jeroen's directive: one NPC per character should be "THE FRIEND" — production-level complex. Full profile, full voice kit, full dialogue, full tell system, full contradiction arc. The rest stay v0.1 simple.
**This fundamentally restructures my writing priorities.**
Before: I was planning to write template content packs (role voice kits, situation scripts) and then layer NPC-specific lines on top. Bottom-up. Generic first, specific later.
Now: THE FRIEND gets written FIRST. Top-down for the most important NPC, then bottom-up for everyone else.
**Why this is the right call:**
THE FRIEND is our quality benchmark. If I write them at full depth — every dialogue layer working, every tell authored, the contradiction arc fully scripted — that becomes the reference implementation for the content pipeline. Every other NPC is a simplified version of THE FRIEND. The template system, the YAML format, the tag taxonomy, the previewer — they all get stress-tested on one NPC before I scale to fifteen.
**What THE FRIEND needs (per character):**
| Deliverable | Volume | Purpose |
|-------------|--------|---------|
| Full voice kit | 15-20 sample lines across all moods | The character's complete speech pattern |
| Greeting pool | 8-10 lines (access-filtered) | First contact variations: insider vs outsider vs authority |
| Trust-gated dialogue | 15-20 lines across surface/real/secret | Progressive revelation through repeated interaction |
| Routine dialogue | 10-12 lines | What they say during normal daily activity |
| Contradiction dialogue | 8-10 lines | The lines that reveal the contradiction — the lies, the deflections, the slip-ups |
| Monologue reactions (per PC) | 10-15 lines per character | How the smuggler and detective each interpret THE FRIEND's behavior |
| Tell descriptions | 5-8 lines per character | Observable behavioral markers that hint at the hidden truth |
| Post-discovery dialogue | 5-8 lines | How they talk after the player knows something is off |
| **Total per FRIEND NPC** | **~75-100 authored lines** | Production-quality NPC |
Two FRIEND NPCs = ~150-200 authored lines. That's a significant chunk of the total content budget (~900-1200 lines). Worth it. These are the NPCs that prove the game works.
**Who is THE FRIEND for each character?**
Paula's relationship web has the answer:
- **Smuggler's FRIEND: NPC-B (Logistics Worker 1 / Kael Davan).** The smuggler's closest colleague. Reliable ring member. The smuggler's anchor. The contradiction: Kael is considering cooperating with authorities (or has a secret the smuggler doesn't know about). The smuggler trusts Kael completely — and that trust is what makes the betrayal devastating.
- **Detective's FRIEND:** This is harder because the detective starts as an outsider. The detective's FRIEND isn't a pre-existing relationship — it's a relationship BUILT during the session. **Proposal: the detective's FRIEND is NPC-F (bar owner / Lera Sessik).** The bartender who becomes the detective's primary social contact. Helpful, warm, seems to genuinely like the detective. The contradiction: Lera knows about the smuggling ring and has been providing cover. The detective's best source of social intelligence is also the ring's most effective shield.
Paula — I need your sign-off on these two FRIEND assignments before I start writing.
---
## 3. Missing Tickets Identified from All Round 1 Outputs
Reading all six outputs, I'm seeing deliverables referenced that don't have tickets. Here's what's missing:
| Proposed Ticket | Owner | Priority | Rationale |
|-----------------|-------|----------|-----------|
| **THE FRIEND: Smuggler's NPC (Kael Davan) — full content pack** | Mellanie + Paula | Critical | Production-level NPC. Full voice kit, full dialogue, full tell system, full contradiction arc. Tests entire pipeline. |
| **THE FRIEND: Detective's NPC (Lera Sessik) — full content pack** | Mellanie + Paula | Critical | Same as above, detective perspective. |
| **Sova Transit District slang and idiom guide** | Miri | High | Speech-level setting detail needed before dialogue authoring. Colloquialisms, register differences, what's said on-Meridian vs off. |
| **Knowledge state vocabulary for v0.1** | Gestalt + Dudley | High | List of knowledge flags (e.g., `knows: smuggling_operation`, `met: kael_davan`) that monologue prerequisites reference. Blocks monologue authoring. |
| **Opening hook content — smuggler** | Mellanie | Critical | First 10-15 monologue lines. Diegetic tutorial. Sets voice, teaches mechanics, establishes motivation. |
| **Opening hook content — detective** | Mellanie | Critical | Same for detective. |
| **Monologue files: separate per character per location** | Mellanie | High | 6 monologue files total (2 characters x 3 locations). Confirmed by Jeroen: separate pools, non-negotiable. |
| **Audio: minimum viable sound set (6-8 files)** | TBD (AI-generated) | Medium | Station ambient, 3 location variants, footsteps, monologue chime. Jeroen confirmed for v0.1. |
| **Wiki taxonomy structure** | Miri + Qatux | Critical | Full taxonomy of characters, factions, lore, star systems, technology. Jeroen: non-negotiable, must be established NOW. |
| **Line pool format specification (formal document)** | Gestalt | High | Gestalt proposed the YAML format in Round 1. Needs to be a standalone spec document, not buried in a workshop output. |
| **Spatial layout designs — 3 social sites** | Araminta | High | Floor plans, sightlines, NPC positions. Araminta identified this in Round 1. Directly affects content (what can be overheard from where). |
| **Dual Lens Authoring Guide** | Paula | Critical | Paula proposed writing it. The single most important pre-content document. Blocks everything downstream. |
| **Character voice speech patterns** | Paula + Mellanie | High | The speech-level detail from my 5 asks in Round 1. Blocks voice kits. |
| **Mirror moment design document** | Paula + Mellanie | Medium | 10-15 scripted dual-perspective observation triggers. Blocks the most impactful monologue content. |
Some of these may overlap with existing tickets (#189, #190-192, #261, etc.). Si should cross-reference and create only what's genuinely new.
---
## 4. Dependency Chain: What Must Come Before What
Here's the full content dependency chain, updated with Round 1 inputs and Jeroen's directives:
```
Phase 0: FOUNDATIONS (parallel work, no dependencies between them)
|
|-- Miri: Sova slang/idiom guide
|-- Miri + Qatux: Wiki taxonomy structure
|-- Gestalt: Line pool format spec (standalone document)
|-- Gestalt + Dudley: Knowledge state vocabulary
|-- Paula: Dual Lens Authoring Guide (draft)
|-- Araminta: v0.1 Visual Grammar document
|
Phase 1: CHARACTER ARCHITECTURE (needs Phase 0)
|
|-- Paula + Mellanie: Character voice speech patterns
| |
| v
|-- Mellanie: Smuggler voice kit (needs speech patterns + Dual Lens Guide)
|-- Mellanie: Detective voice kit (needs speech patterns + Dual Lens Guide)
|
Phase 2: THE FRIEND (needs Phase 1 voice kits)
|
|-- Paula: THE FRIEND profiles (Kael + Lera) — full Tier 1 NPC profiles
| |
| v
|-- Mellanie: THE FRIEND content packs (full dialogue + monologue + tells)
| |
| v
|-- VALIDATION: Play-test THE FRIEND content through previewer
| — Does the voice sound right?
| — Does the contradiction land?
| — Does the tag system produce correct line selection?
|
Phase 3: OPENING HOOKS (parallel with Phase 2)
|
|-- Mellanie: Opening hook — smuggler (10-15 lines, diegetic tutorial)
|-- Mellanie: Opening hook — detective (10-15 lines, diegetic tutorial)
|
Phase 4: REMAINING NPCs (needs Phase 2 validation)
|
|-- Paula: NPC profiles (remaining 13 NPCs, Tier 1-3)
|-- Mellanie: NPC voice paragraphs for triangle/entangled NPCs
|
Phase 5: CONTENT PACKS (needs Phase 4)
|
|-- Mellanie: Logistics Hub content pack (#190)
|-- Mellanie: Bar content pack (#191)
|-- Mellanie: Smuggling Ring content pack (#192)
|
Phase 6: POLISH CONTENT (needs Phase 5)
|
|-- Mellanie: Environmental text (signs, terminals, notices)
|-- Mellanie: News ticker / Meridian feed (20-30 lines)
|-- Mellanie: UI microcopy
|-- Mellanie: Tell monologue lines (30-50 lines)
|-- Paula + Mellanie: Mirror moment pass
|-- Araminta: Spatial layouts (parallel with content packs)
|-- Audio: AI-generated sound set (parallel with content)
```
**Critical path: Paula's Dual Lens Guide -> Voice kits -> THE FRIEND -> Validation -> Scale.**
If the Dual Lens Guide is delayed, everything downstream shifts. That's the single highest-risk dependency.
---
## 5. My Proposed Work Order
Here's what I'm proposing to work on, in sequence, with what I can start NOW vs. what's blocked:
### Can start immediately (no dependencies):
1. **Tag taxonomy smoke test.** Write 20 lines in Gestalt's YAML format covering one location (logistics hub), both characters' monologue, and dialogue across access tiers. Ship to Gestalt for validation. This tests the format before I scale. **~2 hours.**
2. **Environmental text templates (generic).** Safety notices, terminal screens, door labels, shift schedule boards. These work in any station. I'll use Miri's Sova details where I have them, leave placeholders where I don't. **~3 hours.**
3. **News ticker first draft.** 15-20 Meridian feed headlines using Miri's setting. "Concord Assembly approves Krenn System infrastructure allocation." "Span gate Terminal B maintenance: 0200-0400." "Security advisory: report unregistered freight to Commission terminal." These are cheap worldbuilding with high atmospheric return. **~2 hours.**
### Needs Paula's Dual Lens Guide (Phase 0):
4. **Smuggler voice kit.** 15-20 sample lines. Provisional until Paula validates. I'll write three voice options (sardonic-observational, anxious-relational, casual-competent) and let Paula pick. **~4 hours.**
5. **Detective voice kit.** Same approach, three options (clinical-precise, weary-professional, sharp-intuitive). **~4 hours.**
### Needs voice kit validation (Phase 1):
6. **Opening hooks.** The first 10-15 lines each character thinks. The most important content in the game. These set voice, teach mechanics, and establish motivation simultaneously. Can't write them until the voice is locked. **~6 hours per character.**
### Needs THE FRIEND profiles (Phase 2):
7. **THE FRIEND: Kael Davan full content pack.** ~75-100 lines. Full voice kit, greeting pool, trust-gated dialogue, routine, contradiction arc, monologue reactions, tells. **~2 days.**
8. **THE FRIEND: Lera Sessik full content pack.** Same depth. **~2 days.**
### Needs remaining NPC profiles (Phase 4-5):
9. **Content packs x3.** Logistics hub, bar, smuggling ring. ~55-70 dialogue + 30-40 monologue per pack. **~3-4 days total.**
10. **Tell lines, mirror moments, UI copy.** Final polish pass. **~2 days.**
**Total estimated writing time: ~12-15 working days for all v0.1 content.**
That's achievable IF the dependency chain doesn't stall. The risk isn't my writing speed. The risk is waiting for inputs.
---
## 6. Revised Content Volume Estimates
With THE FRIEND approach and separate monologue pools confirmed, my Round 1 estimates need updating:
| Category | Round 1 Estimate | Revised Estimate | Change |
|----------|-----------------|------------------|--------|
| Template dialogue (3 packs) | 500-600 | 400-500 | Reduced — THE FRIEND lines come out of the template budget |
| THE FRIEND: Kael (full pack) | (not estimated) | 75-100 | NEW — production-level NPC |
| THE FRIEND: Lera (full pack) | (not estimated) | 75-100 | NEW — production-level NPC |
| NPC-specific lines (~13 remaining) | 115-205 | 80-140 | Reduced — two major NPCs pulled into FRIEND category |
| Monologue — smuggler | 100-150 | 120-160 | Increased — separate pools means no shared lines |
| Monologue — detective | 100-150 | 120-160 | Same |
| Opening hooks (2 characters) | (included in monologue) | 20-30 | Broken out — these are the most important lines |
| Environmental text | 50-60 | 50-60 | Unchanged |
| News ticker / Meridian feed | 15-20 | 20-30 | Increased — Ozzie's right, cheap worldbuilding |
| UI microcopy | 20-30 | 40-50 | Increased — Gestalt's UI text inventory is larger |
| Tell monologue lines | (included in monologue) | 30-50 | Broken out — 5 categories x 3-5 lines x 2 characters |
| **Total authored** | **~900-1,215** | **~1,030-1,380** | |
After 4x generation expansion on dialogue: **~3,200-4,200 total lines available to the system.**
The increase comes from THE FRIEND approach (deeper content for two NPCs) and from breaking out content categories that were previously lumped together. The actual writing workload is similar — I'm just being more precise about what goes where.
---
## 7. Concrete Asks and Open Questions
### Asks (actions needed from specific people):
| Ask | For Whom | Urgency |
|-----|----------|---------|
| Lock the Dual Lens Guide draft — this is the single biggest blocker | Paula | Immediate |
| Provide slang/idiom guide for Sova (5-10 colloquialisms, register rules) | Miri | High |
| Confirm bar name: "The Last Shift" / "Lera's" dual naming? | Miri | Quick answer |
| Confirm logistics hub name: "Sova Transit Freight Terminal" / "The Terminal"? | Miri | Quick answer |
| Define knowledge state vocabulary for monologue prerequisites | Gestalt + Dudley | High |
| Confirm or modify YAML format with my dual_lens cross-reference proposal | Gestalt | Medium |
| Confirm separate monologue files per character per location (not one file with character tags) | Gestalt | Medium |
| Sign off on THE FRIEND assignments (Kael for smuggler, Lera for detective) | Paula | High |
| Visual Grammar doc for my environmental text constraints (character limits, display rules) | Araminta | Medium |
### Open questions I can't answer alone:
1. **What does the generation pass actually do?** D-028 says "write 10, generate 40." But WHO generates? An LLM? A template-based system? Rule-based variation? I need to know because it affects how I write base lines. If the generator is an LLM, I need to write lines that are style-strong enough to anchor generation. If it's rule-based, I need to write lines with clear substitution patterns.
2. **How does the previewer handle THE FRIEND's contradiction arc?** The previewer (#193) needs to simulate a SEQUENCE of interactions, not just single-line filtering. For THE FRIEND, I need to preview: "Meeting 1, the player gets surface lines. Meeting 3, they get real lines. Meeting 5, they get the contradiction. Meeting 6, post-discovery lines." Can the previewer handle temporal progression? If not, I'm testing the most important content blind.
3. **Audio timing with monologue.** Jeroen confirmed a monologue chime in the audio set. When does it fire relative to the monologue text? Before? Simultaneous? Does it interrupt ambient audio or layer over it? I need this for writing rhythm — if there's a chime, my first monologue word needs to land AFTER the chime registers. That means the first word shouldn't be the important one.
---
## 8. The Wiki Taxonomy
Jeroen says a full wiki taxonomy must be established NOW. From a copywriting perspective, here's what the taxonomy needs to support my work:
### Categories I need to reference while writing:
| Category | Why I Need It | Examples |
|----------|---------------|---------|
| **Characters** | Every NPC I write dialogue for needs a canonical entry | Kael Davan, Lera Sessik, Voss, Torek Lintar |
| **Locations** | Every location-entry monologue references a place by name | Sova Transit District, The Last Shift, The Terminal |
| **Factions / Organizations** | Institutional references in dialogue and monologue | Lattice Commission, Concord Assembly, Syndic logistics consortium |
| **Technology** | Characters reference tech casually — I need consistent terminology | Lattice, Meridian, span gate, neural insert, Severance tech |
| **Star Systems** | Background references in news ticker and NPC dialogue | Krenn System, gate routes, planetary references |
| **Cultural Concepts** | Social norms, religions, philosophies characters reference | Unbound, Guardians/Severance, re-embodiment |
| **Contraband Types** | What the ring is actually smuggling — I need to write around it | Unlicensed lattice components, Severance tech, off-manifest biologicals |
**Miri should own the taxonomy structure. Qatux should maintain it.** I'm a consumer of the wiki, not a producer — but I need it to exist before I write 1000+ lines that reference setting elements.
**Minimum viable wiki for my purposes:** A single document with canonical names, brief definitions, and usage notes for each entry. Not a full encyclopedia — a reference card. "Lattice: neural implant technology. Everyone has one unless Unbound. Smuggler has Baseline tier. Detective has Augmented tier. Colloquial: 'lattice,' 'insert,' 'overlay.'" That's enough for me to write consistently.
---
## 9. Summary: The Content Plan
**Write THE FRIEND first. Scale from there.**
The project lead's directive reshapes the content approach from bottom-up (templates first, NPCs later) to quality-first (one production NPC proves the pipeline, then scale). This is the right call. Here's the plan in three sentences:
1. **Now:** Tag taxonomy smoke test, environmental text templates, news ticker draft. No dependencies. Start writing today.
2. **Next:** Voice kits and opening hooks as soon as Paula's Dual Lens Guide lands. THE FRIEND content packs immediately after.
3. **Then:** Validate THE FRIEND through the previewer. If it works, scale to all 15 NPCs and three content packs. If it doesn't, we learn what's broken before we've written 1000 lines.
Scaffold. Validate. Scale. Same three words from Round 1. THE FRIEND is the validation step.
---
*Mellanie out. Give me the voice, give me the friend, and I'll give you the words.*
docs/workshops/content-gap-analysis_v0_1/round2-miri.md
-686
View File
@@ -1,686 +0,0 @@
# Round 2 — Miri's Worldbuilding Synthesis
**Agent:** Miri (Worldbuilder & Setting Designer)
**Date:** 2026-02-11
**Workshop:** v0.1 Content Gap Analysis — Round 2
**Input:** All 6 Round 1 outputs (Mellanie, Paula, Araminta, Gestalt, Ozzie, Miri)
---
## Part 1: The Krenn System Milestone
Jeroen has flagged this and he's right to: **Sova Transit District in the Krenn System is the first concrete, named star system in The Settled Reach.** Everything before this was structural — factions, technology tiers, gate network topology. Sova is where the setting stops being architecture and starts being a *place*.
This matters because every decision we make about Krenn sets precedent. The naming conventions, the cultural texture, the economic model, the institutional presence — whatever we establish here becomes the reference point for every system we build afterwards. "Is this consistent with how we did Krenn?" will be the first question for every future location.
Let me check my Round 1 Sova brief against what the team needs, informed by their Round 1 outputs.
---
## Part 2: How Sova Serves the Team (Cross-Referencing Round 1 Feedback)
### For Mellanie — Texture, Not Lore
Mellanie asked for five specific things (Round 1, Layer 3): smells, slang, wall decoration, ambient sound, local complaints. Let me check what my Round 1 provided and fill the gaps.
| Mellanie's Ask | What I Provided (Round 1) | What's Still Missing |
|---|---|---|
| **Smells** | Industrial lubricant, recycled air, cooking, span gate ozone | Covered. Mellanie can write from this. |
| **Slang** | Naming conventions (Kael, Voss, Drin, etc.), first-name-primary culture | **Missing: occupational slang.** Do dock workers say "shift" or "rotation"? "Credits" or a local term? "Container" or "pod" or "crate"? Need a 15-word slang glossary. |
| **Wall decoration** | Bilingual signage (Concordat Standard + Krenn vernacular), hand-lettered informal signs | **Missing: non-institutional decoration.** Is there graffiti? Stickers? Shift change artwork? Personal touches on lockers? The *human mark* on the institutional surface. |
| **Ambient sound** | Span gate hum, cargo machinery, ventilation, bar clinks | Covered. Ozzie wants audio files; at minimum these descriptions feed monologue. |
| **Local complaint** | Implied (economic pressure, tight-enough-to-be-tempting wages) | **Missing: a specific, named grievance.** Every community has one. Suggestion: the ventilation in Sector 3 has been unreliable for months. Station maintenance says it's on the list. Everyone mentions it. It's the universal safe topic — and for the detective, it's useful: people who are talking about ventilation are *not* talking about something else. |
**Action item: Write a "Sova Texture Appendix" — 1 page covering slang glossary (15-20 terms), informal decoration details, the local complaint, and any other sensory details Mellanie needs. This unblocks her environmental text and monologue work.**
### For Paula — Economic Engine and NPC Motivation
Paula's Round 1 nailed the motivational chain: Station Economics -> Employment Pressure -> Individual Desperation -> Criminal Opportunity -> Social Complicity. My Round 1 Sova brief provides the economic engine (freight-based, steady-but-tight wages, Commission presence intermittent). Let me validate her specific requests:
| Paula's Need | Status |
|---|---|
| The economic squeeze — what makes legitimate life just hard enough | **Covered.** "Comfortable enough to be complacent, tight enough that an extra income source is tempting." |
| The interdependencies — who benefits from the grey economy | **Partially covered.** My Round 1 notes that the bar benefits, that flat NPCs deliberately don't ask. Need to make this more explicit: the *community's immune system* framing (Paula's phrase) needs a concrete list of who benefits and how. |
| The recent pressure point — what changed recently | **Covered.** Three triggers: Commission liaison rotation (3 months), increased freight volume (6 weeks), detective arrival (2 weeks). |
Paula's relationship web (15 NPCs, 7 triangles) is excellent architecture. My Round 1 NPC name suggestions (Kael, Voss, Lera, Torek, Drin, Maret) need to map onto her NPC-A through NPC-O structure. Let me do that explicitly:
**Proposed Name Mapping (Miri names -> Paula's structure):**
| Paula's ID | Role | Miri's Suggested Name | Notes |
|---|---|---|---|
| NPC-A | Shift Supervisor (Hub) | **Voss** | Authority figure. Surname usage by subordinates: "Supervisor Voss" or just "Voss." |
| NPC-B | Logistics Worker 1 (Hub, Ring bridge) | **Kael Davan** | The smuggler's closest colleague. First-name basis. |
| NPC-C | Logistics Worker 2 (Hub, new hire) | **Resha** | New, compact name. Slightly softer than the Krenn norm — could suggest off-system origin, which is *why* they ask too many questions. They haven't internalized "mind your business." |
| NPC-D | Dock Inspector (Hub, Bar bridge) | **Torek Lintar** | Reassigned from my Round 1 "getting sloppy" role to the compromised inspector. Same name works — Torek is the kind of name that sounds exhausted. |
| NPC-E | Maintenance Tech (Hub, flat) | **Drin** | Single name. The type who's been here long enough that nobody uses a surname. |
| NPC-F | Bar Owner (Bar, Ring bridge) | **Lera Sessik** | Reassigned from bartender to owner (Paula's structure has the owner as the key figure). Lera works — established, observant, careful. |
| NPC-G | Off-duty Security (Bar, Hub bridge) | **Harek** | New name. Compact, military-adjacent. Someone who sits at the bar with the posture of a person who's technically off-duty. |
| NPC-H | Regular / Teacher-Family (Bar) | **Maret Korr** | Reassigned from ring-adjacent freight scheduler to the worried partner. Maret is the name of someone with a life outside the docks — domestic, personal, the mundane anchor. |
| NPC-I | Bartender (Bar, flat) | **Sess** | Short, functional. Nickname from a longer name nobody uses. The kind of name that means "I've been behind this bar for years." |
| NPC-J | Drifter / New Arrival (Bar, flat) | **No fixed Krenn name** | If they're new, they might have a different naming convention — could be from a different system. This is itself a tell. Suggestion: **Olin** — slightly longer vowel, not Krenn-standard. |
| NPC-K | Ring Leader (Ring, Bar bridge) | **Devra** | New name. Needs to sound capable, not theatrical. Devra is compact, decisive. A name that works as a legitimate business operator and a criminal coordinator. |
| NPC-L | Courier (Ring, Hub bridge) | **Renn** | Short, kinetic. A name that moves. |
| NPC-M | Fence/Buyer (Ring, external) | **Off-system name** | Not Krenn convention. Suggestion: **Sabel** — slightly different phoneme pattern. External contacts should *sound* external. |
| NPC-N | Ring Member, wavering (Ring) | **Pell** | Small, vulnerable. A name that sounds like it could break. |
| NPC-O | Lookout/Runner (Ring, flat) | **Tav** | Clipped. Young. A name with no history yet. |
Setting note — 15 names following the Krenn convention (compact, consonant-heavy, first-name-primary) with deliberate breaks for off-system characters. The naming itself is worldbuilding: when the detective hears "Sabel" among all these Krenn-standard names, their trained instinct should flag the phoneme difference. The smuggler already knows Sabel is from outside — it's just a name to them.
### For Araminta — Visual Framework
Araminta's spatial layout work (floor plans, sightline diagrams) needs setting constraints from me. My Round 1 covered the general feel (mid-Reach, 40 years old, layered construction), but she needs specifics:
| Spatial Requirement | Setting Constraint |
|---|---|
| Logistics Hub layout | Modular prefab base, retrofitted partitions. Regular grid in the main bay, irregular in older back sections. At least one area where wall layers create hidden space between the original prefab shell and the interior partition. |
| Bar layout | Converted from an older use (originally a maintenance staging area?). The irregular layout is structural, not decorative — the booths were built into spaces that already existed. The back room is a genuine maintenance access that Lera has "adopted." |
| Smuggling spaces | NOT a dedicated room. Repurposed infrastructure — a maintenance corridor between two sections of the logistics hub where the old and new construction don't quite meet. Access through a service hatch in the break room area. The ring didn't build this space; they *found* it. |
| Transition zones | The corridor between the hub and the bar district is a chokepoint — everyone who goes from work to drinks passes through the same 40 meters of corridor. This is where the smuggler notices who's heading where, and where the detective can observe patterns. |
Gestalt's Layer 3 note about spatial information asymmetry requirements (publicly accessible area with hidden back, area with smuggler-natural-access, cross-template chokepoint) is satisfied by this layout.
### For Gestalt — Setting Tags Validated
Gestalt's line pool format (YAML, 6 structural tags, 3 content tags) integrates cleanly with my setting-grounded tag proposals from Round 1. Cross-referencing:
| Miri's Setting Tag | Maps to Gestalt's Schema | Notes |
|---|---|---|
| `lattice_tier` (baseline/augmented) | Could be a `character` filter or a `prerequisite` | Determines what the character's overlay shows. Detective's augmented lattice feeds different `observe_npc` monologue. |
| `shift_phase` (on_shift/off_shift/transition) | Maps to `situation` (routine/working/social) | Setting-grounded version of the same concept. Gestalt's taxonomy works; I'd add `shift_transition` as a situation value — that's when things happen in a freight district. |
| `district_familiarity` (local/newcomer) | Maps to `situation` (first_meeting vs. repeated_visit) | Already captured in Gestalt's situation taxonomy. |
| `institutional_context` (civilian/commission/syndic) | Subset of `access` tier | The detective registers as `authority` *because* of their Commission lattice signature. This is the setting-grounded explanation for why the access tier system works in-fiction. |
**Setting validation: the tag taxonomy is consistent with established worldbuilding. No conflicts.**
### For Ozzie — The First 30 Seconds
Ozzie wants five things in the first 30 seconds: sound, movement, news ticker, something out the window, a named NPC. Let me check what the setting provides for each:
1. **Sound:** The span gate hum. This is the "you're on a space station" signal, delivered continuously. Setting note — the hum *changes pitch* with traffic volume. Morning shift startup: it rises. Late night: it settles. The change is subtle enough that residents ignore it, but specific enough that monologue can reference it.
2. **Movement:** NPCs heading to shift. The logistics hub runs on freight schedules — people move at predictable times. Game start for the smuggler should be just before shift change: people walking past, greeting each other, the district waking up. Game start for the detective should be mid-morning: the district is already active, and the detective is arriving into an established rhythm.
3. **News ticker:** Covered in my Round 1 Layer 8. Three types: Concord Assembly proceedings (boring), freight market prices (relevant), Commission notices (pointed). Ozzie's specific suggestion ("Dock 7 maintenance: scheduled closure 14:00-18:00" / "Security reminder: report unregistered cargo") is exactly right and setting-consistent.
4. **Something out the window:** Setting note — Sova Transit District is on a station. There should be at least one viewport or observation area showing the Krenn system's primary: a G-type star, slightly cooler than Sol, giving a faintly amber quality to natural light. The span gate terminal area has an observation gallery above the freight bays where you can see the gate itself — a ring structure that occasionally flickers with transit energy. This is the "you are in space" moment.
5. **A named NPC within 10 seconds:** For the smuggler: Kael, walking the same direction, same shift. "There's Kael. Early for once." For the detective: an unnamed dockworker who becomes named through institutional query — "Dock worker, second shift. ID: Drin. No flags." The detective's first NPC contact is *mediated by their insert*, not personal familiarity.
---
## Part 3: Contraband Resolution
I proposed in Round 1 that the primary smuggled cargo should be **unlicensed lattice components** — aftermarket neural lattice modifications that bypass Commission regulation. After reading all Round 1 outputs, let me pressure-test this.
**Does "unlicensed lattice components" work for each team member's needs?**
| Team Member | Their Need | Does Lattice Contraband Serve It? |
|---|---|---|
| **Paula** | Moral ambiguity — the smuggling should be sympathetic | **Yes.** People want better lattice access than Commission-regulated channels provide. The ring isn't moving weapons; they're moving *capability*. The moral question ("Is it wrong to give people better brain implants?") is genuinely ambiguous. |
| **Mellanie** | Writable dialogue — NPCs should be able to discuss the cargo in ways that feel natural | **Yes.** Dock workers can reference "restricted components," "aftermarket inserts," "upgrade kits." The vocabulary is concrete and setting-specific. Not drugs, not weapons — tech. Workers might personally want some of this cargo. |
| **Gestalt** | Mechanical relevance — the contraband should connect to game systems | **Yes.** Lattice components connect to the lattice/insert system (D-013, D-017). A smuggled lattice upgrade could theoretically *change what the player can perceive*. This is a gameplay hook for future development: the smuggler could acquire enhanced perception through contraband, while the detective has it through institutional issue. |
| **Ozzie** | Emotional weight — the player should feel something about what's being smuggled | **Partially.** Lattice components are abstract. Need to ground them: a specific NPC who wants a lattice upgrade for their child (medical necessity, can't afford Syndic pricing) or a worker whose failing lattice could be replaced with aftermarket components but can't get Commission clearance. The *people who need the product* make the product emotionally real. |
| **Araminta** | Visual representation — contraband should be representable at boxes-with-labels fidelity | **Yes.** Cargo containers. Manifest discrepancies. Nothing that requires special visual treatment. |
**Contraband decision: Unlicensed lattice components as primary cargo holds up.** Secondary cargo (Severance counter-surveillance tech, off-manifest biologicals) adds variety without changing the core moral dynamic.
**One addition:** The specific lattice components being smuggled should include **medical-grade neural lattice replacements** diverted from Syndic supply chains. This adds a humanitarian dimension: some of this cargo is going to people whose lattices are degrading and who can't afford institutional replacement. The ring isn't just moving luxury upgrades — it's also moving healthcare. This deepens the moral ambiguity and gives NPCs like Maret (NPC-H) a personal stake: maybe their aging parent needs a lattice replacement they can't afford through legitimate channels.
---
## Part 4: Missing Tickets for Worldbuilding Work
After reviewing all Round 1 outputs, here are the worldbuilding tickets that don't exist yet:
| Proposed Ticket | Priority | Type | Rationale | Depends On |
|---|---|---|---|---|
| **Sova Texture Appendix** (slang glossary, informal decoration, local complaints, sensory details) | Critical | Story | Mellanie's monologue and environmental text are blocked without this. | #189 (Cultural generation guide) — this is a sub-deliverable |
| **Krenn System Profile** (star type, settlement history, political position, economic role) | High | Story | The wiki's first star system entry. Establishes the template for all future systems. | Nothing — can start immediately |
| **Sova Station Profile** (station type, population, districts beyond the Transit District, governance) | High | Story | NPCs reference the wider station. Dialogue needs to know what's "off-district." | Krenn System Profile |
| **Contraband Specification** (primary: lattice components, secondary: Severance tech, biologicals; with supply chain details) | High | Story | Paula's NPC motivations and Mellanie's dialogue both need to know what's being smuggled and why people want it. | Nothing — this document resolves the open question |
| **Detective Institutional Chain of Command** (who assigned the investigation, stated mandate, political pressures) | High | Story | Paula flagged this. The detective's narrative arc requires knowing who they report to and what constraints they operate under. | Krenn System Profile (jurisdiction questions) |
| **Meridian Coverage Map for Sova Transit** (where coverage is strong, where it degrades, dead spots the ring exploits) | Medium | Story | Affects detective investigation capability, smuggler operational planning, and NPC behavior (off-Meridian communication in dead spots). | Sova Station Profile |
| **Off-Station Connections Brief** (who receives the contraband, the coordinator's location, external contact details) | Medium | Story | NPC dialogue references off-station contacts. Need enough detail for consistency without building full external locations. | Contraband Specification |
| **Span Gate Transit Schedule** (how often the gate cycles, peak times, maintenance windows) | Medium | Story | The freight rhythm is the district's heartbeat. NPC routines depend on it. The ring's operational timing depends on it. | Nothing |
| **Observation Gallery / Viewport Description** (what you see looking out at the Krenn system) | Low | Story | Ozzie's "something out the window" — the visual anchor that says "space station." | Krenn System Profile |
---
## Part 5: Cultural and Environmental Detail Priorities
Reading all six Round 1 outputs, the team converges on one point: **the setting details that matter most are the ones that differentiate the two characters' experience of the same place.** Atmosphere is nice; asymmetric atmosphere is the game.
**Priority order for cultural/environmental details:**
1. **Details that read differently per character** (highest priority)
- The span gate schedule board: routine data for the smuggler, investigation material for the detective
- Cargo manifests: familiar paperwork vs. potential evidence
- NPC naming and greeting conventions: the smuggler *knows* everyone's name; the detective has to *learn* them
- Institutional signage: background noise for the smuggler, professional context for the detective
2. **Details that establish presence** (high priority)
- The span gate hum (Ozzie's "sound first")
- The news ticker (worldbuilding in 30 words)
- The local complaint (ventilation in Sector 3)
- Food and drink specifics (what the bar serves, what the food vendors sell)
3. **Details that feed investigation** (high priority)
- Meridian dead spots where off-channel communication is possible
- Architectural secrets (spaces between wall layers, repurposed maintenance corridors)
- Shift transition timing (when oversight is thinnest)
- Spending pattern indicators (what "living beyond your means" looks like in Sova)
4. **Details that build attachment** (medium priority)
- Community events (the bar's regular card game, shift-end rituals)
- Interpersonal customs (how Krenn System people express trust, discomfort, affection)
- Personal spaces (what a locker area looks like, how people personalize their workstations)
5. **Lore depth** (low priority for v0.1)
- Krenn System settlement history (establishes depth but doesn't directly serve gameplay)
- Broader Reach political context (Concord Assembly, Commission politics — background texture)
- The Unbound presence in the district (mentioned in Round 1, not load-bearing for v0.1)
---
## Part 6: Dependencies Between Setting Work and Content/Character Work
Here's the dependency chain with setting work highlighted:
```
IMMEDIATE (no dependencies):
Contraband Specification (Miri) ──> NPC motivations (Paula)
Krenn System Profile (Miri) ──> Wiki foundation
Span Gate Transit Schedule (Miri) ──> NPC routine design (Paula/Gestalt)
FAST FOLLOW:
Sova Station Profile (Miri) ──> Off-station references in dialogue (Mellanie)
Sova Texture Appendix (Miri) ──> Environmental text (Mellanie)
──> Monologue sensory details (Mellanie)
Detective Chain of Command (Miri+Paula) ──> Detective character build (#181)
──> Detective voice kit (Mellanie)
PARALLEL WITH CONTENT WORK:
Meridian Coverage Map (Miri) ──> Investigation mechanics (Gestalt/Tyre)
Off-Station Connections (Miri) ──> Ring NPC dialogue consistency (Mellanie)
Observation Gallery (Miri) ──> First-30-seconds experience (Araminta/Ozzie)
```
**The critical path for content:** Paula's Dual Lens Guide and my Sova setting work are the two roots. They can proceed in parallel. Mellanie is blocked until both exist. The contraband specification is the fastest-to-resolve blocker — I can write it now and unblock Paula's NPC motivation work immediately.
---
## Part 7: The Wiki Taxonomy
This is the big one. Jeroen has flagged this as non-negotiable: we need a complete, future-proof wiki structure established now, while we're building the first entry. It must scale from v0.1 (one system, one station, 15 NPCs) to the full game (hundreds of systems, thousands of NPCs).
### Design Principles for the Wiki
1. **Game-first, not encyclopedia-first.** The wiki exists to serve the game's content pipeline. Every entry should be writable by a team member and consumable by the game systems (even if that consumption is indirect — an NPC profile feeds dialogue authoring, which feeds YAML content packs).
2. **Hierarchical with cross-references.** Star systems contain stations contain districts contain locations. But NPCs move between locations. Factions span systems. Technology is everywhere. The hierarchy is spatial; the cross-references are relational.
3. **Metadata-rich.** Every entry has structured frontmatter (YAML) that enables programmatic queries. "Give me all NPCs in the Krenn System with a smuggling connection" should be answerable from metadata alone.
4. **Template-driven.** Each category has a template. New entries follow the template. This ensures consistency and tells authors exactly what information is required vs. optional.
5. **Scale-tested.** The structure must work with 1 star system and with 500. No nesting depth that becomes unmanageable. No category that becomes a dumping ground.
### Proposed Wiki Directory Structure
```
wiki/
_templates/ # Entry templates (one per category)
star-system.md
station.md
district.md
location.md
character.md
faction.md
technology.md
cultural-group.md
lore-entry.md
contraband-type.md
institution.md
species.md
event.md
concept.md
star-systems/ # Top-level spatial hierarchy
krenn/
_index.md # Krenn System profile
stations/
sova/
_index.md # Station Sova profile
districts/
transit-district/
_index.md # Sova Transit District profile
locations/
logistics-hub.md # The Terminal
the-last-shift.md # The bar
maintenance-corridor-7b.md # Smuggling space
observation-gallery.md
commission-kiosk.md
characters/ # All named characters, flat structure
kael-davan.md
voss.md
lera-sessik.md
torek-lintar.md
drin.md
maret-korr.md
resha.md
harek.md
sess.md
olin.md
devra.md
renn.md
sabel.md
pell.md
tav.md
factions/ # Political and institutional bodies
concord-assembly.md # The galactic legislature
lattice-commission.md # Technology regulatory body
syndics/
_index.md # Syndic overview
# Individual Syndics as they're created
guardians-of-severance.md # Counter-surveillance movement
the-unbound.md # Lattice refusers
technology/ # Technology categories
neural-lattice/
_index.md # Lattice overview
tiers/
baseline.md
augmented.md
enhanced.md
transcendent.md
meridian.md # Information network
span-gates.md # Local gates
horizon-gates.md # Interstellar gates
re-embodiment.md # Death/resurrection technology
severance.md # Counter-surveillance tech
cultural-groups/ # Cultures, subcultures, movements
krenn-system-culture.md # First entry
# Future: other system cultures, station subcultures
contraband/ # Illegal/restricted goods
unlicensed-lattice-components.md
severance-equipment.md
off-manifest-biologicals.md
institutions/ # Formal organizations (non-faction)
# Courts, academies, services, etc. as needed
species/ # Non-human entities
# As defined — currently placeholder category
lore/ # Historical events, concepts, cosmology
the-interstitium.md # Gate medium / between-space
settlement-eras/
_index.md
# Individual era entries
founders.md # Progenitor civilization
builders.md # Gate builders
concepts/ # Game-mechanical concepts with lore basis
information-asymmetry.md # How the game's core mechanic is grounded in setting
lattice-surveillance.md # How monitoring works in-universe
severance-culture.md # Counter-culture movement
_meta/ # Wiki maintenance files
naming-conventions.md # Per-system naming rules
style-guide.md # Writing conventions for wiki entries
cross-reference-index.md # Auto-generated or maintained
changelog.md # Wiki revision history
```
### Entry Metadata Schema (YAML Frontmatter)
Every wiki entry has structured frontmatter. Here are the schemas per category:
#### Star System Entry
```yaml
---
type: star-system
id: krenn # Unique slug
name: Krenn System
classification: mid-reach # core | mid-reach | frontier | deep-frontier
star_type: G3V # Stellar classification
settlement_age: ~180 years # How long since first settlement
population: ~2.4 million # System-wide estimate
governance: concord-assembly # Primary governing body
gate_connections: # Horizon/span gate links
- target: [system-id]
type: horizon # horizon | span
economic_base: [logistics, mining] # Primary industries
meridian_coverage: standard # comprehensive | standard | sparse | minimal
commission_presence: moderate # heavy | moderate | light | nominal
cultural_notes: "Working-class pragmatic. Values reliability and minding your business."
tags: [v0.1, playable, mid-reach]
status: canonical # canonical | draft | proposed
created: 2026-02-11
updated: 2026-02-11
---
```
#### Station Entry
```yaml
---
type: station
id: sova
name: Station Sova
system: krenn
classification: logistics-hub # Functional type
construction_era: mid-settlement # When built relative to system history
population: ~12,000
districts:
- id: transit-district
name: Sova Transit District
type: commercial-logistics
governance: station-administrator # Local governance type
gate_access:
- type: span
connects_to: krenn-planetary-depot
traffic: freight-primary
notable_features:
- "Gate-adjacent logistics hub"
- "Mixed-era construction"
tags: [v0.1, playable]
status: canonical
created: 2026-02-11
updated: 2026-02-11
---
```
#### District Entry
```yaml
---
type: district
id: sova-transit-district
name: Sova Transit District
station: sova
system: krenn
age: ~40 years
construction: prefab-modular-retrofitted
economic_engine: freight-logistics
atmosphere: quotidian-with-undertow # One-phrase mood descriptor
population: ~800 (workers + residents)
meridian_coverage:
logistics_hub: strong
bar_district: strong
older_sections: degraded
maintenance_corridors: minimal
commission_presence: intermittent # permanent | intermittent | minimal | none
locations:
- id: logistics-hub
name: The Terminal
type: workplace
- id: the-last-shift
name: The Last Shift
type: social-venue
- id: maintenance-corridor-7b
name: Corridor 7B
type: infrastructure
hidden: true
key_npcs: [kael-davan, voss, lera-sessik, torek-lintar, drin, maret-korr]
cultural_group: krenn-system-culture
local_issues:
- "Ventilation reliability in Sector 3"
- "Commission liaison rotation gap"
tags: [v0.1, playable, vertical-slice]
status: canonical
created: 2026-02-11
updated: 2026-02-11
---
```
#### Location Entry
```yaml
---
type: location
id: the-last-shift
name: The Last Shift
district: sova-transit-district
station: sova
system: krenn
location_type: social-venue # workplace | social-venue | residential | infrastructure | commercial | institutional
template: bar # Game template this instantiates
capacity: 30 # Max occupancy
owner_npc: lera-sessik
regular_npcs: [kael-davan, torek-lintar, drin, maret-korr, harek]
operating_hours: "14:00 - 02:00 station time"
atmosphere: "Mid-grade bar. Not upscale, not a dive. The kind of place where working people go after shift."
architectural_notes: "Converted maintenance staging area. Irregular layout from pre-existing structure. Long bar, scattered tables, semi-private corner booth."
sensory:
sound: "Conversation, glass on surfaces, Meridian music feed"
smell: "Recycled air with cooking undertones"
lighting: "Warm, cheaper fixtures, irregular"
temperature: "Climate-controlled, comfortable"
signage:
- "Lera's -- Cold Drinks, Hot Food, No Questions"
- Shift schedule board (community use)
tags: [v0.1, social-site, bar-template]
status: canonical
created: 2026-02-11
updated: 2026-02-11
---
```
#### Character Entry
```yaml
---
type: character
id: kael-davan
name: Kael Davan
system_origin: krenn
cultural_group: krenn-system-culture
age: 34
role: dock-worker # Occupational role
employer: sova-logistics-consortium # Who they work for
home_district: sova-transit-district
entanglement: entangled # flat | triangle | entangled
triangle_ids: [hub-new-hire, ring-power-dynamic]
smuggling_role: ring-member # null if not involved
lattice_tier: baseline
relationship_to_smuggler: close-colleague
relationship_to_detective: person-of-interest
personality_summary: "Reliable, protective, loyal to people rather than institutions. The smuggler's anchor."
want: "Protect the operation and the people in it"
secret: "Smuggling ring member, mid-level"
tolerance_threshold: moderate
contentment: moderate-low
daily_routine:
- "Morning shift at logistics hub"
- "Break room during midday"
- "The Last Shift after shift end"
- "Occasional late-night ring operations"
voice_notes: "Direct, practical. Uses first names. Speaks in short declarative sentences. Doesn't waste words."
tags: [v0.1, hub-npc, ring-npc, bridge-npc]
status: canonical
created: 2026-02-11
updated: 2026-02-11
---
```
#### Faction Entry
```yaml
---
type: faction
id: lattice-commission
name: The Lattice Commission
scope: reach-wide # reach-wide | regional | system | local
governance_role: regulatory # regulatory | legislative | executive | military | commercial | religious | subversive
mandate: "Regulation of neural lattice technology, certification of lattice tiers, enforcement of lattice compliance standards"
headquarters: [system-id] # TBD
structure: bureaucratic-hierarchical
public_perception: "Necessary but intrusive. The tax authority of neural technology."
player_relevance:
smuggler: "The adversary. Commission regulation is what makes lattice smuggling profitable."
detective: "The employer (or contractor). Institutional backing and constraints."
key_personnel: [] # As defined
sub_organizations: [] # Regional offices, special divisions
cultural_impact: "Commission presence shapes social behavior — people modulate what they say when Commission-tagged individuals are present."
tags: [institution, regulatory, reach-wide]
status: canonical
created: 2026-02-11
updated: 2026-02-11
---
```
#### Technology Entry
```yaml
---
type: technology
id: neural-lattice
name: Neural Lattice
category: biotechnology # biotechnology | infrastructure | communication | transportation | weaponry | surveillance
prevalence: universal # universal | common | specialized | rare | unique
access:
baseline: "Standard-issue, factory default"
augmented: "Institutional or premium, enhanced capability"
enhanced: "Specialist, rare, significant capability"
transcendent: "Theoretical or post-human"
regulation: commission-controlled
contraband_relevance: "Unlicensed components bypass Commission certification, providing enhanced capability without institutional approval"
gameplay_relevance: "Determines perception modes, insert overlay capability, Meridian access depth"
setting_notes: "The lattice is to citizens of the Reach what smartphones are to us — ubiquitous, always-on, unreflectively used. Its absence (the Unbound) is more notable than its presence."
tags: [core-tech, perception, ubiquitous]
status: canonical
created: 2026-02-11
updated: 2026-02-11
---
```
#### Contraband Entry
```yaml
---
type: contraband
id: unlicensed-lattice-components
name: Unlicensed Lattice Components
category: technology # technology | biological | information | material | cultural
legality: restricted # banned | restricted | controlled | gray-market
severity: moderate # severe | moderate | minor
commission_classification: "Category 3 violation — unauthorized modification of certified neural technology"
supply_chain: "Aftermarket manufacturers (often Syndic-adjacent) -> freight networks -> local distributors -> end users"
demand_drivers:
- "Enhanced capability beyond Baseline tier at affordable price"
- "Medical-grade replacements for degrading lattices at below-Syndic pricing"
- "Custom modifications for specific occupational needs"
moral_dimension: "These components serve real needs — medical, professional, personal autonomy. The Commission's regulatory monopoly prices many citizens out of legitimate access."
detection_methods: "Manifest scanning, lattice signature analysis, physical inspection"
evasion_methods: "Doctored manifests, scanner blind spots, shift-transition timing, off-Meridian coordination"
gameplay_relevance: "Primary contraband for v0.1 smuggling scenario. Establishes moral ambiguity: the player is smuggling access, not weapons."
tags: [v0.1, smuggling, lattice, moral-ambiguity]
status: canonical
created: 2026-02-11
updated: 2026-02-11
---
```
### How the Wiki Scales
| Scale | v0.1 | v0.5 | v1.0 | Full Game |
|---|---|---|---|---|
| Star systems | 1 (Krenn) | 3-5 | 10-20 | 100+ |
| Stations/worlds | 1 (Sova) | 5-10 | 30-50 | 500+ |
| Districts | 1 (Transit) | 5-15 | 50-100 | 1000+ |
| Characters | 15 | 50-100 | 300-500 | 5000+ |
| Factions | 5 | 8-12 | 15-20 | 30+ |
| Technology entries | 8-10 | 20-30 | 50-75 | 100+ |
| Contraband types | 3 | 8-12 | 20-30 | 50+ |
| Cultural groups | 1 | 5-10 | 20-40 | 100+ |
| Lore entries | 5-8 | 20-30 | 50-100 | 200+ |
**Scaling notes:**
- **Characters are flat, not nested under locations.** An NPC might move between systems over the course of the game. Their entry lives in `characters/` with location references in metadata, not under a specific station directory.
- **Star systems are the primary spatial hierarchy.** System -> station/world -> district -> location. This is four levels deep maximum. Future expansion adds *breadth* (more systems), not *depth* (more nesting levels).
- **Cross-references use IDs, not file paths.** When `kael-davan.md` references `sova-transit-district`, it uses the ID `sova-transit-district`, not a relative path. This means entries can be reorganized without breaking links.
- **The `_templates/` directory is the schema contract.** When Mellanie or Paula need to add an NPC, they copy `_templates/character.md`, fill in the frontmatter and prose, and save it in `characters/`. The template tells them exactly what's required.
- **Tags enable cross-cutting queries.** "Show me all `v0.1` content" or "all entries tagged `smuggling`" or "all `canonical` characters in `krenn`" — these are tag queries, not directory traversals.
### Wiki Governance
| Rule | Rationale |
|---|---|
| **Miri owns the wiki structure.** New categories, template changes, and structural decisions go through me. | Consistency requires a single maintainer for the schema. |
| **Anyone can create entries** within their domain, following templates. | Paula creates character entries. Mellanie adds voice notes. Gestalt annotates gameplay relevance. |
| **Every entry has a `status` field.** `proposed` -> `draft` -> `canonical`. | Prevents confusion about whether something is decided or speculative. Only `canonical` entries are treated as setting truth. |
| **The `_meta/naming-conventions.md` file is mandatory reading** before creating any named entity. | Name consistency is the most visible form of worldbuilding consistency. IP originality checks happen here. |
| **Cross-references must use valid IDs.** Dead links are caught by a validation script. | Referential integrity. We'll need a simple script that checks all ID references resolve. |
| **Lore entries explain WHY, not just WHAT.** Every lore entry must connect to gameplay relevance or setting texture. | Prevents lore bloat that serves nobody. If it doesn't affect gameplay or atmosphere, it doesn't need an entry yet. |
---
## Part 8: IP Originality Audit (Round 2)
After reading all Round 1 outputs, I'm doing a second IP pass on everything proposed:
| Element | Source Risk | Assessment |
|---|---|---|
| "The Last Shift" (bar name) | Generic working-class bar name | **Clear.** No franchise association. |
| NPC names (Kael, Voss, Lera, Torek, etc.) | Constructed for Krenn System | **Clear.** Checked against Hamilton (contemporary English), Banks (Culture names), Reynolds (Dutch/Germanic). No overlap. |
| Unlicensed lattice components as contraband | Setting-specific | **Clear.** "Aftermarket neural implant mods" is common SF but our specific lattice/Commission framework makes it original. |
| "The Arrangement" (smuggling ring name) | Generic, possibly echoes John le Carre | **Watch.** Not a direct copy, but le Carre uses similar understated espionage terminology. Acceptable for now — it's an in-universe informal name, not a title. If it starts feeling too spy-novel, we rename. |
| Krenn System naming convention | Constructed | **Clear.** Consonant-heavy, compact names don't map to any specific franchise. |
| The span gate hum as atmospheric element | Setting-specific | **Clear.** Gate hum is a natural consequence of the technology. No franchise owns "infrastructure makes noise." |
| "Quotidian-with-undertow" as mood descriptor | Literary, not franchise-specific | **Clear.** This is a design note, not in-universe text. |
| Paula's NPC relationship web structure | Narrative architecture | **Clear.** Triangle dynamics are a storytelling tool, not franchise IP. |
| The Commission as regulatory body | Setting-specific | **Clear.** "Government regulates neural technology" is a natural worldbuilding consequence. Checked against Eclipse Phase (Firewall is different), Altered Carbon (Protectorate is different). Our Commission's specific mandate is original. |
| Araminta's relationship-to-player color system | Game design, not worldbuilding | **Clear.** Standard game design technique. |
**No IP concerns flagged in Round 2.** The team is building on established original foundations. The Krenn System and Sova Transit District feel like our own.
---
## Part 9: Synthesis — What Happens Next
### Miri's Immediate Deliverables (ordered by dependency urgency)
| Deliverable | Priority | Unblocks | Est. Effort |
|---|---|---|---|
| 1. Contraband Specification | Critical | Paula's NPC motivations, Mellanie's cargo dialogue | Small — 1-2 pages, can write now |
| 2. Sova Texture Appendix | Critical | Mellanie's environmental text, monologue sensory content | Small — 1 page |
| 3. Wiki Structure + First Entries | Critical | Entire content pipeline's organizational foundation | Medium — structure is defined above; first entries are Krenn System, Station Sova, Sova Transit District |
| 4. Krenn System Profile | High | Wiki foundation, all downstream location entries | Medium — first wiki entry, sets template precedent |
| 5. NPC Name Finalization | High | Paula's relationship web, Mellanie's voice kits | Small — mapping in Part 2 above, needs team sign-off |
| 6. Detective Chain of Command | High | Paula's detective character build, detective voice kit | Medium — institutional worldbuilding required |
| 7. Span Gate Transit Schedule | Medium | NPC routine design, ring operational timing | Small — 1 page |
| 8. Meridian Coverage Map | Medium | Investigation mechanics, ring operational geography | Small — 1 page |
| 9. Off-Station Connections Brief | Medium | Ring NPC dialogue consistency | Small — 0.5 page |
### Key Dependencies Resolved
1. **Contraband question:** Resolved. Unlicensed lattice components as primary, with medical-grade neural replacements as the humanitarian dimension.
2. **NPC names:** Mapped to Paula's 15-NPC structure with setting-consistent Krenn System names.
3. **Sova serves all team needs:** Validated against every Round 1 participant's specific requirements.
4. **Wiki structure:** Proposed, with templates, metadata schemas, and governance rules.
### One Last Setting Note
Sova Transit District is a deliberately ordinary place. It's a freight hub where people work, drink, gossip, and try to get by. The extraordinary thing about Sova is not its setting — it's what happens when you look at it through the wrong eyes.
The smuggler sees home. The detective sees a crime scene. Neither is wrong. Both are incomplete.
That's the game. And that's why the setting work matters: if Sova doesn't feel real, the dual lens has nothing to refract.
---
*Setting note — Krenn System is now canonical. Sova is grounded. The wiki has a skeleton. Let's build.*
*Miri out.*
docs/workshops/content-gap-analysis_v0_1/round2-ozzie.md
-452
View File
@@ -1,452 +0,0 @@
# Round 2: Ozzie — Player Experience Synthesis
## v0.1 Content Gap Analysis Workshop
**Agent:** Ozzie (Player Experience & Wow Factor)
**Date:** 2026-02-11
**Inputs:** All 6 Round 1 outputs + project lead direction on audio, THE FRIEND, color system, wiki
---
## Reactions to Round 1 Outputs
Before I get into the structured work, here's what hit me reading the other five.
### Miri: I'm IN
Sova Transit District. THE LAST SHIFT. The span gate hum. "Quotidian-with-undertow."
Miri, you gave me goosebumps. The setting brief is the single most important output from Round 1, because it turns every other agent's proposals from abstract to CONCRETE. When Mellanie talks about a dock worker greeting, I can now HEAR it in the corridors of Sova. When Paula designs the worried partner triangle, I can SEE H sitting alone at The Last Shift, watching the door.
The span gate hum as atmospheric anchor is EXACTLY right. That constant low vibration is our Nostromo air recycler, our Ceres spin-drum rumble. When it changes, that's a player moment. When it STOPS, that's a wow moment. We'll come back to this in audio.
**One thing that surprised me:** The contraband being lattice components. That's GENIUS for the moral ambiguity and I didn't see it coming. The smuggler isn't moving drugs or weapons. They're moving ACCESS. They're a Robin Hood with cargo manifests. That makes the detective's investigation morally complicated in a way that pure criminal enterprise wouldn't. It makes the player's SECOND playthrough — as the character who opposes this — emotionally devastating. "Oh. I was the bad guy last time? Or was I the bad guy THIS time?"
THAT'S the game.
### Paula: The Relationship Web Is Terrifying (In a Good Way)
Seven triangles. Fifteen NPCs. Every single one connected to at least two others with tension, dependency, or deception. The cross-template informant triangle (N-D-G) as the mechanism for the ring's unraveling is structurally perfect.
But here's what actually stopped me cold: **The Worried Partner triangle (H-B-F).** H doesn't know what their partner B does after hours. F reassures H while protecting the operation. B is oblivious to the anxiety they're causing. That's not a conspiracy mechanic. That's a HUMAN STORY. And the player who discovers it — whether as smuggler or detective — is going to feel something real.
Paula's mirror moments are also exactly what I was groping toward in Round 1 when I talked about "emotional divergence moments." Mirror 3 (The Worried Partner) and Mirror 4 (The Empty Corridor) are going to be the moments players tell their friends about.
**What aligned:** Paula and I converged independently on the idea that the emotional centerpiece is a relationship that gets contaminated by information. I called it THE FRIEND. She designed the structural web that makes THE FRIEND possible.
**What worried me (Round 1):** The Tier 1 full profiles are 1 page each. Five pages for five NPCs. That sounds like a lot but Paula's Layer 5 relationship web is SO detailed that it basically writes itself. I'm no longer worried about this being a bottleneck.
### Mellanie: The Line Counts Are Real
900-1,215 authored lines. ~3,000-3,600 after generation expansion. That's the content floor for a 30-minute session where the player encounters ~150-200 lines.
What I love about Mellanie's breakdown is the SPECIFICITY. She didn't say "we need dialogue." She said "15-20 greeting lines, filtered by access tier and relationship." She broke #190 into five concrete sub-deliverables (role voice kits, situation scripts, monologue hooks, environmental text, trait guide). She proposed the tag taxonomy BEFORE Gestalt did and they converged on nearly identical structures. That's confidence-building.
**What surprised me:** Mellanie's recommendation to DEFER audio and carry the atmosphere through text. She's not wrong that she CAN carry it. But — and this is why the project lead's decision matters — text-carried atmosphere is a backup plan, not the plan. With audio confirmed for v0.1, Mellanie's monologue load actually gets LIGHTER. The station hum carries ambient mood. Footsteps carry spatial presence. The monologue chime trains attention. Mellanie writes the CHARACTER. The audio carries the WORLD.
"Scaffold, validate, scale" is the right process. I trust her completely on the writing side.
### Araminta: Color = Relationship to Player
YES. This is the visual system that sells asymmetric information at MINIMUM fidelity.
The same NPC is green for the smuggler and teal for the detective. Same room, different visual reality. That's our core mechanic rendered in the cheapest possible way, and it WORKS.
The fog rendering spec (visible / fog-edge / hidden / remembered) is also load-bearing. The "remembered" state — desaturated, static snapshot, NPCs vanished — is the visual representation of "I was here, but things may have changed." That communicates information decay without a single word of text. When the player returns and sees that things HAVE changed, that's a discovery moment.
**What aligned:** Araminta and I both identified the same gap — the need for ONE signature visual element in the first 5 seconds. She's proposing to solve it through spatial composition (the bar feels different from the hub through room shape and density). I was thinking about a viewport showing stars. Both can work. Both should exist.
**What I'd push back on:** Araminta recommends deferring audio entirely. The project lead has overruled this. Audio is IN. Araminta's sound indicator visual spec is still needed — we'll want visual indicators for sounds at fog edge even WITH audio, because audio communicates "something's there" and visuals communicate "where."
### Gestalt: The Pipeline Is Ready for Content
The YAML line pool format is clean. The selection pipeline (access filter -> situation filter -> trust filter -> mood+topic weighting) is elegant. The monologue trigger taxonomy (9 trigger types) maps directly to authoring work.
Gestalt said something in Layer 6 that I want to amplify: **"Most tells in v0.1 will be TEXT, not visual. The monologue system IS the tell renderer."** This is exactly right. We can't animate fidgeting on colored rectangles. But we CAN write "Kael keeps checking the corridor before entering the back room" and that tells the player everything they need to know.
The line previewer (#193) also got flagged by both Gestalt and Mellanie as critical. I agree — it's not a content deliverable, it's a content QUALITY tool. Without it, we ship content that reads well in YAML and sounds dead in the game.
---
## Section 1: Missing Tickets for Player Experience Work
Reading all six Round 1 outputs, I'm tracking these gaps that don't have tickets and should:
### Tickets That Must Exist
| # | Title | Priority | Type | Rationale |
|---|-------|----------|------|-----------|
| NEW-1 | **THE FRIEND NPC — Smuggler version (full production)** | Critical | Story | One deeply authored NPC for the smuggler's playthrough. Full profile, full voice kit, full contradiction arc. Project lead confirmed: one production-level NPC per character. Emotional centerpiece of v0.1. |
| NEW-2 | **THE FRIEND NPC — Detective version (full production)** | Critical | Story | Same treatment for the detective. Different NPC, different relationship, different contradiction. Must hit the same emotional beats through a different lens. |
| NEW-3 | **Opening 5-minute content sequence (per character)** | Critical | Story | The first 20 monologue lines, the first named NPC encounter, the first news ticker glance, the first environmental text read. Tightly sequenced. This IS the first impression. Blocks all playtest feedback. |
| NEW-4 | **Audio asset set — minimum viable (6-8 files)** | High | Story | Station ambient, 3 location variants, footsteps, monologue chime. AI-generated via local model. See Section 4 below for full spec. |
| NEW-5 | **News ticker / announcement board content** | High | Story | 20-30 ticker lines for The Last Shift and the logistics hub. Cheapest wow-per-word in the project. |
| NEW-6 | **Diegetic insert flavor text (per character)** | Medium | Story | POI labels, status text, notification strings — different per character. The smuggler's insert says "The Last Shift." The detective's says "Licensed establishment — District 7." |
| NEW-7 | **Flat NPC "almost interesting" pass** | High | Story | The 4-5 flat NPCs each need: one memorable trait, one "seems important but isn't" line, and a visible routine. Without this, the investigation noise floor collapses. |
| NEW-8 | **First monologue surprise moment (per character)** | High | Story | The specific monologue line where the character notices something the player didn't. Must fire before minute 15. This is our signature mechanic in content form. Requires coordination between Paula (the observation), Mellanie (the line), and Gestalt (the trigger). |
| NEW-9 | **Spatial layout review — sightlines for wow moments** | Medium | Story | Araminta's spatial layouts need a player experience pass. Where does the player FIRST see the bar? Where do they FIRST glimpse the restricted area? First impressions of each space shape the entire experience. |
### Tickets Proposed by Others That I'm Co-Signing
| Proposed by | Ticket | My endorsement |
|---|---|---|
| Mellanie | Smuggler voice kit | YES — blocks everything. Character voice is the foundation. |
| Mellanie | Detective voice kit | YES — same. |
| Mellanie | Monologue starter set (universal) | YES — unblocked, should start NOW. |
| Mellanie | Tag taxonomy specification | YES — Gestalt has already drafted this. Validate and lock. |
| Paula | Dual Lens Guide (full draft) | YES — the single most important document. Everything downstream needs it. |
| Araminta | v0.1 Visual Grammar | YES — root dependency for all visual work. |
| Araminta | Entity color system implementation | YES — this IS the visual proof of concept for asymmetric information. |
| Araminta | Spatial layout design (3 sites) | YES — sightlines are gameplay, not decoration. |
| Gestalt | Line previewer CLI (#193) | YES — content quality tool. Mellanie can't test without it. |
---
## Section 2: Priority Ranking — Content Gaps That Hurt Most
Here's my ranking of which gaps, if left unfilled, would DESTROY the player experience. Not "slightly diminish." DESTROY.
### Tier 1: The Game Doesn't Exist Without These (Sprint 2 must-haves)
1. **Character voice kits + Dual Lens Guide** — If the two characters sound the same or interpret the world the same way, there IS no game. The dual-lens is the premise. No voice = no premise.
2. **THE FRIEND (one per character)** — D-027 success criterion #3: "player names an NPC they felt conflicted about." Without THE FRIEND, we have a technically competent social simulation with no emotional anchor. The FRIEND is the moment the game stops being a system and starts being a story.
3. **Opening 5-minute content** — If the first 5 minutes are flat, no playtester finishes the 30. The opening monologue, the first named face, the first environmental text — these ARE the game's first impression. They must exist before any playtesting happens.
4. **Monologue observation lines (pre-contamination)** — The character noticing what the player didn't. This is the core mechanic expressed as content. If the monologue only fires atmosphere lines and never flags something specific about an NPC's behavior, the investigation has no foothold.
### Tier 2: The Game Feels Empty Without These (Sprint 2 high priority)
5. **Flat NPC "almost interesting" pass** — If flat NPCs are obviously wallpaper, the 30/50/20 ratio is exposed and investigation collapses. The noise floor must be indistinguishable from signal at first glance.
6. **Audio asset set (6-8 files)** — Confirmed in scope. The difference between silence and a station hum is the difference between "spreadsheet" and "world." See Section 4.
7. **News ticker / environmental text** — 20-30 lines that make the station breathe. Cheapest content investment, highest presence return.
8. **Template content packs (#190-192)** — The bulk dialogue that populates the social sites. Without these, the player talks to NPCs and gets nothing back.
### Tier 3: The Game Feels Rough Without These (Sprint 2/3 medium priority)
9. **Mirror moments (10-15 paired observations)** — The second playthrough's "oh THAT'S what that was" beats. Essential for replayability, but the first playthrough works without them.
10. **Diegetic insert flavor text** — Character-specific HUD text. Sells the dual-lens through the UI layer. Not needed for first playtest but needed before the experience feels polished.
11. **Spatial layout wow-moment pass** — First impressions of each location. Can be adjusted after initial layouts exist.
12. **UI microcopy** — Menu text, interaction prompts, save/load. Functional placeholder strings are fine for early playtests.
---
## Section 3: THE FRIEND — The Emotional Centerpiece
Project lead confirmed: one production-level NPC per character. Full depth. This is the emotional centerpiece of v0.1.
Good. Now let me define what "full depth" means for player experience. Not the narrative structure (that's Paula). Not the line count (that's Mellanie). The FEELING.
### What THE FRIEND Must Deliver
THE FRIEND is the NPC designed to make the player answer "yes" to D-027 success criterion #3: **"Name an NPC you felt conflicted about."**
That means THE FRIEND must produce, in sequence:
1. **Warmth** — The player must genuinely LIKE this NPC before anything goes wrong.
2. **Trust** — The player must rely on this NPC for something practical or emotional.
3. **Doubt** — One observed contradiction must crack the trust.
4. **Conflict** — The player must want two incompatible things: to trust them AND to know the truth.
If any of these four beats is missing or weak, the criterion fails. Let me get specific.
### THE FRIEND: Smuggler Version
**Who:** The smuggler's closest colleague at the logistics hub. They share shifts, they cover for each other, they eat lunch together. This is the person who makes the smuggler's double life BEARABLE. When the operation feels dangerous, this friend makes it feel manageable.
Mapped to Paula's web: this is **NPC-B** — the logistics worker who's a reliable ring member. The smuggler's anchor.
**The warmth beat (minutes 1-10):**
- THE FRIEND greets the smuggler by nickname within the first 2 minutes of the game.
- THE FRIEND covers for the smuggler on something small and mundane — takes over a manifest check, brings them a drink, warns them about the supervisor's mood.
- Monologue fires: something affectionate, familiar, comfortable. *"Kael's got my back. He always does."*
- THE FRIEND's dialogue is warm, easy, uses insider language. Layer 1 access = peer. Layer 3 trust = real (they share genuine conversation from the start).
**The trust beat (minutes 5-15):**
- THE FRIEND is useful. They tell the smuggler something they need to know — a shift change, a cargo update, who's asking questions.
- THE FRIEND demonstrates loyalty. They deflect when someone asks where the smuggler was during a gap in their schedule.
- Monologue fires: trust confirmation. *"If everything went sideways, Kael's the one I'd call."*
**The contradiction beat (minutes 20-25, during or shortly after contamination):**
- The smuggler observes THE FRIEND in a place they shouldn't be. Not the ring spaces — that would be expected. Somewhere ELSE. A section of the station with no ring business. Near the Commission kiosk. Near the detective's known area. Or meeting with someone from outside the district — NPC-M (the fence/buyer) at a strange time, or someone the smuggler has NEVER seen.
- The observation must be VISUAL — the smuggler SEES it, not hears about it. The monologue fires IMMEDIATELY: *"What's Kael doing near the Commission terminal? He's got no business there."*
- If the smuggler asks THE FRIEND about it, THE FRIEND deflects. Casual. Maybe too casual. *"Oh, just checking the freight schedule on the public board. You know me."*
- Monologue fires after the deflection: *"That wasn't the freight schedule board. That was the compliance office entrance."*
- THE FRIEND LIED. To the smuggler's face. And now every warm interaction is CONTAMINATED.
**The conflict beat (minutes 25-30+):**
- The smuggler is now watching THE FRIEND. Every routine action has a shadow. Is Kael still reliable? Is Kael talking to the detective? Is Kael cutting a deal? Is Kael trying to LEAVE the ring?
- But also: Kael is still kind. Still covers for you. Still brings you a drink. The contradiction isn't resolved. The player wants to confront AND to protect.
- D-027 criterion fires: "Name an NPC you felt conflicted about." The player says "Kael."
**Why this works:** The contradiction isn't a betrayal — it's AMBIGUITY. Maybe Kael IS cutting a deal. Maybe Kael is protecting the smuggler by keeping them out of something dangerous. Maybe Kael is trying to leave and doesn't know how to tell the smuggler. The player doesn't know. They CAN'T know in 30 minutes. And that unresolved ambiguity is what makes them FEEL something.
### THE FRIEND: Detective Version
**Who:** The detective's contact in the district. Not a formal informant — someone who offered help when the detective arrived. Maybe they work at the logistics hub, maybe they're a bar regular. They've been the detective's GUIDE to this unfamiliar place — explaining who's who, which areas to check, how things work around here.
Mapped to Paula's web: this could be **NPC-D** (the dock inspector with the gambling debt) or a new NPC designed specifically for this role. I'd argue for NPC-D — someone who has legitimate authority AND a vulnerability.
**The warmth beat (minutes 1-10):**
- THE FRIEND approaches the detective early. Offers help. *"You look like you could use a map. I'm Drin. I know this place."*
- THE FRIEND is genuinely helpful. Accurate information. No obvious agenda. They point out useful things: where the bar is, when the shift changes happen, who the supervisor is.
- Monologue fires: cautious appreciation. *"Helpful. Maybe too helpful. But the information checks out."*
**The trust beat (minutes 5-15):**
- THE FRIEND provides intel the detective can verify. A tip about an NPC's routine that turns out to be accurate. A warning about a corridor that's usually watched.
- THE FRIEND shows vulnerability — mentions the card game debt (if it's NPC-D), or talks about personal struggles. They become HUMAN, not just a source.
- Monologue fires: warming. *"Drin's solid. Not the usual reluctant-witness type. Maybe they actually want this district cleaned up."*
**The contradiction beat (minutes 20-25):**
- The detective observes THE FRIEND behaving inconsistently with their stated motivations. For NPC-D: they're seen meeting privately with NPC-A (the supervisor who's taking a cut from the ring). The meeting is brief, tense, and ends with THE FRIEND looking agitated.
- Monologue: *"Ana met with the shift supervisor. Off-record. In the maintenance corridor, not the office. Why?"*
- If the detective asks THE FRIEND, they deflect. *"Just sorting out some scheduling issues. You know how it is."*
- Monologue after: *"Scheduling issues don't make you look like that."*
- THE FRIEND's information has been good. But THE FRIEND has connections they're not disclosing. And now the detective wonders: was the help GENUINE, or was it STEERING? Were they being guided toward certain things and AWAY from others?
**The conflict beat (minutes 25-30+):**
- The detective realizes: if THE FRIEND is compromised, then some of the "helpful" intel might have been curated. Not false — but SELECTIVE. Showing the detective the small stuff to hide the big stuff.
- But also: THE FRIEND's personal vulnerability was real. The stress was real. Maybe they're TRAPPED, not malicious.
- D-027 criterion fires: "Name an NPC you felt conflicted about." The player says "Drin."
### What Both Versions Share
1. **The contradiction is OBSERVED, not told.** The player sees it. The monologue interprets it. The FRIEND deflects when asked. This is our core mechanic — observation + monologue + social interaction — working in concert.
2. **The contradiction activates during or shortly after contamination.** This is the emotional bridge between daily-life (warmth, trust) and investigation (doubt, conflict). The FRIEND's contradiction IS the contamination hitting home.
3. **The contradiction is AMBIGUOUS.** THE FRIEND might be a traitor. They might be a victim. They might be trying to HELP in a way the player can't see yet. The 30-minute vertical slice ends before resolution. The player is left with doubt, not answers.
4. **THE FRIEND requires production-level content.** Full voice kit. Custom dialogue for all four layers. Specific monologue lines for each beat. Environmental staging (they need to BE in the wrong place at the right time). This is NOT a template NPC with extra lines — it's a fully authored character.
### Content Requirements for THE FRIEND
| Content type | Per FRIEND NPC | Total (x2) |
|---|---|---|
| Custom dialogue lines (all 4 layers) | 25-35 | 50-70 |
| Character-specific monologue reactions | 15-20 | 30-40 |
| Contradiction observation trigger setup | 2-3 events | 4-6 events |
| Deflection dialogue (when asked about contradiction) | 3-5 lines | 6-10 lines |
| Post-deflection monologue | 3-5 lines | 6-10 lines |
| Daily routine (authored, not generated) | 1 schedule | 2 schedules |
| Voice kit (full production) | 1 page | 2 pages |
| **Total custom lines** | **~50-65** | **~100-130** |
This is a LOT of content for two NPCs. But these two NPCs carry D-027 criterion #3. They're the emotional centerpiece. The investment is proportional to the payoff.
**Owners:** Paula designs the arc. Mellanie writes the voice. Gestalt defines the triggers. Ozzie validates the FEELING.
---
## Section 4: Audio Assets — The Concrete Spec
Project lead confirmed: audio is IN for v0.1. Minimum viable: station ambient, 3 location variants, footsteps, monologue chime. 6-8 files. AI-generated via local model.
Here's the full spec. Every file, what it does, and where it plays.
### The Audio Asset List
| # | File name | Type | Duration | Description | Where it plays | Why it matters |
|---|-----------|------|----------|-------------|---------------|----------------|
| 1 | `amb_station_base.ogg` | Ambient loop | 60-90s | Low-frequency station hum. The span gate's subsonic vibration. Ventilation. Distant machinery. This is the sound of Sova Transit District EXISTING. | **Everywhere.** Global ambient. Plays from game start, never stops. | The "you're on a space station" signal. Ozzie's #1 priority. Without this, the world is a boardgame. With it, the world BREATHES. |
| 2 | `amb_workplace_layer.ogg` | Ambient overlay | 45-60s | Cargo machinery. Grav-lift hum. Scanner pings. Manifest terminal beeps. Distant crew voices (unintelligible). Layered on top of base ambient. | **Logistics hub** — fades in on entry, fades out on exit. | The workplace SOUNDS like work. Industrial, purposeful. Creates contrast with the bar's warmth. |
| 3 | `amb_bar_layer.ogg` | Ambient overlay | 45-60s | Muffled conversation murmur. Glass on surface. A Meridian music feed (low, indistinct — just the bass). Occasional laughter. | **The Last Shift** — fades in on entry, fades out on exit. | The bar is ALIVE. Social. Warm. When it's quiet (late night, bad day), the absence of these sounds IS information. |
| 4 | `amb_corridor_layer.ogg` | Ambient overlay | 45-60s | Echoing footsteps (not the player's — distant NPCs). Ventilation whistle. The span gate hum is louder here — less insulation. A distant door closing. | **Corridors, maintenance areas, restricted sections.** | The lonely spaces between social sites. This is where tension lives. The echo makes you feel small and exposed. |
| 5 | `sfx_footstep_metal.ogg` | SFX, looping | 0.3-0.5s | Single footstep on metal grating. Clean, defined. Not heavy — working boots on station decking. | **Player movement.** Triggers on walk. Pitch-shifted slightly each step for variation. | The single highest bang-for-buck audio asset in any game. Your feet on the deck. You are HERE. You are PHYSICAL. |
| 6 | `sfx_footstep_metal_run.ogg` | SFX, looping | 0.2-0.3s | Faster footstep. Slightly louder. Urgent. | **Player run.** Triggers on run speed. | Running should SOUND different than walking. The urgency sells the moment. |
| 7 | `sfx_monologue_chime.ogg` | UI SFX | 0.5-1.0s | A soft, crystalline tone. Not a notification bell — something subtler. A gentle harmonic that suggests "an insight is forming." Think: a neural lattice firing. Not mechanical. Organic-digital hybrid. | **Monologue appearance.** Triggers when a new monologue line fades in. | This trains the player to NOTICE monologue. It becomes Pavlovian: chime = your character is thinking = pay attention. Without it, monologue text appears silently and gets missed. THIS SOUND IS THE GAME'S SIGNATURE. |
| 8 | `sfx_monologue_chime_urgent.ogg` | UI SFX | 0.5-1.0s | Same harmonic base as #7 but with a sharper attack, slightly discordant overtone. The "your character noticed something IMPORTANT" variant. | **Observation monologue.** Triggers when the monologue flags a contradiction, anomaly, or THE FRIEND's suspicious behavior. | Two chime variants: normal thinking and "WAIT, WHAT." The player learns the difference unconsciously. When the urgent chime fires during THE FRIEND's contradiction beat, the player's stomach drops before they even read the text. |
**That's 8 files.** 6 ambient/overlay + 2 SFX.
### Audio Technical Notes
- **Format:** OGG Vorbis. Godot's preferred compressed audio format. Good quality at small file sizes.
- **Generation:** AI-generated via local model on Mac or Linux server (per project lead). Suggest: stable-audio or audioldm2 for ambient, basic synthesis for SFX.
- **Looping:** Ambient files must loop seamlessly. Design with fade-in/fade-out tails that cross-fade at loop point.
- **Mixing:** Base ambient at -20dB (barely conscious). Location overlays at -15dB (audible but not dominant). Footsteps at -10dB (present, grounding). Monologue chime at -8dB (catches attention without startling).
- **Integration point:** The sound event system (#124) emits events. The client audio manager receives events and plays the appropriate file. If no file exists for an event type, fall back to visual indicator. This means audio is ADDITIVE — remove any file and the game still works through text + visuals.
### What's NOT in the 8-file minimum
- NPC-specific audio (voices, unique sounds) — deferred to later
- Door sounds, scanner sounds, cargo sounds — atmospheric but not essential
- Music — no music in gameplay, per Araminta's recommendation (which I support)
- Three-range directional audio (muffled voices through walls, distant conversations) — system architecture supports it, content deferred
- Span gate transit event sound — would be amazing but is a milestone feature, not v0.1
### The Monologue Chime Is Non-Negotiable
I want to emphasize this. If we ship 8 files, 7 of them could be ambient loops and the 8th MUST be the monologue chime. The chime is our tutorial. It's our attention director. It's the audio equivalent of Araminta's eye-icon observation marker. It says "YOUR CHARACTER IS THINKING" before the player consciously processes the text.
Two variants (normal + urgent) is ideal. If we can only do one, make it the normal chime. The urgent variant can come later.
---
## Section 5: The "Wow Moment" Budget
Every game has a limited number of moments that make the player go "WHOA." In a 30-minute vertical slice, we get maybe 4-5 of these. Spend them wisely. Spend them wrong and the game is forgettable.
Here's my wow moment budget for v0.1, ordered chronologically through the 30-minute session:
### The Essential Wow Moments (MUST hit in v0.1)
**Wow Moment #1: Arrival (minute 0-1)**
> The game starts. The station hum is already playing. The player sees their hab unit / starting location. NPCs are already moving — the world was here before them. Their first monologue line fires with a soft chime. They read it. They're a PERSON in a PLACE.
- **What delivers it:** Audio (station hum) + NPC movement + monologue chime + first monologue line
- **Content required:** Opening monologue sequence, station ambient audio, pre-populated NPC routines
- **Emotional target:** Curiosity, grounding. "Where am I? This feels real."
**Wow Moment #2: The Character's Eye (minute 5-15)**
> The player walks into The Last Shift. They see NPCs. The monologue fires: "Riks is at his usual table. But he's not drinking. He's watching the door." The player didn't notice this. Their CHARACTER did. The player looks at Riks with new eyes.
- **What delivers it:** Observation monologue with the urgent chime variant. An NPC whose behavior was VISUALLY present but not obviously remarkable.
- **Content required:** Observation monologue lines (Mellanie), NPC routine with observable deviation (Paula/Gestalt), urgent monologue chime (audio)
- **Emotional target:** Surprise, respect for the character. "My character is smarter than me."
**Wow Moment #3: THE FRIEND's Contradiction (minute 20-25)**
> The smuggler sees Kael near the Commission terminal. Or the detective sees Drin meeting the supervisor in the maintenance corridor. The urgent chime fires. The monologue: "What's Kael doing there?" The player asks. Kael lies. The monologue knows it's a lie.
- **What delivers it:** THE FRIEND's full contradiction arc (see Section 3). Audio urgency chime. Visual positioning (THE FRIEND must be in the WRONG place for the player to SEE them there).
- **Content required:** Full FRIEND content package. Spatial staging. Specific monologue for the observation, the question, and the aftermath.
- **Emotional target:** Dread, betrayal, conflict. "I trusted you. What are you doing?"
**Wow Moment #4: The Divergence Reveal (second playthrough, minute 5-10)**
> The player starts their second character. They walk into the same logistics hub. But it's DIFFERENT. The colors are different (Araminta's relationship color system). The names are different (the detective sees "Worker" where the smuggler saw "Kael"). The monologue is different (analytical vs. familiar). Same room. Different world. The player realizes: "Oh. I was only seeing HALF of this."
- **What delivers it:** The dual-lens system working in concert across ALL layers. Entity colors. Access tiers. Character voice. Insert text.
- **Content required:** All dual-lens content for the logistics hub. Both character voice kits. Both opening sequences.
- **Emotional target:** Revelation, awe. "THE GAME IS DOING SOMETHING I'VE NEVER SEEN."
### The Nice-to-Have Wow Moments (target for v0.1, survive without)
**Wow Moment #5: The News Ticker Gut-Punch**
> The smuggler is at The Last Shift. The news ticker scrolls: "Commission advisory: increased cargo inspections at logistics hubs system-wide." Monologue: "...That's not good."
> The detective sees the same ticker. Monologue: "About time."
- **What delivers it:** Environmental text + dual-lens monologue response
- **Content required:** Ticker content (Mellanie), dual monologue reactions, ticker display system
- **Emotional target:** The same information hits differently. The asymmetry in THREE WORDS of monologue.
**Wow Moment #6: The Quiet Moment**
> Late in the session. The player is alone in a corridor. The station hum is the only sound. The monologue fires, unprompted: "Sometimes I wonder if it's worth it." (Smuggler) / "Sometimes I forget why I started doing this." (Detective)
> A moment of vulnerability. The character is a person, not just a lens.
- **What delivers it:** Time-idle monologue trigger. Audio ambience (corridor layer). Character voice depth.
- **Content required:** Reflective monologue lines (Mellanie). Time-idle trigger (Gestalt).
- **Emotional target:** Connection. Empathy. "I care about this person."
### The Wow Budget Summary
| Moment | Essential? | Content load | Risk if missing |
|---|---|---|---|
| #1 Arrival | YES | Low (audio + 3-5 lines) | Game feels dead from second 1 |
| #2 Character's Eye | YES | Medium (observation system + lines) | Core mechanic unproven |
| #3 FRIEND Contradiction | YES | HIGH (full NPC package) | D-027 criterion #3 fails |
| #4 Divergence Reveal | YES (2nd playthrough) | HIGH (dual-lens across all systems) | Replayability argument collapses |
| #5 Ticker Gut-Punch | Nice-to-have | Low (ticker + 2 lines) | Missed opportunity, not fatal |
| #6 Quiet Moment | Nice-to-have | Very low (2 monologue lines) | Character depth feels thin |
Four essential, two stretch. That's the budget.
---
## Section 6: Cross-Agent Alignment & Worries
### Where Everyone Converged (High Confidence)
- **Dual Lens Guide is the root dependency.** All six of us identified this. Paula writes, everyone else consumes. Nothing starts until it exists.
- **The monologue is the game.** Gestalt, Mellanie, and I all agree: the monologue carries perception, tells, atmosphere, tutorial, and character voice. It's the hardest-working system in the project.
- **Color = relationship to player.** Araminta proposed it. Project lead approved it. I am thrilled. This IS asymmetric information rendered visually.
- **YAML for line pools.** Mellanie proposed it. Gestalt refined it. No disagreement. Lock it and go.
- **Spatial layout matters.** Araminta's sightline diagrams and my "first impression" approach are the same concern from different angles. The bar should be entered from a specific direction that shows you a specific view first.
- **Miri's setting is the substrate.** Everyone is building on Sova Transit District. The naming, the economics, the atmosphere — it's all load-bearing now.
### Where I Disagree or Have Concerns
**1. Mellanie wanted to defer audio. Project lead overruled.**
Mellanie said she can carry atmosphere through text alone. She CAN. But text-carried atmosphere is the fallback, not the plan. With the monologue chime in place, Mellanie's observation lines hit HARDER. Audio and text are multiplicative, not competitive. The chime primes the player's attention. The text delivers the insight. Together they're more than either alone.
**2. Araminta wanted to defer audio entirely. Also overruled.**
Same reasoning. But Araminta's visual sound indicators are still needed alongside audio — the fog-edge ripple that shows sound direction is visual information that audio alone can't communicate in a top-down view.
**3. Paula's relationship web may be too complex for v0.1.**
Seven triangles across 15 NPCs is structurally beautiful. But can we actually populate all seven with authored content in time? My instinct says: build the web, but prioritize content for the triangles the player is MOST LIKELY to encounter in 30 minutes. The Worried Partner (H-B-F) and The New Hire Problem (B-C-A) are the highest-impact mundane triangles. The Wavering Member (K-N-L) is the highest-impact entangled triangle. Start there. Fill the others as time allows.
**4. Gestalt's 4x generation expansion worries me for monologue.**
Dialogue generation (write 10, expand to 40) works because dialogue is situational and fungible. Monologue generation is riskier — the character's PRIVATE THOUGHTS need to feel specific and authored, not templated. Mellanie flagged this too: "I'd estimate a 2x generation pass on monologue at best." I agree. Budget for 2x on monologue, 4x on dialogue. Don't let generated monologue flatten the character voice.
**5. The line previewer (#193) needs to exist before content is "done."**
Both Gestalt and Mellanie flagged this. I'm escalating it: without the previewer, we can't test the FEEL of content. We can read YAML. We can check tag coverage. But we can't experience the rhythm of monologue lines firing in sequence, the pace of dialogue encounters, the feeling of walking through the bar while text populates the world. The previewer is our only pre-integration quality tool. It should be Sprint 2.
### What I'm Most Worried About
**Repetition in a 30-minute session.** Mellanie estimates the player encounters ~150-200 lines per playthrough. With ~3,000-3,600 total lines after expansion, that's a 5-7% utilization rate per session. Sounds fine. But monologue is different — the player might enter the logistics hub 4-5 times in 30 minutes. If they get the same "Busy morning" line twice, the spell breaks. We need DEPTH in high-frequency triggers (enter_location, observe_npc) and can get away with less variety in low-frequency triggers (discover_evidence, witness_interaction).
**The 30-minute runway before contamination.** D-027 says 30 minutes of daily life before the conspiracy activates. I championed this. I still believe it. But 30 minutes of UNCONTAMINATED daily life needs to be genuinely engaging — not "waiting for the plot to start." This is where the mundane triangles, THE FRIEND's warmth phase, the news ticker, and the monologue observation system all need to fire. If even one of those is thin, the first 20 minutes feel like a waiting room.
---
## Section 7: Dependency Chain (Player Experience View)
Here's the order things need to happen from a "when does the player experience come alive" perspective:
```
WEEK 1-2: Foundation
Paula: Dual Lens Authoring Guide (THE critical path document)
Miri: Finalize Sova setting details (contraband specifics, detective chain of command)
Gestalt: Lock tag taxonomy + line pool format
Audio: Generate amb_station_base.ogg + sfx_monologue_chime.ogg (the two most important files)
WEEK 2-3: Character Voice
Mellanie: Smuggler voice kit + Detective voice kit
Paula: THE FRIEND profile (smuggler version) + THE FRIEND profile (detective version)
Araminta: Visual Grammar doc + Entity color system spec
WEEK 3-4: Opening Experience
Mellanie: Opening 5-minute content (both characters)
Mellanie: Monologue starter set (universal)
Mellanie: News ticker content (20-30 lines)
Audio: Generate remaining 6 files
Araminta: Spatial layouts (3 sites)
WEEK 4-6: Depth
Paula: Full NPC profiles (Tier 1 entangled first, then Tier 2, then Tier 3)
Mellanie: THE FRIEND full content package (both versions)
Mellanie: Template content packs (#190-192)
Mellanie: Flat NPC "almost interesting" pass
Gestalt: Line previewer (#193)
WEEK 6+: Polish
Paula: Mirror moment design pass
Mellanie: Observation monologue lines (tell-driven)
Mellanie: Diegetic insert flavor text
Ozzie: Playtest and gut-check
```
The player experience comes online at WEEK 4 — when we have character voice, THE FRIEND's warmth phase, and the opening 5 minutes working together. Everything before that is infrastructure. Everything after is depth and polish.
---
## The Bottom Line
Round 1, I said: "We need to write the moments, not just design them."
Round 2, I'm saying: **"We now know WHICH moments. Let's write THESE."**
Four essential wow moments. THE FRIEND at the center. Eight audio files. A monologue chime that becomes the game's heartbeat. An opening 5 minutes that makes the player forget they're looking at colored rectangles. A contradiction that makes them forget they're playing a game.
The team is aligned. The setting is concrete. The systems are ready. The content gaps are mapped and prioritized.
Let's fill the canyon.
---
*Written by Ozzie. Still from the gut. But now the gut has a spreadsheet.*
docs/workshops/content-gap-analysis_v0_1/round2-paula.md
-469
View File
@@ -1,469 +0,0 @@
# Round 2 — Paula's Narrative Synthesis
**Agent:** Paula (Narrative & Political Depth)
**Workshop:** v0.1 Content Gap Analysis — Round 2
**Date:** 2026-02-11
---
## What I Read and What Changed
I read all six Round 1 outputs. Here's what landed:
- **Mellanie** gave me exactly what I needed: a concrete authoring model (scaffold, validate, scale), a tag taxonomy that maps to my four dialogue layers, and a clear dependency chain back to my deliverables. She also confirmed what I suspected — separate monologue pools per character are non-negotiable. Jeroen has confirmed this. Good. That's the game.
- **Gestalt** translated my relational layers into a selection pipeline (hard filter, hard filter, soft selector, weighted selection). The entanglement math tracks with my 30/50/20 split, though Gestalt's NPC distribution proposal differs from mine in detail. I'll reconcile below.
- **Miri** delivered Sova Transit District. This is the setting I was waiting for. The economics/motivation chain works — I'll react in detail below. The naming conventions (Kael, Voss, Lera, Torek, Drin, Maret) are concrete enough to start writing relationship webs.
- **Ozzie** crystallized THE FRIEND concept. His emotional journey map (curiosity > grounding > comfort > attachment > unease > dread > investigation) is the template I need for the contradiction arc design. He's right that the contradiction must be discoverable through observation, not told through dialogue.
- **Araminta** confirmed color = relationship to player (Jeroen approved). This means the visual system directly expresses my access tier model — green/teal/amber/red maps to trusted/unknown/flagged/hostile. The fog rendering spec (visible/fog-edge/hidden/remembered) has narrative implications I'll address.
Three things changed from my Round 1 position:
1. **THE FRIEND is now a confirmed design requirement**, not a suggestion. Jeroen says: one production-level complex NPC per character, full pipeline depth. This elevates my relationship web work — two NPCs need to be designed at a completely different depth than the other 13.
2. **Audio is in v0.1 scope** (6-8 files, AI-generated). This means Mellanie doesn't need to carry 100% of the sensory atmosphere through monologue. Some of those sound-interpretation lines can be lighter.
3. **Wiki structure is non-negotiable and must be established NOW.** This has implications for how I organize NPC profiles and relationship data — it needs to be future-ready, not just v0.1-ready.
---
## 1. Missing Tickets Identified from Round 1
Reading all six outputs, I found content work that nobody has ticketed yet. Some of these were implied across multiple outputs but never explicitly called out as deliverables.
### Tickets that must exist
| Proposed Title | Type | Owner | Rationale | Dependencies |
|---|---|---|---|---|
| **THE FRIEND: Smuggler's Friend NPC — full profile + contradiction arc** | Story | Paula (profile) + Mellanie (voice) | Jeroen confirmed: production-level NPC. Full 10-axis, backstory, voice kit, dialogue set, tell system, contradiction arc. Pipeline depth test. | Dual Lens Guide, Setting brief |
| **THE FRIEND: Detective's Friend NPC — full profile + contradiction arc** | Story | Paula (profile) + Mellanie (voice) | Same as above, detective perspective. Different NPC, different contradiction, different emotional register. | Dual Lens Guide, Setting brief |
| **Contradiction arc design document** | Story | Paula | Defines how THE FRIEND's shift works mechanically: trigger conditions, monologue sequence, observable tells, dialogue changes pre/post discovery. Reusable pattern for future complex NPCs. | THE FRIEND profiles |
| **Opening hook content — smuggler (first 5 minutes)** | Story | Mellanie | Gestalt's opening-hook.yaml concept. 10-15 tightly sequenced monologue lines. The most important lines in the game. | Voice kits, Dual Lens Guide |
| **Opening hook content — detective (first 5 minutes)** | Story | Mellanie | Same for detective. Different emotional register, different tutorial pathway. | Voice kits, Dual Lens Guide |
| **Access tier shift design document** | Story | Paula + Gestalt | How access tiers change during gameplay. Gestalt flagged this in Round 1: tier shifts ARE the social gameplay. Need concrete shift paths per character per social site. | Dual Lens Guide |
| **News ticker content — Sova Transit District** | Story | Mellanie + Miri | 20-30 ticker lines. Ozzie and Miri both flagged this as high-value, low-cost. Needs Miri for setting consistency. | Setting brief |
| **Spatial layout design — Logistics Hub** | Story | Araminta | Floor plan, sightlines, NPC positions. Araminta proposed this. Layout affects what content makes sense — must be parallel with content packs, not after. | Setting brief |
| **Spatial layout design — Bar (The Last Shift)** | Story | Araminta | Same for bar. | Setting brief |
| **Spatial layout design — Smuggling spaces** | Story | Araminta | Same for ring spaces. | Setting brief |
| **Wiki taxonomy and structure** | Story | Miri + Qatux | Jeroen: non-negotiable, must be NOW. Full future-ready taxonomy: characters, factions, lore, star systems, technology, species, cultures, etc. Sova/Krenn is the first entry. | None — can start immediately |
| **Krenn System wiki entry** | Story | Miri | First concrete star system. Worldbuilding milestone. Establishes the pattern for all future system entries. | Wiki taxonomy |
| **Setting-grounded tag additions for line pools** | Story | Miri + Gestalt | Miri proposed lattice_tier, shift_phase, district_familiarity, institutional_context. These need to be validated against Gestalt's format spec and integrated. | Line pool format spec |
| **Monologue presentation spec** | Story | Araminta | Typography, animation, stacking, priority rules. Araminta defined this in Round 1 but it needs to be a spec document, not just workshop notes. | Visual Grammar |
| **Sound indicator visual spec** | Story | Araminta | Fog-edge indicators for the three-range model. Required even if audio exists — visual fallback for information. | Visual Grammar |
| **Diegetic tutorial monologue lines** | Story | Mellanie | Gestalt's diegetic tutorial concept needs actual authored lines. 8-10 per character, covering movement, fog, sound, NPC interaction, insert. | Voice kits, Opening hooks |
### Tickets that already exist but need scope updates
| Existing Ticket | Update Needed |
|---|---|
| #261 (Dual Lens Authoring Guide) | Scope confirmed. Add: emotional divergence moments (Ozzie's ask), access tier shift paths (Gestalt's ask), authoring checklist with display context tags (Araminta's ask). |
| #189 (Cultural generation guide) | Now includes Sova Transit District as first concrete instance. Miri's Round 1 output IS the v0.1 slice of this guide. |
| #190-192 (Template content packs) | Each pack now needs a parallel spatial layout (Araminta) as co-deliverable. Content and layout must be developed together, not sequentially. |
| #179 (NPC profiles) | Two NPCs (THE FRIEND x2) now require production-level depth. Remaining 13 stay at v0.1 tiers. Ticket scope must reflect this split. |
---
## 2. Dependency Chain for Narrative Content
Round 1 showed me, Mellanie, and Gestalt all proposing slightly different dependency chains. After reading all three, here's the reconciled version. The key insight: three tracks can run in parallel, converging at the content pack stage.
```
TRACK A: Narrative Architecture (Paula) TRACK B: Setting (Miri) TRACK C: Systems (Gestalt + Araminta)
1. Dual Lens Authoring Guide (#261) 1. Sova Setting Brief (#189) 1. Line Pool Format Spec (done R1)
| | |
2. Relationship Web + Triangles 2. Wiki Taxonomy + Krenn Entry 2. Visual Grammar (Araminta)
| | |
3. THE FRIEND profiles (x2) 3. NPC Cultural Notes 3. Spatial Layouts (x3) (Araminta)
| | |
4. NPC Profiles (Tier 1-3) 4. Environmental Detail Catalog 4. Line Previewer (#193)
| |
└──────────────────────┬────────────────────────┘ |
| |
v |
5. Character Voice Kits (Mellanie) |
| |
6. Opening Hooks (Mellanie) |
| |
└──────────────────────────────────────────────────────────────┘
|
v
7. Content Packs (x3) (Mellanie)
|
8. Tell Lines + Mirror Moment Pass (Paula reviews)
|
9. News Ticker + Environmental Text (Mellanie + Miri)
```
### What can start NOW (no dependencies)
| Deliverable | Owner | Status |
|---|---|---|
| Dual Lens Authoring Guide | Paula | Can begin immediately. Draft in this document. |
| Sova Setting Brief | Miri | **Done** (Round 1 output). Needs formalization into a document. |
| Line Pool Format Spec | Gestalt | **Done** (Round 1 output). Needs formalization. |
| Wiki Taxonomy | Miri + Qatux | Can begin immediately. Structure-only, content follows. |
| Visual Grammar | Araminta | Can begin immediately. |
| Provisional Voice Kit drafts | Mellanie | She proposed writing 3 options per character without waiting. Good instinct. |
| Monologue starter set (universal) | Mellanie | 50-60 lines for common situations. Unblocked. |
### What blocks the most work
The **Dual Lens Authoring Guide** is the single highest-leverage document. It blocks:
- Mellanie's voice kits (she needs emotional profiles before writing voice)
- NPC profiles (dual-lens notes per NPC require the guide)
- Content packs (the authoring checklist lives in the guide)
- Mirror moments (defined by the dual-lens framework)
I'm delivering the refined outline in Section 3 below. The full draft is my next deliverable after this workshop.
---
## 3. Dual Lens Authoring Guide — Refined Outline
Round 1 gave me the bones. Round 2 input refines the structure. Here's the updated outline incorporating feedback from all six agents.
### Part 1: The Two Characters (retained from Round 1, expanded)
The character comparison table from my Round 1 (core identity, emotional starting state, relationship to district, what they notice, what they miss, internal monologue voice, relationship default) stays. It was well-received.
**Addition from Ozzie:** Emotional divergence moments. 5 concrete situations where the characters have opposite emotional reactions. Not just "who knows what" — "who FEELS what." These become Mellanie's writing atoms.
**Addition from Mellanie:** Voice signature section. Not personality traits — speech patterns. Short/long sentences, vocabulary register, internal monologue style (observations vs. feelings vs. hypotheses). The five things Mellanie needs: voice signature, what they notice, relationship to authority, what they lie about, emotional baseline.
### Part 2: The Dual-Lens Rule (retained, refined)
The core test: "Does it read differently through each lens?" with the three types of difference (access, interpretation, emotional weight).
**Addition from Gestalt:** The examples must include the tag implications. When I show an NPC arriving late as a dual-lens example, I also show which `access`, `trust`, and `situation` tags would be different per character. The guide must bridge narrative intent to mechanical expression.
### Part 3: Access Tier Mapping (retained, expanded with shift paths)
The per-NPC-role access tier table stays.
**Addition from Gestalt:** Access tier SHIFT paths. For each social site, the 2-3 most likely tier transitions per character. Not every combination — just the ones content packs must support.
| Social Site | Character | Starting Tier | Likely Shift | Trigger |
|---|---|---|---|---|
| Logistics Hub | Smuggler | insider + peer | insider > hostile | Cover blown — seen with detective, or ring member reports suspicion |
| Logistics Hub | Detective | authority | authority > peer | Earns trust by keeping a minor infraction quiet |
| Bar | Smuggler | insider (regular) | insider > hostile | Same as above — social contamination from hub |
| Bar | Detective | public | public > insider | Repeated visits, earns regular status (3-4 visits) |
| Ring | Smuggler | insider + peer | peer > hostile | Suspected of cooperation with detective |
| Ring | Detective | public (doesn't know ring exists) | public > hostile | Stumbles into ring awareness — NPCs react defensively |
This table directly feeds content packs: Mellanie needs lines for each starting state AND each shifted state.
### Part 4: Divergence Escalation Curve (retained)
The four-phase timeline (Arrival > Daily life > Tension > Crisis point) stays. This is the narrative arc that the storyteller orchestrates.
### Part 5: Authoring Checklist (retained, expanded)
The three-question checklist stays.
**Addition from Araminta:** Question 4 — "What display context does this line use?" (spoken dialogue, overheard conversation, monologue reaction, environmental text). Every line must declare its rendering pipeline.
**Addition from Mellanie:** Question 5 — "What tags express the dual-lens difference?" If the access tier is different per character, the line needs the correct `access` list. If the trust tier is different, the `trust` tag must reflect the lower threshold.
### Part 6: THE FRIEND (new section — Jeroen's directive)
Full specification of the production-level Friend NPC for each character. See Section 5 below for the detailed design.
### Estimated Length
~12-15 pages. Longer than I estimated in Round 1 (~10 pages) because Gestalt's mechanical mapping and the FRIEND section add depth. But this is the bible — better thorough than thin.
---
## 4. Relationship Web and Triangle Design — Reconciliation
My Round 1 proposed 15 NPCs with 7 triangles. Gestalt proposed a different NPC distribution and 4 triangles. Miri provided the Sova setting with triangle opportunities per template. Let me reconcile.
### Where We Agree
- 15 NPCs across 3 templates (5 per template)
- 3 flat, 7-8 mundane triangle, 3-4 entangled
- Bridge NPCs connect templates
- Cross-template triangles are essential
- The ring's vulnerability is social, not physical
### Where We Diverge
| Dimension | Paula (Round 1) | Gestalt (Round 1) | Resolution |
|---|---|---|---|
| **Number of triangles** | 7 (2 per template + 1 cross) | 4 (1 per template + 1 cross) | **5 triangles.** 7 is too many for 15 NPCs — too many overlapping roles. 4 is mechanically minimal but doesn't test mundane triangles enough. 5 gives us 1 entangled + 1 mundane per hub/bar, 1 entangled for ring, 1 cross-template. |
| **Ring structure** | Named ring leader, courier, fence, waverer, lookout | Ring leader, courier, lookout, contact, fixer | **Merge.** The waverer is narratively essential (potential informant). The contact (ring's bar presence) is mechanically essential (cross-template bridge). Drop the fence (M) and fixer — external contacts can be referenced, not instantiated. |
| **Flat NPC count** | 5 (E, I, J, M, O) | 4-5 | **3 flat NPCs.** Miri's setting gives even flat NPCs social texture. With only 15 total, 5 flat feels wasteful. 3 flat NPCs (maintenance tech, bartender, stranger/drifter) provide the noise floor. The bartender moves from flat to mundane — Miri's Lera Sessik is too socially positioned to be wallpaper. |
| **THE FRIEND placement** | Not explicitly in web | Not explicitly in web | **THE FRIEND NPCs are the most important nodes.** They must be placed where they have maximum narrative leverage. See Section 5. |
### Revised Relationship Web (15 NPCs, 5 Triangles)
Using Miri's Krenn System names where proposed, creating new ones for gaps.
**Template 1: Logistics Hub ("The Terminal") — 5 NPCs**
| # | Name | Role | Entanglement | Triangle | THE FRIEND? |
|---|---|---|---|---|---|
| 1 | **Voss** | Shift Supervisor | Mundane (compromised by cut, but thinks of it as pragmatism) | Triangle 1: Hub Power | No |
| 2 | **Kael Davan** | Dock Worker, ring member | Entangled | Triangle 1, Triangle 5 (cross) | **Smuggler's FRIEND** |
| 3 | **Maret Korr** | Freight Scheduler, ring-adjacent | Mundane (aware, silent, conflicted) | Triangle 2: Worried Knowledge | No |
| 4 | **Drin** | Dock Inspector | Mundane (gambling debt, compromisable) | Triangle 2, Triangle 5 (cross) | No |
| 5 | **Pael** | Maintenance Tech | Flat | None | No |
**Template 2: Bar ("The Last Shift") — 5 NPCs**
| # | Name | Role | Entanglement | Triangle | THE FRIEND? |
|---|---|---|---|---|---|
| 6 | **Lera Sessik** | Bartender/Owner | Mundane (complicit through willful ignorance) | Triangle 3: Bar Tensions | No |
| 7 | **Torek Lintar** | Bar regular, off-duty dock worker, ring-adjacent | Mundane (getting sloppy with spending) | Triangle 3, Triangle 5 (cross) | No |
| 8 | **Hael** | Bar regular, teacher/family person (Kael's partner) | Mundane (worried about Kael's late nights) | Triangle 4: The Worried Partner | No |
| 9 | **Sera Venn** | Bar regular, Commission field tech (off-duty) | Mundane (institutional presence in social space) | Triangle 4 | **Detective's FRIEND** |
| 10 | **Ren** | Drifter/new arrival | Flat | None | No |
**Template 3: Smuggling Ring ("The Arrangement") — 5 NPCs**
| # | Name | Role | Entanglement | Triangle | THE FRIEND? |
|---|---|---|---|---|---|
| 11 | **Nils Davan** | Ring coordinator (Kael's older sibling) | Entangled | Triangle 1: Hub Power | No |
| 12 | **Kosse** | Courier | Entangled | Triangle 5: The Informant Question | No |
| 13 | **Naia** | Ring member, wavering (considering cooperation) | Entangled | Triangle 5: The Informant Question | No |
| 14 | **Tev** | Lookout/runner | Flat | None | No |
| 15 | *Off-station coordinator* | Referenced, not instantiated | — | — | No |
### The Five Triangles
**Triangle 1: Hub Power (Voss - Kael - Nils)**
- Voss (supervisor) takes a cut to smooth inspections. Kael (dock worker) is the ring's hands on the floor. Nils (ring coordinator) gives orders through intermediaries.
- Tension: Voss resents being managed by someone who technically works under him. Kael is loyal to Nils by blood but uncomfortable with the escalation. Nils pushes for higher volume.
- **Smuggler relevance:** Navigates this daily. Knows the hierarchy, the resentments, the pressure points.
- **Detective relevance:** Sees Voss's anxiety, Kael's efficiency, senses something beneath the surface. Doesn't know Nils exists initially.
**Triangle 2: Worried Knowledge (Maret - Drin - Voss)**
- Maret (freight scheduler) sees the manifest discrepancies. She's not in the ring — she just processes the paperwork and has noticed patterns. Drin (dock inspector) has a gambling debt and has been compromised into looking away during inspections. Voss (supervisor) maintains the schedule that creates the windows.
- Tension: Maret suspects but doesn't know whom to tell. Drin is being squeezed and might crack. Voss needs both of them functional and quiet.
- **Smuggler relevance:** Knows Maret is smart and worried — a risk. Knows Drin is compromised — a tool. Must manage both.
- **Detective relevance:** Maret is a potential cooperative witness. Drin is a potential turned asset. Both paths lead toward the operation.
**Triangle 3: Bar Tensions (Lera - Torek - Ren)**
- Lera (bartender) runs a tight establishment and knows the after-hours crowd keeps the lights on. Torek (bar regular, dock worker) has been spending visibly beyond his income — new jacket, buying rounds, latest lattice accessories. Ren (drifter) is new in town and asking questions that could be innocent job-seeking or something else.
- Tension: Lera is protective of her regulars but Torek's spending is drawing attention. Ren's questions make everyone nervous. Is Ren competition? An informant? Just looking for work?
- **Smuggler relevance:** Torek's spending is a liability. Ren is an unknown variable. Lera is an ally who needs managing.
- **Detective relevance:** Torek's spending is a flag. Ren is a potential fresh source. Lera is the social hub who sees everything.
- **Note:** This is a mundane triangle with potential entanglement. Torek's spending COULD be from the ring, or from a side hustle, or from an inheritance. The ambiguity is the point.
**Triangle 4: The Worried Partner (Hael - Kael - Sera)**
- Hael (teacher, Kael's partner) is worried about Kael's late nights and evasive answers. Hael confides in Sera (the detective's friend, a Commission field tech) over drinks at the bar. Sera hears Hael's worries and, depending on the detective's actions, might connect them to the investigation — or might protect Hael by not reporting.
- Tension: Hael's loyalty to Kael vs. growing suspicion. Sera's friendship with Hael vs. institutional duty. Kael's obliviousness to the anxiety he's causing at home.
- **Smuggler relevance:** The most emotionally loaded triangle. Kael is the smuggler's FRIEND. Hael is Kael's partner. The smuggler knows why Kael is busy and can't say. If Hael asks the smuggler directly, there's no good answer.
- **Detective relevance:** Sera is the detective's FRIEND. Hael is a potential source — a partner who suspects something. If the detective asks Sera about Hael, Sera faces a loyalty test: friend vs. duty.
**Triangle 5: The Informant Question (Naia - Kosse - Drin) [CROSS-TEMPLATE]**
- Naia (wavering ring member) is considering cooperation with authorities. Kosse (courier) suspects Naia is unreliable and has told Nils. Drin (dock inspector, compromised) is the institutional contact who could receive Naia's information — but Drin is himself compromised.
- Tension: Three ways the ring unravels. Naia turns informant (from inside). Drin breaks under pressure and cooperates (institutional corruption cracks). Kosse's suspicion of Naia creates internal ring conflict that becomes observable.
- **Smuggler relevance:** Naia is the biggest threat. Must decide: support, report to Nils, or try to calm them down. Each choice has cascading consequences.
- **Detective relevance:** Doesn't know any of this yet. But the consequences of this triangle — nervous behavior, hushed arguments, people avoiding each other — are the observable signals that the investigation follows.
### Triangle Distribution Validation
| Category | NPCs | Count | Percentage | D-029 Target |
|---|---|---|---|---|
| Flat | Pael, Ren, Tev | 3 | 20% | ~30% |
| Mundane triangle | Voss, Maret, Drin, Lera, Torek, Hael, Sera | 7 | 47% | ~50% |
| Entangled | Kael, Nils, Kosse, Naia, (+ Torek borderline) | 4 | 27% | ~20% |
Slightly under on flat, slightly over on entangled compared to D-029. For a 15-NPC vertical slice, this is acceptable — we need enough conspiracy thread to prove the investigation mechanic. In a full game district of 40+ NPCs, the ratio normalizes. The flat count being lower than target is offset by the 3 flat NPCs being genuinely ordinary — Pael fixes things, Ren is genuinely just looking for work (or isn't — the ambiguity stays), Tev watches corridors.
---
## 5. THE FRIEND: Contradiction Arc Design
Jeroen's directive: one production-level complex NPC per character. Full profile, full voice kit, full dialogue, full tell system, full contradiction arc.
Let me design both.
### Smuggler's FRIEND: Kael Davan
**Who they are:** Dock worker at the Logistics Hub. The smuggler's closest colleague — they share shifts, eat lunch together, cover for each other. Kael is in the ring. He handles the physical cargo: routing flagged containers, managing the dock-side handoffs. He's been doing this for two years and is good at it.
**Surface presentation (first 10 minutes):** Warm, reliable, slightly sardonic. Greets the smuggler with genuine affection. Talks about shift schedules, complains about Voss, asks about your weekend. Feels like the best coworker you've ever had.
**What the smuggler knows:** Kael is a ring member. This isn't a secret from the smuggler — it's shared context. They work together on the legitimate side AND the illegitimate side. The smuggler trusts Kael because they've shared risk.
**The contradiction:** Kael is meeting with someone the smuggler doesn't recognize. Late. In the restricted maintenance corridor. The smuggler's monologue: *"That's Kael. But who's he talking to? I don't know that face."*
This is NOT the detective. This is someone else. Someone from outside the ring's known network. Kael has a side arrangement the smuggler doesn't know about — and the monologue's certainty ("I know everyone Kael knows") is what makes the discovery hit.
**The shift arc:**
| Phase | Timing | What the smuggler observes | Monologue register | Tell |
|---|---|---|---|---|
| **Comfort** | 0-10 min | Kael is warm, reliable, present. Business as usual. | Fond, casual: *"Kael's already at the dock. Good. The day's better when he's on shift."* | None — Kael is baseline comfortable |
| **First crack** | 10-15 min | Kael checks his lattice more often than usual. Excuses himself from lunch. | Mild curiosity: *"Kael's distracted today. Probably nothing."* | Behavioral: increased lattice checking, shortened social interactions |
| **The observation** | 15-20 min | The smuggler sees Kael in the restricted corridor talking to an unknown person. The person leaves before the smuggler gets close. | Alarm + confusion: *"That wasn't anyone from our rotation. And Kael didn't tell me about a meeting."* | Spatial: Kael in unexpected location at unexpected time |
| **Confrontation opportunity** | 20-25 min | The smuggler can ask Kael about it. Kael deflects: "Just a thing. Don't worry about it." He's lying. The smuggler KNOWS he's lying because they know Kael's tells. | Betrayal crystallizing: *"He looked left before answering. He always looks left when he's making something up. Kael is lying to me."* | Dialogue: evasion, subject change, forced casualness |
| **New equilibrium** | 25-30 min | Everything looks normal again. But the smuggler is now watching Kael. Every warm interaction is contaminated with doubt. | Conflicted: *"Same old Kael. Laughing at the same jokes. ...What are you not telling me?"* | Emotional: the smuggler's observation lines about Kael shift from fond to analytical |
**What Kael is actually doing (the truth the player may or may not discover):** Kael's partner Hael has been asking questions. Kael is scared. The unknown person is someone from a different district who's offered to help Kael exit the ring — for a price. Kael is trying to get out to protect Hael. He's not betraying the smuggler — he's trying to save his family. But from the smuggler's perspective, any unauthorized contact is a security breach.
**Why this works narratively:** The contradiction isn't "Kael is secretly evil." The contradiction is "Kael is secretly desperate, and his desperation is making him do exactly the kind of thing that could get everyone caught." The smuggler's anger is justified (Kael broke protocol). Kael's motivation is sympathetic (he's protecting his family). There's no clean answer. That's the conflict that Ozzie's D-027 criterion #3 is looking for: an NPC the player feels conflicted about.
**What this tests in the pipeline:** Full 10-axis profile, multi-phase dialogue that changes based on observation state, tell system (lattice checking, spatial deviation, dialogue evasion), monologue that tracks emotional shift over time, dual-lens notes (the detective sees Kael's behavior change too — but reads it as guilt, not desperation).
---
### Detective's FRIEND: Sera Venn
**Who they are:** Commission field technician, off-duty bar regular. Sera is the detective's pre-existing contact in the district — someone from the same institutional world who transferred to Sova a year ago. They're the detective's social anchor: the one person in the district who speaks their language, who understands institutional culture, who can be honest over a drink.
**Why a Commission tech, not another investigator:** Sera isn't the detective's partner or supervisor. She's lateral — a technician who maintains Commission equipment, not an investigator. This means she has institutional access (she knows Commission systems, she can look things up) but no investigative mandate. She helps the detective because they're friends, not because it's her job. That makes her help feel personal, not procedural.
**Surface presentation (first 10 minutes):** Competent, slightly wry, comfortable in the district. When the detective visits the bar, Sera waves them over. Easy rapport. She fills in background — who the regulars are, what the district's like, which areas to avoid after dark. She's the detective's guide to a place they don't know yet.
**What the detective knows:** Sera is reliable. She transferred to Sova for routine work after a stressful posting elsewhere. She doesn't have skin in the smuggling game. She's the detective's safe harbor in an unfamiliar social landscape.
**The contradiction:** Sera always leaves when Torek Lintar arrives at the bar. Always. Three times in a row. The detective's monologue: *"That's the third time Sera's left when Torek walked in. That's not coincidence."*
**The shift arc:**
| Phase | Timing | What the detective observes | Monologue register | Tell |
|---|---|---|---|---|
| **Trust** | 0-10 min | Sera is warm, informative, helpful. Shares district intel freely. Offers to look things up in Commission systems. | Professional + personal warmth: *"Good to see a familiar face. Sera always was the reliable one."* | None — Sera is baseline comfortable |
| **Background data** | 10-15 min | Sera mentions Hael (Kael's partner) as "a friend from the district." Hael joins them occasionally. Sera and Hael have a genuine friendship. | Noting: *"Sera's connected here. Good. She knows the locals."* | Social: Sera has relationships outside institutional channels |
| **The pattern** | 15-20 min | Third time Sera excuses herself when Torek arrives. Different excuses each time. "Early shift." "Headache." "Need to check on something." | Suspicion activating: *"That's the third time. Sera leaves when Torek arrives. Why?"* | Behavioral: avoidance pattern, excuse variety, timing correlation |
| **The question** | 20-25 min | The detective asks Sera about Torek. Sera tenses. "He's just a loud drunk. I don't like loud drunks." She's deflecting. Not quite lying — but not telling the whole truth. The detective's training flags the evasion. | Professional analysis + personal conflict: *"She's not lying. But she's not telling me everything. Sera, what do you know?"* | Dialogue: controlled deflection, topic change, re-establishing warmth quickly |
| **Contaminated trust** | 25-30 min | Sera continues being helpful. Maybe even MORE helpful — as if compensating. But the detective can't stop watching her. Is Sera compromised? Is she protecting someone? Is she protecting the detective from something? | Analytical doubt: *"Still the same Sera. Still reliable. ...But reliable about what?"* | Emotional: the detective's observation lines about Sera shift from trusting to evaluating |
**What Sera actually knows (the truth the player may or may not discover):** Sera knows Torek. She knows him because Hael confided in her about Kael's behavior, and Sera — being a Commission tech with access to systems — ran an unofficial check on Kael's work patterns. She found the manifest discrepancies. She knows something is wrong at the logistics hub. She hasn't reported it because Hael is her friend and reporting would mean Hael's partner gets investigated, possibly arrested, and Hael's life falls apart. Sera is protecting Hael by not reporting. She avoids Torek because Torek is connected to the ring and she doesn't want to be seen near him while she's sitting on unreported evidence.
**Why this works narratively:** Sera isn't corrupt. She isn't a traitor. She's a good person making a terrible choice: loyalty to a friend vs. duty to her institution. The detective's discovery doesn't reveal a villain — it reveals a moral compromise that the detective themselves might understand. The conflict becomes: do I report Sera? Do I use what she knows? Do I confront her and risk losing my only ally in the district?
**Why the Sera-Hael-Kael chain works:** Triangle 4 (The Worried Partner) feeds directly into Sera's contradiction. Hael's worry about Kael becomes Sera's knowledge. Sera's silence becomes the detective's discovery. The detective's investigation into the smuggling ring passes directly through their friend's concealment. Every thread is connected. That's the web.
### THE FRIEND Design Principles (Reusable Pattern)
Both FRIEND NPCs follow the same structural pattern. This is the reusable template for production-level complex NPCs:
| Element | Requirement |
|---|---|
| **Relationship phase** | 3+ phases with distinct monologue registers (trust, crack, contamination) |
| **Observable contradiction** | Discoverable through the observation system, NOT told through dialogue |
| **Sympathetic motivation** | The FRIEND isn't evil — their concealment comes from a place of care or fear |
| **No clean resolution** | The player can't "fix" the situation without cost. Every response (confront, ignore, exploit, protect) has consequences |
| **Dual-lens resonance** | The other character's playthrough recontextualizes the FRIEND's behavior. Kael's desperation reads differently when you've played the detective and know the investigation is closing in. Sera's silence reads differently when you've played the smuggler and know what she's protecting. |
| **Triangle integration** | The FRIEND's contradiction connects to at least one triangle, creating cascade potential |
| **Tell progression** | 3+ observable behavioral changes that the monologue system can flag |
| **Dialogue shift** | Pre-discovery and post-discovery dialogue pools must feel different — same person, different tension |
---
## 6. Mirror Moments — Refined by Mellanie's Monologue Approach
Mellanie confirmed: separate pools, observation-event-triggered, independently coherent. This is the right foundation for mirror moments. Let me refine my Round 1 proposals against her authoring model.
### What Changed
In Round 1, I proposed mirror moments as paired monologue lines tagged to the same observation trigger. After reading Mellanie's approach, I'm refining: mirror moments aren't a special content type — they're a **quality of certain monologue lines that only becomes apparent on replay.** The authoring format doesn't need a "mirror" tag. It needs two independently authored lines that happen to respond to the same trigger, written by someone (me, reviewing Mellanie's work) who understands both characters well enough to ensure the ironic resonance.
### The Mirror Moment Authoring Process
1. Mellanie writes the monologue pools per character, per trigger.
2. I review both pools side by side and identify **natural mirrors** — places where the two characters' responses to the same trigger create dramatic irony.
3. Where natural mirrors don't exist but should, I flag the gap. Either Mellanie writes a new line, or I propose one for her to voice-match.
4. I tag mirrors in the authoring notes (the `dual_lens` field in Gestalt's format), NOT as a system tag. Mirrors are an authoring-layer quality check, not a runtime filter.
### Revised Mirror Moments for v0.1
I'm keeping my Round 1 proposals but grounding them in Miri's Sova setting and Mellanie's trigger taxonomy.
| Mirror | Trigger | Smuggler Line | Detective Line | What replay reveals |
|---|---|---|---|---|
| **1: The Friend's Routine** | `observe_npc` (Kael arriving at work) | *"Kael's here. Good — I was starting to worry."* | *"The dock worker from the case file. Davan, K. Unremarkable on paper."* | The smuggler's warmth + the detective's clinical assessment of the same person. On replay, the player recognizes that one character's friend is the other character's suspect. |
| **2: The Empty Corridor** | `enter_location` (maintenance corridor, night) | *"South access is clear. Nobody using the route tonight. Good."* | *"This corridor should see foot traffic during shift change. It's empty. Why?"* | The smuggler's relief IS the detective's clue. On replay, the player understands the silence is manufactured. |
| **3: The Worried Partner** | `observe_npc` (Hael at the bar, looking tired) | *"Hael looks rough. I should probably not mention seeing Kael at the hub so late."* | *"Spouse of hub worker Davan. Visible stress markers. Possible entry point for information."* | The smuggler sees a friend to protect. The detective sees a source to cultivate. Hael is caught between two people who both think they're acting in Hael's interest. |
| **4: The Spending** | `observe_npc` (Torek buying a round) | *"Torek's generous tonight. He needs to be more careful with that."* | *"The dock worker — Lintar — buying drinks for the table. On a standard logistics salary?"* | The smuggler knows (or suspects) where the money comes from and worries about exposure. The detective sees the spending as a financial tell. Same observation, different fear. |
| **5: Sera Leaving** | `witness_interaction` (Sera excuses herself when Torek arrives) | *"Sera's headed out. Smart — Torek gets loud after three drinks. Nobody wants to deal with that."* | *"That's twice now. Venn leaves when Lintar arrives. Coincidence? Filing it."* | The smuggler has the innocent explanation (Sera avoids loud drunks). The detective has the investigative read (avoidance pattern). On replay as the smuggler, the player who played detective first thinks: "Wait — WAS it just the noise?" |
| **6: The Hum** | `enter_location` (near span gate terminal) | *"The gate hum's stronger today. More transits than usual. Should be a busy shift."* | *"Increased gate activity. Higher cargo volume means more opportunity for irregularities."* | Same sensory data, different interpretive framework. Smuggler thinks logistics. Detective thinks investigation. Both are right. |
| **7: The Commission Kiosk** | `enter_location` (passing the Commission terminal in the hub) | *"The Commission kiosk. Nobody ever uses it for anything real. Keep walking."* | *"Institutional presence. Minimal. That's either reassuring or concerning."* | The smuggler dismisses institutional infrastructure. The detective evaluates it. On replay, the player understands how the ring benefits from the smuggler's attitude being universal. |
**Target: 10-12 mirror moments for v0.1.** These 7 are the core structural mirrors tied to major narrative elements (THE FRIEND, the triangles, the setting). I'll identify 3-5 more during the review pass on Mellanie's monologue pools — organic mirrors that emerge from the content rather than being pre-designed.
---
## 7. Reaction to Miri's Sova Transit District
### Does the economics/motivation chain work for my narrative?
**Yes. Emphatically.**
Miri's Sova setting is exactly the economic substrate I asked for in Round 1. Let me trace the chain:
```
Freight economy (steady but modest wages)
→ Permanent mild financial pressure (comfortable but tight)
→ Smuggling as supplemental income (rational risk calculus)
→ Community complicity (everyone benefits indirectly)
→ Institutional thin-ness (Commission is intermittent)
→ Normalized deviance (the abnormal becomes normal)
→ The detective walks into a community that resists investigation not from malice, but from self-interest
```
This chain does three critical things for my narrative design:
**1. It makes the smuggler sympathetic.** The smuggler isn't a cartel boss — they're a logistics worker who said yes to moving a container and discovered they're good at it. The ring isn't violent, isn't chaotic, isn't even particularly ambitious. It's a community survival mechanism. When the detective threatens to dismantle it, they're threatening the economic immune system Miri described. That's genuine moral complexity, not just "both sides."
**2. It makes the detective's job genuinely hard.** The detective enters a district where non-cooperation is the default — not because people are criminal, but because the grey economy is everyone's business. Even flat NPCs have a reason to be unhelpful. Pael the maintenance tech doesn't know about the ring, but he's noticed his paycheck covers more than it should (contractors paid through ring-adjacent money). Drin the inspector looks away not because he's evil but because his gambling debt makes him vulnerable and the ring made that vulnerability work for them. Every NPC Miri describes has a motivation chain that starts with "the economy is slightly too tight for comfort."
**3. It grounds the triangles in economic reality.** Triangle 2 (Worried Knowledge) exists because Maret processes manifests for a living and notices discrepancies. Triangle 3 (Bar Tensions) exists because Torek's spending is visible in a community where everyone knows everyone's financial position. Triangle 4 (Worried Partner) exists because Kael's late nights are economically implausible on a standard salary. The economic substrate generates the social signals that the observation system tracks.
### What I need from Miri in Round 2 or a follow-up
Three small additions to the Sova brief that would tighten the narrative:
1. **The specific contraband mix.** Miri proposed unlicensed lattice components as primary cargo. I endorse this strongly — it creates the moral ambiguity of "they're moving access, not weapons." But I also want one item in the mix that's darker: something the smuggler doesn't look at too closely, that hints at the ring being connected to something bigger than local commerce. A sealed container that Nils says is "just components" but is heavier than it should be. This is the storyteller's contamination seed — the thing that makes the smuggler question whether they really know what they're part of.
2. **The Commission liaison rotation detail.** Miri says the previous liaison was reassigned 3 months ago. I need to know: was this actually routine, or was it arranged? If the ring (or someone above the ring) influenced the rotation to get a less experienced liaison, that's a deeper conspiracy thread the detective can discover. If it was genuinely routine, that's a red herring the detective might chase. Either way, I need to know so I can write the NPC dialogue around it.
3. **Hael's profession detail.** Miri placed a "teacher/family person" in the bar. If Hael is a teacher, what do they teach? Station kids? Adult education? This matters because Hael's social position affects how their worry reads to both characters. A teacher is someone the community trusts and respects — their worry carries social weight. If Hael starts asking questions publicly, the community pays attention in a way they wouldn't if Hael were just "someone's partner."
### One strong validation
Miri's naming conventions work. Kael, Voss, Lera, Torek, Drin, Maret — compact, consonant-heavy, first-name-primary in social contexts. These names are writeable. Mellanie can put these in dialogue and they feel natural. The IP distance from Hamilton's conspicuously-English names (Ozzie, Nigel, Paula) is exactly right. I've added Nils, Hael, Sera, Naia, Kosse, Pael, Tev, and Ren to fill the remaining roster slots, following Miri's conventions.
---
## 8. Cross-Agent Synthesis: What I Need From Each Person
| From | What I need | Why | When |
|---|---|---|---|
| **Mellanie** | Provisional voice kit drafts (3 options per character) | I can't finalize THE FRIEND dialogue until I know how the characters sound. Give me the options, I'll select/blend based on narrative needs. | Before content packs |
| **Mellanie** | Review of my mirror moment proposals | Are these writable? Do the voice registers hold? Would you phrase them differently? | After voice kits |
| **Gestalt** | Confirmation that the access tier shift table (Section 3) maps cleanly to the line selection pipeline | If tier shifts change the `access` tag mid-game, does the selection pipeline handle that? Or does it need a state flag? | Before Dual Lens Guide final draft |
| **Gestalt** | Tell trigger specification for THE FRIEND arcs | Kael's lattice-checking and Sera's avoidance pattern need to be expressible as observation triggers. Are they in the taxonomy? | Before FRIEND profiles |
| **Miri** | Contraband specifics, Commission rotation backstory, Hael's profession | Three small setting details that tighten narrative threads. See Section 7. | Before NPC profiles |
| **Miri** | Review of my NPC naming additions | Do Nils, Hael, Sera, Naia, Kosse, Pael, Tev, Ren fit Krenn System conventions? | Quick validation |
| **Araminta** | Spatial layouts for all three templates | I need to know where NPCs physically ARE before I finalize routine descriptions and observation opportunities. Where does the "restricted corridor" meeting happen? Where is the bar's corner booth? | Parallel with content packs |
| **Araminta** | Confirmation that color shifts support THE FRIEND arc | When the smuggler discovers Kael's secret meeting, does Kael's color shift from green to amber? What triggers that visually? | Before FRIEND profiles |
| **Ozzie** | Gut check on THE FRIEND contradiction arcs | Do Kael and Sera's shifts feel right emotionally? Is the discovery satisfying? Does the replay resonance work? | After this document |
---
## 9. Summary: What I Deliver Next
| Deliverable | Priority | Depends On | Target |
|---|---|---|---|
| **Dual Lens Authoring Guide — full draft** | Critical (blocks everything) | Nothing — writing now | Next sprint |
| **THE FRIEND: Kael Davan — full production profile** | Critical (pipeline test) | Dual Lens Guide, Mellanie voice kits, Miri setting details | After DLG |
| **THE FRIEND: Sera Venn — full production profile** | Critical (pipeline test) | Same as above | After DLG |
| **Relationship web (this document, Section 4) — formalized** | High | Miri validation, Araminta layouts | After layouts |
| **NPC Profiles: Tier 1 (4 entangled: Nils, Kosse, Naia, + Kael enhanced)** | High | Relationship web, Dual Lens Guide | After DLG |
| **NPC Profiles: Tier 2 (7 mundane: Voss, Maret, Drin, Lera, Torek, Hael, Sera enhanced)** | High | Tier 1 profiles | After Tier 1 |
| **NPC Profiles: Tier 3 (3 flat: Pael, Ren, Tev)** | Medium | Setting brief | After setting |
| **Access tier shift design document** | High | Gestalt validation | After DLG |
| **Mirror moment review pass** | Medium | Mellanie's monologue pools | During content pack authoring |
| **Contradiction arc design document** (reusable pattern) | Medium | Both FRIEND profiles complete | After FRIEND profiles |
The Dual Lens Guide is the critical path. Everything else follows from it. I'm starting the full draft immediately after this workshop concludes.
---
*The honest truth is: Round 1 gave us the parts. Round 2 is about the connections between the parts. The relationship web isn't just NPCs in a grid — it's a chain of consequences where Kael's fear for Hael becomes Sera's silence becomes the detective's doubt becomes the smuggler's betrayal. Every thread pulls on every other thread. That's what makes 15 NPCs feel like a community, not a cast list. And THE FRIEND, at the center of each character's web, is the emotional proof that the whole system works.*
*Paula out. The web is woven. Now we write the people in it.*
docs/workshops/content-gap-analysis_v0_1/workshop-outcomes.md
-82
View File
@@ -1,82 +0,0 @@
# Workshop Outcomes: v0.1 Content Gap Analysis
**Workshop:** v0.1 Content Gap Analysis
**Date:** 2026-02-11
**Rounds:** 2 (Analysis + Synthesis)
**Participants:** Mellanie, Paula, Araminta, Miri, Gestalt, Ozzie
**Facilitator:** Jeroen
**Documenter:** Qatux
**Status:** DONE — all decisions actioned, tickets created
**Full notes:** `docs/workshops/content-gap-analysis_v0_1/SUMMARY.md`
---
## What the Workshop Accomplished
Six agents independently analyzed 9 content layers across the vertical slice (D-027), then synthesized across all outputs. The project lead issued 9 directive decisions between rounds. Remarkable cross-agent convergence: the Dual Lens Guide, monologue as primary carrier, and the tag taxonomy were independently identified by multiple agents without coordination. THE FRIEND concept evolved from Ozzie's emotional instinct to Paula's structural design to Mellanie's authoring plan in a single workshop.
---
## Decisions Produced
| ID | Decision | Domain | Source |
|----|----------|--------|--------|
| D-032 | Separate monologue pools per character | content.md | Lead directive #1 |
| D-033 | Entity color = relationship to player | perception.md | Araminta R1 + lead directive #2 |
| D-034 | THE FRIEND production-level NPC pattern | content.md | Ozzie concept + lead directive #4 + Paula design |
| D-035 | Converged tag taxonomy for line pools (6+3 tags) | content.md | Gestalt + Mellanie convergence |
| D-036 | Sova Transit District / Krenn System as v0.1 setting | content.md | Miri R1 + lead directive #6 |
| D-037 | Contraband specification | content.md | Miri R1/R2 |
| D-038 | Audio in v0.1 scope via Stable Audio Open (8 files) | scope.md | Lead directives #3 + #9 |
| D-039 | v0.1 wow moment scope — all 6 moments | scope.md | Ozzie R1/R2 + lead directive #8 |
| D-040 | Wiki taxonomy structure | process.md | Miri R2 + lead directive #5 |
All 9 decisions confirmed by project lead between rounds as non-negotiable directives.
---
## Open Questions Identified
| ID | Question | Owner | Status |
|----|----------|-------|--------|
| Q-012 | How does the generation expansion pass work? LLM, template-based, or rule-based? | Gestalt, Mellanie | Raised this workshop |
| Q-013 | How does the line previewer handle THE FRIEND's temporal progression? | Gestalt, Dudley | Raised this workshop |
| Q-014 | Audio timing with monologue — when does the chime fire relative to text? | Gestalt, Ozzie | Raised this workshop |
| Q-015 | Does 4x generation expansion apply to THE FRIEND's custom lines? | Mellanie, Gestalt | Raised this workshop |
| Q-016 | Knowledge hierarchy for monologue prerequisites | Gestalt, Paula | Raised this workshop |
| Q-017 | Triangle pressure threshold — what events trigger escalation? | Gestalt, Paula | Raised this workshop |
---
## Tickets Created
48 total tickets (42 new + 6 updates). See `docs/workshops/content-gap-analysis_v0_1/TICKETS.md` for full list.
**Critical (9 new):** #297 Kael Davan full profile, #298 Sera Venn full profile, #299 Opening hook (smuggler), #300 Opening hook (detective), #301 Wiki taxonomy, #302 Sova Texture Appendix, #303 v0.1 Visual Grammar, #304 Entity Color System Spec, #305 Dialogue selection pipeline.
**High (23 new):** Content and narrative (#306, #307, #310, #328), visual and spatial layouts (#311-318), worldbuilding (#319-322), systems and implementation (#308, #309, #323-327).
**Medium (10 new):** Mirror moments, tutorial content, environmental standards, tell derivation (#329-338).
**Updated (6):** #261 promoted to critical with expanded scope; #189, #168, #124, #90, #193 updated.
---
## Key Flags
- Detective's FRIEND confirmed as Sera Venn (Paula, not Mellanie's Lera proposal). Lera Sessik remains the bar owner.
- NPC triangle count: Paula reconciled from 7 to 5 triangles in Round 2. Five-triangle model is canonical.
- Tag taxonomy convergence was independent: Mellanie and Gestalt proposed nearly identical structures without coordination.
- Dual Lens Guide (#261) is the single highest-risk dependency — everything downstream blocks on it.
---
## Critical Path Produced
Dual Lens Guide (#261) → Voice Kits → THE FRIEND Content Packs → Validation → Content at Scale.
Three parallel tracks: narrative (Paula), setting (Miri), systems (Gestalt + Araminta) — converging at content pack production.
---
*Compiled by Qatux. Source: `docs/workshops/content-gap-analysis_v0_1/SUMMARY.md`, `TICKETS.md`. Decisions in `decisions/content.md` (D-032 through D-040 excl. D-033 in perception.md, D-038/D-039 in scope.md, D-040 in process.md).*
docs/workshops/v01-content-scoping/SUMMARY.md
-325
View File
@@ -1,325 +0,0 @@
# v0.1 Content Scoping Workshop — Summary
**Date:** 2026-02-12
**Called by:** Jeroen
**Participants:** Gestalt (Systems Design), Paula (Narrative), Tyre (Architecture), Mellanie (Copywriter), Stig (UI), Dudley (Server), SI (Project Manager), Qatux (Documenter)
**Rounds:** 2 + closing round (lead resolutions)
**Purpose:** Scope and prioritize content work for v0.1 vertical slice. Apply Wiki Review long-term strategy (300-world generator model) to the hand-authored Sova Transit District proof.
**Key constraint:** v0.1 proves the interaction model. All structures must be generator-compatible for the 300-world future.
**Source files:**
- `docs/workshops/v01-content-scoping/round1-tracking.md`
- `docs/workshops/v01-content-scoping/round2-tracking.md`
- `docs/workshops/v01-content-scoping/si-ticket-changes.md`
- `docs/workshops/v01-content-scoping/v01-content-scoping-workshop-brief.md`
- Round 1 responses: `round1-gestalt.md` through `round1-si.md`
- Round 2 responses: `round2-gestalt.md` through `round2-si.md`
---
## 1. Workshop Overview
**Round 1** — 7 responses across 6 topics (wiki fixes, NPC architecture, content directory, interaction model, scope boundary, tickets). Produced 17 consensus items, 5 disagreements, 7 wiki gaps, 7 decisions ready to formalize, 26 surviving tickets + 7 new proposals.
**Round 2** — Lead issued 4 decisions resolving the major disagreements (NPC mapping, content format, interaction model, pause behavior). 7 responses addressed remaining convergence work. Gestalt changed 6 of 10 NPC mapping positions to Paula's reads. Tyre and Dudley independently produced structurally identical ObserverSnapshot v3 definitions. Mellanie delivered canonical PC voice registers and the Kael Davan content pack template.
**Closing round** — Lead resolved 3 remaining questions: Q-012 (16 EntityKnowledge keys), Q-013 (server-authoritative pause, NEW-12 killed), Q-016 (`verbs[]` rename confirmed). Established process rule: no ticket merges across domain teams.
---
## 2. Decisions Made (D-042 through D-061)
### From Round 1 Consensus (7)
| ID | Decision |
|----|----------|
| D-042 | Drin promoted from Tier 3 to Tier 2. |
| D-043 | THE NOBODY mechanic deferred to v0.2; hidden pattern+motivation data ships in v0.1 content files. |
| D-044 | v0.1 interaction model: 7 interactions (Move, Look, Monologue, Examine Object, Examine NPC, Talk, Overhear). |
| D-045 | v0.1 scope IN additions: News ticker, PC-as-NPC, Time progression, Relationship state transitions. |
| D-046 | v0.1 scope OUT additions: Inventory, Stealth, Combat, Player-facing save/load, Lattice modification. |
| D-047 | v0.1 triangles: 3 active forks (T1, T2, T4), 2 passive tensions (T3, T5). |
| D-048 | Client receives all text from server via state updates; client does not load or evaluate content files. |
### From Round 2 + Closing (13)
| ID | Decision |
|----|----------|
| D-049 | YAML is the content file format for v0.1. RON converter available as optional build-time tool. Server loads YAML directly; RON cache is a future production optimization. |
| D-050 | Gestalt's NPC pattern/motivation mapping is canonical for v0.1. Paula's emotional/narrative layer becomes v0.2 annotations. Version-toggle approach. |
| D-051 | v0.1 ships single context-sensitive action; multi-verb architecture modeled underneath. Server computes N available verbs per entity. v0.1 client shows priority-0 only. v0.2 client reads full list — no server changes. |
| D-052 | 3-state pause: Normal (100%), Overlay (50%), Paused (0%). Server-authoritative — client is a dumb renderer. Client sends pause IPC command; reads `sim_speed` from ObserverSnapshot. |
| D-053 | Self-contained triangle forks for v0.1. No cross-triangle cascade. v0.2 adds storyteller-managed cascade. |
| D-054 | ObserverSnapshot v3 protocol. Extends v2 with: `sim_speed`, `nearby_interactions`, `active_dialogue`, `monologue`, `overheard`, `knowledge_updates`, `examine_result`, `ticker_headlines`. Backward compatible via serde defaults. |
| D-055 | 16 EntityKnowledge keys. 4 new generic role-perspective keys. `trust_read` merged into `trust_level`. `secret_held` renamed to `leverage_held` (expanded value space). `secret_confidence` → `leverage_confidence`. `social_debt` and `loyalty_conflict` deferred to v0.2. |
| D-056 | PC voice registers defined. Smuggler: feeling-first, fragments, concrete/physical. Detective: analysis-first, complete sentences, institutional vocabulary. |
| D-057 | Content directory: `content/` with `schema/`, `global/`, `districts/` top-level split. JSON Schema validation at build time. Dialogue by location+role. Monologue partitioned by character. |
| D-058 | THE FRIEND content pack template: Kael Davan. 91 lines across 5 arc phases. Becomes template for all subsequent packs. |
| D-059 | Monologue display: 160 char max, 2-line max, 4-6s display, 2s cooldown, queue depth 1, 9-level priority ordering. |
| D-060 | `actions[]` renamed to `verbs[]` across all surfaces (server, client, YAML, wiki, decisions). |
| D-061 | No ticket merges across domain teams. Shared epics fine; each team gets own ticket with own definition of done. |
---
## 3. EntityKnowledge — 16 Keys
**Architecture:** All keys are observer-to-target. Interpretation lives in content (monologue pools, voice registers, archetype briefs), not schema. Same key, same enum, different meaning per archetype.
### 12 Existing Keys
| # | Key | Category |
|---|-----|----------|
| 1 | `name` | Identity |
| 2 | `role` | Identity |
| 3 | `faction` | Identity |
| 4 | `species` | Identity |
| 5 | `location` | Spatial |
| 6 | `routine_pattern` | Behavioral |
| 7 | `trust_level` | Relational (absorbs `trust_read`) |
| 8 | `leverage_held` | Relational (renamed from `secret_held`; expanded: secrets, debts, promises, obligations, compromising positions) |
| 9 | `leverage_confidence` | Relational (renamed from `secret_confidence`) |
| 10 | `relationship_state` | Relational |
| 11 | `behavior_flags` | Behavioral (tracks tells + contradictions) |
| 12 | `known_associates` | Social |
### 4 New Role-Perspective Keys
| # | Key | Values | What It Stores |
|---|-----|--------|---------------|
| 13 | `risk_assessment` | none / low / moderate / high / critical | How this NPC threatens observer's position |
| 14 | `loyalty_assessment` | solid / dependable / uncertain / wavering / hostile | How predictably this NPC serves observer's interests |
| 15 | `position_integrity` | solid / thin / cracking / blown / N/A | Status of active deception involving this NPC |
| 16 | `moral_weight` | innocent / peripheral / complicit / compromised / willing | Observer's subjective moral assessment |
**Deferred to v0.2:** `social_debt` (no favor economy in 30-min session), `loyalty_conflict` (inferable from `behavior_flags` + `loyalty_assessment`).
**Not added:** `tell_observed`, `contradiction_flagged` — tracked in existing `behavior_flags`.
---
## 4. NPC Mapping
### v0.1 Canonical (Gestalt's Mechanical Mapping)
| # | Name | Tier | Pattern | Motivation |
|---|------|------|---------|-----------|
| 1 | Kael Davan | T1 | FRIEND | OPERATOR |
| 2 | Sera Venn | T1 | FRIEND | WITNESS |
| 3 | Naia Tamm | T1* | MIRROR | CIVILIAN |
| 4 | Voss | T2 | SYSTEM | OPERATOR |
| 5 | Lera Sessik | T2 | ANCHOR | OPERATOR |
| 6 | Torek Lintar | T2 | CATALYST | CIVILIAN |
| 7 | Devra | T2 | THRESHOLD | HANDLER |
| 8 | Maret Korr | T2 | WITNESS | SKEPTIC |
| 9 | Resha | T2 | CATALYST | CIVILIAN |
| 10 | Drin | T2 | SYSTEM | TURNCOAT |
| 11 | Renn | T2 | THRESHOLD | OPERATOR |
| 12 | Pell | T2 | CATALYST | TURNCOAT |
| 13 | Harek | T2 | ANCHOR | HANDLER |
| 14 | Sess | T3 | ANCHOR | CIVILIAN |
| 15 | Olin | T3 | CATALYST | CIVILIAN |
| 16 | Sabel | T3 | GHOST | OPERATOR |
| 17 | Tav | T3 | SYSTEM | CIVILIAN |
**Off-stage:** Nils Davan — GHOST + HANDLER
**Distribution:** 8 of 9 patterns present (REMNANT correctly absent; NOBODY deferred). All 6 motivations present. CIVILIAN at 6/17 (35%) matches D-029 noise floor (~30%).
### v0.2 Emotional Layer (Paula's Annotations)
Paula annotated all 10 disagreement NPCs with emotional/narrative depth descriptions specifying what content each v0.2 motivation/pattern unlocks (~30-50 lines per NPC). The version-toggle approach: same NPCs, same schema, deeper analytical lens.
### Resolution Process
Gestalt changed 6 of 10 Round 1 disagreement positions to Paula's reads (Maret pattern+motivation, Resha motivation, Harek pattern, Drin pattern, Sabel pattern, Olin motivation). Gestalt held on 3 (Voss motivation, Devra motivation, Sess pattern). Tav was a design-choice change (NOBODY deferred = SYSTEM+CIVILIAN instead).
---
## 5. Content Architecture
### Format
YAML for all content files (D-049). RON converter in `tooling/` as optional build-time optimization. Server loads YAML directly via `serde_yaml`. JSON Schema validation at authoring and build time.
### Directory Structure
```
content/
content.yaml # manifest
_schema/ # JSON Schema files
_meta/ # infrastructure
global/
facts.yaml
factions.yaml
enums/ # situations, topics, moods, triggers, access-tiers, activities
knowledge/
entity-attributes.yaml
regions/
districts/
sova-transit/
district.yaml
npcs/ # per-NPC YAML (tier-conditional fields)
locations/
triangles/ # 5 triangle definitions
lines/
dialogue/ # by location + role (not NPC)
monologue/ # partitioned by character
routines/
templates/
```
**Canonical ID format:** `{system}.{station}.{district}.{type}.{slug}`
### Validation Pipeline (3-tier)
1. **Authoring time:** IDE with JSON Schema autocomplete
2. **Build time:** `make validate-content` — JSON Schema + cross-reference validation
3. **Load time:** serde_yaml deserialization + semantic validation (StableId assignment, relationship wiring)
### Schemas Defined
- `npc-profile.schema.json` — tier-conditional fields, pattern/motivation enums, axes, tells, access tiers, trust levels, friend_arc, triangle membership
- `dialogue-pool.schema.json` — tagged per D-028/D-035, role+location based, access/trust/situation gating, knowledge_grants
- `monologue-pool.schema.json` — character-partitioned (D-032), trigger+prerequisite (AND-only)+priority+cooldown, 160 char max
---
## 6. Interaction Model
### 7 Verbs (D-044)
Move, Look, Monologue, Examine Object, Examine NPC, Talk, Overhear.
### Architecture
- Server computes N available verbs per entity every tick via `verbs[]` field (D-060 rename from `actions[]`)
- Priority-sorted: context determines which verb surfaces as `[E]` prompt
- Post-contradiction: Examine can rise above Talk (detective investigating flagged NPC)
- `verbs[]` embedded in ObserverSnapshot via `nearby_interactions`, not separate message
### v0.1 Client
Single context-sensitive action. `[E] Talk` / `[E] Examine`. One keybind. `InteractPrimary` PlayerAction variant sends priority-0 verb.
### v0.2 Extension
`[E] Talk [F] Observe` — horizontal label row. `InteractWith` PlayerAction variant. Client reads full `verbs[]` list. **No server changes needed.**
### Convergence
Tyre (`AvailableActions`/`ActionOption`), Dudley (`EntityInteractions`/`AvailableAction`), and Stig (`InteractionOptions`) independently produced structurally identical designs. Naming unification deferred to implementation (Q-015).
---
## 7. Pause System
### 3 States (D-052)
| State | Speed | Trigger |
|-------|-------|---------|
| Normal | 100% (1.0) | Default |
| Overlay | 50% (0.5) | Knowledge panel, dialogue |
| Paused | 0% (0.0) | Spacebar (always) |
### Authority
**Server-authoritative.** Tick rate is a server simulation concern. Client is a dumb renderer — renders ObserverSnapshots at whatever rate the server sends them. Client sends pause IPC command to server. Client reads `sim_speed` from ObserverSnapshot for visual feedback.
Spacebar from any state goes to Paused. Spacebar from Paused resumes to pre-pause state. Multiple overlays don't stack below 50% in v0.1.
**NEW-12 (client pause state machine) killed** — client doesn't manage time. Stig's `PauseManager` reduced to sending IPC commands and reading `sim_speed`.
---
## 8. Scope Boundary
### IN (v0.1)
- WASD movement + collision
- Context-sensitive interaction (7 verbs, single-action prompt)
- Monologue system (tagged triggers, FactId prerequisites, AND-only)
- Knowledge graph (player learns facts, relationships change)
- 2 playable characters (smuggler, detective)
- THE FRIEND arc (Kael for smuggler, Sera for detective)
- 5 triangles: 3 active forks (T1, T2, T4), 2 passive tensions (T3, T5)
- 6 wow moments (D-039)
- 3 social sites (Terminal, Last Shift, Maintenance Corridors)
- NPC routines (schedule-based movement)
- News ticker (world-space at bar)
- PC-as-NPC (other character exists as NPC)
- Time progression (DayPhase)
- Relationship state transitions (Friendly → PersonOfInterest)
- Self-contained triangle forks (no cross-triangle cascade)
- ~695 authored content items (~200 monologue + ~350 dialogue + ~50 environmental + ~20 ticker + ~50 UI + ~25 PC-as-NPC)
### OUT (v0.1)
- THE NOBODY / dynamic tier promotion (data ships, mechanic deferred)
- Archetype transitions
- Multiple FRIEND candidates per character
- Secondary contraband variation
- Gate network / multi-world
- Content generation / randomization
- Modding support (mod-compatible conventions ship; overlay implementation doesn't)
- Inventory system (evidence is knowledge, not physical items)
- Stealth mechanics (social stealth, not mechanical)
- Combat system
- Player-facing save/load (session-based 30-minute slice)
- Lattice modification/upgrade
- Cross-triangle cascade (storyteller-managed, v0.2)
- `social_debt` / `loyalty_conflict` EntityKnowledge keys
---
## 9. Ticket Summary
### Counts
| Category | Count | Teams |
|----------|-------|-------|
| Wiki fixes (A-series) | 8 | copy |
| Style guides & specs (B-series) | 5 | copy |
| Content directory & schema (C-series) | 10 | copy (1), server (8), ci (1) |
| Design specs (D-series) | 2 | server (1), copy (1) |
| Workshop tickets (NEW 1-7) | 7 | copy |
| Lead decision tickets (NEW 8-14, excl. killed NEW-12) | 6 | server (4), client (2) |
| **Total new tickets** | **38** | **copy (21), server (13), client (2), ci (1)** |
| Existing ticket updates | 10 | — |
### Sprint 3 Allocation
**Copy team (15 tickets):**
- P0: #261 (Dual Lens Guide — **critical path root**, blocks 9 tickets), C1 (content dir design), A1 (canonical names), A2 (Naia Tamm rename), A7 (smuggler attributes)
- P1: B2 (MIRROR spec), B4 (smuggler voice + moral arc), NEW-1 (NPC mapping), NEW-5 (wow moment checklist), A10 (Nils stub), A11 (Triangle 1 fix)
- P2: B3 (PC-as-NPC spec), A8 (shortcode fix), NEW-2 (Drin expansion), NEW-7 (interaction verb spec)
**Server team (6 additions to existing 10):**
- C2 (directory skeleton), C3 (schemas), C9 (validate-content CLI), NEW-9 (proximity + InteractionOptions), #326-P1 (loader skeleton), NEW-11 (tick rate scaling)
**Client team (1 addition):**
- NEW-10 (extensible interaction prompt)
### Critical Paths
**Chain 1 — Content Authoring:**
`#261` → B4 → A6 (Sprint 4) → NEW-4 (Sprint 4) → content packs (Sprint 5)
**Chain 2 — Content Architecture:**
C1 → C2+C3 (Sprint 3) → C4-C8+NEW-3 (Sprint 4) → #326-P2 (Sprint 4)
**Chain 3 — Interaction Pipeline:**
NEW-7 (soft) → NEW-9 (server) → NEW-10 (client)
**#261 (Dual Lens Authoring Guide) is the single biggest blocker.** Blocks 9 downstream tickets across the entire content pipeline. Recommended: Paula as owner, 5-day time-box.
### Key Existing Ticket Updates
- #368: Close (wiki delivered)
- #369: Repurpose as parent epic
- #326: Split into Phase 1 (Sprint 3, skeleton) + Phase 2 (Sprint 4, real content)
- #86: Update ECS component list to workshop output
- #88: Add #237 (A* pathfinding) dependency
---
## 10. Open Items Carried Forward
| ID | Item | Owner | Priority |
|----|------|-------|----------|
| Q-014 | 3 NPC surnames awaiting Miri validation: Drin Vassar, Sess Torin, Tav Lenn | Miri | Low |
| Q-015 | Interaction struct naming: `AvailableActions` (Tyre) vs `EntityInteractions` (Dudley). Trivial — resolved at implementation time. | Tyre/Dudley | Low |
| Q-017 | 695 authored items validated as scope input but not independently verified by other agents. | SI/Mellanie | Low (informational) |
None of these block Sprint 3 work.
---
*Compiled by Qatux. Workshop produced 20 decisions (D-042 through D-061), 38 new tickets + 10 updates, canonical NPC mapping for 17 NPCs, 16-key EntityKnowledge spec, full content architecture, and Sprint 3-5 roadmap. 3 minor open items carried forward. #261 is the critical path root.*
docs/workshops/v01-content-scoping/round1-dudley.md
-826
View File
@@ -1,826 +0,0 @@
# Round 1 — Dudley (Server Developer)
## Topic 2: NPC Architecture — Server-Side Entity Data & ECS Design
### Current State
The server already has a basic NPC component set from D-024 (`server/src/npc/mod.rs`): `Npc` marker, `Want`, `Secret`, `Relationships`, `ToleranceThreshold`, `DailyRoutine`, `InformationInventory`, `Contentment`, `PersonalityTraits`, `TellSystem`, `SkillSet`, `CombatCapability`. These implement the 10-axis model but are string-heavy placeholders. They don't yet encode the three-system NPC model (pattern + motivation + composition).
The knowledge graph (`server/src/knowledge/`) is production-ready for Sprint 2 scope: `KnowledgeGraph` component with BTreeMap storage, `EntityKnowledge`/`FactKnowledge` entries, confidence hierarchy, decay system, event-driven updates via `KnowledgeEventQueue`.
### What Each Pattern Requires (System A)
Patterns define what the character *means to the story*. Most pattern behavior emerges from existing D-024 axes plus a pattern tag and pattern-specific state. The simulation doesn't need a unique system per pattern — it needs the pattern tag to gate content selection and a small amount of pattern-specific state.
```rust
/// System A: Thematic pattern tag.
/// Drives content selection (which monologue pool, which dialogue options).
/// The pattern itself is behavioral coloring on top of D-024 axes,
/// not a separate simulation system.
#[derive(Component, Debug, Clone, Copy, PartialEq, Eq, Hash, Serialize, Deserialize)]
pub enum ThematicPattern {
Friend,
Mirror,
Anchor,
Ghost,
Catalyst,
Threshold,
Remnant,
System,
Nobody,
}
```
Pattern-specific server-side state needed for v0.1:
| Pattern | Extra State Beyond D-024 | v0.1? |
|---------|-------------------------|-------|
| FRIEND | `FriendArc` component — phase tracking, contradiction fact IDs, tell progression stage, discovery state | YES (Kael, Sera) |
| MIRROR | None — MIRROR power is *absence* of contradiction. Normal D-024 axes, no secret, no hidden state. | YES (Naia Tamm) |
| ANCHOR | None — contentment axis (already exists) IS the anchor mechanic. | Maybe |
| GHOST | `GhostInfluence` — list of entities this ghost controls, communication channel. Not physically present. | NO (v0.2+) |
| CATALYST | `CatalystTrigger` — arrival condition, disruption event chain. | NO (v0.2+) |
| THRESHOLD | `GateCondition` — what the player needs to pass. Maps to knowledge prerequisites. | Maybe |
| REMNANT | None — InformationInventory with deep historical facts suffices. | Maybe |
| SYSTEM | `InstitutionalRole` — faction affiliation, procedure set, authority level. | YES (Torek) |
| NOBODY | `NobodyState` — promotion stage (Nobody/Noticed/Recognized/Known/Invested), interaction counter, dormant pattern+motivation. | DEFERRED per workshop brief |
THE FRIEND is the only pattern that requires a dedicated component in v0.1:
```rust
/// THE FRIEND arc state (D-034).
/// Tracks the emotional progression that exercises every content pipeline.
/// One per FRIEND NPC (Kael for smuggler, Sera for detective).
#[derive(Component, Debug, Clone, Serialize, Deserialize)]
pub struct FriendArc {
/// Which playable character this FRIEND belongs to.
/// The simulation doesn't know "the player" — it knows character IDs.
pub bonded_character: StableId,
/// Current arc phase. Advances based on knowledge events + interaction count.
pub phase: FriendPhase,
/// FactIds that constitute the contradiction (e.g., "kael.secret_meetings").
/// When the bonded character learns these, phase shifts to Doubt.
pub contradiction_facts: Vec<FactId>,
/// Tell progression: index into the tell sequence.
/// Tells become more visible as phase advances.
pub tell_stage: u8,
/// Has the bonded character directly observed the contradiction?
pub contradiction_discovered: bool,
}
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash, Serialize, Deserialize)]
pub enum FriendPhase {
/// Default — warmth, trust-building. "We're in this together."
Warmth,
/// Player has hints — something is off. Tells become visible.
Trust,
/// Contradiction evidence accumulating. Monologue turns questioning.
Doubt,
/// Direct confrontation or discovery. Relationship fractures.
Conflict,
}
```
### What Each Motivation Requires (System B)
Motivations define what the character *does in gameplay*. Like patterns, most behavior comes from D-024 axes. The motivation tag gates which interaction options the server offers and how the NPC responds in dialogue selection.
```rust
/// System B: Functional motivation tag.
/// Drives NPC behavior in interactions — what they want from the player,
/// what information they'll share, how they respond to pressure.
#[derive(Component, Debug, Clone, Copy, PartialEq, Eq, Hash, Serialize, Deserialize)]
pub enum FunctionalMotivation {
Handler,
Witness,
Turncoat,
Civilian,
Operator,
Skeptic,
}
```
Motivation-specific state:
| Motivation | Extra State | v0.1 Notes |
|-----------|-------------|------------|
| HANDLER | `HandlerState` — which entities they manage, pressure level, directive queue | YES — Voss manages the ring |
| WITNESS | `WitnessKnowledge` — specific observed FactIds, willingness to share, fear level | YES — key investigation mechanic |
| TURNCOAT | `LoyaltyState` — current allegiance, flip conditions, which side they're reporting to | Maybe (depends on NPC mapping) |
| CIVILIAN | None — the *absence* of special state IS the civilian mechanic. Normal D-024 axes. | YES — most Tier 3 NPCs |
| OPERATOR | `OperatorGoal` — current objective, resources managed, competence level | YES — Kael, Lera |
| SKEPTIC | `SkepticTarget` — what institution/system they doubt, what questions they ask | Maybe |
Most motivations don't need dedicated components. The motivation tag + existing D-024 axes + content tagging (D-035) handle the behavioral differentiation. The server's job is to expose the tag for content selection, not to simulate each motivation as a separate state machine.
### Proposed ECS Component Design (v0.1 Complete)
Here's the full component bundle for spawning an NPC entity. Components are split into identity (always present), behavioral (from D-024), pattern/motivation (System A+B), and optional:
```rust
/// Identity components — every NPC has these
pub struct NpcIdentity {
pub stable_id: StableId, // server-side, never changes
pub canonical_id: String, // content-addressing key ("sova.kael_davan")
pub display_name: String, // "Kael Davan"
pub short_name: String, // "Kael" — used in social contexts (D-036)
}
/// Content tier — determines simulation depth (D-026 + D-029)
#[derive(Component, Debug, Clone, Copy, PartialEq, Eq, Hash, Serialize, Deserialize)]
pub enum ContentTier {
Tier1, // Production-level (FRIEND, MIRROR) — full sim, all axes active
Tier2, // Templated with variation — full sim, most axes active
Tier3, // Procedural filler — background sim, minimal axes
}
/// Access tier map — D-028 Layer 1.
/// Determines which dialogue access tiers this NPC responds to
/// for each interacting character.
#[derive(Component, Debug, Clone, Serialize, Deserialize)]
pub struct AccessTierMap {
/// Default access tier for unknown characters
pub default_access: AccessTier,
/// Per-entity overrides (e.g., Kael treats smuggler as "insider")
pub overrides: BTreeMap<StableId, AccessTier>,
}
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash, Serialize, Deserialize)]
pub enum AccessTier {
Public,
Insider,
Authority,
Peer,
Hostile,
}
/// Trust level for gossip gating — D-028 Layer 3.
/// Per-relationship trust determines disclosure tier.
#[derive(Component, Debug, Clone, Serialize, Deserialize)]
pub struct TrustLevels {
/// Per-entity trust level. Absent = surface only.
pub levels: BTreeMap<StableId, TrustTier>,
}
#[derive(Debug, Clone, Copy, PartialEq, Eq, PartialOrd, Ord, Hash, Serialize, Deserialize)]
pub enum TrustTier {
Surface = 0,
Real = 1,
Secret = 2,
}
/// Triangle membership — which social triangles this NPC participates in.
/// Used by the server to determine which events ripple through which NPCs.
#[derive(Component, Debug, Clone, Serialize, Deserialize)]
pub struct TriangleMembership {
pub triangles: Vec<TriangleRef>,
}
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct TriangleRef {
pub triangle_id: String, // "hub_power", "dock_loyalty", etc.
pub role: String, // NPC's role within this triangle
}
/// NPC routine — schedule-based movement (D-031 day phases)
#[derive(Component, Debug, Clone, Serialize, Deserialize)]
pub struct NpcRoutine {
pub schedule: Vec<RoutineEntry>,
}
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct RoutineEntry {
pub phase: DayPhase,
pub location: String, // canonical location ID ("sova.terminal", "sova.last_shift")
pub tile: TilePosition, // exact position within location
pub activity: String, // "working", "drinking", "patrolling" — drives animation + availability
}
/// Mood state — drives D-035 mood tag selection for dialogue lines
#[derive(Component, Debug, Clone, Serialize, Deserialize)]
pub struct MoodState {
pub current_mood: Mood,
pub stress: f32, // 0.0-1.0, accumulated from events
}
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash, Serialize, Deserialize)]
pub enum Mood {
Neutral,
Friendly,
Guarded,
Anxious,
Hostile,
Distracted,
Resigned,
Amused,
}
```
**Full NPC entity bundle for spawning:**
```rust
/// Everything needed to spawn a v0.1 NPC entity.
/// Not all components required — ContentTier determines which are populated.
struct NpcBundle {
// Always present:
npc: Npc,
identity: NpcIdentity,
content_tier: ContentTier,
pattern: ThematicPattern,
motivation: FunctionalMotivation,
position: TilePosition,
knowledge: KnowledgeGraph,
routine: NpcRoutine,
// Tier 1-2:
want: Want,
secret: Secret,
relationships: Relationships,
tolerance: ToleranceThreshold,
information: InformationInventory,
contentment: Contentment,
personality: PersonalityTraits,
tells: TellSystem,
skills: SkillSet,
access_tiers: AccessTierMap,
trust_levels: TrustLevels,
mood: MoodState,
triangles: TriangleMembership,
// Pattern-specific (optional):
friend_arc: Option<FriendArc>,
// Combat (optional, D-024):
combat: Option<CombatCapability>,
}
```
### Key Design Principle
The simulation guarantees: **pattern and motivation are tags for content selection, not unique simulation subsystems.** The server doesn't run 9 different pattern AIs. It runs one NPC tick loop that checks the pattern tag when selecting dialogue, scheduling tell visibility, and evaluating arc progression. THE FRIEND is the sole exception in v0.1 because its arc progression is load-bearing for the vertical slice.
---
## Topic 3: Content Loader — Load Sequence & NPC Spawning
### What the Server Content Loader Needs
The server needs to transform content files into ECS entities with components. State consistency requires a defined load sequence with validation at each stage.
**Server content requirements:**
1. **District definition** — map dimensions, chunk layout, walkability grid, z-levels, location boundaries
2. **NPC profiles** — identity, axes, pattern, motivation, routine, relationships, knowledge, access tiers
3. **FactId catalog** — all valid fact identifiers with metadata (what category, what it means)
4. **Triangle definitions** — which NPCs, what roles, escalation conditions
5. **Dialogue line pools** — tagged lines per D-035 (server does selection, client does display)
6. **Monologue pools** — tagged lines per D-035 (separate per character, D-032)
7. **Contraband definitions** — what items exist, manifest templates for ring operations
**What the server does NOT need from content files:**
- Visual assets (sprites, tilesets) — client only
- Audio assets — client only
- UI text that isn't dialogue/monologue — client only
- Wiki prose — authoring format only
### Proposed Load Sequence
```
PHASE 1: VALIDATE
Read content manifest (content/manifest.ron)
Validate all referenced files exist
Validate schema compliance (FactId catalog, NPC profiles, etc.)
FAIL FAST if any validation error — do not partially load
PHASE 2: GLOBAL RESOURCES
Load FactId catalog → FactCatalog resource
Load contraband definitions → ContrabandDefs resource
Load triangle definitions → TriangleDefs resource
Load dialogue pools → DialoguePool resource
Load monologue pools → MonologuePool resource (per-character, D-032)
PHASE 3: MAP
Load district walkability grid → WalkabilityMap resource (already exists)
Load location boundaries → LocationMap resource (new)
Load interactable object positions → spawn Object entities
PHASE 4: ENTITIES
For each NPC profile:
Allocate StableId via EntityRegistry
Spawn entity with NpcBundle components (derived from profile)
Initialize KnowledgeGraph with background facts
Set initial position from routine (current day phase)
For each playable character:
Spawn with PlayerCharacter marker + full component set
Initialize KnowledgeGraph with character-specific background
PHASE 5: RELATIONSHIPS
Wire up Relationships components (now that all StableIds exist)
Wire up AccessTierMap overrides (per-entity access)
Wire up TrustLevels (per-entity trust)
Wire up FriendArc.bonded_character
Wire up TriangleMembership references
PHASE 6: VERIFY
Assert all StableId references resolve
Assert all routine locations exist in LocationMap
Assert all FactIds in NPC knowledge exist in FactCatalog
Assert FriendArc NPCs exist and are bonded to valid characters
Log load summary: N entities, M facts, K dialogue lines
```
Phase ordering matters. Phase 5 requires all entities from Phase 4 to exist (StableId resolution). Phase 3 must complete before Phase 4 (NPCs need valid positions). Phase 2 must complete before Phase 4 (NPCs reference FactIds and dialogue pools).
### How an NPC Profile Becomes a Spawned Entity
Assuming RON format (Tyre's call on format — I need structured, typed data, not free-form YAML):
```
// content/districts/sova/npcs/kael_davan.ron
NpcProfile(
canonical_id: "sova.kael_davan",
display_name: "Kael Davan",
short_name: "Kael",
content_tier: Tier1,
pattern: Friend,
motivation: Operator,
// D-024 axes
want: "Exit the ring, protect partner Naia. Wants a clean life.",
secret: "Meeting unknown contact in restricted corridor. Trying to leave the ring.",
tolerance_threshold: 0.65,
contentment: 0.4,
personality: ["loyal", "cautious", "practical"],
skills: ["cargo_handling", "logistics", "forging_manifests"],
combat_trained: false,
// Routine (D-031 day phases)
routine: [
(phase: Morning, location: "sova.terminal", tile: (42, 18, 0), activity: "working"),
(phase: Afternoon, location: "sova.terminal", tile: (45, 20, 0), activity: "working"),
(phase: Evening, location: "sova.last_shift", tile: (80, 55, 0), activity: "drinking"),
(phase: Night, location: "sova.residential", tile: (30, 70, 0), activity: "sleeping"),
],
// Knowledge — what Kael knows at game start
background_facts: [
("contraband.ring_exists", KnowsDetails),
("contraband.lattice_components", KnowsDetails),
("npc.voss.is_handler", KnowsDetails),
("npc.naia.partner", KnowsDetails),
("location.restricted_corridor", KnowsOf),
],
// Relationships (resolved to StableIds at load time via canonical_id lookup)
relationships: [
(target: "sova.naia_tamm", kind: "partner", trust: Real),
(target: "sova.voss", kind: "handler", trust: Real),
(target: "sova.drin", kind: "colleague", trust: Surface),
],
// Access tiers — who can talk to Kael at what level
access: (
default: Public,
overrides: [
("sova.smuggler", Insider), // smuggler PC gets insider access
("sova.detective", Public), // detective is just another face
("sova.voss", Peer),
],
),
// FRIEND-specific (only if pattern == Friend)
friend_arc: Some((
bonded_character: "sova.smuggler",
initial_phase: Warmth,
contradiction_facts: [
"kael.secret_meetings",
"kael.restricted_corridor_visits",
],
)),
// Tell system (D-034)
tells: [
"Checks comm device when alone — frequency increases as stress rises",
"Avoids eye contact with Voss after receiving new instructions",
"Takes longer routes to avoid restricted corridor during busy hours",
],
)
```
**Load transformation:**
1. Parser reads `NpcProfile` from RON file
2. Loader allocates `StableId` via `EntityRegistry::register()`
3. Canonical ID → StableId mapping stored in `ContentAddressMap` resource
4. Components constructed from profile fields — string references to other NPCs deferred to Phase 5
5. `KnowledgeGraph::with_background()` called with the background_facts list
6. Entity spawned with full component bundle
7. Phase 5: `relationships`, `access.overrides`, `trust_levels`, and `friend_arc.bonded_character` resolved using `ContentAddressMap` canonical_id → StableId lookup
### Resources the Loader Creates
```rust
/// Maps canonical content IDs to runtime StableIds.
/// Created during Phase 4, used in Phase 5 for reference resolution.
#[derive(Resource)]
pub struct ContentAddressMap {
pub by_canonical: BTreeMap<String, StableId>,
}
/// All valid FactIds in this district + global facts.
/// Used for validation and monologue prerequisite checking.
#[derive(Resource)]
pub struct FactCatalog {
pub facts: BTreeMap<FactId, FactMetadata>,
}
pub struct FactMetadata {
pub category: String,
pub description: String,
pub discoverable_by: Vec<String>, // which characters can learn this
}
/// Location boundaries within the district.
/// Maps location IDs to tile regions for proximity triggers.
#[derive(Resource)]
pub struct LocationMap {
pub locations: BTreeMap<String, LocationDef>,
}
pub struct LocationDef {
pub canonical_id: String,
pub bounds: Vec<TilePosition>, // bounding polygon or rect
pub z_level: i32,
}
/// Tagged dialogue line pool (D-028, D-035).
/// Server selects lines; client displays them.
#[derive(Resource)]
pub struct DialoguePool {
pub lines: Vec<DialogueLine>,
// Indices by role, access, trust for fast filtering
pub by_role: BTreeMap<String, Vec<usize>>,
}
/// Tagged monologue line pool (D-032, D-035).
/// Separate per playable character — hard partition.
#[derive(Resource)]
pub struct MonologuePool {
pub smuggler: Vec<MonologueLine>,
pub detective: Vec<MonologueLine>,
}
```
---
## Topic 4: Interaction Model — Server Events & Availability
### Minimum Server Events for v0.1
The simulation needs to support four interaction types: approach + dialogue, monologue triggers, object examination, and overhearing. Each requires specific server-side events.
```rust
/// Interaction events flowing through the server.
/// Produced by interaction systems, consumed by dialogue/monologue/knowledge systems.
#[derive(Debug, Clone)]
pub enum InteractionEvent {
/// Player entered proximity range of an NPC (triggers interaction availability).
/// Range: configurable, default 3 tiles (Manhattan distance).
ProximityEnter {
character: Entity,
target: Entity,
distance: u32,
},
/// Player left proximity range of an NPC.
ProximityExit {
character: Entity,
target: Entity,
},
/// Player requested interaction with target entity.
/// Server validates: is target in range? Is target interactable? What options?
InteractionRequest {
character: Entity,
target: Entity,
tick: u64,
},
/// Server response: available interaction options for this target.
/// Sent to client via ObserverSnapshot extension.
InteractionOptions {
character: Entity,
target: Entity,
options: Vec<InteractionOption>,
},
/// Player selected a dialogue topic/line.
DialogueSelect {
character: Entity,
npc: Entity,
topic: String,
tick: u64,
},
/// Server selected a dialogue response (D-035 pipeline output).
DialogueResponse {
npc: Entity,
line_id: String,
text: String,
// Knowledge updates that result from this line being spoken
knowledge_grants: Vec<KnowledgeGrant>,
},
/// Conversation ended (player walked away, topic exhausted, NPC terminated).
DialogueEnd {
character: Entity,
npc: Entity,
reason: DialogueEndReason,
},
/// Monologue triggered by game state (D-035 trigger types).
MonologueTrigger {
character: Entity,
trigger_type: MonologueTriggerType,
context: MonologueContext,
},
/// Player examined an interactable object.
ExamineObject {
character: Entity,
object: Entity,
tick: u64,
},
/// Overheard conversation fragment (proximity-based, D-018 sound model).
OverheardFragment {
listener: Entity,
speakers: Vec<Entity>,
content_hint: String, // not full text — what the listener picked up
knowledge_grants: Vec<KnowledgeGrant>,
},
}
#[derive(Debug, Clone)]
pub struct InteractionOption {
pub kind: InteractionKind,
pub label: String, // displayed to player
pub enabled: bool, // false = visible but greyed out (shows the player what's possible)
pub disabled_reason: Option<String>, // why it's greyed out
}
#[derive(Debug, Clone, Copy, PartialEq, Eq)]
pub enum InteractionKind {
Talk, // initiate dialogue
Examine, // look more closely
Overhear, // listen to nearby conversation (passive — may not need explicit action)
}
#[derive(Debug, Clone, Copy, PartialEq, Eq)]
pub enum DialogueEndReason {
PlayerLeft, // walked out of range
TopicExhausted, // no more lines available
NpcTerminated, // NPC ended conversation (mood, tolerance)
Interrupted, // another event broke the conversation
}
/// What knowledge a dialogue line grants when spoken.
#[derive(Debug, Clone)]
pub struct KnowledgeGrant {
pub grant_type: KnowledgeGrantType,
}
#[derive(Debug, Clone)]
pub enum KnowledgeGrantType {
LearnFact { fact_id: FactId, confidence: KnowledgeConfidence },
LearnAttribute { target: StableId, key: String, value: String },
UpdateRelationship { target: StableId, new_state: RelationshipState },
}
/// Monologue trigger types (D-035 `trigger` enum).
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash, Serialize, Deserialize)]
pub enum MonologueTriggerType {
EnterLocation,
ObserveNpc,
HearSound,
ObserveAnomaly,
PostConversation,
DiscoverEvidence,
WitnessInteraction,
TimeIdle,
ReturnVisit,
}
/// Context passed with monologue triggers for line selection.
#[derive(Debug, Clone)]
pub struct MonologueContext {
pub location: Option<String>,
pub observed_npc: Option<StableId>,
pub relevant_facts: Vec<FactId>,
}
```
### Proximity Trigger System
```rust
/// System: check proximity between player character and NPCs each tick.
/// Emits ProximityEnter/ProximityExit events when distance crosses threshold.
/// v0.1 uses Manhattan distance on same z-level. Simple, deterministic.
const INTERACTION_RANGE: u32 = 3;
fn check_proximity(
player_query: Query<(Entity, &TilePosition), With<PlayerCharacter>>,
npc_query: Query<(Entity, &TilePosition), With<Npc>>,
mut proximity_state: ResMut<ProximityState>,
mut events: ResMut<InteractionEventQueue>,
time: Res<SimulationTime>,
) {
let Ok((player_entity, player_pos)) = player_query.single() else { return };
for (npc_entity, npc_pos) in npc_query.iter() {
let distance = player_pos.manhattan_distance(npc_pos);
let in_range = distance.is_some_and(|d| d <= INTERACTION_RANGE);
let was_in_range = proximity_state.is_near(player_entity, npc_entity);
if in_range && !was_in_range {
proximity_state.set_near(player_entity, npc_entity);
events.push(InteractionEvent::ProximityEnter {
character: player_entity,
target: npc_entity,
distance: distance.unwrap(),
});
} else if !in_range && was_in_range {
proximity_state.set_far(player_entity, npc_entity);
events.push(InteractionEvent::ProximityExit {
character: player_entity,
target: npc_entity,
});
}
}
}
/// Tracks which entities are currently in proximity.
/// BTreeSet for deterministic iteration.
#[derive(Resource, Default)]
pub struct ProximityState {
near_pairs: BTreeSet<(Entity, Entity)>,
}
```
### How the Server Determines Available Interaction Options
When the player sends `PlayerAction::Interact`, the server runs a pipeline:
```
1. RANGE CHECK
Is there an NPC or interactable object within INTERACTION_RANGE?
If multiple targets, pick closest (Manhattan distance tiebreaker: lowest StableId).
2. AVAILABILITY CHECK (per target)
Is the NPC in an interactable activity? (not sleeping, not in combat)
What's the NPC's current mood? (Hostile NPCs may refuse)
Is the NPC already in conversation with someone else?
3. ACCESS TIER RESOLUTION
Look up AccessTierMap for the interacting character.
Determine: Public / Insider / Authority / Peer / Hostile access level.
4. OPTION GENERATION
Talk: always available if NPC is interactable + not hostile
Examine: always available for objects, available for NPCs if in LOS
(Overhear is passive — triggered by proximity to NPC-NPC conversations, not by player action)
5. RESPONSE
Pack InteractionOptions into ObserverSnapshot extension.
Client renders the context-sensitive prompt.
```
The critical insight: **the server never sends dialogue text unprompted.** The flow is:
- Server tells client "you can Talk to Kael" (via snapshot)
- Client shows interaction prompt
- Player selects "Talk"
- Server runs dialogue selection pipeline (D-035: access filter → situation filter → trust filter → mood/topic weighted selection)
- Server sends selected line + any knowledge grants
- Client displays line, processes knowledge grants
This keeps the server authoritative over what you can learn and when.
### What Goes into the ObserverSnapshot (v3)
The ObserverSnapshot needs new fields for interaction support:
```rust
pub struct ObserverSnapshot {
// ... existing v2 fields ...
/// NPCs currently in interaction range with available options.
pub nearby_interactions: Vec<NearbyInteraction>,
/// Active dialogue state (if in conversation).
pub active_dialogue: Option<ActiveDialogue>,
/// Monologue lines triggered this tick.
pub monologue_lines: Vec<MonologueLine>,
/// Overheard fragments (proximity-based).
pub overheard: Vec<OverheardLine>,
}
pub struct NearbyInteraction {
pub entity_id: u64, // StableId
pub display_name: String,
pub options: Vec<InteractionOption>,
}
pub struct ActiveDialogue {
pub npc_entity_id: u64,
pub npc_name: String,
pub current_line: Option<DialogueLineDisplay>,
pub available_topics: Vec<String>,
}
pub struct DialogueLineDisplay {
pub line_id: String,
pub text: String,
pub mood: String,
}
pub struct MonologueLine {
pub line_id: String,
pub text: String,
pub trigger: MonologueTriggerType,
}
pub struct OverheardLine {
pub speaker_id: u64,
pub fragment: String,
}
```
---
## Topic 5: Server Features Blocked by Missing Content
### What I Can Build Right Now (No Content Dependency)
These server systems are purely structural — they need the *schema* but not the *data*:
| System | Status | Blocked? |
|--------|--------|----------|
| Content loader framework (Phase 1-6 skeleton) | Can build | NOT blocked — test with fixture data |
| Proximity trigger system | Can build | NOT blocked |
| Interaction event pipeline | Can build | NOT blocked |
| Dialogue selection pipeline (D-035 tag filtering) | Can build | NOT blocked — test with synthetic tagged lines |
| Monologue trigger system | Can build | NOT blocked — test with synthetic lines |
| Monologue prerequisite checker | Already built (KnowledgeGraph.fact_at_least) | Done |
| NPC routine scheduler (day phase → position) | Can build | NOT blocked |
| Knowledge decay | Already built | Done |
| FriendArc phase transition logic | Can build | NOT blocked — trigger conditions are structural |
### What I Cannot Build Without Content
| Blocked Feature | What Content Is Missing | Who Produces It |
|----------------|------------------------|-----------------|
| **Actual NPC spawning** | NPC profiles in RON/YAML format. Need all 17 Sova NPCs with axes, routine, relationships, background knowledge, access tiers. | Paula (profiles) + Tyre (format) |
| **Dialogue selection testing with real lines** | Tagged dialogue line pools per D-035. Need at minimum THE FRIEND lines (Kael: ~70-100, Sera: ~70-100) and a baseline pool for Tier 2-3 NPCs. | Mellanie (authored lines) |
| **Monologue testing with real lines** | Tagged monologue pools per D-032/D-035. Need smuggler pool + detective pool, minimum viable before repetition. | Mellanie (authored lines) |
| **NPC routine pathfinding** | District map with walkability data and location definitions. Need the Sova Transit District spatial layout. | Tyre (map format) + Stig (Godot map editor?) |
| **Overheard conversations** | NPC-to-NPC conversation scripts or generation rules. Which NPCs talk to each other, about what, when. | Paula (scripts) + Gestalt (rules) |
| **FactId catalog** | Complete list of discoverable facts for Sova, categorized. Currently wiki has some fact vocabulary but not a machine-readable catalog. | Gestalt (catalog design) + Paula (fact content) |
| **Triangle escalation logic** | Formal escalation conditions for each triangle. "When X learns Y, Z happens." Currently prose descriptions only. | Gestalt (conditions) + Paula (narrative) |
| **Contraband manifest data** | Manifest templates, discrepancy patterns, cargo types. Detective investigation vectors need concrete data. | Miri (setting) + Gestalt (mechanics) |
### Priority Order for Unblocking
1. **FactId catalog** — blocks everything knowledge-related. I need the schema NOW, content can come incrementally.
2. **NPC profiles in structured format** — blocks spawning. Even partial profiles unblock integration testing.
3. **District spatial layout** — blocks routine scheduler, proximity system integration testing.
4. **Dialogue line pools** — blocks dialogue pipeline integration. Synthetic data works for unit tests but not for end-to-end.
5. **Monologue line pools** — blocks monologue pipeline integration. Same story.
### What I Propose to Do in Parallel
While content is being produced, I'll build with fixture/synthetic data:
- **Fixture NPC profiles**: hand-write 3-4 test profiles (Kael, Sera, one Tier 2, one Tier 3) in whatever format Tyre proposes. These become the "reference implementation" that real profiles must match.
- **Synthetic dialogue pool**: ~20-30 tagged lines exercising all D-035 tags. Enough to test the selection pipeline, not enough to feel like a game.
- **Synthetic monologue pool**: ~10-15 lines per character with varied trigger types and prerequisites.
- **Test district map**: 50x50 walkable area with 3 blocked-out locations (terminal, bar, corridors).
This lets me build and test every system end-to-end. When real content arrives, it drops into the same loader — the schema is the contract.
### One Dependency I Need Resolved
**The Interact action is currently a no-op** (`server/src/simulation/input.rs:86`). To build the interaction pipeline, I need to extend `PlayerAction` with:
```rust
pub enum PlayerAction {
// ... existing variants ...
Interact, // becomes: interact with nearest target
InteractWith(u64), // interact with specific entity by StableId
SelectDialogueTopic(String), // choose a topic in active dialogue
EndDialogue, // walk away from conversation
}
```
This is a protocol change (ObserverSnapshot v2 → v3). Stig needs to know about the new snapshot fields. I need Tyre's sign-off on the protocol evolution strategy.
docs/workshops/v01-content-scoping/round1-gestalt.md
-468
View File
@@ -1,468 +0,0 @@
# Round 1 — Gestalt (Systems Design)
*cracks knuckles*
Let me break down what all of this actually means mechanically.
---
## Topic 1: Wiki Fixes
### 1a. Do any triangles need restructuring beyond Triangle 1?
**Triangle 1 (Hub Power)**: Yes, needs a fork. Addressed below.
**Triangle 2 (Worried Knowledge)**: Structurally sound but smuggler lens is weak. The smuggler "manages" Maret and Drin — that's passive. The smuggler needs a DECISION in this triangle too. Proposed fix: when Maret gets close to reporting, the smuggler can either (a) feed Maret a cover story through Voss, (b) pressure Drin to reassure Maret, or (c) let it ride and hope Maret stays scared. This isn't a restructure — it's adding a smuggler decision node to an existing triangle.
**Triangle 3 (Bar Tensions)**: Fine as-is. This is a MUNDANE triangle (D-029: 50% mundane). Its job is to be noise floor. Torek's ambiguous spending, Olin's ambiguous intent, Lera's ambiguous loyalty — the player reads signals that might mean nothing. That IS the mechanic. Don't add a fork — the ambiguity IS the fork. The player decides whether to investigate or ignore, and both decisions have consequences (wasted time or missed signal).
**Triangle 4 (Worried Partner)**: Excellent. No changes. Both FRIEND NPCs are nodes. The triangle IS the contradiction structure. This is the best-designed triangle in the set.
**Triangle 5 (Informant Question)**: Structurally sound but resolution timing matters. Pell's wavering, Renn's suspicion, Drin's vulnerability — all three paths toward unraveling operate on different timescales. In a 30-minute session, the player observes the TENSION but probably doesn't see the RESOLUTION. That's fine for v0.1 — the tension is the content, the resolution is the hook for continued play. No restructure needed, but we need to be explicit: Triangle 5 is a **passive triangle** in v0.1 (observable tension, unresolved fork).
**Summary: Active vs. Passive Triangles for v0.1**
| Triangle | Status | Smuggler Decision? | Detective Decision? | Resolution in 30 min? |
|----------|--------|---------------------|---------------------|----------------------|
| 1: Hub Power | **Active** | YES (escalation fork) | No (observes consequences) | Partial |
| 2: Worried Knowledge | **Active** | YES (manage Maret) | YES (flip Drin or work Maret) | Partial |
| 3: Bar Tensions | **Passive** | No (assess risk) | No (read signals) | No (ambiguity is permanent) |
| 4: Worried Partner | **Active** | YES (protect Kael/lie to Hael) | YES (ask Sera about Hael) | Yes (FRIEND contradiction) |
| 5: Informant Question | **Passive** | No (observes Pell's nervousness) | No (sees downstream signals) | No (hook for continuation) |
**3 active forks, 2 passive tensions. That's correct for 30 minutes.**
---
### 1b. Triangle 1 Fork Design
The existing triangle: Nils (off-stage) pushes for higher volume. Voss (shift supervisor) wants stability. Kael is caught between sibling loyalty and operational caution. The smuggler's role is currently passive — they just watch.
**The fork: The Escalation Decision**
**Setup (minute 5-10):** Devra approaches the smuggler during a routine shift. Message from Nils: next shipment is double volume. Nils needs more hands and wider timing windows. Voss has to adjust the shift schedule to create a bigger gap. The smuggler is asked to help convince Voss — or handle the extra volume personally.
**The smuggler decides:**
| Choice | Immediate Effect | Triangle Consequence | Detective Signal | Mechanical Outcome |
|--------|-----------------|---------------------|-----------------|-------------------|
| **Side with Nils (escalate)** | Extra shipment gets handled. More money. Kael is relieved (less family pressure). | Voss gets more anxious, becomes sloppy. Voss's tells accelerate. Operation becomes more visible. | Manifest discrepancies spike. Voss's behavior flags: `"nervous,schedule_changes,evasive"`. Detective investigation ACCELERATES. | `exposure_risk` increases globally. `cover_integrity` of ring drops to `"thin"`. Wow moment #2 (Character's Eye) triggers EARLIER. |
| **Side with Voss (stabilize)** | Shipment gets rejected or delayed. Nils applies more pressure on Kael directly. | Kael's distraction increases (more contact with exit coordinator). Operation stays quiet but INTERNAL tension builds. | Fewer observable signals. Detective investigation SLOWS. But Kael's tells (lattice checking, distraction) become more visible. | `exposure_risk` stays low. But Kael's `behavior_flags` escalate faster. FRIEND contradiction (wow moment #3) hits HARDER because it comes from internal pressure, not external. |
| **Mediate (delay)** | Smuggler proposes a compromise: half volume increase, phased over two shipments. Neither side satisfied. | Nils loses confidence in the smuggler. Voss is temporarily calmed. Kael is confused ("I thought you were handling this"). | Mixed signals. Operation is inconsistent — some shifts are busier, others normal. Detective reads organizational confusion accurately. | Smuggler's `operational_trust` with Nils drops. Smuggler's relationship with Devra becomes strained. Creates a SECOND decision point later when Nils sends a more forceful message. |
**What the detective observes (per smuggler choice):**
The detective doesn't see the decision. They see its CONSEQUENCES:
- **Post-escalation:** "Voss changed the night shift schedule. Third time this week. The pattern is getting louder." Monologue trigger: `observe_anomaly` + `prerequisite: { "investigation.shift_mismatch": "Suspects" }`. The detective's investigation accelerates because Voss's anxiety produces more observable signals.
- **Post-stabilize:** "The hub's been quiet this week. Schedules normal. But that dock worker — Kael — he's checked his lattice eleven times this shift." The detective's investigation pivots from institutional signals (schedules, manifests) to personal signals (Kael's behavior).
- **Post-mediate:** "Something's off. Last night's shift had extra cargo. Tonight it's normal. There's no pattern I can find, and that's the pattern." The detective is confused, which is realistic and interesting — real investigations hit dead ends.
**Key design note:** The fork doesn't change WHAT the detective discovers — it changes WHEN and HOW. All three paths lead to the ring. The smuggler's choice shapes the detective's journey, not the detective's destination.
---
### 1c. Should Drin be promoted to Tier 2?
**Yes. Unambiguously.**
Drin is doing Tier 2 work in a Tier 3 body. Mechanically, Drin is:
- Member of Triangle 2 (Worried Knowledge) — one of our 3 active triangles
- Member of Triangle 5 (Informant Question) — one of our 2 passive triangles
- Compromised by Harek (gambling debt) — a coercion arc
- The easiest NPC for the detective to flip
- The most vulnerable ring asset for the smuggler to manage
- A bridge between 2 triangles across 2 social sites
A Tier 3 NPC gets ~10-15 authored lines and 3 axes (Want, Routine, Personality). That's not enough for an NPC who appears in 2 triangles and is a potential informant.
**Tier 2 requires:**
| Axis | Drin's Content |
|------|---------------|
| **Want** | Keep his job, clear the debt, stop looking over his shoulder |
| **Secret** | Gambling debt to Harek. Harek holds IOUs. Drin looks the other way during inspections in exchange for debt forgiveness. |
| **Relationship 1** | Harek (debt holder, coercer) — fear-based, asymmetric |
| **Relationship 2** | Voss (depends on Drin's compliance) — professional, strained |
| **Relationship 3** | Maret (colleague, doesn't know about Drin's compromise) — guilt-adjacent |
| **Tolerance** | LOW — already past breaking. The compromise IS his post-threshold state. |
| **Routine** | Maintenance shifts, inspection rounds (these ARE the windows he's leaving open) |
| **Information** | Knows inspection schedule gaps, knows he's being used, doesn't know ring structure beyond "someone benefits from my compliance" |
| **Contentment** | Very low. Trapped. Remembers when the job was just a job. |
| **Personality** | Quiet, avoidant, anxious. Doesn't make eye contact during compromised inspections. |
| **Tell** | Changes route when Harek is present. Shorter inspection times on specific shifts. Increased break frequency (stress smoking equivalent). |
| **Skills** | Maintenance tech, inspection procedures. No combat. |
**Content requirement: ~40-60 authored lines** (Tier 2 standard):
- 15-20 dialogue (routine greetings, deflection, cracking under pressure)
- 8-12 trust-gated (what Drin reveals when scared vs. when trusting)
- 5-8 unprompted (nervous comments, redirect attempts)
- 5-8 monologue per character (detective: "He's hiding something, his inspection times are irregular" / smuggler: "Drin's been twitchy. If he cracks, we're all exposed")
**Tier adjustment: Tier 3 roster drops from 5 to 4** (Sess, Olin, Sabel, Tav). Tier 2 grows from 10 to 11. Total content budget increase: +30-45 authored lines. This is well within scope for the value Drin provides.
---
## Topic 2: v0.1 NPC Architecture
### 2a. Full NPC → Pattern + Motivation Mapping
Here's every NPC mapped. I'm assigning based on what each character DOES in v0.1, not what they might become at 300-world scale.
| # | Name | Tier | Thematic Pattern | Functional Motivation | Composition Rationale |
|---|------|------|-----------------|----------------------|----------------------|
| 1 | Kael Davan | **T1** | **FRIEND** | **OPERATOR** | Trust anchor hiding a contradiction + running ring cargo operations. FRIEND+OPERATOR = identity betrayal ("I didn't know who you really were") |
| 2 | Sera Venn | **T1** | **FRIEND** | **WITNESS** | Trust anchor hiding a contradiction + carrying unreported evidence. FRIEND+WITNESS = loyalty vs. duty ("She saw something and chose silence") |
| 3 | Voss | T2 | **SYSTEM** | **OPERATOR** | Institutional authority (shift supervisor) + running the schedule that enables smuggling. SYSTEM+OPERATOR = corrupted authority ("The system works for the wrong people") |
| 4 | Lera Sessik | T2 | **ANCHOR** | **OPERATOR** | "Is this enough?" embodied + running a business on willful ignorance. ANCHOR+OPERATOR = contentment with a price ("She makes it work by not looking") |
| 5 | Torek Lintar | T2 | **CATALYST** | **CIVILIAN** | His spending disrupts equilibrium + he's just living his life (spending money, going to the bar). CATALYST+CIVILIAN = accidental disruption ("He doesn't know he's a liability") |
| 6 | Devra | T2 | **THRESHOLD** | **HANDLER** | Gatekeeper between player and ring's deeper layers + managing operations from above. THRESHOLD+HANDLER = obstacle with authority ("You go through her or you don't go") |
| 7 | Maret Korr | T2 | **SYSTEM** | **WITNESS** | Institutional scheduler (the manifests, the numbers) + saw discrepancies she hasn't reported. SYSTEM+WITNESS = honest system under threat ("The numbers don't lie, but she might have to") |
| 8 | Resha | T2 | **CATALYST** | **SKEPTIC** | New hire whose questions force defensiveness + doubts the "mind your business" culture. CATALYST+SKEPTIC = innocent disruption ("They just asked a question. Everyone flinched.") |
| 9 | Naia Tamm | T2 | **MIRROR** | **CIVILIAN** | Honest transparency reveals others' dishonesty + living her life (teaching, worrying about Kael). MIRROR+CIVILIAN = innocence endangered ("The one person who isn't lying, surrounded by liars") |
| 10 | Drin | **T2** (promoted) | **REMNANT** | **TURNCOAT** | Remembers when the job was just a job + loyalty coerced from institution to ring by debt. REMNANT+TURNCOAT = corruption's collateral ("He was an honest inspector once") |
| 11 | Sess | T3 | **ANCHOR** | **CIVILIAN** | Quiet contentment behind the bar + uninvolved, discreet. ANCHOR+CIVILIAN = social wallpaper with depth ("The bartender sees everything and says nothing — because nothing's wrong with his life") |
| 12 | Olin | T3 | **CATALYST** | **SKEPTIC** | New arrival whose presence forces everyone to assess threat + asks questions with ambiguous intent. CATALYST+SKEPTIC = the unknown variable ("Friend or threat? The question itself is the disruption.") |
| 13 | Renn | T2 | **THRESHOLD** | **OPERATOR** | Physical gatekeeper of cargo movement (courier) + competent, goal-oriented, runs the route. THRESHOLD+OPERATOR = the machinery of the operation ("Renn moves the product. Get past Renn, you're inside.") |
| 14 | Pell | T2 | **CATALYST** | **TURNCOAT** | Wavering creates potential disruption to entire operation + loyalty actively shifting. CATALYST+TURNCOAT = ticking bomb ("When Pell breaks, everything moves.") |
| 15 | Harek | T2 | **GHOST** | **HANDLER** | Shapes events through debt leverage on Drin, not through direct ring membership + applies pressure from above (off-duty security with information and leverage). GHOST+HANDLER = invisible power ("Harek doesn't run the ring. He just owns the inspector.") |
| 16 | Sabel | T3 | **THRESHOLD** | **OPERATOR** | Off-station gatekeeper of supply chain + runs the external logistics. THRESHOLD+OPERATOR = distant machinery (1-2 brief appearances, mostly off-stage) |
| 17 | Tav | T3 | **SYSTEM** | **CIVILIAN** | Ring lookout following procedure + uninvolved beyond their assigned role. SYSTEM+CIVILIAN = the lowest rung ("Tav watches the door. That's it. That's the whole job.") |
**Pattern distribution:**
| Pattern | Count | NPCs | v0.1 Coverage |
|---------|-------|------|--------------|
| FRIEND | 2 | Kael, Sera | Full (production-level, D-034) |
| MIRROR | 1 | Naia Tamm | Full (T2, emotional depth) |
| ANCHOR | 2 | Lera, Sess | Full + sketch |
| SYSTEM | 3 | Voss, Maret, Tav | Full + sketch |
| THRESHOLD | 3 | Devra, Renn, Sabel | Full + sketch |
| CATALYST | 4 | Torek, Resha, Olin, Pell | Full + sketch |
| GHOST | 1 | Harek | Light (indirect power) |
| REMNANT | 1 | Drin | Light (promoted T2) |
| NOBODY | 0 | — | Deferred to v0.2 |
**Motivation distribution:**
| Motivation | Count | NPCs |
|-----------|-------|------|
| OPERATOR | 5 | Kael, Voss, Lera, Renn, Sabel |
| WITNESS | 2 | Sera, Maret |
| HANDLER | 2 | Devra, Harek |
| TURNCOAT | 2 | Drin, Pell |
| CIVILIAN | 5 | Torek, Naia Tamm, Sess, Olin, Tav |
| SKEPTIC | 2 | Resha, Olin |
Note: Olin gets dual motivation (CIVILIAN/SKEPTIC) because his intent is ambiguous. In the data, he's tagged SKEPTIC (asking questions), but the player doesn't know if that's genuine curiosity or something else.
**Composition check — does this create interesting interactions?**
Sova has 4 CATALYSTs. That's a lot. But it's thematically correct: this is a district under pressure. Multiple disruption sources is what makes the ring fragile and the investigation possible. Every CATALYST threatens the status quo differently — Torek through visibility, Resha through innocence, Olin through ambiguity, Pell through betrayal.
The 5 OPERATORs show a district where everyone is RUNNING something — cargo (Kael), schedules (Voss), a bar (Lera), a route (Renn), a supply line (Sabel). The district hums with operational competence. That's the "quotidian-with-undertow" atmosphere of D-036.
---
### 2b. Required vs. Deferrable Patterns and Motivations
**Required for v0.1** (must be present AND mechanically exercised):
| System | Required | Why |
|--------|----------|-----|
| FRIEND | Must ship | Emotional core, D-034, wow moments #3 and #4 |
| MIRROR | Must ship | Proves non-FRIEND Tier 1 depth works. Naia Tamm's honesty is the contrast that makes the liars visible. |
| ANCHOR | Must ship | "Is this enough?" is the thematic question. Lera must embody contentment-with-a-price. |
| SYSTEM | Must ship | Institutional authority is what the detective works within and the smuggler works around. Voss is essential. |
| THRESHOLD | Must ship | The investigation REQUIRES gatekeepers. Devra is the wall between the detective and the ring's interior. |
| CATALYST | Must ship | Without disruption, nothing happens in 30 minutes. Torek or Pell must force someone's hand. |
| OPERATOR | Must ship | People who run things ARE the district. |
| WITNESS | Must ship | Investigation requires witnesses. Sera and Maret. |
| HANDLER | Must ship | Pressure from above drives tension. Devra. |
| TURNCOAT | Must ship | Loyalty shifting is the detective's lever and the smuggler's fear. Drin or Pell. |
| CIVILIAN | Must ship | Noise floor (D-029). Without civilians, every NPC is suspicious. |
| SKEPTIC | Should ship | Questions create friction. Resha's honest questions. Low effort — just give Resha dialogue that asks inconvenient things. |
**Deferrable to v0.2+:**
| System | Status | Why Deferrable |
|--------|--------|----------------|
| GHOST (full) | Present, light | Harek's indirect power works at T2 without GHOST-specific mechanics. The "absent power" system (Nils operating off-stage, Ghost entities sending messages through intermediaries) is v0.2 content. |
| REMNANT (full) | Present, light | Drin's "remembers simpler times" is narrative color, not a mechanical system. v0.2 can add REMNANT-specific content (history triggers, memory-based dialogue). |
| NOBODY | **Deferred** | Dynamic tier promotion is a separate system. See 2c. |
---
### 2c. THE NOBODY — Ship in v0.1 or Defer?
**Recommendation: Ship DATA, defer MECHANIC.**
| What | v0.1 | v0.2 |
|------|------|------|
| Hidden pattern+motivation in NPC data | YES | YES |
| Tier 3 NPCs have name, routine, greeting | YES | YES |
| Interaction counter (track player attention) | NO | YES |
| Stage transitions (NOBODY → NOTICED → RECOGNIZED → KNOWN → INVESTED) | NO | YES |
| Dormant content activation (hidden Tier 2 content unlocks) | NO | YES |
| Content pool for promotion paths | NO | YES |
**Why defer the mechanic:**
1. **System scope**: Dynamic tier promotion requires an interaction counter, trigger evaluation, content activation pipeline, and enough dormant content to justify promotion. Each of those is a system to build, test, and prove. That's v0.2 scope.
2. **The wow moments don't need it**: D-039 lists 6 wow moments. None require NOBODY promotion. The 30-minute session proves observation, contradiction, divergence, and emotional attachment. NOBODY promotion is a 60+ minute payoff.
3. **Architectural compatibility**: The content schema includes hidden fields for pattern and motivation from day one. Tier 3 NPCs have `hidden_pattern` and `hidden_motivation` in their content files. The promotion engine reads these when it exists. Zero rework needed.
4. **Risk reduction**: If NOBODY promotion doesn't work (feels gamey, triggers too easily, content feels thin at activation), we haven't spent v0.1 effort on it.
**What this means for Tier 3 NPCs in v0.1:**
Sess, Olin, Sabel, Tav are functional sketches. They have names, routines, greetings, and 10-15 authored lines each. They feel like PEOPLE — they nod at you, they move through the district on schedule, they have brief exchanges with each other. They're just not promotion targets yet. In v0.1, the player's attention is on the 13 NPCs who are already activated (2 Tier 1, 11 Tier 2). That's plenty for 30 minutes.
---
### 2d. Smuggler Attributes → EntityKnowledge Keys
The wiki review identified 8 smuggler-specific attributes. Here's how they map to the knowledge graph.
**Existing keys that already serve double duty:**
| Wiki Attribute | Maps To | How It Works |
|----------------|---------|-------------|
| `trust_read` | **`trust_level`** (existing) | Same key, different interpretation per character. Detective: "will they cooperate?" Smuggler: "will they hold under pressure?" Values already cover both: `"trusted"`, `"reliable"`, `"uncertain"`, `"suspicious"`, `"compromised"`. |
| `leverage_held` | **`secret_held`** (existing) | Leverage IS secret knowledge. Smuggler knowing Drin's gambling debt is stored as `secret_held: "gambling_debt"`. The fact that this is leverage is contextual — the smuggler's operational framework makes it leverage, the detective's framework makes it evidence. Same data, different interpretation. |
**New smuggler-specific keys (4 for v0.1):**
| New Key | Value Format | Example | Mechanical Purpose |
|---------|-------------|---------|-------------------|
| `exposure_risk` | enum: `"minimal"`, `"moderate"`, `"high"`, `"critical"` | Torek: `"high"` (spending is visible). Maret: `"moderate"` (smart, might report). | Smuggler risk assessment. Gates monologue: "Torek's spending is going to get us all caught." Drives smuggler decisions about which NPCs to manage. |
| `loyalty_assessment` | enum: `"solid"`, `"reliable"`, `"uncertain"`, `"wavering"`, `"turned"` | Pell: `"wavering"`. Renn: `"solid"`. Kael: `"reliable"` (smuggler doesn't know about exit yet). | Operational trust map. Different from `trust_level` — that's interpersonal, this is operational. You can trust someone personally but doubt their operational loyalty. |
| `cover_integrity` | enum: `"solid"`, `"thin"`, `"cracking"`, `"blown"` | Kael: `"solid"` (baseline) → `"cracking"` (post-contradiction). Voss: `"thin"` (after escalation fork). | Cover assessment. When `cover_integrity` drops, smuggler monologue shifts: "Kael's cover is slipping. If I can see it, so can the detective." |
| `moral_weight` | enum: `"innocent"`, `"peripheral"`, `"complicit"`, `"compromised"`, `"willing"` | Naia Tamm: `"innocent"`. Drin: `"compromised"`. Lera: `"complicit"`. Kael: `"willing"`. | Moral arc driver. The smuggler's Comfort→Doubt→Reckoning→Compromise phases are tracked through who they've assessed as `"innocent"` vs. `"complicit"`. When innocents are threatened, the smuggler doubts. |
**Deferred to v0.2 (2 keys):**
| Deferred Key | Why Defer |
|-------------|-----------|
| `social_debt` | Favor economy doesn't have time to develop in 30 minutes. The smuggler doesn't owe or collect favors in the vertical slice — they make decisions. |
| `loyalty_conflict` | Can be inferred from `behavior_flags` + `loyalty_assessment`. Kael's conflict (ring vs. partner) shows up as `behavior_flags: "distracted,evasive"` + implicit knowledge from the smuggler's pre-existing information about Kael's home life. A dedicated key is cleaner but not essential. |
**Updated EntityKnowledge key count: 18** (14 existing + 4 new smuggler-specific)
| Category | Keys | Character |
|----------|------|-----------|
| Identity | `name`, `role`, `faction`, `species` | Both |
| Social | `relationship_type`, `trust_level` | Both |
| Behavioral | `routine_pattern`, `behavior_flags` | Both |
| Secret | `secret_held`, `secret_confidence` | Both |
| Detective-specific | `tell_observed`, `contradiction_flagged` | Detective |
| Smuggler-specific | `exposure_risk`, `loyalty_assessment`, `cover_integrity`, `moral_weight` | Smuggler |
**Symmetry note:** The detective has 2 specific keys (`tell_observed`, `contradiction_flagged`). The smuggler has 4. This asymmetry is intentional and correct. The detective's knowledge graph is EVIDENCE-focused (fewer keys, deeper per-NPC). The smuggler's is RISK-focused (more keys, broader assessment across all NPCs). Different information architectures for different gameplay loops.
**Full example — Smuggler's knowledge of Drin (post-Drin-promotion, mid-game):**
```rust
EntityKnowledge {
last_known_position: Some(TilePosition { x: 52, y: 18 }),
last_observed_tick: 1600,
last_updated_tick: 1600,
confidence: KnowledgeConfidence::KnowsDetails,
source: KnowledgeSource::Inferred {
basis: vec![FactId("relationship.trust_network".to_string())],
},
state: KnowledgeState::Active,
relationship: RelationshipState::Known,
known_attributes: BTreeMap::from([
("name".to_string(), "Drin".to_string()),
("role".to_string(), "maintenance tech".to_string()),
("faction".to_string(), "civilian".to_string()),
("relationship_type".to_string(), "asset".to_string()),
("trust_level".to_string(), "compromised".to_string()),
("routine_pattern".to_string(), "maintenance shifts, inspection rounds".to_string()),
("behavior_flags".to_string(), "nervous,avoids_harek_eye_contact".to_string()),
("secret_held".to_string(), "gambling_debt".to_string()),
("secret_confidence".to_string(), "confirmed".to_string()),
// Smuggler-specific:
("exposure_risk".to_string(), "high".to_string()),
("loyalty_assessment".to_string(), "uncertain".to_string()),
("cover_integrity".to_string(), "cracking".to_string()),
("moral_weight".to_string(), "compromised".to_string()),
]),
}
```
**How this drives gameplay:** The smuggler sees Drin and their monologue fires: "Drin's twitchy again. His cover's cracking. If the detective gets to him first, he'll fold in ten seconds." The `exposure_risk: "high"` + `cover_integrity: "cracking"` combination gates a smuggler decision: spend time reassuring Drin (protecting the operation) or write him off and plan for what happens when he breaks.
---
## Topic 4: Minimum Interaction Set
### What proves the core loop?
The core loop (D-027 criterion #4): **OBSERVE → NOTICE → FOLLOW → DISCOVER**
Let me map this to concrete interactions:
**7 interactions. No more.**
| # | Interaction | Input | System | Output | Proves |
|---|-------------|-------|--------|--------|--------|
| 1 | **Move** | WASD keys | Movement + collision | Position change, LOS update | Physical embodiment, exploration |
| 2 | **Look** | Passive (automatic) | Perception + LOS | See NPCs, objects, environment | Observation, spatial awareness |
| 3 | **Monologue** | Triggered (automatic) | Monologue system | Internal text + audio chime | Character voice, anomaly detection |
| 4 | **Examine Object** | Context-key on environment | Interaction system | Description text, knowledge update | Environmental investigation |
| 5 | **Examine NPC** | Context-key on NPC (non-dialogue) | Observation system | Behavioral observations, tell detection | Passive intelligence gathering |
| 6 | **Talk** | Context-key on NPC (dialogue) | Dialogue system | Tagged line selection, response | Active information gathering, confrontation |
| 7 | **Overhear** | Passive (proximity) | Sound/proximity system | Overheard dialogue fragments | Environmental intelligence, atmosphere |
**Why these 7 and not 6 or 8:**
The critical split is **Examine NPC vs. Talk**. These MUST be separate interactions:
- **Examine NPC** = study without initiating contact. You watch Kael from across the hub. Monologue fires: "He's checked his lattice three times since I sat down." Updates `behavior_flags` and `tell_observed`. No dialogue, no social cost.
- **Talk** = initiate dialogue. You walk up to Kael and say something. Tagged line selection fires based on access tier, trust level, situation. Social cost: Kael knows you engaged. NPCs react to being approached.
The detective's loop is: **Examine first** (accumulate tells across multiple observations) → **Talk later** (use evidence in confrontation). If you collapse Examine and Talk into one "Interact" action, the detective can't study behavior without initiating contact. That breaks the investigation loop.
The smuggler's loop is inverted: **Talk first** (social, operational, casual) → **Examine when suspicious** ("something's off with Kael, let me watch him"). If you collapse them, the smuggler can't shift from social mode to surveillance mode.
**Context-sensitive prompt logic:**
| Target | Range | Available Actions | Prompt Text |
|--------|-------|-------------------|-------------|
| NPC | Out of LOS | None | (not visible) |
| NPC | In LOS, far | Look (auto) | (no prompt — monologue may fire) |
| NPC | In LOS, mid | Look + Examine | `[E] Observe` |
| NPC | In LOS, close | Look + Examine + Talk | `[E] Observe` / `[F] Talk` |
| Object | In LOS, close | Examine | `[E] Examine` |
| NPC conversation | In earshot | Overhear (auto) | (no prompt — text appears as overheard) |
**What's explicitly NOT in the minimum set:**
| Excluded | Why | When |
|----------|-----|------|
| Inventory (pick up items) | v0.1 is about observation, not collection. Evidence is knowledge-graph entries, not physical items. | v0.2 |
| Stealth (crouch, hide) | No stealth system. The player's presence is always visible. Managing attention is social, not mechanical. | v0.3+ |
| Combat | Not in D-027 success criteria. No combat encounters in 30-minute session. | v0.2+ |
| Lattice query (search databases) | The detective's analytical lattice works through monologue, not a separate interaction. "Checking the manifest" = Examine Object, not a lattice query UI. | v0.2 (as expansion of Examine) |
| Trade/buy/sell | No economic interaction in v0.1. | v0.3+ |
| Use item | No item use. | v0.2+ |
**Does this minimum prove the 6 wow moments?**
| Wow Moment | Required Interactions | Covered? |
|------------|----------------------|----------|
| 1. Arrival | Move + Look + Monologue | YES |
| 2. Character's Eye | Look + Monologue (auto-triggered) | YES |
| 3. FRIEND Contradiction | Look + Examine NPC + Talk | YES |
| 4. Divergence Reveal | Move + Look + Monologue (replay) | YES |
| 5. News Ticker Gut-Punch | Look (read ticker) + Monologue | YES (requires ticker as environmental object, Examine not needed — it's passive text in the environment) |
| 6. Quiet Moment | Move (idle) + Monologue (time_idle trigger) | YES |
All 6 wow moments are achievable with 7 interactions. No additional interactions required.
---
## Topic 5: v0.1 Scope Boundary
### Is the IN/OUT split correct?
Let me go item by item.
**IN list review:**
| # | Item | Verdict | Notes |
|---|------|---------|-------|
| 1 | WASD movement + collision | **CORRECT IN** | Non-negotiable. |
| 2 | Context-sensitive interaction | **CORRECT IN** | The 7-interaction model above. |
| 3 | Monologue system | **CORRECT IN** | Drives wow moments #2, #5, #6. |
| 4 | Knowledge graph | **CORRECT IN** | Core mechanic. Without it, nothing gates. |
| 5 | 2 playable characters | **CORRECT IN** | D-027. Non-negotiable. |
| 6 | THE FRIEND arc | **CORRECT IN** | D-034. Non-negotiable. |
| 7 | 5 triangles, 1 fork each | **ADJUST** | 5 triangles YES. But only **3 active forks** (T1, T2, T4). Triangles 3 and 5 are passive (tension visible, fork not resolved). See Topic 1a. |
| 8 | 6 wow moments | **CORRECT IN** | D-039. Non-negotiable (lead directive). |
| 9 | 3 social sites | **CORRECT IN** | Required for triangles and bridge NPCs. |
| 10 | NPC routines | **CORRECT IN** | Routines create the patterns the player reads. Essential for Examine NPC and tell detection. |
**MISSING from IN — should be added:**
| Missing Item | Why It Must Be IN | Dependency |
|-------------|-------------------|------------|
| **News ticker** | Wow moment #5 requires a ticker with dual monologue reactions. Must exist as environmental text. | Client (Stig): ticker display. Copy (Mellanie): ticker text + monologue lines. |
| **PC-as-NPC** | When playing smuggler, the detective exists as an NPC (and vice versa). Required for Divergence Reveal (wow moment #4) — second playthrough reveals the other character was there all along. | Content: ~20-30 authored items per PC-as-NPC (SUMMARY confirms). Server: spawn the other PC as an NPC entity. |
| **Time progression** | NPC routines require time to pass. The 30-minute session maps to in-game time (D-031). Without time, routines don't advance, shift transitions don't happen, the smuggling window never opens. | Server (Dudley): game clock. Already decided in D-031. |
| **Relationship state transitions** | The knowledge graph stores `RelationshipState` (Unknown/Known/Friendly/PersonOfInterest/Hostile). FRIEND arc requires Friendly→PersonOfInterest transition. Without state transitions, the color shift (green→amber) never happens. | Server: state machine. Knowledge graph: transition triggers. |
**OUT list review:**
| # | Item | Verdict | Notes |
|---|------|---------|-------|
| 1 | THE NOBODY / dynamic tier promotion | **CORRECT OUT** | Data ships, mechanic deferred. See Topic 2c. |
| 2 | Archetype transitions | **CORRECT OUT** | No archetype system in v0.1. |
| 3 | Multiple FRIEND candidates | **CORRECT OUT** | 1 per character. Pool architecture from day one, selection deferred. |
| 4 | Secondary contraband variation | **CORRECT OUT** | Primary contraband fixed (lattice components). Secondary (medical/severance) referenced in dialogue but not mechanically varied per seed. |
| 5 | Gate network / multi-world | **CORRECT OUT** | 1 district. No gates. |
| 6 | Content generation / randomization | **CORRECT OUT** | v0.1 is hand-authored. |
| 7 | Modding support | **CORRECT OUT** | Obviously. |
**MISSING from OUT — should be explicitly excluded:**
| Should Be Explicitly OUT | Why | Risk If Not Excluded |
|--------------------------|-----|---------------------|
| **Inventory system** | No item pickup or management. Evidence is knowledge, not physical. | Feature creep. Someone will want "pick up the manifest printout." No. The detective READS the manifest (Examine Object). Knowledge graph updates. No physical item. |
| **Stealth mechanics** | No crouch, hide, LOS manipulation. | Immersive sim instincts will demand it. Defer. The smuggler's "stealth" is social (being in the right place at the right time, having the right cover identity). |
| **Combat system** | No fighting. Zero combat encounters. | D-027 success criteria don't mention combat. If combat appears in v0.1, it ate someone else's scope. |
| **Save/load** | Session-based. Play 30 minutes, experience the slice. No mid-session save. | Testing needs save/load (Dudley's concern). But SHIPPED v0.1 doesn't. Dev-mode save is fine, player-facing save is v0.2. |
| **Lattice modification/upgrade** | Player cannot modify their neural lattice. | Contraband IS lattice components. Someone will ask "can the player use smuggled mods?" No. Not in v0.1. |
**Revised scope boundary summary:**
```
IN (v0.1 — SHIPS):
Core Systems:
[x] WASD movement + collision
[x] 7-interaction model (Move, Look, Monologue, Examine Object, Examine NPC, Talk, Overhear)
[x] Monologue system (tagged triggers, FactId prerequisites, audio chime)
[x] Knowledge graph (EntityKnowledge, FactIds, RelationshipState transitions)
[x] Time progression (game clock, day phases)
[x] NPC routines (schedule-based movement, routine deviations as tells)
Content:
[x] 2 playable characters (smuggler, detective)
[x] PC-as-NPC (~20-30 authored items per character)
[x] THE FRIEND arc (Kael/smuggler, Sera/detective)
[x] THE MIRROR (Naia Tamm)
[x] 5 triangles (3 active forks, 2 passive tensions)
[x] 3 social sites (Terminal, Last Shift, Maintenance Corridors)
[x] News ticker (environmental text + dual monologue reactions)
[x] 6 wow moments (D-039)
[x] 17 NPCs (2 T1, 11 T2, 4 T3) — Drin promoted
[x] 8 patterns exercised (NOBODY data-only)
[x] 6 motivations exercised
[x] 18 EntityKnowledge keys (14 shared + 2 detective + 4 smuggler, symmetry note: 2 detective-specific keys are deliberately not mirrored as they are not needed)
OUT (v0.2+):
[ ] THE NOBODY mechanic (dynamic tier promotion)
[ ] Archetype transitions
[ ] Multiple FRIEND candidates per character
[ ] Secondary contraband variation per seed
[ ] Gate network / multi-world
[ ] Content generation / randomization
[ ] Modding support
[ ] Inventory system
[ ] Stealth mechanics
[ ] Combat system
[ ] Player-facing save/load
[ ] Lattice modification/upgrade
[ ] social_debt / loyalty_conflict EntityKnowledge keys
```
**Final scope assessment:** The IN list is tight. Every item serves at least one wow moment or D-027 criterion. The 4 additions (news ticker, PC-as-NPC, time progression, relationship state transitions) are all REQUIRED by existing scope items — they're dependencies, not additions. The 5 explicit exclusions (inventory, stealth, combat, save/load, lattice mods) prevent the most likely scope creep vectors.
Is this fun? Does this create interesting decisions? YES — because the smuggler and detective have different interaction priorities (Talk-first vs. Examine-first), different knowledge keys (operational vs. evidential), and different relationships to the same NPCs. The same 17 NPCs, 5 triangles, and 3 social sites produce two fundamentally different 30-minute experiences. That's the proof.
docs/workshops/v01-content-scoping/round1-mellanie.md
-261
View File
@@ -1,261 +0,0 @@
# Round 1 — Mellanie (Copywriter / LIBRARIAN)
## v0.1 Content Scoping Workshop
---
## Topic 1: Wiki Fixes — Voice Review
### 1a. Naia Tamm (THE MIRROR) — Voice Samples Needed: YES
The current Hael profile has three voice samples. All three are anxious: worried-to-Sera, warm-with-Kael-reference, brittle-near-breaking. That's the Worried Partner voice. It's a good voice. It's not THE MIRROR voice.
THE MIRROR is Tier 1 emotional depth with NO contradiction arc, no secret. Her power is transparency. The wiki summary says: "When events drag the MIRROR into the conspiracy, the damage is devastating — the player broke the one genuinely innocent person." That needs voice samples that establish what innocence sounds like so the player recognizes what they're losing.
**Naia Tamm needs 5 voice samples minimum:**
1. **Baseline warm** — How she talks when nothing's wrong. Open, direct, no subtext. This is the calibration line. The player needs to hear what "no hidden agenda" sounds like in a world where everyone has one.
> *"The kids did something brilliant today — Ren figured out the cycle conversion problem by herself. Eight years old. I almost cried in front of the class."*
2. **Concerned for Kael** — Not the anxious spiral from the current profile. Straightforward worry from someone who doesn't play games.
> *"Kael's been quiet. I don't need an explanation, I need to know they're okay. That's it. That's the whole thing."*
3. **Perceptive without suspicion** — THE MIRROR reads emotional states accurately but doesn't weaponize the reading. Notices things, says them plainly.
> *"You seem different today. Not bad-different. Just... carrying something. You know you can put it down here, right?"*
4. **Under pressure** — When events start closing in. THE MIRROR doesn't become evasive or strategic. She becomes more honest, not less. That's what makes it devastating.
> *"Something's happening that nobody's telling me about. I can feel it. I don't want to guess. I want someone to just say it."*
5. **Damaged** — After events have touched her. THE MIRROR doesn't transform into a different archetype. She stays herself — honest, transparent — but now the honesty includes pain.
> *"I didn't do anything wrong. I know that. But everything's different now, and I can't make it go back."*
**Voice discipline for THE MIRROR:** Complete sentences. No operational subtext. No evasion vocabulary. Naia doesn't deflect — she states. Where Kael clips ("Don't worry about it") and Sera redirects ("He's just loud"), Naia just... says the thing. That directness is her signature and her vulnerability.
**Dual-lens note:** Both characters should monologue differently about Naia. The smuggler sees someone to protect ("Naia doesn't know. She can't know."). The detective sees someone too trusting for this environment ("Tamm. Open book. Either she's genuine or she's the best liar in the district. ...No. She's genuine. And that's worse.").
**Action:** Paula does the rename cascade. I'll write the voice samples above into the updated profile. These five samples are enough for me to author monologue about Naia and dialogue for her.
---
### 1b. Kael and Sera Voice Distinctness — SUFFICIENT, with one gap
**Kael's voice:** Direct, clipped, practical. Short sentences. Warm through understatement. Evasive through brevity.
- Casual: *"Shift's looking smooth today."* (7 words, done.)
- Evasive: *"It's nothing. Just a thing."* (No elaboration. The silence IS the tell.)
**Sera's voice:** Competent, precise, conversational. Complete sentences with context. Professional warmth. Evasive through redirection.
- Casual: *"There you are. Grab a seat — Hael was here earlier, you just missed them."* (Provides context, frames the social landscape.)
- Evasive: *"Torek? He's just loud. Gets a couple drinks in him and decides everyone needs to hear his opinions."* (Plausible alternative explanation, delivered smoothly.)
These are authoring-ready. I can write Kael lines and Sera lines and they won't sound like each other. The distinction is structural: Kael speaks in fragments, Sera speaks in sentences. Kael's warmth is physical presence ("There you are — good"), Sera's warmth is social attention ("Grab a seat, let me tell you about...").
**The gap:** I need voice parameters for the smuggler and detective as internal narrators, not just for the NPCs they observe. The monologue guide has example lines but no formal voice sample set for the PC voices. I know what Kael sounds like when he talks. I know what the smuggler sounds like when she thinks ABOUT Kael. But I need a sharper definition of:
- **Smuggler internal voice:** How terse? How emotional? How operational? The authoring guide examples lean toward short + feeling-forward ("Kael's here. Good — I was starting to worry."). Is that the canonical register?
- **Detective internal voice:** How clinical? How personal? How much institutional vocabulary? The examples lean analytical-with-subtext ("Dock worker. Davan, K. Unremarkable on paper."). Confirm or adjust.
**Ask:** This might be the voice kit work that's blocked on Paula's Dual Lens Guide (#261). If the workshop can confirm the internal voice registers from the monologue guide examples as canonical, I can start writing without waiting. The examples in the authoring guide are good. Just tell me they're the baseline and I'll scale from there.
---
## Topic 4: Interaction Model — Monologue Pool Sizing
### How Much Monologue Does v0.1 Need?
Short answer: **80-110 monologue lines per character, 160-220 total.**
Here's the math.
### Trigger Frequency in a 30-Minute Session
I walked through a mental playthrough. Player enters 3 locations, observes NPCs, has conversations, discovers things, idles, returns to places. Estimated trigger fires:
| Trigger Type | Fires Per Session | Notes |
|---|---|---|
| `enter_location` | 8-12 | 3 sites, multiple visits |
| `observe_npc` | 15-20 | Known NPCs entering sightlines |
| `hear_sound` | 3-5 | Rare, high-impact |
| `observe_anomaly` | 4-6 | Tells, cargo anomalies |
| `post_conversation` | 6-10 | After dialogue exchanges |
| `discover_evidence` | 3-5 | Physical evidence moments |
| `witness_interaction` | 4-6 | NPC-NPC observations |
| `time_idle` | 3-5 | Player pauses, watches |
| `return_visit` | 4-6 | Returning to familiar locations |
| **Total triggers** | **50-75** | |
Not every trigger should fire a line. Monologue competes with gameplay for attention. If the inner voice never shuts up, the player stops listening. I'd say the system should fire on **40-50% of eligible triggers** = the player hears **~25-35 monologue lines per playthrough**.
### Why 80-110 Lines Per Character, Not 25-35?
Three reasons:
**1. Prerequisite gating creates narrow windows.** A line gated on `relationship_state: PersonOfInterest` only fires after the contradiction (~minute 15-20). A line with `prerequisite: null` fires from the start. The pool isn't flat — it's a funnel. Many lines are only eligible for part of the session. You need more authored lines than the player will hear because most lines are locked most of the time.
**2. Repetition threshold.** If the player enters the Terminal 3 times and hears the same arrival line twice, the world feels like a game. Minimum 3 lines per location per trigger type that shares a prerequisite window. Some trigger types need 4-5 variants (especially `observe_npc` for THE FRIEND, who the player sees repeatedly).
**3. Knowledge progression creates parallel tracks.** The smuggler who knows `contraband.ring_exists` at `KnowsDetails` hears different lines than the smuggler at `Suspects`. Same trigger, same location, different prerequisite — different line. Each confidence level on important FactIds needs its own line.
### Per-Trigger Breakdown (One Character, All Locations)
| Trigger Type | Lines Needed | Per Location | Rationale |
|---|---|---|---|
| `enter_location` | 12-15 | 4-5 | Baseline + knowledge-gated variants per site |
| `observe_npc` | 20-25 | varies | 2-3 per observable NPC across relationship states |
| `hear_sound` | 6-8 | 2-3 | Rare trigger, each must count |
| `observe_anomaly` | 8-12 | 3-4 | Tell observations, cargo anomalies, schedule breaks |
| `post_conversation` | 10-15 | varies | 1-2 per NPC conversation, gated on content/outcome |
| `discover_evidence` | 6-8 | 2-3 | Specific evidence moments, heavily gated |
| `witness_interaction` | 6-8 | 2-3 | NPC-NPC observation, relationship-dependent |
| `time_idle` | 6-8 | 2-3 | Character-revealing, atmospheric |
| `return_visit` | 6-8 | 2-3 | Location revisits with accumulated knowledge |
| **Total per character** | **80-107** | | |
**Two characters x ~95 average = ~190 monologue lines total.**
Round up for safety margin: **~200 monologue lines** is the target. That gives the player ~25-35 heard lines per session with minimal repetition and knowledge-state variation.
### THE FRIEND Gets Disproportionate Coverage
Kael (smuggler's perspective) and Sera (detective's perspective) should each have **15-20 monologue lines** from their respective character's pool — more than any other single NPC. THE FRIEND contradiction is the emotional core. The player needs to feel the warmth, notice the cracks, experience the shift, and live in the contaminated aftermath. That's 4-5 phases x 3-4 lines per phase.
Other NPCs get 2-4 monologue lines each (first observation, notable behavior, knowledge-gated reactions). Background NPCs might get 1 generic observation line or none.
---
## Topic 5: v0.1 Scope — Content That Must Ship
### The Hard Numbers
Everything below is the **floor** — minimum viable for a 30-minute session that doesn't feel empty, repetitive, or placeholder.
#### 1. Monologue Pools — ~200 lines
| Category | Smuggler | Detective | Total |
|---|---|---|---|
| THE FRIEND observations | 15-20 | 15-20 | 30-40 |
| Other NPC observations | 20-30 | 20-30 | 40-60 |
| Location arrival/return | 15-20 | 15-20 | 30-40 |
| Evidence/anomaly reactions | 12-15 | 12-15 | 24-30 |
| Atmosphere/idle/sound | 10-12 | 10-12 | 20-24 |
| Post-conversation reactions | 8-12 | 8-12 | 16-24 |
| **Subtotal** | **80-109** | **80-109** | **160-218** |
**Target: ~200 monologue lines, hard-partitioned by character.**
#### 2. NPC Dialogue — ~300-400 lines
| NPC Tier | NPCs | Lines Per NPC | Total |
|---|---|---|---|
| Tier 1 — THE FRIEND (Kael, Sera) | 2 | 70-100 | 140-200 |
| Tier 1 — THE MIRROR (Naia Tamm) | 1 | 50-70 | 50-70 |
| Tier 2 — Essential (Voss, Lera) | 2 | 25-35 | 50-70 |
| Tier 2 — Triangle support (Torek, Maret, others) | 3-4 | 15-25 | 45-100 |
| Tier 3 — Background | 5-8 | 5-10 | 25-80 |
| **Subtotal** | **13-17** | | **310-520** |
**Target: ~350 dialogue lines across all NPCs.** The FRIEND NPCs account for 40-50% of the dialogue budget. That's correct — they exercise every pipeline.
#### 3. Environmental Text — ~50 items
| Category | Count | Examples |
|---|---|---|
| Terminal screens | 8-10 | Shift schedules, manifest summaries, status readouts |
| Safety/regulatory notices | 6-8 | "Authorized personnel beyond this point," hazard markings |
| Bar signage | 4-6 | Menu, house rules, "The Last Shift" sign, back room door |
| Corridor markers | 4-6 | Section labels, access warnings, maintenance tags |
| Lattice/kiosk displays | 4-6 | Commission notices, calibration status, public announcements |
| Interactable documents | 5-8 | Manifest pages, crew rosters, posted schedules (evidence) |
| **Subtotal** | | **~50** |
#### 4. News Ticker / Meridian Feed — ~20 items
Headlines that create atmosphere and occasionally deliver world-state information. Mix of:
- Gate network status (3-4 lines)
- Krenn System local news (4-5 lines)
- Commission regulatory notices (3-4 lines)
- Economic/trade reports (3-4 lines)
- Human interest / cultural (3-4 lines)
**Target: 20 ticker items.** Some are static background; 3-5 should be reactive to game state (new headlines after key events).
#### 5. UI Microcopy — ~50 strings
| Category | Count |
|---|---|
| Interaction prompts ("Talk," "Examine," "Listen") | 10-12 |
| Knowledge panel labels and descriptors | 12-15 |
| Relationship state labels (Friendly, PersonOfInterest, etc.) | 5-8 |
| Status messages ("New information," "Contradiction discovered") | 8-10 |
| Tutorial/onboarding monologue (diegetic, D-016) | 10-15 |
| **Subtotal** | **~50** |
The tutorial text is monologue, not HUD — per D-016, the character teaches the player through internal voice. "How do I interact with this person?" becomes the character thinking *"Sera's over there. Should go say hello."* That's 10-15 lines of contextual teaching buried in the monologue pool.
#### 6. PC-as-NPC Content — ~20-30 lines
The other playable character exists as an NPC (D-029 Concept A). The detective exists in the smuggler's world; the smuggler exists in the detective's world.
- NPC dialogue for the other PC: ~10-15 lines (surface-level, public access, functional)
- Monologue about the other PC: ~5-8 lines per character (identification, assessment, interaction reactions)
- Environmental evidence of the other PC: ~3-5 items (schedule entries, incident reports, lattice traces)
**Target: ~25 items across both perspectives.**
---
### Grand Total: v0.1 Content That Must Ship
| Category | Items | Priority |
|---|---|---|
| Monologue pools (2 characters) | ~200 lines | **Critical** — core interaction proof |
| NPC dialogue | ~350 lines | **Critical** — interaction model requires it |
| Environmental text | ~50 items | **High** — world must feel inhabited |
| News ticker | ~20 items | **Medium** — atmosphere, can be thin at launch |
| UI microcopy | ~50 strings | **High** — game is unplayable without it |
| PC-as-NPC content | ~25 items | **Medium** — D-027 requires both characters exist |
| **TOTAL** | **~695** | |
**~695 authored content items.** Not lines of code. Not generated output. Hand-written, tagged, reviewed content.
For context: the authoring guide already contains ~40 example monologue lines across 3 sample pools. Those are usable as-is — they're tagged, prerequisite-gated, and voice-correct. That's ~6% of the monologue target. A start, not a finish.
---
### Authoring Order (What I Write First)
1. **THE FRIEND: Kael content pack** — ~100 lines (dialogue + monologue from both characters). This exercises every tag, every trigger type, every prerequisite format, every access tier. If this works, everything else is variation.
2. **THE FRIEND: Sera content pack** — ~100 lines. Different contradiction mechanics (cumulative vs. sudden), different voice, same pipeline depth.
3. **THE MIRROR: Naia Tamm** — ~60-70 lines. Tests the honest-NPC pattern. Simpler prerequisites, no contradiction arc, but full emotional depth.
4. **Tier 2 NPCs** — ~100-150 lines across Voss, Lera, Torek, Maret. Each gets a focused pack covering their triangle roles.
5. **Environmental text + ticker** — ~70 items. Can be written in parallel with NPC packs. Uses Miri's setting details.
6. **Remaining monologue fill** — Top up the pools to ~200 total. Fill gaps in trigger coverage, add knowledge-state variants, idle lines, atmosphere.
7. **UI copy + tutorial monologue** — ~50 strings. Blocked on Stig's UI spec (need display constraints and interaction prompt format).
8. **Tier 3 background + PC-as-NPC** — ~50 items. Last priority. These can be thin and still work.
---
### Dependencies / Asks
| I Need | From | Blocking |
|---|---|---|
| Confirm monologue guide examples as canonical PC voice registers | Gestalt or Paula | Monologue authoring (all) |
| Naia Tamm rename cascade complete | Paula | MIRROR content pack |
| Smuggler-lens sections in NPC profiles | Paula | Smuggler monologue about Tier 2 NPCs |
| Display constraints (char limits, stacking rules, ticker format) | Stig + Araminta | UI microcopy, ticker, environmental text |
| Knowledge state vocabulary (which FactIds gate which content) | Gestalt | Prerequisite authoring for monologue |
| Content file schema (YAML structure confirmed) | Tyre | All content files |
**Biggest risk:** THE FRIEND content packs are the critical path. If those work — tags validate, prerequisites fire correctly, voice is distinct, dual-lens reads land — everything else scales from the pattern. If those don't work, we find out with 200 lines already written.
Write the benchmark first. Validate. Then scale.
---
*Mellanie, Round 1. Three words, not thirty — except when you need the numbers.*
docs/workshops/v01-content-scoping/round1-paula.md
-519
View File
@@ -1,519 +0,0 @@
# Round 1 — Paula (Librarian / Narrative & Political Depth)
## Topic 1: Wiki Fixes
### 1a. Hael → Naia Tamm Rename — Full Cascade Plan
**16 files require changes.** The rename touches every file that references Hael by name, including cross-references in profiles, location descriptions, knowledge system examples, and the monologue authoring guide.
#### File-by-file rename plan
| # | File | Change Type | Details |
|---|------|-------------|---------|
| 1 | `wiki/npcs/hael.md` | **Rename + rewrite** | File becomes `wiki/npcs/naia-tamm.md`. All internal references change. Header becomes "Naia Tamm — THE MIRROR". Pattern assignment changes from implicit to explicit MIRROR. |
| 2 | `wiki/npcs/index.md` | Content update | Roster table row 9: "Hael" → "Naia Tamm". Triangle 4 diagram: all 3 "Hael" labels. Bridge NPCs table: not listed (Naia isn't a bridge NPC). Social site listing for The Last Shift: "Hael (Teacher)" → "Naia Tamm (Teacher)". |
| 3 | `wiki/index.md` | Content update | NPC listing under Tier 2: `[Hael](npcs/hael.md) — Kael's partner` → `[Naia Tamm](npcs/naia-tamm.md) — Kael's partner`. |
| 4 | `wiki/npcs/kael-davan.md` | Content update | **Heaviest single file.** 20+ occurrences. Axis 1 secondary Want, Axis 2 (deep secret), Relationship 2 (full section), Axis 4 tolerance, Axis 5 routine, Axis 6 information inventory, Axis 7 contentment, Voice sample (Mood: Protective), Dual-lens smuggler notes, Triangle 4 role notes, Secret section, Contradiction arc Phase 1 through 5, Authoring notes. Every "Hael" → "Naia" in dialogue/casual references (Krenn first-name-primary convention). Every "Hael" → "Naia Tamm" in formal/profile references. |
| 5 | `wiki/npcs/sera-venn.md` | Content update | ~15 occurrences. Relationship 2 (full section), Axis 4 tolerance, Axis 5 routine, Axis 6 information inventory, Axis 7 contentment, Tell system, Voice sample, Dual-lens notes, Triangle 4 role notes, Secret section, Contradiction arc, Authoring notes. Same casual/formal distinction as Kael's file. |
| 6 | `wiki/npcs/lera-sessik.md` | Content update | Axis 6 information inventory: "Hael's worry about Kael" → "Naia Tamm's worry about Kael". |
| 7 | `wiki/npcs/maret-korr.md` | Content update | Axis 5 routine: "goes for Hael's company sometimes" → "goes for Naia's company sometimes". |
| 8 | `wiki/authoring/monologue-guide.md` | Content update | Any monologue examples referencing Hael. |
| 9 | `wiki/locations/krenn-system/the-last-shift.md` | Content update | NPC presence list, social dynamics references. |
| 10 | `wiki/world/sova-transit-district.md` | Content update | Any district NPC references. |
| 11 | `wiki/factions/the-ring.md` | Content update | Likely references Hael as collateral/vulnerability for Kael. |
| 12 | `wiki/knowledge/relationship-states.md` | Content update | Any example entries using Hael as a relationship target. |
| 13 | `wiki/knowledge/entity-attributes.md` | Content update | Scan for Hael in example EntityKnowledge entries. |
| 14 | `wiki/knowledge/fact-catalog.md` | Content update | FactId entries referencing Hael (e.g., `npc.hael.worry`, `relationship.kael.hael`). IDs change to `npc.naia_tamm.*` and `relationship.kael.naia_tamm`. |
| 15 | `wiki/world/krenn-system.md` | Content update | NPC naming examples list. |
| 16 | `decisions/content.md` | Content update | D-034 references Hael twice (Kael's partner, Triangle 4). D-036 references Hael in the naming examples list. |
#### Naming convention for the rename
Per Krenn System conventions (D-036, Miri Round 1):
- **Formal/profile references:** "Naia Tamm" (full canonical name)
- **Casual/dialogue/in-character references:** "Naia" (first-name-primary, Krenn convention)
- **NPC profile page title:** "Naia Tamm — THE MIRROR"
- **Canonical ID:** `krenn.naia-tamm`
- **Filename:** `naia-tamm.md`
#### Profile header changes for naia-tamm.md
The renamed file also needs structural updates to reflect the MIRROR pattern:
```
# Naia Tamm — THE MIRROR
**Tier 1 (MIRROR) NPC** | The Last Shift (Bar) | Mundane
```
Note: The brief identifies Naia Tamm as the first MIRROR instance with "Tier 1 emotional depth." The SUMMARY confirms: "50-70 authored lines." This is between Tier 1 (70-100) and Tier 2 (40-60). The profile needs a content requirement update reflecting MIRROR-specific depth:
- ~50-70 authored lines (no generation expansion — same rule as FRIEND)
- Full 10-axis profile (already present in current Tier 2 format)
- NO contradiction arc, NO secret — this is the MIRROR's defining constraint
- Emotional weight comes from what HAPPENS TO Naia, not what Naia hides
---
### 1b. Smuggler Attribute Vocabulary
The existing EntityKnowledge attributes (entity-attributes.md) are detective-shaped: `tell_observed`, `contradiction_flagged`, `secret_held`, `secret_confidence` all describe an investigative lens. The smuggler needs parallel attributes that describe an operational lens.
#### Proposed Smuggler-Specific EntityKnowledge Keys
| Key | Value Format | What It Captures | Examples |
|-----|-------------|------------------|----------|
| `trust_read` | enum: `solid`, `reliable`, `shaky`, `unknown`, `compromised` | Smuggler's assessment of whether this person can be trusted with operational knowledge | Kael: `"solid"` (pre-contradiction), `"compromised"` (post-observation). Voss: `"reliable"`. Drin: `"compromised"` (known vulnerability). |
| `exposure_risk` | enum: `none`, `low`, `moderate`, `high`, `critical` | How much this NPC's behavior threatens operational security | Torek: `"high"` (spending beyond means). Maret: `"moderate"` (observant, could notice). Resha: `"moderate"` (asks questions). Pell: `"critical"` (might turn). |
| `loyalty_assessment` | enum: `committed`, `dependable`, `neutral`, `wavering`, `hostile` | Smuggler's read on where this person's loyalty lies | Renn: `"committed"`. Kael: `"dependable"` (pre-contradiction). Pell: `"wavering"`. Voss: `"dependable"` (financially motivated). |
| `leverage_held` | string or null | What the smuggler knows they could use against this person | Drin: `"gambling debt to Harek"`. Voss: `"schedule manipulation evidence"`. Pell: `"ring membership knowledge"`. |
| `social_debt` | string or null | Favors owed, obligations, reciprocal relationships | Kael: `"years of mutual cover, personal friendship"`. Lera: `"bar provides meeting space, ring provides revenue"`. |
| `moral_weight` | enum: `none`, `light`, `heavy`, `crushing` | How much guilt or moral cost the smuggler feels about this relationship | Naia Tamm: `"heavy"` (lying to Kael's innocent partner). Renn: `"none"` (operational colleague, no personal bond). Maret: `"light"` (knows she's worried, pragmatically ignores it). |
| `cover_integrity` | enum: `solid`, `stressed`, `cracking`, `blown` | Whether this person's cover/role is holding up | Kael: `"stressed"` → `"cracking"` (tells accumulating). Torek: `"cracking"` (spending visible). Devra: `"solid"` (brokering cover holds). |
| `loyalty_conflict` | string or null | Which competing loyalties this person faces | Kael: `"ring vs. Naia Tamm, ring vs. exit attempt"`. Sera: `"Commission vs. Naia Tamm's friendship"`. Voss: `"shift authority vs. Nils's demands"`. |
#### How smuggler attributes map to EntityKnowledge
These 8 keys would be added to the `known_attributes` BTreeMap alongside the existing 14. They use the same string:string format. The smuggler's knowledge graph populates them; the detective's does not (or populates them differently — the detective's `trust_read` of an NPC reflects institutional trust, not operational trust).
#### What a smuggler-lens section looks like in an NPC profile
Every NPC profile currently has "Dual-Lens Notes" with a "Smuggler" and "Detective" subsection. The smuggler-lens expansion adds structured operational data below the monologue note. Here's what the expanded format looks like, using Voss as an example:
```markdown
### How the Smuggler Sees Voss
**Operational Profile:**
| Attribute | Value | Rationale |
|-----------|-------|-----------|
| trust_read | reliable | Financially motivated, predictable |
| exposure_risk | moderate | Institutional face — first person investigated |
| loyalty_assessment | dependable | Compliant because the money is good |
| leverage_held | schedule manipulation evidence | Smuggler knows Voss adjusts manifests |
| social_debt | null | No personal relationship |
| moral_weight | none | Voss chose this; smuggler doesn't feel guilt |
| cover_integrity | stressed | Manifest reworks are increasing |
| loyalty_conflict | shift authority vs. Nils's demands | Resents being managed, might cooperate if pressured |
**Monologue tone (baseline):** Operational assessment. *"Voss is tense today.
Nils must have changed the window again."*
**Monologue tone (post-escalation):** Risk evaluation. *"Voss reworked the
manifest three times today. He's rattled. If he cracks, we're all exposed."*
**Moral arc phase:** Comfort (baseline) — Voss is a tool, not a person the
smuggler thinks about. If Voss breaks, the phase shifts to Doubt ("Am I
responsible for what happens to him?").
```
Each NPC profile gets this treatment. The smuggler-lens sections should match the detective-lens sections in depth and specificity. The detective reads people through behavioral analysis; the smuggler reads people through operational risk assessment.
#### Smuggler Moral Arc Phases
The brief identifies 4 phases: **Comfort → Doubt → Reckoning → Compromise.** These map to the smuggler's relationship with the consequences of the operation:
| Phase | Trigger | Internal State | Monologue Tone |
|-------|---------|---------------|----------------|
| **Comfort** | Default. The operation is manageable. Money helps. People are fine. | Pragmatic rationalization. "This is a service. Nobody's getting hurt." | Matter-of-fact, confident |
| **Doubt** | Sees the operation's human cost. Naia Tamm's worry. Maret's anxiety. Pell's terror. | Questions the rationalization. "Nobody's getting hurt — except everyone adjacent to this." | Reflective, unsettled |
| **Reckoning** | A specific harm: Pell disappears. Drin is broken. Naia Tamm discovers Kael's secret. The smuggler's actions contributed. | Can't rationalize. Must choose: continue, reform, or exit. | Conflicted, sharp |
| **Compromise** | Player choice determines resolution. Some damage is done. The question becomes: can you live with it? | Whatever the player decided, the cost is visible. | Quiet, weighted |
Every NPC's smuggler-lens section should include a note about which moral arc phase the relationship triggers or inhabits.
---
### 1c. Nils Davan Stub Page + Triangle 1 Escalation Sequence
#### Nils Davan Stub Page
```markdown
# Nils Davan
**Off-Stage NPC** | Smuggling Ring (Coordinator) | Entangled
---
## Core Identity
**Name**: Nils Davan
**Age**: 39
**Role**: Ring coordinator (strategic — personnel, security, growth decisions)
**System Origin**: Krenn System, Station Sova (born and raised, same as Kael)
**Lattice Tier**: Standard professional
**Employer**: Self-employed (freight consulting cover); The Arrangement
(ring leadership)
**Relationship to Kael**: Older sibling
---
## Function
Nils is the ring's strategic leader — the person who decides volume,
personnel, risk tolerance. Nils brought Kael into the ring ("It's just
moving containers. You're good at logistics. We take care of our own.").
Nils pushes for escalation: higher volume, tighter margins, more profit.
This push is the primary source of tension in Triangle 1 and the catalyst
for Kael's exit attempt.
**Off-stage in v0.1.** Nils is referenced constantly but never directly
encountered by the player. Nils exists through:
- Kael's dialogue ("Nils wants the next shipment doubled")
- Voss's resentment ("Another 'adjustment' from above")
- Devra's coordination ("Nils says push the timeline forward")
- Renn's reporting ("I told Nils about Pell")
This is the GHOST pattern: absent power shaping events through influence.
---
## What the Player Knows
**Smuggler:** Knows Nils exists, knows Nils is Kael's sibling, knows Nils
gives strategic orders. May receive direct instructions from Nils via
lattice communication (voice only — Nils doesn't appear in person). The
smuggler experiences Nils as a disembodied authority figure whose decisions
create consequences the smuggler must manage.
**Detective:** Doesn't know Nils exists initially. Nils's name surfaces
through investigation: Kael's family records (lattice query), ring members'
references in overheard conversations, Pell's potential testimony. The
detective builds Nils as a conceptual entity before ever having a name —
"someone is giving orders" → "the coordinator" → "Nils Davan, Kael's
sibling."
---
## Escalation Pressure
Nils is pushing for increased volume because:
1. External demand (Sabel reports higher demand for lattice components
from other systems)
2. Profit motive (higher volume = higher margins, Nils takes the
largest cut)
3. Ambition (Nils wants to expand beyond Sova to other districts on the
station)
This escalation creates the pressure that:
- Makes Voss anxious (more schedule manipulation, more risk)
- Makes Kael desperate (higher stakes, more danger for Naia)
- Makes Pell crack (risk-to-reward ratio inverted)
- Makes the whole operation more detectable (the detective arrives
during this escalation, not by coincidence)
---
## Pattern + Motivation
**Pattern:** GHOST — absent power shaping events
**Motivation:** HANDLER — managing operations, applying pressure from above
---
**Cross-References:** [Kael Davan](kael-davan.md), [Voss](voss.md),
[Devra](devra.md), [Renn](renn.md), [Pell](pell.md)
```
#### Triangle 1 Escalation Sequence
Triangle 1 (Hub Power: Voss - Kael - Nils) is currently the weakest triangle because the smuggler role is passive — the smuggler observes tension but doesn't make decisions. Here's the escalation fork:
**The Nils-vs-Voss Escalation Decision**
Nils (via lattice message or Devra intermediary) orders a doubled shipment during a window when Voss has already flagged the schedule as too tight. Voss refuses to create the schedule gap. Kael is caught in the middle.
**Escalation sequence (5 beats across the 30-minute session):**
| Beat | Timing | Event | Smuggler Sees | Detective Sees |
|------|--------|-------|---------------|----------------|
| 1 | ~5 min | Nils sends order for doubled volume next cycle via Devra | Devra relays: "Nils wants double. Next cycle." Smuggler knows this means tighter windows, more risk. | Nothing visible. Normal hub operations. |
| 2 | ~10 min | Voss pushes back — refuses to rework schedule for the doubled window | Voss is visibly stressed. Clipped with Kael. "I already posted the rotation." | Voss reworks the manifest for the third time (tell). Detective notes nervous schedule adjustments. |
| 3 | ~15 min | Kael asks the smuggler for advice — **THE FORK** | **Decision point.** Kael says: "Nils wants double. Voss says no. I need to talk to one of them. Which one?" | Kael and smuggler have a private conversation the detective can't hear. Observable: Kael and an unknown colleague talking intensely near the break room. |
| 4 | ~20 min | **Path A**: Smuggler backs Voss → smuggler tells Kael to push back on Nils. Kael contacts Nils (via lattice), argues for maintaining current volume. Nils is unhappy. **Path B**: Smuggler backs Nils → smuggler tells Kael to pressure Voss. Kael pressures Voss to comply. Voss capitulates, resentfully. **Path C**: Smuggler stays neutral → smuggler tells Kael to handle it himself. Kael freezes, does nothing. Nils interprets silence as refusal. | **Path A**: Voss relaxes slightly. Manifests stabilize. But Nils has marked the smuggler as unreliable. **Path B**: Voss's schedule suddenly changes again. Fourth manifest revision. Detective monologue: "Something just changed. The schedule revised again — after hours." **Path C**: Nothing changes immediately. But the unresolved tension escalates into Beat 5. | **All paths**: Detective observes varying levels of hub stress. Path B is most detectable (visible schedule change). Path A is least detectable (tension decreases). Path C delays visibility to Beat 5. |
| 5 | ~25 min | **Consequences arrive.** **Path A**: Nils sends a cold message to Kael: "We'll discuss this." Kael is frightened. The smuggler realizes pushing back on Nils has consequences for Kael — and the smuggler is the one who recommended it. **Path B**: The doubled shipment goes through during Voss's reluctant window. Renn runs the courier route. The operation succeeds but Voss's fourth manifest revision creates a data anomaly Maret will find. **Path C**: Nils acts unilaterally — sends the shipment anyway, bypassing normal coordination. Devra scrambles. The operation succeeds sloppily. More detectable. | **Path A**: Kael is visibly shaken. Smuggler monologue: "I told Kael to push back. Now Nils is angry. Did I just put a target on Kael's back?" **Path B**: Smuggler monologue: "It worked. But Voss looks like he's going to break. And Maret was watching the manifests." **Path C**: Smuggler monologue: "I didn't decide. Nils decided for everyone. That's what happens when you don't choose." | **All paths produce detective-visible signals** — the question is timing and magnitude. Path B is loudest. Path C is messiest. Path A is quietest but pushes consequences to the FRIEND contradiction arc. |
**Why this works:** The smuggler is no longer passive. The decision has immediate consequences (Beat 4) and delayed consequences (Beat 5) that feed into other triangles. Path B feeds Triangle 2 (Maret sees the anomaly). All paths affect Kael's emotional state, which feeds Triangle 4 (Worried Partner). The detective sees the EFFECTS without understanding the cause — which is exactly how occlusion-based investigation works.
---
### 1d. Drin — Tier 2 Promotion Content
If Gestalt confirms promotion, here's what the expanded Tier 2 profile contains. Drin currently has 3 axes (Want, Routine, Personality) + voice hint + function note. Tier 2 requires all 10 axes + voice sample + dual-lens notes + triangle notes + ~40-60 authored lines.
#### Axes to add (7 new axes for Drin):
**2. Secret / Vulnerability:**
- Surface secret: Gambling debt to Harek. Known to bar regulars, not formally reported.
- Deep secret: Drin knows his inspection negligence is being used by the ring. He's not looking away by accident anymore — after the first few "coincidental" clean inspections during flagged container processing, Drin understood the pattern. He's complicit, not just negligent. The debt is the lever; the knowledge is the chain.
- Vulnerability: Double bind. Reporting his compromise exposes him to institutional consequences (negligent inspections). Not reporting makes him deeper complicit each cycle.
**3. Relationships:**
- Harek: Debt holder. The relationship started as friendly (card games, bar nights). The debt transformed it into a power dynamic Drin can't escape. Harek doesn't even know he's a tool — Harek thinks it's just a card game debt.
- Voss: Shift supervisor. Voss needs Drin's inspections to stay clean. Drin reads Voss's professional attention as surveillance. Every "good work, Drin" from Voss feels loaded.
- Maret Korr: Fellow hub worker. Maret processes the manifests Drin's inspections clear. They share break room time occasionally. Drin is aware that Maret is smart enough to connect his inspection reports to the manifest anomalies. He avoids prolonged interaction with her — not out of guilt, but out of fear.
**4. Tolerance Threshold:**
- Low and declining. The gambling debt was manageable. The inspection negligence was uncomfortable. The realization that he's actively enabling a smuggling operation has pushed Drin past functional tolerance. He's operating on routine, not commitment. One external push — the detective asking about inspection protocols, Pell approaching him for help, Harek calling in the debt — could trigger a break.
**5. Daily Routine** (expanded from current):
- 06:00-14:00: Day shift (maintenance rounds + dock inspections)
- Inspection windows: 3-4 per shift, scheduled by Voss. The "compromised" inspections happen during specific bay rotations that align with ring activity. Drin knows which ones. His body language changes during those inspections — faster, less thorough, eyes forward not searching.
- 10:30: Break room. Avoids Harek if present. Avoids Maret for different reasons. May eat alone.
- 14:00-16:00: Post-shift. Home or bar for card games (2x/week — the games continue because stopping would signal awareness).
- Night: Home, insomnia, reviewing what he ignored during the day.
**6. Information Inventory:**
- Knows: Which containers receive cursory inspections (operational awareness). Harek's debt amount and terms. Voss's schedule patterns. The maintenance corridors' physical layout (pipe access, junction boxes, environmental systems — maintenance tech knowledge). Which corridors have Meridian dead spots. Maret's increasing scrutiny of manifests (observed her checking records after his shifts).
- Doesn't know: Ring structure (Drin doesn't know names, hierarchy, or the operation's scope — only that specific containers are expected to pass). Kael's involvement (Drin works different parts of the bay). Pell, Renn, Devra (has no ring contact — the compromise flows through the debt, not through recruitment).
**7. Contentment:**
- Very low. Was moderate before the debt became leverage. Drin found satisfaction in maintenance work — fixing things, keeping systems running. The inspection compromise pollutes that satisfaction. Every clean report filed is a small self-betrayal. Drin's contentment trajectory: steady → declining → collapsed. He still finds momentary peace in pure maintenance tasks (pipe repair, wiring, physical work with no moral dimension).
**8. Personality Traits** (expanded from "quiet, methodical, avoidant"):
- Primary: Avoidant — dodges confrontation, minimizes interaction, retreats into procedural work.
- Secondary: Competent — genuinely skilled at maintenance. The competence is his last source of self-respect.
- Tertiary: Guilty — the guilt is corrosive but suppressed. Manifests as insomnia, shortened social interactions, inability to maintain eye contact during compromised inspections.
**9. Tell System** (new):
| Tell | Trigger | Observable To |
|------|---------|---------------|
| Faster inspections on flagged bays | Ring-relevant containers scheduled for his inspection window | Smuggler (knows the pattern), Maret (if comparing inspection times to bay traffic), Detective (if tracking inspection duration data) |
| Avoids Harek at the bar | Debt anxiety — doesn't want casual interaction that reminds him of the leverage | Bar regulars, Detective (if tracking avoidance patterns) |
| Insomnia tells — tired eyes, slower response | Accumulated guilt disrupting sleep | Maret (works near him), Voss (notices the performance dip), anyone paying attention at the hub |
| Refuses to discuss inspection procedures | Topic triggers defensive response — "I run them by the book" | Detective (classic deflection — compare with Sera's topic avoidance), Resha (asks procedural questions, gets stonewalled) |
**10. Skill Set** (expanded):
- Occupational: Environmental systems maintenance, pipe/wiring repair, dock inspection protocols, equipment calibration, facility safety checks.
- Ring-relevant (involuntary): Knows which inspection windows matter, can identify containers by routing codes, understands bay access schedules.
- Combat tag: No.
- Lattice capability: Baseline.
#### Voice Sample (Tier 2: 2-3 lines):
**Mood: Professional (baseline)**
*"Junction 4-C has a pressure variance. I'll need 20 minutes with the coupling. Standard repair."*
**Mood: Evasive (pressed about inspections)**
*"I run them by the book. Every container gets the standard check. If you've got questions about the process, talk to Voss."* [Flat delivery, eye contact avoided]
**Mood: Breaking (if directly confronted)**
*"What do you want me to say? I do the inspections. I file the reports. If there's a problem, it's not — I didn't — I just do the job."* [Voice cracks. Eyes down.]
#### Content requirement: ~40-60 authored lines
---
### 1e. Canonical Names — Which NPCs Need Them
**5 NPCs already have full canonical names:**
- Kael Davan
- Sera Venn
- Lera Sessik
- Torek Lintar
- Maret Korr
**1 NPC gains a full name through the rename:**
- Hael → Naia Tamm
**1 off-stage NPC has a full canonical name:**
- Nils Davan (Kael's sibling — surname established)
**10 NPCs currently have first names only and need canonical surnames:**
| NPC | Current Name | Proposed Full Name | Surname Source | Rationale |
|-----|-------------|-------------------|---------------|-----------|
| Voss | Voss | Voss Harsk | Miri's surname list | Short-form first name + consonant-heavy surname. Harsk has the authoritative weight appropriate for a shift supervisor. |
| Devra | Devra | Devra Rosta | Miri's surname list | Mid-form + fluid surname. Rosta has the off-station feel (Devra was born on Orbital Manufacturing Platform 3). |
| Resha | Resha | Resha Neven | Miri's surname list | Mid-form + softer surname. Neven feels younger, matches Resha's 23-year-old new-hire energy. |
| Renn | Renn | Renn Kosse | Miri's surname list | Short-form + double-s surname. Kosse is one of Miri's example names — works as surname for a young courier. |
| Pell | Pell | Pell Talvik | Miri's surname list | Short-form + heritage-weight surname. Talvik is an "old founding family" name per Miri — ironic for someone cracking under pressure. |
| Harek | Harek | Harek Pellam | Miri's surname list | Mid-form + institutional-feeling surname. Pellam has the station security weight. |
| Drin | Drin | Drin Vassar | Extrapolated from Krenn phonetics | Short-form + mid-weight surname. Vassar follows the consonant-vowel-consonant pattern. Not on Miri's list — propose for Miri to validate. |
| Sess | Sess | Sess Torin | Extrapolated from Krenn phonetics | Short-form + compact surname. Torin echoes the utilitarian Krenn naming style. Propose for Miri validation. |
| Olin | Olin | Olin (no surname given) | Deliberate omission | Olin is the ambiguity NPC. A drifter who doesn't volunteer a surname is itself a data point. The detective notes the missing surname; the smuggler reads it as evasion. The absence is load-bearing. |
| Sabel | Sabel | Sabel (surname unknown) | Off-station character | Sabel operates from elsewhere in the Krenn System. No one in Sova uses Sabel's surname — the transactional relationship doesn't require it. If needed later, Miri can generate one. |
| Tav | Tav | Tav Lenn | Extrapolated from Krenn phonetics | Short-form + monosyllabic surname. Tav is young and peripheral — a short, working-class name pair. Propose for Miri validation. |
**Notes for Miri:**
- 3 surnames are extrapolated (Vassar, Torin, Lenn) and need validation against Krenn phonetic rules.
- 2 NPCs (Olin, Sabel) deliberately omit surnames for narrative reasons.
- Olin's missing surname should be noted in the profile as a deliberate character detail, not a gap.
**Implementation note:** Per D-036, Krenn convention is first-name-primary in social contexts. Adding surnames does NOT change how NPCs are addressed in dialogue. Surnames appear in: profile headers, formal identification (detective lattice queries), and the player's knowledge graph when they learn the full name. Most players will never use or need the surnames — they exist for world consistency and investigative depth.
---
### 1f. Other Wiki Gaps Not in the Brief
Having reviewed all 17 NPC profiles, the 3 location files, knowledge system files, and the authoring guide, here are gaps I identified beyond what the brief covers:
#### Gap 1: PC-as-NPC Profiles Missing
D-029 references "PC-as-NPC Concept A for v0.1" — the other playable character exists as an NPC (~20-30 authored items). **No wiki content exists for this.** We need:
- A smuggler-as-NPC profile (how the detective sees and interacts with the smuggler character when not played)
- A detective-as-NPC profile (how the smuggler sees and interacts with the detective character when not played)
These are load-bearing for the dual-lens experience. The smuggler player should encounter "the Commission investigator" as a threatening NPC. The detective player should encounter "the dock worker" as an unremarkable colleague of Kael's.
**Blocks:** Server entity spawning, dialogue systems, monologue content about the other PC.
#### Gap 2: Monologue Content Pool — Zero Authored Lines
The wiki profiles contain example monologue lines (embedded in contradiction arc descriptions), but there is no monologue content file. The authoring guide (`wiki/authoring/monologue-guide.md`) defines the format, but no actual pool exists. Mellanie needs a minimum viable pool before the monologue system can be tested.
**Blocks:** Monologue system integration testing, client UI monologue display.
#### Gap 3: NPC Routine YAML Layer Missing
D-028 and the SUMMARY specify a 2-layer routine format: YAML (engine-readable) + prose (human-readable). The wiki has the prose layer for all NPCs (Section 5 in each profile). The YAML layer does not exist.
**Blocks:** Server NPC scheduling, routine deviation detection.
#### Gap 4: Triangle Fork Decision Points Not Mechanically Specified
Triangle 1's fork is designed above (1c). But Triangles 2-5 also need player decision points specified for both characters. Currently the triangles describe tension but not player agency. Specifically:
- **Triangle 2 (Worried Knowledge):** What decision does the detective make about Maret? (Approach as witness? Apply pressure? Wait?) What does the smuggler decide about Drin? (Reinforce the compromise? Try to relieve pressure?)
- **Triangle 3 (Bar Tensions):** What decision does either character make about Olin? (Investigate? Befriend? Ignore?) What about Torek's spending? (Smuggler: warn him? Detective: follow the money?)
- **Triangle 4 (Worried Partner):** Decision points exist implicitly (in the FRIEND contradiction arcs) but aren't formalized as explicit player choices.
- **Triangle 5 (Informant Question):** What does the smuggler decide about Pell? (Support, report, or manage?) How does the detective find Pell?
**Blocks:** Storyteller event triggers, dialogue branching, consequence propagation.
#### Gap 5: FactId Catalog — Smuggler Path Entries Sparse
The fact catalog (`wiki/knowledge/fact-catalog.md`) likely has detective-oriented entries (manifest discrepancies, behavioral observations). Smuggler-path FactIds need equivalent coverage: operational facts (who handles what), risk assessments, loyalty intelligence.
**Blocks:** Knowledge graph population for smuggler character, monologue prerequisite checking.
#### Gap 6: Location Files Lack Smuggler-Specific Detail
The three location files (Terminal, Last Shift, Maintenance Corridors) describe physical spaces but don't map smuggling-relevant features: dead spots, timing windows, surveillance gaps, handoff points. The smuggler experiences these spaces as an operational landscape; the locations need that layer.
**Blocks:** Environmental monologue triggers (smuggler entering a corridor and thinking about the operation), spatial gameplay design.
#### Gap 7: Harek Is Tier 2 But Missing Triangle Membership
Harek has a full Tier 2 profile (10 axes, voice sample, dual-lens notes) but is explicitly "not a triangle member." He's described as "external pressure on Drin" in Triangle 2. This is structurally odd — Harek does Tier 2 work (the leverage dynamic is essential to Triangle 2 and Triangle 5) without being IN a triangle. If Drin is promoted, Harek's role as the unseen fourth wall of Triangle 2 should be formalized — either as a triangle member or as a named structural role ("external pressure node").
---
## Topic 2: v0.1 NPC Architecture — Pattern/Motivation Mapping
The workshop brief asks whether the existing 17 NPCs implicitly match the three-system NPC architecture. **Yes — the profiles were designed before the formal system was named, but the patterns are already present.** Let me make the mapping explicit.
### Full NPC → Pattern + Motivation Assignment
| # | NPC | Tier | Pattern | Motivation | Implicit Evidence in Current Profile |
|---|-----|------|---------|-----------|--------------------------------------|
| 1 | Kael Davan | 1 | **FRIEND** | **OPERATOR** | Definitionally THE FRIEND (D-034). Runs dock operations + ring cargo handling. Competent, goal-oriented. |
| 2 | Sera Venn | 1 | **FRIEND** | **WITNESS** | Definitionally THE FRIEND (D-034). Accidentally witnessed manifest discrepancies. Carries information she can't act on. |
| 3 | Naia Tamm | 1* | **MIRROR** | **CIVILIAN** | Established as THE MIRROR (SUMMARY). No contradiction, no secret. Uninvolved in conspiracy. Living their life. |
| 4 | Voss | 2 | **SYSTEM** | **HANDLER** | Institutional embodiment — the shift supervisor IS the legitimate system. Manages operations, applies scheduling pressure. Procedure-citing under stress. |
| 5 | Lera Sessik | 2 | **ANCHOR** | **OPERATOR** | Embodies contentment — "Is this enough? Yes, if the bar stays open." Running the bar is her life. Genuine answer to the thematic question. |
| 6 | Torek Lintar | 2 | **CATALYST** | **CIVILIAN** | His spending forces others to react. Disrupts the bar's equilibrium. Not managing anything — just living visibly. The disruption is unintentional. |
| 7 | Devra | 2 | **THRESHOLD** | **OPERATOR** | Gatekeeper between the local ring and the external supply chain. Running the external coordination. The detective must get past Devra to reach the upstream network. |
| 8 | Maret Korr | 2 | **WITNESS** | **SKEPTIC** | Accidentally witnessed manifest discrepancies (parallel to Sera but from the data side). Doubts the system — the numbers don't add up, and she can't ignore them. |
| 9 | Resha | 2 | **CATALYST** | **CIVILIAN** | Her questions force hub workers to react defensively. New energy disrupting an equilibrium. Not suspicious — just curious in the wrong direction. |
| 10 | Renn | 2 | **THRESHOLD** | **OPERATOR** | Physical gatekeeper — the courier who controls corridor access. Running the transport operation. The detective must trace Renn's routes to map the physical smuggling chain. |
| 11 | Pell | 2 | **CATALYST** | **TURNCOAT** | His potential defection forces a crisis. Loyalty actively shifting. The most dangerous NPC in the ring because his decision cascades everywhere. |
| 12 | Harek | 2 | **ANCHOR** | **HANDLER** | Embodies complacent contentment — "Is this enough? Yes, absolutely." But unconsciously manages Drin through debt leverage. The comfortable man whose comfort creates a tool for others. |
| 13 | Drin | 3→2 | **SYSTEM** | **TURNCOAT** | Institutional embodiment — the dock inspector IS the inspection system. His compromise means the system itself is corrupted. Loyalty shifting under pressure (could crack and cooperate). |
| 14 | Sess | 3 | **NOBODY** | **CIVILIAN** | Social wallpaper. Sees everything, says nothing. Background that could become foreground through player investment. Living their life. |
| 15 | Olin | 3 | **CATALYST** | **CIVILIAN** | New variable forcing evaluation. Ambiguous intent creates productive uncertainty. Uninvolved (as far as anyone knows). |
| 16 | Sabel | 3 | **GHOST** | **OPERATOR** | Absent power — off-station, never fully present. Shapes events through shipments. Running the upstream supply operation. |
| 17 | Tav | 3 | **NOBODY** | **OPERATOR** | Peripheral, barely visible. Running lookout operations at the lowest level. Background ring member who the detective might never notice. |
*Naia Tamm at "Tier 1 (MIRROR)" — not THE FRIEND tier but production emotional depth.
#### Off-stage NPC:
| NPC | Pattern | Motivation | Notes |
|-----|---------|-----------|-------|
| Nils Davan | **GHOST** | **HANDLER** | Absent authority applying pressure through intermediaries. Classic GHOST+HANDLER composition. |
### Pattern Coverage Analysis
| Pattern | v0.1 Count | NPCs | Notes |
|---------|-----------|------|-------|
| FRIEND | 2 | Kael, Sera | Core v0.1 requirement (D-034) |
| MIRROR | 1 | Naia Tamm | First MIRROR instance |
| ANCHOR | 2 | Lera, Harek | Both embody "is this enough?" differently |
| GHOST | 2 | Sabel, Nils | Both off-stage — absent power |
| CATALYST | 3 | Torek, Resha, Olin (+ Pell) | Pell is CATALYST by effect, TURNCOAT by motivation |
| THRESHOLD | 2 | Devra, Renn | Both gatekeep access to the operation |
| SYSTEM | 2 | Voss, Drin | Both ARE institutional processes (scheduling, inspection) |
| NOBODY | 2 | Sess, Tav | Minimum viable NOBODY presence |
| REMNANT | 0 | — | **Not represented in v0.1.** No character embodies "remembers when things were different." Acceptable — REMNANT is a long-game pattern that requires historical depth v0.1 doesn't have. |
**Missing: REMNANT.** This is fine for v0.1. Sova Transit District is 40 years old — there's no deep history for a REMNANT to remember. REMNANT patterns belong on older worlds (mature/ancient drift stages) where someone lived through the founding generation.
### Motivation Coverage Analysis
| Motivation | v0.1 Count | NPCs |
|-----------|-----------|------|
| HANDLER | 3 | Voss, Harek, Nils |
| WITNESS | 2 | Sera, Maret |
| TURNCOAT | 2 | Pell, Drin |
| CIVILIAN | 5 | Naia Tamm, Torek, Resha, Olin, Sess |
| OPERATOR | 5 | Kael, Lera, Devra, Renn, Tav |
| SKEPTIC | 1 | Maret |
**SKEPTIC is underrepresented.** Only Maret doubts the system. But this is mechanically correct — Sova's culture is pragmatic, mind-your-business. Questioning is rare. The detective IS the external skeptic. One internal SKEPTIC (Maret) is enough for v0.1.
### Composition Highlights
The most dramatically rich compositions in v0.1:
| Composition | NPC | Why It Works |
|------------|-----|-------------|
| FRIEND+OPERATOR | Kael | "I was your friend AND I was running the operation you're investigating." Identity betrayal at maximum. |
| FRIEND+WITNESS | Sera | "I was your friend AND I was sitting on evidence the whole time." Concealment as betrayal. |
| MIRROR+CIVILIAN | Naia Tamm | "I was the one innocent person, and the conspiracy touched me anyway." Innocence endangered. |
| SYSTEM+TURNCOAT | Drin | "The system itself is corrupt, and the person embodying it might break." Institutional rot. |
| CATALYST+TURNCOAT | Pell | "The person forcing the crisis is the person whose loyalty is shifting." Maximum instability. |
| GHOST+HANDLER | Nils | "The invisible authority whose pressure creates every visible consequence." Classic absent power. |
| ANCHOR+HANDLER | Harek | "The comfortable man whose comfort creates tools for others." Unconscious complicity. |
---
## Topic 5: Scope Boundary — What Content Is Missing That Blocks Implementation?
### Content that MUST be authored before coding starts
These are items where the server or client team cannot proceed without authored content:
| # | Missing Content | Blocks | Priority | Team |
|---|----------------|--------|----------|------|
| 1 | **Smuggler-lens sections for all 17 NPC profiles** | Smuggler character knowledge graph population, dual-lens monologue selection, smuggler EntityKnowledge examples | Critical | Copy (Paula + Mellanie) |
| 2 | **PC-as-NPC profiles** (smuggler seen by detective, detective seen by smuggler) | Server entity spawning for second character, dialogue with other PC, monologue about other PC | Critical | Copy (Paula) |
| 3 | **Minimum monologue pool** (~50-80 lines per character) | Monologue system integration testing, client UI display, tag taxonomy validation | Critical | Copy (Mellanie) |
| 4 | **NPC routine YAML layer** (engine-readable schedules for all 17 NPCs) | Server NPC scheduling, routine-based movement, deviation detection | Critical | Copy (Paula) + Server (Dudley) format spec |
| 5 | **Triangle fork decision points** (mechanically specified for all 5 triangles) | Storyteller event triggers, dialogue branching, consequence system | High | Copy (Paula + Gestalt) |
| 6 | **Smuggler EntityKnowledge attribute definitions** (8 new keys) | Smuggler knowledge graph implementation, smuggler monologue prerequisites | High | Copy (Paula) + Server (Dudley) |
| 7 | **FactId catalog — smuggler path entries** | Knowledge graph population, monologue prerequisite validation | High | Copy (Paula) |
| 8 | **Content file schema** (wiki → engine-readable format) | Content loader development, hot-reload testing | High | Tyre + Dudley |
| 9 | **Location files — smuggler operational layer** (dead spots, timing windows, handoff points) | Environmental monologue triggers, spatial gameplay, smuggler navigation | Medium | Copy (Paula + Miri) |
| 10 | **Naia Tamm MIRROR-depth content** (~50-70 authored lines) | MIRROR pattern validation, emotional baseline testing | Medium | Copy (Mellanie) |
| 11 | **Nils Davan stub** (as designed in 1c above) | Triangle 1 fork implementation, GHOST pattern reference | Medium | Copy (Paula) — draft provided above |
| 12 | **Drin Tier 2 expansion** (if promoted) | Triangle 2 + Triangle 5 implementation, TURNCOAT pattern testing | Medium | Copy (Paula) — draft provided above |
### Content that is nice-to-have but does NOT block implementation
- Full canonical names (surnames) — cosmetic, knowledge graph uses canonical_id not surnames
- NOBODY tier promotion content — explicitly OUT for v0.1
- Archetype transition mechanics — v0.2+
- Secondary contraband variation — deferred
- Gate topology — not relevant to single-district v0.1
### The honest truth about the gap
The wiki is detective-complete and smuggler-incomplete. Every NPC profile has a "How the Detective Sees [NPC]" section that provides enough mechanical detail for implementation. The smuggler sections are 1-2 sentence monologue notes. This means the server team could build and test the detective's knowledge graph, monologue system, and interaction model from existing content. They CANNOT do the same for the smuggler.
The smuggler-lens content is the single largest content gap blocking v0.1 implementation. It's not a small fix — it requires adding structured operational data, moral arc phases, and smuggler-specific EntityKnowledge attributes to every NPC profile. Estimated scope: 17 NPC profiles x ~30 minutes of writing each = ~8-10 hours of focused copy work.
But what SUSTAINS that across hours of play is the smuggler moral arc. The detective has a clear progression (investigate → discover → confront → resolve). The smuggler needs an equally clear progression (participate → doubt → reckon → compromise). Every NPC interaction should advance or complicate one of those phases. The smuggler-lens sections need to map every NPC to a moral arc phase, not just an operational assessment.
Let me complicate this further: the smuggler and detective paths aren't just parallel — they're entangled through the NPCs. When the smuggler makes a decision about Pell (Triangle 5), the consequences affect what the detective sees when investigating Pell's disappearance. When the detective pressures Maret (Triangle 2), the smuggler sees Maret's increased anxiety. The cross-character consequence propagation is the v0.1 proof of concept. If we ship smuggler content that doesn't map to detective consequences (and vice versa), we've built two separate games in the same district, not one occlusion-based experience.
**Recommendation:** Prioritize items 1-4 (smuggler-lens, PC-as-NPC, monologue pool, routine YAML) as Sprint 3 copy team deliverables. Items 5-7 can proceed in parallel with server architecture work. Items 8-12 are dependencies that should be ticketed and scheduled.
docs/workshops/v01-content-scoping/round1-si.md
-233
View File
@@ -1,233 +0,0 @@
# Round 1 — SI (Project Manager)
## Topic 6: Ticket Landscape for v0.1 Content Scoping
---
## 1. Round 2 Ticket List Review — What Survives the 300-World Reframe?
The Round 2 list (`si-ticket-changes.md`) proposed 29 new tickets across 4 groups. The reframe changes their priority and framing but kills fewer than expected — because v0.1 is hand-authored, most content tickets are still needed. The key shift: every structure created now must be a generator template later.
### 1a. Tickets That Survive Unchanged
These are v0.1 essentials unaffected by the 300-world reframe:
| R2 ID | Title | Team | Rationale |
|-------|-------|------|-----------|
| A1 | Apply canonical full names to all NPC wiki pages | copy | Required for v0.1 content. Names are content, not metadata. |
| A2 | Rename Hael → Naia Tamm across all wiki files | copy | Unanimous decision. Blocks all Naia content. |
| A7 | Add 5 smuggler-specific entity attributes | copy | Dual-lens parity is a v0.1 requirement (D-027). |
| A8 | Standardize location shortcodes in monologue-guide | copy | Bug fix. Blocks monologue authoring. |
| A10 | Stub NPC profile for Nils Davan | copy | Required for Triangle 1 fix. |
| A11 | Fix Triangle 1 — add Volume Escalation decision | copy | v0.1 requires 5 triangles with forks (D-027, D-039). |
| B2 | THE MIRROR pattern spec | copy | Required for Naia Tamm. Also becomes a generator template. |
| B3 | PC-as-NPC unified spec | copy | Required for two-character proof (D-027). |
| B4 | Smuggler voice card + moral arc spec | copy | Dual-lens parity. Also becomes a generator template. |
| B5 | NPC-format briefs for both PCs | copy | Required for wow moment #4 (Divergence Reveal). |
| C1 | Content directory structure design doc | copy | Prerequisite for all content conversion. |
### 1b. Tickets That Survive — Reframed
These still need doing but their framing shifts to "generator template first":
| R2 ID | Title | Team | Reframe |
|-------|-------|------|---------|
| A3 | Create wiki/cultural-groups/krenn-system.md | copy | Becomes the reference implementation for seed.yaml + brief.md dual artifact. Overlaps with existing #319. **Merge** A3 into #319 with expanded scope. |
| A4 | Create regional style guide template | copy | Becomes the seed.yaml template definition, not just a wiki template. Every field must map to a generator input. |
| A6 | Add smuggler-perspective FactId progression text | copy | Survives. Blocked by B4 (smuggler voice). |
| A9 | Add Thematic Question field to Tier 1 profiles | copy | Low priority. Nice-to-have for authoring guidance. |
| A12 | Create environmental text examples | copy | Needed for wow moments (#1 Arrival, #5 News Ticker). |
| B1 | NPC Authoring Style Guide | copy | Reframed: this becomes the NPC generator specification. The style guide IS the generator input format. Most complex ticket — many blockers. |
| C2 | Create content/ directory skeleton | server | Schema must be 300-world compatible from day one. |
| C3 | Content schema definitions | server | Schemas become validation rules for generated content too. |
| C4-C8 | Enum, attribute, pool, template, triangle YAMLs | server | All survive. These ARE the v0.1 content in engine-readable format. |
| C9 | Implement make validate-content CLI | server | Validates hand-authored v0.1 AND future generated output. |
| C10 | Pre-commit FactId typo check | ci | Cheap safety net. Survives. |
| D2 | Seed configuration schema | server | Needed for v0.1 (even with 1-candidate pools). |
### 1c. Tickets That Are Obsolete or Deferred
| R2 ID | Title | Disposition | Rationale |
|-------|-------|-------------|-----------|
| A5 | Add Cultural Groups section to wiki/index.md | **Defer** (v0.2+) | Wiki index restructuring is cosmetic. Content itself matters more. |
| D1 | cultural_gate modifier design doc | **Defer** (v0.2+) | Not in v0.1 IN list. Cultural gating is a generator-era feature. |
| D3 | Secondary contraband variant FactId text | **Kill** | Explicitly OUT in v0.1 scope ("Secondary contraband variation" listed as v0.2+). |
**Score: 26 survive, 1 deferred, 1 deferred, 1 killed = 26 actionable for v0.1.**
---
## 2. Existing Ticket Updates
These existing tickets need status changes based on workshop context:
| ID | Title | Current Status | Action |
|----|-------|---------------|--------|
| #368 | Knowledge vocabulary for v0.1 content | in_progress (Sprint 2) | **Close when wiki review is accepted.** The wiki at `wiki/` is the output. Workshop is the review. |
| #369 | Wiki Review Workshop Outputs (epic) | backlog | **Repurpose** as parent epic for v0.1 content scoping tickets. Update description to reflect this workshop's scope. |
| #301 | Wiki taxonomy and structure | backlog | **Assign to copy team.** Downscope for v0.1: focus on Sova district structure only. Full 500+ world taxonomy is a generator-era concern. |
| #319 | Krenn System wiki entry | backlog | **Merge with A3.** Expanded scope: wiki page + seed.yaml reference implementation. Assign to copy. |
| #261 | Dual Lens Authoring Guide | backlog | **Still critical.** Workshop confirms it blocks all content authoring (#190, #191, #192, #297, #298, #299, #300). Assign to copy. Sprint 3 target. |
| #310 | Character voice speech patterns | backlog | **Overlaps with B4** (smuggler voice card). Merge or make B4 block #310. |
| #306 | News ticker / Meridian feed content | backlog | **Overlaps with D4.** D4 expands scope from 20-30 to 40-50 headlines. Update #306 description. |
| #326 | YAML content loader | backlog | **Assign to server.** Blocked by C1 + C2. Sprint 4 target (after content exists). |
---
## 3. New Tickets Needed (Not in Round 2 List)
The IN list and workshop topics reveal gaps not covered by the Round 2 tickets:
| Proposed ID | Title | Type | Team | Priority | Description | Dependencies |
|-------------|-------|------|------|----------|-------------|--------------|
| NEW-1 | NPC pattern/motivation mapping for v0.1 | task | copy | high | Assign System A pattern + System B motivation to all 17 Sova NPCs. Output: mapping table in wiki. Informs all NPC content authoring and server component design. | None |
| NEW-2 | Drin tier promotion evaluation | task | copy | medium | Evaluate whether Drin should be promoted from Tier 3 to Tier 2. Drin participates in Triangle 2 and Triangle 5 and is compromised by Harek — Tier 2 work in a Tier 3 profile. If promoted, expand profile. | NEW-1 |
| NEW-3 | Wiki → YAML content conversion (Sova NPCs) | story | copy | high | Convert 17 NPC wiki profiles to engine-readable YAML in content/districts/sova-transit/npcs/. Must match schema from C3. First concrete content files. | C1, C2, C3 |
| NEW-4 | Monologue content pool — minimum viable set | story | copy | high | Author minimum monologue line pool to avoid repetition in a 30-minute session. Size TBD by Mellanie (Topic 4 answer), but estimate 80-120 lines covering: arrival observations, NPC routine commentary, environmental flavor, contradiction hints, idle reflections. Dual-lens (smuggler + detective variants). | #261, B4 |
| NEW-5 | v0.1 wow moment content checklist | task | copy | high | Map D-039's 6 wow moments to specific content deliverables. Track which tickets deliver which moments. Acceptance criteria: every wow moment has identified content backing it. | None |
| NEW-6 | PC-as-NPC content authoring (authored lines) | story | copy | high | Author the actual content for PC-as-NPC: 5-7 routine entries per character, 3-5 observation monologue lines per character when seeing the other PC, reverse dual-lens notes. ~20-30 authored items total. Distinct from B5 (spec) — this is the writing. | B3, B5 |
| NEW-7 | Interaction model minimum spec | story | copy | medium | Document the minimum interaction verbs for v0.1: walk, talk, observe, overhear. What triggers each? What UI does each need? What server events? Bridges Topic 4 into implementation tickets for server/client. | None (informed by workshop Topic 4 answers) |
---
## 4. Sprint Assignment
### Sprint 3 (Know) — Copy Team
Sprint 3's goal: "Player can observe NPCs, track knowledge, interact." The server team needs content to load. Copy's Sprint 3 is the **content foundation sprint**.
**Sprint 3 copy tickets (proposed):**
| Priority | Ticket | Rationale | Blocked By |
|----------|--------|-----------|------------|
| P0 | A2: Hael → Naia Tamm rename | Unblocks all Naia content. Quick win. | — |
| P0 | A1: Apply canonical full names | Unblocks content conversion. Quick win. | — |
| P0 | A7: Smuggler entity attributes | Unblocks smuggler-lens content. | — |
| P0 | C1: Content directory structure design | Unblocks all content conversion. | — |
| P0 | #261: Dual Lens Authoring Guide | Blocks 9 downstream tickets. Critical path. | — |
| P1 | A10: Nils Davan stub | Unblocks A11. | — |
| P1 | A11: Triangle 1 fix | Needed for 5-triangle requirement. | A10 |
| P1 | B2: MIRROR pattern spec | Unblocks Naia content. Generator template. | — |
| P1 | B4: Smuggler voice + moral arc | Unblocks dual-lens authoring. Generator template. | A7 |
| P1 | NEW-1: NPC pattern/motivation mapping | Informs all NPC content + server components. | — |
| P1 | NEW-5: Wow moment content checklist | Tracking ticket. Ensures nothing falls through. | — |
| P2 | A8: Shortcode fix | Cleanup. Blocks monologue authoring quality. | — |
| P2 | B3: PC-as-NPC spec | Unblocks B5 and NEW-6. | A7 |
| P2 | NEW-7: Interaction model minimum spec | Bridges workshop into server/client tickets. | — |
**Sprint 3 server tickets (content-related, proposed additions):**
| Priority | Ticket | Rationale | Blocked By |
|----------|--------|-----------|------------|
| P1 | C2: Create content/ directory skeleton | Unblocks all YAML content files. | C1 |
| P1 | C3: Content schema definitions | Unblocks validation + content conversion. | C1 |
### Sprint 4+ (later sprints)
| Ticket | Team | Rationale for Deferral |
|--------|------|----------------------|
| A3/merged #319: Krenn brief + seed.yaml | copy | Needs A4 template first. Not blocking Sprint 3 content. |
| A4: Regional style guide / seed template | copy | Generator-era format. v0.1 can use wiki directly. |
| A6: Smuggler FactId progression text | copy | Blocked by B4. Sprint 4 if B4 completes Sprint 3. |
| A9: Thematic Question field | copy | Low priority authoring guidance. |
| A12: Environmental text examples | copy | Sprint 4. Needed for wow moment #1 but not blocking server. |
| B1: NPC Authoring Style Guide | copy | Most complex ticket with 5+ blockers. Sprint 4-5 assembly. |
| B5: PC NPC-format briefs | copy | Blocked by B3. Sprint 4. |
| NEW-3: Wiki → YAML conversion | copy | Blocked by C1, C2, C3. Sprint 4. |
| NEW-4: Monologue content pool | copy | Blocked by #261, B4. Sprint 4-5. |
| NEW-6: PC-as-NPC content authoring | copy | Blocked by B3, B5. Sprint 5. |
| C4-C8: Content YAML files | server | Blocked by C2. Sprint 4. |
| C9: validate-content CLI | server | Blocked by C3. Sprint 4. |
| C10: FactId pre-commit | ci | No blockers but low urgency. Sprint 4. |
| D2: Seed configuration schema | server | Sprint 4-5. Needed before game-start flow. |
| #326: YAML content loader | server | Blocked by C2. Sprint 4-5. |
---
## 5. Dependency Chain — Critical Path
```
Sprint 3 Critical Path (Copy):
#261 (Dual Lens Guide) ─────────────────────────────┐
├── blocks #297 (FRIEND: Kael) │
├── blocks #298 (FRIEND: Sera) │
├── blocks #299 (Opening hook: smuggler) │
├── blocks #300 (Opening hook: detective) │
├── blocks #310 (Voice speech patterns) │
├── blocks NEW-4 (Monologue pool) │
└── blocks #190, #191, #192 (Content packs) │
│
A7 (Smuggler attributes) ──┬── blocks B4 (Voice+arc) │
├── blocks B3 (PC-as-NPC) │
│ │
B4 (Smuggler voice+arc) ──┼── blocks A6 (FactId text)│
│ blocks NEW-4 │
│ │
B3 (PC-as-NPC spec) ──────┼── blocks B5 (PC briefs) │
│ blocks NEW-6 (Content) │
│ │
C1 (Content dir design) ──┬── blocks C2 (skeleton) │
├── blocks C3 (schemas) │
│ │
C2 (skeleton) ────────────┼── blocks C4-C8 (YAMLs) │
│ blocks NEW-3 (convert) │
│ blocks #326 (loader) │
│ │
C3 (schemas) ─────────────┼── blocks C9 (validator) │
│ blocks NEW-3 (convert) │
│
A10 (Nils stub) ──────────┼── blocks A11 (Triangle 1) │
│
B2 (MIRROR spec) ─────────┼── blocks A9 (Thematic Q) │
│ blocks Naia authoring │
```
**The two critical chains for Sprint 3 are:**
1. **Content authoring chain:** #261 → B4 → A6 → content packs → monologue pool
2. **Content architecture chain:** C1 → C2/C3 → C4-C8/NEW-3 → #326 (loader)
Both chains must begin in Sprint 3 even though they won't complete until Sprint 4-5. Sprint 3's job is to lay the foundation: get #261, C1, A7, and B2 done.
---
## 6. IN List → Ticket Coverage Map
| v0.1 IN List Item | Existing Tickets | New Tickets Needed | Status |
|-------------------|------------------|--------------------|--------|
| WASD movement + collision | Sprint 1-2 (done) | — | Covered |
| Context-sensitive interaction | #240 (Sprint 3) | NEW-7 (spec) | Partially covered — needs spec |
| Monologue system | #45, #119, #120, #122, #253 | NEW-4 (content pool) | Architecture covered, content gap |
| Knowledge graph | #351, #368, #309 | — | Covered |
| 2 playable characters | #57, #180, #182 | — | Covered (architecture) |
| THE FRIEND arc (Kael, Sera) | #297, #298 (blocked by #261) | — | Covered but blocked |
| 5 triangles with forks | #42, #106, #188, #250 | A11 (Triangle 1 fix), C8 (YAML) | Partially covered — weak Triangle 1 |
| 6 wow moments (D-039) | No dedicated tickets | NEW-5 (checklist) | Gap — needs tracking ticket |
| 3 social sites | #54, #190, #191, #192 | C7 (YAML templates) | Covered but blocked by #261 |
| NPC routines | #88, #101 (Sprint 3) | — | Covered (server) |
| Dual-lens parity | #261 | A7, B4, A6 | Major gap — smuggler lens incomplete |
| PC-as-NPC | — | B3, B5, NEW-6 | Gap — no tickets exist yet |
| Content directory | #326 (loader only) | C1, C2, C3 | Gap — structure undefined |
| Content validation | — | C9, C10 | Gap — no validation exists |
---
## 7. Summary
**Round 2 list scorecard:** 26 of 29 tickets survive (1 killed: D3 secondary contraband; 2 deferred: A5 wiki index, D1 cultural_gate).
**New tickets proposed:** 7 (NEW-1 through NEW-7).
**Sprint 3 copy team:** 14 tickets proposed. Critical path starts with #261 (Dual Lens Guide) and C1 (Content directory design).
**Biggest risk:** #261 is the single biggest blocker in the entire content pipeline. It blocks 9 tickets directly and cascades into everything. If it slips, Sprint 4-5 content authoring is delayed. Recommend it gets assigned immediately with Paula as owner.
**Action items for Round 2:**
1. Other agents answer Topics 1-5 — their answers refine NEW-1 (pattern mapping), NEW-4 (pool size), NEW-7 (interaction minimum)
2. Lead approves ticket list
3. SI creates tickets
4. Qatux documents scope decisions
---
*Compiled by SI. Source: Round 2 ticket list, current ticket database (369 tickets), workshop brief, decisions/scope.md (D-027, D-039).*
docs/workshops/v01-content-scoping/round1-stig.md
-373
View File
@@ -1,373 +0,0 @@
# Round 1 Response: Stig (UI Developer)
## v0.1 Content Scoping Workshop
---
## Topic 3: What Does the Client Need from Content Files?
The client is a renderer. It doesn't decide what happens — the server does. So the client's content needs are narrow: display strings, visual parameters, and layout hints. Everything else stays server-side.
### What the client loads directly
| Data | Format | Why |
|------|--------|-----|
| **NPC display names** | `display_name: "Kael Davan"` | Name label above entity rectangle. Must be the name the *player character* knows — "Dock Worker" before identification, "Kael Davan" after. Server sends the current display name per entity via state update, not the content file. |
| **Location display names** | `display_name: "The Terminal"` | HUD location indicator, minimap labels. Short names only — "The Terminal", not "Sova Transit Logistics Hub, Bay 7-C". |
| **Monologue text** | `text: "Morning shift. Recycled air..."` | Rendered by the monologue display system. The server selects the line; the client receives the `id` + `text`. Client doesn't evaluate prerequisites. |
| **Dialogue text** | `text: "Container 4471 sat in temp..."` | Rendered in the dialogue panel. Server selects, client displays. |
| **Entity color palette** | `relationship_colors` map in a client config | D-033 palette. Client derives color from `RelationshipState` sent by server. Not per-NPC content. |
| **Time of day** | Phase enum: `morning`, `afternoon`, `evening`, `night` | HUD clock display. Server sends current phase. Client renders as text and ambient lighting tint. |
### What the client does NOT need
- NPC profiles, axes, secrets, triangle definitions — server-only
- FactId catalog, prerequisite maps — server-only evaluation
- Access tiers, trust levels — server filters before sending to client
- NPC routines/schedules — server simulates, client receives position updates
- Knowledge graph state — server tracks, sends display-relevant slices
### Format recommendation
Client content should be a thin layer. I don't need to parse the full wiki YAML. What I need is:
```yaml
# content/client/strings.yaml
locations:
terminal:
display_name: "The Terminal"
short_name: "Terminal"
minimap_label: "T"
bar:
display_name: "The Last Shift"
short_name: "Last Shift"
minimap_label: "LS"
corridor:
display_name: "Corridor B-7"
short_name: "B-7"
minimap_label: "B7"
hud:
time_phases:
morning: "Morning Shift"
afternoon: "Afternoon"
evening: "Evening"
night: "Night Cycle"
```
Monologue and dialogue text can arrive as part of the server state update — `{type: "monologue", id: "terminal_m_001", text: "Morning shift..."}`. The client doesn't need the full YAML pools on disk. Server selects, client renders. This keeps the client thin and prevents any information leakage (the client literally cannot show what it doesn't have).
**Bottom line:** The client needs display strings + the server's state stream. It should never have access to content it shouldn't be rendering. Every pixel of information passes through the server's information boundary first.
---
## Topic 4: UI Elements for the Minimum Interaction Model
I'll walk through each element: what it looks like, where it sits, how the player reaches it.
### 4.1 The Screen Layout (Overview)
```
+------------------------------------------------------------------+
| |
| |
| |
| GAME WORLD |
| (full viewport) |
| |
| |
| |
| [MONOLOGUE] |
| bottom-left, 1-2 lines |
| |
| [INTERACTION PROMPT] |
| near-player, contextual |
| |
+------------------------------------------------------------------+
| LOCATION | TIME | | [MINIMAP] |
| The Terminal| Morning | | (insert) |
| | | | |
+------------------------------------------------------------------+
```
The game world fills the viewport. UI elements float over it, positioned to stay out of the player's sightline toward the center of the screen where the action is.
**Core principle: the center is sacred.** Nothing permanent lives in the center third of the screen. That's where the character is, where NPCs are, where the player looks. UI lives at the edges and appears only when relevant.
### 4.2 Interaction Prompt
**What it is:** A single-action context label that appears when the player is close enough to interact with something.
**Position:** Offset from the target entity, above and slightly right. Tracks the entity position in world space (not screen-fixed). Small — 12-14px equivalent at reference resolution.
**Appearance:**
```
[Talk] <- NPC within interaction range
Kael Davan <- entity name (if known)
[====] <- entity rectangle
```
Or for objects:
```
[Examine]
Manifest Terminal
[====]
```
**Behavior:**
- **Appears** when player enters interaction radius (~1.5 tiles) AND has line of sight
- **Disappears** when player moves away or breaks LOS
- **Changes based on context:** The same NPC shows "Talk" normally, "Ask about..." after contradiction discovery, or nothing if no interaction is available
- **Single action.** No menus. No radial wheels. The server decides what the primary interaction is based on entity state + player knowledge. The prompt shows ONE thing. Press [E] or [Space] to do it.
- If multiple interactions are available, the prompt shows the most relevant one. The player gets a *decision* about whether to interact, not a *menu* of options.
**Why single-action:** Too many clicks. A radial menu means the player stops, reads, selects, then engages. A single prompt means: approach, press, you're in. The game should feel like walking into a conversation, not operating a database.
**Edge case — multiple valid actions:** If the player needs to choose between "Talk" and "Examine" on the same entity, the prompt changes based on proximity angle or a simple toggle (tap [E] = primary, hold [E] = secondary). But for v0.1, I'd argue: default to "Talk" for NPCs, "Examine" for objects, and handle the edge cases when they arise.
### 4.3 Dialogue Display
**What it is:** How conversation text appears once the player initiates dialogue.
**Position:** Bottom-center of the screen, overlaying the game world. The world stays visible behind it — the player can still see NPCs moving, can still read the room.
**Layout:**
```
+------------------------------------------------------------------+
| |
| GAME WORLD |
| (still visible, slightly dimmed) |
| |
| |
+------------------------------------------------------------------+
| |
| KAEL DAVAN |
| "Container 4471 sat in temp storage overnight. |
| Scheduling backed up again." |
| |
| > [Continue] [End conversation] |
| |
+------------------------------------------------------------------+
```
**Specifications:**
- **Width:** ~60% of screen width, centered horizontally
- **Height:** Variable, 3-5 lines maximum. If the line is longer, it scrolls on input
- **Background:** Semi-transparent dark panel (80% opacity). Not opaque — the world behind bleeds through. The conversation is happening IN the world, not in a separate screen
- **Speaker name:** Top-left of the panel, in the entity's relationship color (D-033). Teal if unknown, green if friendly, amber if person of interest
- **Text:** Off-white, clean sans-serif, left-aligned. One NPC line at a time
- **Advance:** [Space] or [E] advances to next line. No auto-advance — the player controls the pace
- **Exit:** [Escape] or [Q] ends conversation at any point. The NPC reacts (server determines reaction based on conversation progress)
**What this is NOT:**
- No branching dialogue trees visible on screen. The server determines what the NPC says next based on access tier, trust, and state. The player experiences a conversation, not a menu
- No portraits. Top-down game — we see the entities. A portrait would be a second representation that contradicts the top-down perspective
- No response selection in v0.1. The conversation flows. The player's choices are: continue, leave, or (post-discovery) confront. Confrontation is a separate interaction prompt, not a dialogue option
### 4.4 Monologue Display
**What it is:** The player character's internal voice. Text that represents what the character thinks, notices, feels.
**Position:** Bottom-left of the viewport, above the HUD bar. Offset from the dialogue panel position so they never overlap.
**Layout:**
```
+------------------------------------------------------------------+
| |
| GAME WORLD |
| |
| |
| |
| |
| +-----------------------------------------+ |
| | Kael's here. Good -- I was starting | |
| | to worry. | |
| +-----------------------------------------+ |
| |
+------------------------------------------------------------------+
```
**Specifications:**
- **Width:** ~40% of screen width, anchored left
- **Height:** 1-2 lines. Monologue is brief (authoring guide says "one breath")
- **Background:** Minimal. A subtle text shadow or very faint panel (20-30% opacity). The monologue should feel like it's floating in the character's head, not displayed in a UI box
- **Text color:** Character-specific tint. Detective: cool blue-white `#c8d8f0`. Smuggler: warm amber-white `#f0e0c8`. Subtle — not a spotlight, just a whisper of character identity
- **Animation:** Fades in over 0.3s, holds for 4-6 seconds (adjusted by text length), fades out over 0.5s. Does not stack — a new monologue replaces the current one. If the old one hasn't finished, it fades faster (0.15s) before the new one appears
- **Audio cue:** Soft chime on appearance (D-038: `sfx_monologue_chime.ogg`). Sharper variant for anomaly observations (`sfx_monologue_chime_urgent.ogg`)
- **During dialogue:** Monologue can appear DURING a conversation (post_conversation trigger fires after exchange, but observe_anomaly can fire mid-conversation if the player spots something while talking). When dialogue panel is active, monologue shifts up slightly to sit above the dialogue panel, maintaining the same left-anchored position
**Critical rule: monologue must not compete with dialogue.** They occupy different screen regions (left vs. center), use different visual treatments (floating vs. paneled), and serve different functions (character's inner voice vs. NPC's spoken words). If both are on screen simultaneously, the player reads dialogue first (center, larger, solid panel) and catches monologue peripherally (left, smaller, ghostly). This mirrors how internal reactions work — you hear the other person speaking while your own thought forms underneath.
### 4.5 Knowledge Panel (Neural Lattice Interface)
**What it is:** The player's diegetic notebook. A neural lattice overlay that shows what the character knows — people, facts, relationships.
**Diegetic framing:** This isn't a game journal. It's the character checking their implant's records. The detective's Analytical lattice organizes information automatically. The smuggler's Baseline lattice shows simpler records — people they know, places they've been.
**Access:** Press [Tab] to toggle. Pauses the game (or slows to near-pause — design decision for Gestalt). The lattice overlay slides in from the right side of the screen.
**Layout:**
```
+------------------------------------------------------------------+
| |
| GAME WORLD | LATTICE OVERLAY |
| (visible, | |
| dimmed) | PEOPLE [tab] |
| | Kael Davan [green] |
| | Sera Venn [green] |
| | Voss [teal] |
| | "Dock Worker" [teal] |
| | |
| | PLACES |
| | The Terminal |
| | The Last Shift |
| | |
| | OBSERVATIONS |
| | "Manifest discrepancy |
| | — Container 4471" |
| | |
+------------------------------------------------------------------+
```
**Specifications:**
- **Width:** ~30% of screen width, anchored right
- **Sections:** People / Places / Observations. Simple tabs or vertical scroll
- **People entries:** Display name + relationship color dot. Click/select for detail: known attributes, last seen location, relationship state
- **Places:** Location names discovered so far. Click for minimap highlight
- **Observations:** Key facts in plain language. These are the FactIds rendered as human-readable sentences. "Manifest discrepancy observed at Terminal" not "`investigation.manifest_discrepancy: Suspects`"
- **Visual treatment:** Dark panel with a subtle scan-line effect or faint grid overlay — this is a lattice interface, not a paper notebook. The diegetic feel comes from the typography and visual treatment, not from elaborate 3D renders
- **Character-specific:** The detective's lattice shows more analytical structure (observations auto-categorized, flagged items highlighted in amber). The smuggler's lattice is simpler — people and places, fewer analytical overlays
- **Empty state:** At game start, the lattice is sparse. Detective has a few case-file entries. Smuggler knows people but has no "observations" section initially. The lattice fills as the player discovers things
### 4.6 HUD Elements
**What's always visible:**
```
+------------------------------------------------------------------+
| |
| GAME WORLD |
| |
+------------------------------------------------------------------+
| The Terminal | Morning Shift | +----------+ |
| | | | MINIMAP | |
| | | | (D-013)| |
+------------------------------------------------------------------+
```
**Location name:** Bottom-left corner of the HUD bar. Shows current area. Updates on zone transition with a brief fade.
**Time of day:** Next to location. Shows the current phase in plain language ("Morning Shift", "Evening", "Night Cycle"). Updates on phase transition. No clock numbers — the character doesn't check the time, they feel the shift rhythm.
**Minimap (insert):** Bottom-right corner. Small — 120x120px at reference resolution. Shows:
- Player position (character-color dot, D-033)
- Known NPC positions within close range (relationship-colored dots)
- Location boundaries (thin lines, muted)
- POI markers for discovered locations (small icons)
- Fog — areas not yet discovered are dark
The minimap IS the neural lattice navigation overlay (D-013). It should look like a technology interface, not a game map. Subtle grid lines, faint glow at the edges, no terrain texturing. Information appears on it only as the character learns it.
**What's NOT always visible:**
- Character name — the player knows who they are. Don't waste pixels reminding them
- Health/status bars — no health system in v0.1
- Inventory indicators — no inventory in v0.1 (knowledge-based, per Gestalt's direction)
- Quest markers — this is not that kind of game
- Mini-objectives — the player decides what to do
### 4.7 News Ticker
The Meridian news feed in The Last Shift. This is a diegetic element — it exists in the world, on the bar's display screen.
**Implementation:** A world-space text object attached to the bar's display entity. Scrolling text, left-to-right, station news headlines. The player reads it by standing near the display, not through a HUD overlay.
**Why world-space:** D-039 Wow Moment #5 requires the same ticker to produce different monologue reactions per character. If the ticker were a HUD element, it would feel like a notification system. In world space, it's a thing in the bar that you walk over to and read. The monologue fires because your character is looking at it, not because the UI decided to inform you.
---
## Topic 5: Minimum UI for a 30-Minute Vertical Slice
### Must be polished (player-facing, first impression)
| Element | Why polished | Effort level |
|---------|-------------|-------------|
| **Monologue display** | This IS the game's voice. If monologue feels janky, the character feels dead. Smooth fade, correct timing, readable text, audio chime sync. | Medium — text rendering + animation + audio trigger |
| **Interaction prompt** | First thing the player tries. Walk to NPC, see "Talk", press key, it works. If this is clunky, the game feels broken. | Low — context label + input handler |
| **Dialogue panel** | Second thing the player tries. Text must be readable, pacing must feel natural, exit must work cleanly. | Medium — text display + input flow + state management |
| **Entity relationship colors** | D-033. The color palette tells the player who matters before any text appears. Green = safe, amber = something changed. THE FRIEND's color shift (green to amber) is Wow Moment #3. | Low — shader/tint parameter driven by server state |
| **Fog of perception** | D-011. If the player can see everything, there's no game. LOS shadowcasting must work. | High — but this is Dudley/Tyre territory, not UI |
### Can be placeholder (functional, not pretty)
| Element | Why placeholder is OK | Placeholder spec |
|---------|----------------------|-----------------|
| **Minimap** | Players will use it but don't expect polish in a vertical slice. A dot on a dark rectangle is sufficient. | Player dot + area boundary lines. No labels, no icons. |
| **HUD bar** | Location name + time phase in plain text, no styling. | Left-aligned text, default font, dark background strip. |
| **Knowledge panel** | Players may not even find it in 30 minutes. But it must exist for the detective's analytical loop. | Plain text list on a dark overlay. No scan-line effects, no diegetic styling. Functional data display. |
| **News ticker** | D-039 Wow Moment #5 needs it, but the ticker itself can be simple scrolling text. The wow is in the monologue reaction, not the ticker's visual polish. | Scrolling text on a world-space panel. Monospace font. Functional. |
### Can be deferred entirely (v0.2+)
| Element | Why defer |
|---------|----------|
| **Perception mode overlays** | D-017: only natural vision in v0.1. No thermal, no camera feeds, no tracking. |
| **Inventory UI** | No inventory system in v0.1. Knowledge-based interaction. |
| **Character selection screen** | v0.1 can start with a character toggle or separate launch configs. No menu needed. |
| **Settings/options menu** | Dev builds. Hardcode resolution, keybindings. |
| **Tutorial/onboarding** | Monologue IS the tutorial (D-016: "That terminal might have access logs"). No separate tutorial UI. |
| **Map zoom/pan** | Camera locked (D-015). No map interaction beyond the minimap. |
### The 30-minute visual journey
Here's what the player actually sees, minute by minute:
**Minute 0-1 (Arrival):** Black screen fades in. Station ambient plays. The game world appears, character in the center, fog surrounding them. First monologue fades in at bottom-left: "Morning shift. Recycled air and cargo lubricant." Chime sounds. HUD bar shows "The Terminal | Morning Shift". Minimap shows a small illuminated area around the player.
**Minute 1-5 (Exploration):** Player moves with WASD. Fog recedes as they explore. NPC rectangles appear in the viewport — colored dots. Walking near an NPC shows their display name and [Talk] prompt. First dialogue: the panel slides up from the bottom, semi-transparent, NPC name in relationship color. Text advances on input. Conversation ends, panel slides down. Monologue fires: "Kael's here. Good."
**Minute 5-15 (The Character's Eye):** Monologue fires unprompted with the urgent chime — the character noticed something the player didn't. The text is different: sharper, the urgent variant. "Dock worker Davan -- lattice activity spiked." The player hasn't done anything — the game is teaching them that their character has a mind.
**Minute 15-20 (Building routine):** Player moves between Terminal and Bar. Location name transitions on the HUD. The bar is warmer (amber lighting tint). Minimap updates with new area. Monologue at bar entry: different tone, different character voice. Dialogue with Sera Venn — the panel text feels different from Kael's. Same UI, different voice.
**Minute 20-25 (THE FRIEND's contradiction):** Kael's entity color shifts — green to amber. 0.5s fade per D-033. This is silent, visual. No fanfare. The urgent monologue chime fires. "Kael? By the service hatch? And that's -- I don't know them." If the player presses [Tab], the knowledge panel now shows Kael as "Person of Interest" with an observation entry.
**Minute 25-30 (The quiet moment):** Player standing still in a corridor. After idle time, monologue fades in without chime. Reflective. Quiet. "No Meridian signal down here. No eyes, no ears." The game breathes. The UI is invisible. The world is present.
### Summary: v0.1 UI bill of materials
| System | Files/Scenes | Priority |
|--------|-------------|----------|
| Monologue renderer | 1 scene + 1 script | P0 (must ship) |
| Interaction prompt | 1 scene + 1 script | P0 |
| Dialogue panel | 1 scene + 1 script | P0 |
| Entity color system | Shader + config | P0 |
| HUD bar (location + time) | 1 scene + 1 script | P1 (placeholder OK) |
| Minimap | 1 scene + 1 script | P1 |
| Knowledge panel | 1 scene + 1 script | P1 |
| News ticker (world-space) | 1 scene + 1 script | P1 |
| Fog rendering | Shader + integration | P0 (shared with server team) |
Total: ~9 scenes, ~9 scripts, 2 shaders. This is a tight UI. Every element earns its pixel.
---
## Open Questions for Other Participants
**For Dudley (server):**
- What does the state update message look like? I need: entity positions, display names, relationship states, monologue triggers (id + text), dialogue lines (id + text + speaker), time phase, location zone ID. What's the IPC message format?
- Does the server send the full text of monologue/dialogue lines, or just IDs that the client looks up locally? I prefer full text in the message (keeps client thin, prevents info leakage), but there's a bandwidth trade.
**For Gestalt (systems):**
- Does opening the knowledge panel pause the game? Semi-pause? If NPCs keep moving while you read, you miss things. If the game pauses, it breaks immersion. I lean toward semi-pause (simulation runs at 10% speed).
- Single-action interaction prompt: does this work for the systems design? Or does the player need to choose between "Talk" and "Observe" on the same NPC?
**For Mellanie (copy):**
- Maximum monologue line length? I'm designing for 1-2 lines of display text (~80 characters per line, ~160 max). Is that enough for the voice?
- How many monologue lines can fire in sequence before it feels like a wall of text? I'd say 1 at a time with 2-3 second gaps minimum.
**For Araminta (visual):**
- Diegetic styling for the knowledge panel — how far do we push the "lattice interface" look in v0.1? My instinct: minimal. Faint grid, slightly blue-shifted palette, clean type. Save the fancy scan-line effects for when we have art budget.
- Monologue text color per character — I proposed detective blue-white and smuggler amber-white. Does this conflict with the entity color palette (D-033)?
---
*The player's eye goes to the center. Everything else stays out of the way until it's needed. Then it appears, does its job, and vanishes.*
docs/workshops/v01-content-scoping/round1-tracking.md
-491
View File
@@ -1,491 +0,0 @@
# Round 1 Tracking — Qatux (Documenter)
## v0.1 Content Scoping Workshop
**Status:** All 7 responses received (Gestalt, Paula, Tyre, Mellanie, Stig, Dudley, SI). Round 1 complete.
**Date:** 2026-02-12
---
## 1. Agreements (Consensus Items)
These items have clear consensus across respondents and could be decided immediately:
| # | Item | Supporters | Status |
|---|------|-----------|--------|
| A-01 | **Drin promoted to Tier 2** | Gestalt (unambiguous yes), Paula (full Tier 2 profile drafted), Mellanie (implicitly — budgets Drin as Tier 2) | Ready to decide |
| A-02 | **THE NOBODY mechanic deferred to v0.2; data ships in v0.1** | Gestalt (explicit: ship data, defer mechanic), Dudley (NobodyState deferred per brief) | Ready to decide |
| A-03 | **YAML as content format** (with dissent — see D-01) | Tyre (detailed rationale), Stig (accepts server-sent text), Mellanie (needs author-readable format) | Needs resolution with Dudley |
| A-04 | **7-interaction minimum** (Move, Look, Monologue, Examine Object, Examine NPC, Talk, Overhear) | Gestalt (designed it), Stig (UI for each), Dudley (server events for each) | Ready to decide |
| A-05 | **~200 monologue lines total** (~100 per character) | Mellanie (80-110 per character, detailed math), Gestalt (implicitly validates via wow moment mapping) | Ready to decide |
| A-06 | **~695 total authored content items for v0.1** | Mellanie (200 monologue + 350 dialogue + 50 environmental + 20 ticker + 50 UI + 25 PC-as-NPC) | Needs validation from others |
| A-07 | **5 triangles: 3 active forks, 2 passive tensions** | Gestalt (explicit table: T1/T2/T4 active, T3/T5 passive), Paula (aligns with triangle fork detail) | Ready to decide |
| A-08 | **Naia Tamm needs MIRROR-specific voice samples** | Mellanie (5 samples written), Paula (naming cascade planned) | Ready to decide |
| A-09 | **Content directory: `global/` + `districts/` top-level split** | Tyre (detailed tree), Dudley (load sequence matches), Gestalt (aligns with Wiki Review consensus) | Ready to decide |
| A-10 | **Dialogue files by location + role, not by NPC** | Tyre (explicit design choice, per D-035) | Needs validation from Dudley, Gestalt |
| A-11 | **THE FRIEND arc is the critical path for v0.1** | Tyre (Tier 4 risk, "everything converges on wow moment #3"), Dudley (FriendArc is the sole pattern-specific component), Gestalt (maps all wow moments to FRIEND), Mellanie (writes FRIEND content first) | Consensus |
| A-12 | **Client receives text from server, doesn't load content files directly** | Stig (explicit: "server selects, client renders"), Dudley (server authoritative over dialogue/monologue selection), Tyre (aligns with D-010 information boundary) | Ready to decide |
| A-13 | **Single-action interaction prompt (no radial menus)** | Stig (explicit: "single prompt, press E"), Gestalt (context-sensitive prompt table) | Ready to decide |
| A-14 | **PC-as-NPC required for v0.1** | Gestalt (missing from IN list, adds it), Paula (Gap 1: profiles missing, must be authored), Mellanie (budgets ~25 items) | Ready to decide |
| A-15 | **News ticker required for v0.1** | Gestalt (missing from IN list, wow moment #5), Stig (world-space implementation), Mellanie (budgets ~20 items) | Ready to decide |
| A-16 | **Time progression required for v0.1** | Gestalt (missing from IN list, dependency for routines), Dudley (DayPhase already exists), Stig (HUD display designed) | Ready to decide |
| A-17 | **Self-contained triangle forks for v0.1 (no cross-triangle cascade)** | Tyre (explicit scope control recommendation, "strongly recommend self-contained") | Needs validation from Gestalt |
---
## 2. Disagreements (Require Resolution)
### D-01: Content File Format — YAML vs. RON
| Position | Advocate | Argument |
|----------|----------|----------|
| **YAML** | Tyre | Author readability, native multi-line text, JSON Schema validation, any language can emit it, 1.5ms parse difference irrelevant |
| **RON** | Dudley | Structured + typed data, all examples in RON format, mentions "Tyre's call on format" suggesting deference but preference for RON |
**Impact:** Affects every content file, loader implementation, validation pipeline, generator output format.
**Note:** Dudley writes "Tyre's call on format" in his response, which suggests he'll defer. But his manifest example uses `content/manifest.ron` and all NPC profile examples are in RON. The two proposals need reconciliation before implementation.
### D-02: NPC Pattern/Motivation Mapping — 10 of 17 NPCs Disagree
This is the largest disagreement in Round 1. Gestalt and Paula independently mapped all 17 NPCs. They agree on 7 and disagree on 10.
#### Full Comparison Table
| # | NPC | Tier | Gestalt Pattern | Paula Pattern | Match? | Gestalt Motivation | Paula Motivation | Match? |
|---|-----|------|----------------|--------------|--------|-------------------|-----------------|--------|
| 1 | Kael Davan | T1 | FRIEND | FRIEND | YES | OPERATOR | OPERATOR | YES |
| 2 | Sera Venn | T1 | FRIEND | FRIEND | YES | WITNESS | WITNESS | YES |
| 3 | Naia Tamm | T1* | MIRROR | MIRROR | YES | CIVILIAN | CIVILIAN | YES |
| 4 | Voss | T2 | SYSTEM | SYSTEM | YES | **OPERATOR** | **HANDLER** | **NO** |
| 5 | Lera Sessik | T2 | ANCHOR | ANCHOR | YES | OPERATOR | OPERATOR | YES |
| 6 | Torek Lintar | T2 | CATALYST | CATALYST | YES | CIVILIAN | CIVILIAN | YES |
| 7 | Devra | T2 | THRESHOLD | THRESHOLD | YES | **HANDLER** | **OPERATOR** | **NO** |
| 8 | Maret Korr | T2 | **SYSTEM** | **WITNESS** | **NO** | **WITNESS** | **SKEPTIC** | **NO** |
| 9 | Resha | T2 | CATALYST | CATALYST | YES | **SKEPTIC** | **CIVILIAN** | **NO** |
| 10 | Renn | T2 | THRESHOLD | THRESHOLD | YES | OPERATOR | OPERATOR | YES |
| 11 | Pell | T2 | CATALYST | CATALYST | YES | TURNCOAT | TURNCOAT | YES |
| 12 | Harek | T2 | **GHOST** | **ANCHOR** | **NO** | HANDLER | HANDLER | YES |
| 13 | Drin | T2 (promoted) | **REMNANT** | **SYSTEM** | **NO** | TURNCOAT | TURNCOAT | YES |
| 14 | Sess | T3 | **ANCHOR** | **NOBODY** | **NO** | CIVILIAN | CIVILIAN | YES |
| 15 | Olin | T3 | CATALYST | CATALYST | YES | **SKEPTIC** (dual) | **CIVILIAN** | **NO** |
| 16 | Sabel | T3 | **THRESHOLD** | **GHOST** | **NO** | OPERATOR | OPERATOR | YES |
| 17 | Tav | T3 | **SYSTEM** | **NOBODY** | **NO** | **CIVILIAN** | **OPERATOR** | **NO** |
**Summary:** 7 full agreements, 4 pattern-only disagreements, 2 motivation-only disagreements, 4 both-disagree cases.
#### Analysis of Each Disagreement
| NPC | Disagreement | Gestalt's Reasoning | Paula's Reasoning | Assessment |
|-----|-------------|--------------------|--------------------|------------|
| **Voss** (motivation) | OPERATOR vs HANDLER | "Running the schedule that enables smuggling" | "Manages operations, applies scheduling pressure" | Both defensible. Gestalt sees Voss as OPERATING the system; Paula sees Voss as HANDLING people through scheduling authority. Voss arguably does both. |
| **Devra** (motivation) | HANDLER vs OPERATOR | "Managing operations from above" = HANDLER | "Running the external coordination" = OPERATOR | Swapped vs Voss. Gestalt sees Devra as a handler (pressure from above), Paula sees Devra as running things (operational). |
| **Maret** (both) | SYSTEM+WITNESS vs WITNESS+SKEPTIC | "Institutional scheduler... saw discrepancies" | "Accidentally witnessed discrepancies... doubts the system" | Core question: is Maret primarily a SYSTEM embodiment (institutional role) or a WITNESS (defined by what she saw)? Motivation: does she WITNESS (passive) or SKEPTIC (active questioning)? |
| **Resha** (motivation) | SKEPTIC vs CIVILIAN | "Doubts the 'mind your business' culture" | "Not suspicious — just curious" | Key difference: Gestalt interprets Resha's questions as genuine skepticism; Paula interprets them as innocent curiosity (CIVILIAN). |
| **Harek** (pattern) | GHOST vs ANCHOR | "Shapes events through debt leverage, not direct membership" | "Embodies complacent contentment — but unconsciously creates tools" | Gestalt sees Harek's indirect influence as GHOST-like; Paula sees Harek's comfortable contentment as ANCHOR-like. Both are valid reads of different aspects. |
| **Drin** (pattern) | REMNANT vs SYSTEM | "Remembers when the job was just a job" | "The dock inspector IS the inspection system" | Gestalt foregrounds Drin's nostalgia; Paula foregrounds Drin's institutional role. SYSTEM seems mechanically stronger (his compromise corrupts the system). |
| **Sess** (pattern) | ANCHOR vs NOBODY | "Quiet contentment behind the bar" | "Social wallpaper... background that could become foreground" | Gestalt sees Sess as genuinely content (ANCHOR at T3); Paula sees Sess as currently invisible (NOBODY). Depends on whether ANCHOR can be T3. |
| **Olin** (motivation) | SKEPTIC (dual) vs CIVILIAN | "Asks questions with ambiguous intent" = SKEPTIC | "Uninvolved (as far as anyone knows)" = CIVILIAN | Gestalt gives Olin dual motivation (ambiguity IS the character). Paula keeps it simpler. |
| **Sabel** (pattern) | THRESHOLD vs GHOST | "Off-station gatekeeper of supply chain" | "Absent power — off-station, never fully present" | Gestalt sees Sabel as a gatekeeper (THRESHOLD); Paula sees Sabel as absent power (GHOST). Both are right about different functions. |
| **Tav** (both) | SYSTEM+CIVILIAN vs NOBODY+OPERATOR | "Ring lookout following procedure... lowest rung" | "Peripheral, barely visible... running lookout operations" | Gestalt sees a system functionary; Paula sees a background figure doing a job. |
**Resolution path:** These disagreements reflect genuinely different analytical lenses. Gestalt maps from *mechanical function* (what does this NPC do in the system?). Paula maps from *narrative weight* (what does this NPC mean to the story?). Round 2 should produce a single canonical mapping with explicit rationale per NPC.
### D-03: Smuggler EntityKnowledge Keys — 4 New vs 8 New
| Position | Advocate | Keys |
|----------|----------|------|
| **4 new keys** (+ 2 existing repurposed, + 2 deferred) | Gestalt | New: `exposure_risk`, `loyalty_assessment`, `cover_integrity`, `moral_weight`. Repurposed: `trust_level` → `trust_read`, `secret_held` → `leverage_held`. Deferred: `social_debt`, `loyalty_conflict`. |
| **8 new keys** (all as new additions) | Paula | All 8 as separate new keys: `trust_read`, `exposure_risk`, `loyalty_assessment`, `leverage_held`, `social_debt`, `moral_weight`, `cover_integrity`, `loyalty_conflict` |
**Key difference:** Gestalt argues `trust_read` and `leverage_held` already exist as `trust_level` and `secret_held` with per-character interpretation. Paula treats them as distinct keys. Gestalt also defers `social_debt` (no time for favor economy in 30min) and `loyalty_conflict` (inferable from existing keys).
**Impact:** Affects knowledge graph schema, smuggler monologue prerequisite vocabulary, content authoring complexity.
### D-04: Examine NPC vs Talk — Separate or Combined?
| Position | Advocate | Argument |
|----------|----------|----------|
| **Separate interactions** (E to Examine, F to Talk) | Gestalt | Detective loop: examine first → talk later. Smuggler loop: talk first → examine when suspicious. Collapsing them breaks both loops. |
| **Single primary action** (context determines) | Stig | "Default to Talk for NPCs, Examine for objects, handle edge cases when they arise." Asks Gestalt to confirm. |
**Impact:** Directly affects UI design, keybinding, server interaction pipeline.
**Note:** Not a strong disagreement — Stig asks the question, Gestalt has a firm answer. Needs explicit decision.
### D-05: Knowledge Panel Pause Behavior
Stig asks: "Does opening the knowledge panel pause the game? Semi-pause?"
- Stig leans toward semi-pause (10% simulation speed)
- No response from Gestalt yet in this round
---
## 3. Open Questions (From Respondents)
### From Gestalt
- Q: Should triangle forks cascade across triangles in v0.1? (Tyre says no — self-contained)
### From Paula
- Q: Other wiki gaps? (She identified 7 additional gaps beyond the brief's list — see section 7)
- Q: Harek's structural role — formalize as triangle member or "external pressure node"?
### From Tyre
- Q: Protocol evolution v2 → v3 — sign-off needed for new ObserverSnapshot fields
- Q: Line previewer CLI — when to build? (Early, per his recommendation)
### From Mellanie
- Q: Confirm monologue guide examples as canonical PC voice registers? (Blocks all monologue authoring)
- Q: Maximum monologue line length? (She needs char limits from Stig — Stig proposes ~160 chars/2 lines)
- Q: Smuggler internal voice register — how terse? How operational?
- Q: Detective internal voice register — how clinical? How institutional?
### From Stig
- Q: IPC message format for state updates? (For Dudley)
- Q: Server sends full text or line IDs? (Stig prefers full text — keeps client thin)
- Q: Lattice panel diegetic styling — how far in v0.1? (For Araminta)
- Q: Monologue text colors per character — conflict with D-033 entity palette? (For Araminta)
### From Dudley
- Q: `PlayerAction::Interact` is currently a no-op — needs extension (protocol change)
- Q: Need Tyre sign-off on ObserverSnapshot v2 → v3 protocol evolution
---
## 4. Scope Boundary — Revised IN/OUT
### Gestalt's Additions to IN (4 items)
| Added Item | Rationale | Cross-Support |
|-----------|-----------|---------------|
| **News ticker** | Required for wow moment #5 | Stig (designed world-space implementation), Mellanie (budgeted 20 items) |
| **PC-as-NPC** | Required for divergence reveal (wow moment #4) | Paula (identified as Gap 1), Mellanie (budgeted 25 items) |
| **Time progression** | Required for NPC routines, shift transitions | Dudley (DayPhase exists), Stig (HUD designed) |
| **Relationship state transitions** | Required for FRIEND arc (Friendly → PersonOfInterest) | Dudley (RelationshipState in knowledge graph) |
### Gestalt's Additions to OUT (5 items)
| Excluded Item | Rationale | Risk if not excluded |
|-------------|-----------|---------------------|
| **Inventory system** | Evidence is knowledge, not physical items | Feature creep ("pick up the manifest") |
| **Stealth mechanics** | Social stealth, not mechanical stealth | Immersive sim instincts will demand it |
| **Combat system** | Not in D-027 criteria | Ate scope from other features |
| **Player-facing save/load** | Session-based 30-minute slice | Dev-mode save fine, player-facing deferred |
| **Lattice modification/upgrade** | Contraband IS lattice components but player can't use them | "Can the player use smuggled mods?" No. |
---
## 5. Content Volume Estimates (Mellanie)
| Category | Items | Priority |
|----------|-------|----------|
| Monologue pools (2 characters) | ~200 lines | Critical |
| NPC dialogue | ~350 lines | Critical |
| Environmental text | ~50 items | High |
| News ticker | ~20 items | Medium |
| UI microcopy | ~50 strings | High |
| PC-as-NPC content | ~25 items | Medium |
| **TOTAL** | **~695** | |
**Authoring order (Mellanie's proposed sequence):**
1. THE FRIEND: Kael content pack (~100 lines) — exercises every pipeline
2. THE FRIEND: Sera content pack (~100 lines)
3. THE MIRROR: Naia Tamm (~60-70 lines)
4. Tier 2 NPCs (~100-150 lines: Voss, Lera, Torek, Maret)
5. Environmental text + ticker (~70 items)
6. Remaining monologue fill (top up to ~200)
7. UI copy + tutorial monologue (~50 strings)
8. Tier 3 background + PC-as-NPC (~50 items)
---
## 6. Technical Risk Assessment (Tyre)
| Feature | Risk | Primary Factor | Mitigation |
|---------|------|----------------|------------|
| WASD + collision | Low | None significant | Already built |
| 3 social sites | Low | Art (not v0.1 concern) | Functional boxes |
| NPC routines | Low-Medium | Content authoring time | Start schedules early |
| Knowledge graph | Medium | Downstream dependency chain | Sprint 2 narrow scope |
| 2 playable characters | Medium | Content volume doubling | Content validation tooling |
| Context-sensitive interaction | Medium | Dialogue selection tuning | Line previewer CLI |
| **Monologue system** | **High** | Trigger detection + prerequisite eval | Simple AND-only prerequisites |
| **THE FRIEND arc** | **High** | Integration of all systems | Dedicated integration test |
| 5 triangle forks | Medium-High | Cascade complexity | Self-contained forks |
| 6 wow moments | Varies | #3 is the critical path | Prioritize everything unblocking #3 |
**Critical path:** Knowledge graph → Contradiction detection → FRIEND phase transitions → Spatial staging → Monologue trigger → Monologue display → FRIEND content authored and loaded.
**What will take longer than expected (Tyre's warnings):**
1. Monologue prerequisite tuning (gap between "works" and "feels right")
2. Dialogue selection weighting (same tuning problem)
3. Spatial staging for THE FRIEND (Kael in Corridor B-7 when player is nearby, without feeling scripted)
4. Content conversion (17 NPC wiki profiles → YAML, ~2-3 full days)
---
## 7. Wiki Gaps Identified (Paula)
Beyond the 5 issues in the brief, Paula identified 7 additional gaps:
| # | Gap | Blocks | Priority |
|---|-----|--------|----------|
| Gap 1 | **PC-as-NPC profiles missing** | Server entity spawning, dialogue, monologue about other PC | Critical |
| Gap 2 | **Monologue content pool — zero authored lines** | Monologue system integration testing | Critical |
| Gap 3 | **NPC routine YAML layer missing** | Server NPC scheduling, deviation detection | Critical |
| Gap 4 | **Triangle fork decision points not mechanically specified** | Storyteller triggers, dialogue branching | High |
| Gap 5 | **FactId catalog — smuggler path entries sparse** | Knowledge graph population, monologue prerequisites | High |
| Gap 6 | **Location files lack smuggler operational detail** | Environmental monologue triggers, spatial gameplay | Medium |
| Gap 7 | **Harek has no triangle membership despite T2 role** | Triangle 2/5 formalization | Medium |
---
## 8. ECS / Server Architecture (Dudley)
### Components Proposed
| Component | Purpose | v0.1? |
|-----------|---------|-------|
| `ThematicPattern` | System A tag (9 patterns) | Yes |
| `FunctionalMotivation` | System B tag (6 motivations) | Yes |
| `FriendArc` | THE FRIEND phase tracking, contradiction detection | Yes (Kael, Sera only) |
| `ContentTier` | Tier1/Tier2/Tier3 simulation depth | Yes |
| `AccessTierMap` | D-028 Layer 1 dialogue access filtering | Yes |
| `TrustLevels` | D-028 Layer 3 gossip gating | Yes |
| `TriangleMembership` | Triangle role references per NPC | Yes |
| `NpcRoutine` | Schedule-based movement (DayPhase → position) | Yes |
| `MoodState` | D-035 mood tag for dialogue selection | Yes |
| `NobodyState` | Promotion stages + interaction counter | Deferred |
| `GhostInfluence` | Off-stage influence | Deferred |
| `CatalystTrigger` | Arrival/disruption event chain | Deferred |
### Key Design Principle (Dudley)
"Pattern and motivation are tags for content selection, not unique simulation subsystems. THE FRIEND is the sole exception in v0.1 because its arc progression is load-bearing."
### What Dudley Can Build Now (No Content Dependency)
- Content loader framework (Phase 1-6 skeleton)
- Proximity trigger system
- Interaction event pipeline
- Dialogue selection pipeline (D-035 tag filtering)
- Monologue trigger system
- NPC routine scheduler
- FriendArc phase transition logic
- All with fixture/synthetic data
### What Dudley Cannot Build Without Content
- Actual NPC spawning (needs profiles in structured format)
- Real dialogue/monologue testing (needs authored lines)
- NPC routine pathfinding (needs district spatial layout)
- Overheard conversations (needs NPC-NPC scripts)
- FactId catalog (needs machine-readable version)
- Triangle escalation logic (needs formal conditions)
---
## 9. UI Architecture (Stig)
### v0.1 UI Bill of Materials
| Element | Priority | Effort |
|---------|----------|--------|
| Monologue renderer | P0 (must ship) | Medium |
| Interaction prompt | P0 | Low |
| Dialogue panel | P0 | Medium |
| Entity color system | P0 | Low |
| HUD bar (location + time) | P1 (placeholder OK) | Low |
| Minimap | P1 | Medium |
| Knowledge panel | P1 | Medium |
| News ticker (world-space) | P1 | Low |
| Fog rendering | P0 (shared with server) | High |
**Total:** ~9 scenes, ~9 scripts, 2 shaders.
### Key Design Decisions (Stig)
- Center of screen is sacred (no permanent UI)
- Monologue: bottom-left, 40% width, fades in/out, character-tinted text
- Dialogue: bottom-center, 60% width, semi-transparent dark panel, world visible behind
- Interaction prompt: world-space, tracks entity, single action
- Knowledge panel: right-side overlay on [Tab], diegetic lattice interface
- News ticker: world-space text on bar's display entity (not HUD)
- Monologue display time: 4-6 seconds adjusted by text length
- Character text colors: Detective blue-white `#c8d8f0`, Smuggler amber-white `#f0e0c8`
---
## 10. Cross-Reference: Ticket Categories (Tyre)
Tyre proposes ticket splits across 8 categories:
1. **Content Infrastructure** — directory structure, content loader (4 phases), validation schemas, line previewer CLI
2. **Wiki → Content Conversion** — NPC profiles (17), locations (3), fact catalog, triangles (5), routines
3. **Monologue System** — trigger detection, prerequisite evaluation, line pool selection, pacing/cooldown, content authoring, display UI, chime audio
4. **Dialogue System** — pool loader, selection algorithm, content authoring, UI
5. **Interaction Model** — proximity detection, state machine, prompt UI
6. **THE FRIEND Arc** — phase transitions, contradiction detection, tell accumulation, content (Kael + Sera), relationship colors, integration test
7. **NPC Rendering + Routines** — schedule execution, deviation events, sprite/label rendering, movement animation
8. **Cross-Cutting** — PC-as-NPC, news ticker, smuggler lens parity, Naia Tamm rename
**Dependency chain critical path (Tyre):**
```
Content directory structure
-> Content loader (Phase 1-2)
-> NPC profile conversion -> NPC schedule execution
-> Content loader (Phase 3-4)
-> Dialogue pool loader -> Dialogue selection -> Dialogue UI
-> Monologue trigger detection
-> Prerequisite evaluation
-> Line pool selection
-> Monologue pacing -> Monologue display UI
Knowledge graph (Sprint 2)
-> Contradiction detection -> FRIEND phase transitions
-> Monologue prerequisite evaluation
-> Tell system accumulation
```
---
## 11. Items Requiring Round 2 Resolution
| # | Item | Required Participants | Priority |
|---|------|---------------------|----------|
| R2-01 | **Canonical NPC pattern/motivation mapping** (resolve 10 disagreements) | Gestalt, Paula | Critical |
| R2-02 | **Content format: YAML vs RON** | Tyre, Dudley | Critical |
| R2-03 | **Smuggler EntityKnowledge keys: 4 new vs 8 new** | Gestalt, Paula, Dudley | High |
| R2-04 | **Examine NPC vs Talk: separate or combined interaction?** | Gestalt, Stig, Dudley | High |
| R2-05 | **Knowledge panel pause behavior** | Gestalt, Stig | Medium |
| R2-06 | **PC voice register confirmation** (blocks Mellanie's authoring) | Gestalt or Paula | High |
| R2-07 | **Triangle fork cascade: self-contained or cross-triangle?** | Gestalt, Tyre | High |
| R2-08 | **Harek's structural role** (triangle member vs external pressure node) | Gestalt, Paula | Medium |
| R2-09 | **ObserverSnapshot v2 → v3 protocol change** | Tyre, Dudley, Stig | High |
| R2-10 | **SI ticket review** (pending SI response) | SI | High |
---
## 12. Decisions Ready to Formalize
If the lead approves, these can become decisions immediately (no further discussion needed):
| Proposed ID | Decision | Source |
|-------------|----------|--------|
| D-042 | Drin promoted from Tier 3 to Tier 2 | Gestalt (unanimous), Paula (profile drafted) |
| D-043 | THE NOBODY mechanic deferred to v0.2; hidden pattern+motivation data ships in NPC content files for v0.1 | Gestalt, Dudley |
| D-044 | v0.1 interaction model: 7 interactions (Move, Look, Monologue, Examine Object, Examine NPC, Talk, Overhear) | Gestalt (designed), Stig (UI for each), Dudley (server events) |
| D-045 | v0.1 scope: add News ticker, PC-as-NPC, Time progression, Relationship state transitions to IN list | Gestalt (rationale per item) |
| D-046 | v0.1 scope: add Inventory, Stealth, Combat, Player-facing save/load, Lattice modification to explicit OUT list | Gestalt (rationale per item) |
| D-047 | v0.1 triangles: 3 active forks (T1, T2, T4), 2 passive tensions (T3, T5) | Gestalt |
| D-048 | Client receives all text from server via state updates; client does not load or evaluate content files | Stig, Dudley, Tyre (information boundary principle) |
---
## 13. Ticket Analysis (SI)
### Round 2 List Scorecard
**26 of 29 tickets survive the 300-world reframe.**
| Disposition | Count | Tickets |
|-------------|-------|---------|
| Survive unchanged | 11 | A1, A2, A7, A8, A10, A11, B2, B3, B4, B5, C1 |
| Survive reframed | 15 | A3 (merge into #319), A4, A6, A9, A12, B1, C2, C3, C4-C8, C9, C10, D2 |
| Deferred (v0.2+) | 2 | A5 (wiki index restructure), D1 (cultural_gate modifier) |
| Killed | 1 | D3 (secondary contraband variant FactIds — explicitly OUT) |
### 7 New Tickets Proposed
| ID | Title | Team | Priority | Key Dependencies |
|----|-------|------|----------|-----------------|
| NEW-1 | NPC pattern/motivation mapping for v0.1 | copy | high | None |
| NEW-2 | Drin tier promotion evaluation | copy | medium | NEW-1 |
| NEW-3 | Wiki → YAML content conversion (Sova NPCs) | copy | high | C1, C2, C3 |
| NEW-4 | Monologue content pool — minimum viable set | copy | high | #261, B4 |
| NEW-5 | v0.1 wow moment content checklist | copy | high | None |
| NEW-6 | PC-as-NPC content authoring (authored lines) | copy | high | B3, B5 |
| NEW-7 | Interaction model minimum spec | copy | medium | None (informed by workshop Topic 4) |
### Existing Ticket Updates
| ID | Title | Action |
|----|-------|--------|
| #368 | Knowledge vocabulary for v0.1 content | Close when wiki review accepted |
| #369 | Wiki Review Workshop Outputs (epic) | Repurpose as parent epic for v0.1 content scoping |
| #301 | Wiki taxonomy and structure | Assign to copy, downscope for v0.1 (Sova only) |
| #319 | Krenn System wiki entry | Merge with A3 (expanded: wiki page + seed.yaml reference) |
| **#261** | **Dual Lens Authoring Guide** | **CRITICAL BOTTLENECK — blocks 9 downstream tickets** |
| #310 | Character voice speech patterns | Merge with or block on B4 |
| #306 | News ticker / Meridian feed content | Update scope per D4 (40-50 headlines) |
| #326 | YAML content loader | Assign to server, blocked by C1+C2, Sprint 4 |
### Sprint 3 Copy Team (14 tickets proposed)
**P0 — Must start immediately:**
| Ticket | Title | Blocked By |
|--------|-------|------------|
| A2 | Hael → Naia Tamm rename | — |
| A1 | Apply canonical full names | — |
| A7 | Smuggler entity attributes | — |
| C1 | Content directory structure design | — |
| **#261** | **Dual Lens Authoring Guide** | **— (Critical path root)** |
**P1 — Start after P0s:**
| Ticket | Title | Blocked By |
|--------|-------|------------|
| A10 | Nils Davan stub | — |
| A11 | Triangle 1 fix | A10 |
| B2 | MIRROR pattern spec | — |
| B4 | Smuggler voice + moral arc | A7 |
| NEW-1 | NPC pattern/motivation mapping | — |
| NEW-5 | Wow moment content checklist | — |
**P2 — Fit in around P0/P1:**
| Ticket | Title | Blocked By |
|--------|-------|------------|
| A8 | Shortcode fix | — |
| B3 | PC-as-NPC spec | A7 |
| NEW-7 | Interaction model minimum spec | — |
### Sprint 3 Server Tickets (content-related)
| Ticket | Title | Blocked By |
|--------|-------|------------|
| C2 | Create content/ directory skeleton | C1 |
| C3 | Content schema definitions | C1 |
### Critical Path (SI's Analysis)
Two parallel chains must begin in Sprint 3:
**Chain 1 — Content authoring:**
```
#261 (Dual Lens Guide) → B4 (Smuggler voice) → A6 (FactId text) → content packs → monologue pool
```
**Chain 2 — Content architecture:**
```
C1 (Directory design) → C2/C3 (skeleton/schemas) → C4-C8/NEW-3 (YAML files) → #326 (loader)
```
**#261 is the single biggest blocker in the entire content pipeline.** It blocks 9 tickets directly and cascades into everything. SI recommends immediate assignment with Paula as owner.
### v0.1 IN List → Ticket Coverage
| IN List Item | Status | Gaps |
|-------------|--------|------|
| WASD movement + collision | Covered (Sprint 1-2 done) | — |
| Context-sensitive interaction | Partially covered | Needs NEW-7 spec |
| Monologue system | Architecture covered | Content gap (NEW-4) |
| Knowledge graph | Covered | — |
| 2 playable characters | Covered (architecture) | — |
| THE FRIEND arc | Covered but **blocked by #261** | — |
| 5 triangles with forks | Partially covered | Weak Triangle 1 (A11) |
| 6 wow moments | **Gap** | Needs NEW-5 tracking ticket |
| 3 social sites | Covered but blocked by #261 | — |
| NPC routines | Covered (server) | — |
| Dual-lens parity | **Major gap** | Smuggler lens incomplete (A7, B4, A6) |
| PC-as-NPC | **Gap** | No tickets exist (B3, B5, NEW-6) |
| Content directory | **Gap** | Structure undefined (C1, C2, C3) |
| Content validation | **Gap** | No validation exists (C9, C10) |
---
*Qatux, Round 1 tracking. For the record: all 7 responses cataloged, 17 consensus items, 5 disagreements requiring resolution, 7 additional wiki gaps identified, 10 open questions, 7 decisions ready to formalize. SI confirms 26 surviving tickets + 7 new proposals. #261 (Dual Lens Authoring Guide) is the critical bottleneck — blocks 9 downstream tickets across the entire content pipeline.*
docs/workshops/v01-content-scoping/round1-tyre.md
-672
View File
@@ -1,672 +0,0 @@
# Round 1 — Tyre (Technical Architect)
## v0.1 Content Scoping Workshop
*cracks knuckles*
Three topics assigned to me. Let me be honest about what each means technically.
---
## Topic 3: Content Directory Structure
### Format Decision: YAML
Not RON, not JSON, not TOML. YAML. Here's why:
| Criterion | YAML | RON | JSON |
|---|---|---|---|
| Content author readability | Excellent | Poor (Rust syntax) | Decent |
| Multi-line text (dialogue) | Native (`\|`, `>`) | Awkward | Escaped strings |
| serde support in Rust | `serde_yaml` (mature) | `ron` crate (mature) | `serde_json` (mature) |
| Schema validation tooling | JSON Schema (rich) | None standard | JSON Schema (native) |
| Generator output compatibility | Any language can emit YAML | Rust-only ergonomic | Any language |
| Hot-reload parse speed | Fast enough (~2ms for 100KB) | Faster (~0.5ms) | Fast (~1ms) |
RON would be natural if only Rust engineers touched content. But Mellanie and Paula author content, and asking them to write `NpcProfile(axes: Axes(want: "Protect the operation"))` instead of `want: "Protect the operation"` is a tax with no return. The 1.5ms parse speed difference is irrelevant — content loads once at startup and on hot-reload.
**Validation pipeline:** YAML files validate against JSON Schema definitions (one schema per content type). The server's `content_loader` also validates by attempting `serde_yaml::from_reader::<NpcProfile>()` — if it deserializes into the Rust struct, it's valid. Both checks run: schema catches structural issues early (missing required fields, wrong types), serde catches semantic issues (enum variant doesn't exist, value out of range).
### Proposed Directory Structure
```
content/
content.yaml # Manifest: lists all districts, content version
schema/ # JSON Schema definitions for validation
npc.schema.json
location.schema.json
fact.schema.json
district.schema.json
dialogue.schema.json
monologue.schema.json
routine.schema.json
triangle.schema.json
global/ # Shared across ALL districts (generator-safe)
facts/ # FactId definitions — the vocabulary
contraband.yaml # contraband.ring_exists, contraband.lattice_components, ...
location.yaml # location.corridor_b7_restricted, ...
investigation.yaml # investigation.manifest_discrepancy, ...
world.yaml # world.commission_regulations, ...
relationship.yaml # relationship.ring_membership, ...
progress.yaml # progress.initial_suspicion, ...
factions/
lattice-commission.yaml
syndics.yaml
the-ring.yaml # Ring is district-local but faction def is global
concord-assembly.yaml
guardians-of-autonomy.yaml
entity-schema/ # EntityKnowledge attribute definitions
attributes.yaml # The 14 canonical keys from entity-attributes.md
enums/ # Tag enum definitions (D-035)
situations.yaml # 13 situation enums
topics.yaml # 9 topic enums
moods.yaml # 8 mood enums
access-tiers.yaml # public, insider, authority, peer, hostile
trust-tiers.yaml # surface, real, secret
triggers.yaml # 9 monologue trigger types
districts/
sova-transit/ # v0.1: hand-authored district
district.yaml # District metadata, social site refs, NPC roster
npcs/ # One file per NPC
kael-davan.yaml # Tier 1 FRIEND — full 10-axis + tells + contradiction
sera-venn.yaml # Tier 1 FRIEND — full 10-axis + tells + contradiction
voss.yaml # Tier 2
lera-sessik.yaml # Tier 2
torek-lintar.yaml # Tier 2
devra.yaml # Tier 2
maret-korr.yaml # Tier 2
resha.yaml # Tier 2
harek.yaml # Tier 2
naia-tamm.yaml # Tier 1 MIRROR (renamed from Hael)
renn.yaml # Tier 2
pell.yaml # Tier 2
drin.yaml # Tier 2 or 3 (pending promotion decision)
sess.yaml # Tier 3
olin.yaml # Tier 3
sabel.yaml # Tier 3
tav.yaml # Tier 3
locations/
the-terminal.yaml # Social site: logistics hub
the-last-shift.yaml # Social site: bar / "Lera's"
maintenance-corridors.yaml # Social site: smuggling spaces
triangles/
hub-power.yaml # Triangle 1: Voss/Nils power struggle
ring-trust.yaml # Triangle 2: internal ring loyalty
bar-tension.yaml # Triangle 3: bar social dynamics
investigation-pressure.yaml # Triangle 4: detective pressure
leverage-web.yaml # Triangle 5: Harek/Drin/compromise
dialogue/ # Grouped by location, then by role
the-terminal/
dock-worker.yaml # Role-based, not NPC-named
shift-supervisor.yaml
scheduler.yaml
new-hire.yaml
the-last-shift/
bartender.yaml
bar-regular.yaml
bar-owner.yaml
maintenance-corridors/
courier.yaml
ring-operative.yaml
monologue/ # Hard partition per character (D-032)
smuggler/
the-terminal.yaml
the-last-shift.yaml
maintenance-corridors.yaml
general.yaml # time_idle, non-location triggers
detective/
the-terminal.yaml
the-last-shift.yaml
maintenance-corridors.yaml
general.yaml
routines/
schedules.yaml # All NPC schedules: time → location → activity
```
### Key Design Choices
**1. `global/` vs `districts/` split.**
Everything in `global/` is district-independent. FactId vocabulary, faction definitions, attribute schemas, tag enums — these are the *language* the content speaks. Districts are *instances* of content written in that language. When generators produce District #247, they use the same `global/` vocabulary.
**2. Dialogue by location + role, NOT by NPC.**
Per D-035: `role` is a template-defined role, NPC assignment is runtime. The file `dialogue/the-terminal/dock-worker.yaml` contains all dialogue lines for the dock-worker role at the Terminal. At runtime, Kael (or any other dock worker) draws from this pool based on access/trust/situation filtering. This is generator-compatible — a generated district creates its own role pools.
**3. Monologue files are per-character per-location.**
D-032 mandates hard partition. The directory structure enforces it physically. No risk of accidentally sharing lines between characters.
**4. Facts in `global/`, not per-district.**
The FactId vocabulary (`contraband.ring_exists`) is global — it's the *language of knowledge*. The specific confidence progression text in the fact catalog is also global (it describes what each confidence level means for that fact). What varies per district is which facts are *relevant* and which NPCs *know* them — that's in the NPC profiles and the knowledge graph at runtime, not in the fact definitions.
Exception: if future districts introduce district-specific facts (e.g., `mining.union_dispute` on a mining world), those can live in `districts/{district}/facts/` as extensions. The loader merges global + local.
**5. One NPC per file.**
Each NPC profile is self-contained. This means:
- Content authors can work on different NPCs in parallel without merge conflicts
- Generators output one file per generated NPC
- Validation runs per-file (fast feedback)
- Git blame is clean (who wrote what, when)
### Content Addressing
**`canonical_id`** is a required field inside every content YAML file. It uniquely identifies the entity across the entire game. Format: `{type}:{slug}`.
```yaml
# content/districts/sova-transit/npcs/kael-davan.yaml
canonical_id: "npc:kael-davan"
```
```yaml
# content/global/facts/contraband.yaml
facts:
- fact_id: "contraband.ring_exists" # FactId string IS the canonical_id
```
```yaml
# content/districts/sova-transit/locations/the-terminal.yaml
canonical_id: "loc:sova-transit:the-terminal"
```
```yaml
# content/districts/sova-transit/triangles/hub-power.yaml
canonical_id: "tri:sova-transit:hub-power"
```
**Why `canonical_id` is in the file, not derived from the path:**
- Files can be reorganized without breaking references
- Generators can place files anywhere and assign IDs programmatically
- Cross-file references use the `canonical_id` string, not file paths
- Duplicate ID detection is a validation rule (build fails if two files claim the same canonical_id)
**Runtime mapping:** At content load, the server builds a `ContentRegistry`:
```rust
struct ContentRegistry {
// canonical_id string → StableId (assigned deterministically via hash or sequential)
id_map: BTreeMap<String, StableId>,
// Reverse lookup
reverse_map: BTreeMap<StableId, String>,
}
```
The `StableId(u64)` assigned at load time is deterministic — same content files always produce same IDs (sorted canonical_ids, sequential assignment). This satisfies D-010 principle 4 (deterministic simulation).
### Wiki → Content File Mapping
The wiki is the **authoring reference** (narrative intent, character depth, prose descriptions). Content files are the **engine data** (structured values, tagged lines, schedule timings). The transformation is:
| Wiki Source | Content Target | Transformation |
|---|---|---|
| `wiki/npcs/kael-davan.md` | `districts/sova-transit/npcs/kael-davan.yaml` | 10-axis prose → structured YAML fields. Routine prose → time/location pairs. Tells prose → tell tag list. |
| `wiki/locations/krenn-system/the-terminal.md` | `districts/sova-transit/locations/the-terminal.yaml` | Prose description → spatial properties (bounds, sightlines, Meridian coverage, access requirements). |
| `wiki/knowledge/fact-catalog.md` | `global/facts/*.yaml` | Per-FactId entries, split by category file. Confidence progression text included as authoring reference. |
| `wiki/knowledge/entity-attributes.md` | `global/entity-schema/attributes.yaml` | Attribute key definitions + valid values + usage notes. |
| `wiki/factions/*.md` | `global/factions/*.yaml` | Faction identity → mechanical properties (access tier modifiers, trust defaults). |
| `wiki/authoring/monologue-guide.md` | `global/enums/*.yaml` + schema definitions | Tag taxonomy → enum value lists + schema. |
| `wiki/npcs/index.md` (triangles) | `districts/sova-transit/triangles/*.yaml` | Triangle descriptions → structured NPC references + fork definitions. |
**The wiki doesn't go away.** Wiki remains the human reference for "why is Kael this way?" The content file says `want: "Protect the operation and the people in it"` — the wiki explains what that means narratively, what the secondary want is, how it evolved. Writers read wiki, engine reads content files.
### NPC Profile File Example
```yaml
# content/districts/sova-transit/npcs/kael-davan.yaml
canonical_id: "npc:kael-davan"
display_name: "Kael Davan"
tier: 1
pattern: "FRIEND" # System A (thematic)
motivation: "OPERATOR" # System B (functional) — pending Gestalt's mapping
district: "sova-transit"
# D-024: 10-axis model
axes:
want: "Protect the operation and the people in it"
secret:
surface: "Ring member, handles physical cargo"
deep: "Trying to exit the ring via unauthorized contact"
relationships:
- target: "npc:nils-davan"
kind: "sibling"
trust: 0.85
- target: "npc:naia-tamm" # Renamed from Hael
kind: "partner"
trust: 0.95
- target: "npc:smuggler-pc" # PC-as-NPC reference
kind: "close_colleague"
trust: 0.90
tolerance:
current_stress: 0.55
threshold: 0.75
routine:
description: "Morning shift 06:00-14:00, bar after shift, home evenings"
information:
known_facts:
- "contraband.ring_exists:KnowsDetails"
- "contraband.lattice_components:KnowsDetails"
- "contraband.supply_chain:KnowsOf"
- "location.corridor_b7_restricted:KnowsDetails"
- "location.smuggling_route:KnowsDetails"
- "world.shift_schedule:KnowsDetails"
contentment: 0.45
# D-024: 3 supporting axes
personality:
traits: ["loyal", "careful", "conflict-avoidant"]
tells:
- trigger: "lying"
behavior: "looks left"
- trigger: "stressed"
behavior: "lattice checking"
- trigger: "discussing_exit"
behavior: "forced casualness"
skills:
set: ["logistics", "cargo_handling", "dock_operations"]
combat_trained: false
# Entity attribute defaults (what a NEW observer would learn)
initial_attributes:
role: "dock worker"
faction: "civilian" # True faction hidden until discovered
species: "human"
routine_pattern: "morning shift at logistics hub, bar after shift"
# THE FRIEND arc data (Tier 1 only)
friend_arc:
character: "smuggler" # This NPC is FRIEND to the smuggler
phases:
- name: "warmth"
triggers: [] # Default state
- name: "trust"
triggers:
- fact: "relationship.trust_network"
min_confidence: "KnowsOf"
- name: "doubt"
triggers:
- observation: "kael_in_corridor_b7" # Spatial staging trigger
- name: "conflict"
triggers:
- attribute_set: "contradiction_flagged"
contradiction:
type: "spatial" # Seen in wrong place
location: "loc:sova-transit:maintenance-corridors"
expected_location: "loc:sova-transit:the-terminal"
time_window: "shift_transition"
```
### Dialogue File Example
```yaml
# content/districts/sova-transit/dialogue/the-terminal/dock-worker.yaml
role: "dock_worker"
location: "loc:sova-transit:the-terminal"
lines:
- id: "terminal_d_001"
text: "Manifest says 240 kilos but that container's sitting heavy. Could be packing material. Could be anything."
access: [insider, peer]
trust: surface
situation: [routine, shift_start]
topic: [cargo]
mood: [comfortable]
- id: "terminal_d_002"
text: "Voss moved the schedule again. Third time this rotation. Says it's efficiency."
access: [public]
trust: surface
situation: [routine, shift_end]
topic: [routine, colleague]
mood: [comfortable]
- id: "terminal_d_003"
text: "You want to know about the night shift? Nobody wants the night shift. That's your answer."
access: [authority]
trust: surface
situation: [investigation]
topic: [routine, investigation]
mood: [suspicious]
- id: "terminal_d_015"
text: "Nils has been... look, I can't talk about family here. Not with the scanners running."
access: [insider, peer]
trust: real
situation: [social, alone]
topic: [trust, personal]
mood: [worried, conflicted]
tags: ["nils_reference", "ring_internal"]
```
### Monologue File Example
```yaml
# content/districts/sova-transit/monologue/smuggler/the-terminal.yaml
character: smuggler
location: "loc:sova-transit:the-terminal"
lines:
- id: "terminal_m_s_001"
text: "Same dock, same hum, same shift. Kael's already at his station. Reliable as the gate cycle."
trigger: enter_location
prerequisite: null
topic: [routine, colleague]
mood: [comfortable]
tags: ["opening", "kael_reference"]
- id: "terminal_m_s_007"
text: "That container's been in temp storage fourteen hours. Standard turnaround is six. Someone's buying time."
trigger: observe_anomaly
prerequisite:
facts:
contraband.supply_chain: KnowsOf
topic: [cargo]
mood: [analytical]
tags: ["investigation_seed"]
- id: "terminal_m_s_012"
text: "Kael? In Corridor B-7? During shift transition? He has no reason to be there. None that I know of."
trigger: observe_npc
prerequisite:
entity:
target: "npc:kael-davan"
attribute: "routine_pattern"
condition: "deviation"
facts:
location.corridor_b7_restricted: KnowsOf
topic: [colleague, danger]
mood: [suspicious, conflicted]
tags: ["friend_contradiction", "wow_moment_3"]
dual_lens:
detective: "The dock worker — Davan — in a restricted corridor during transition. That's not routine maintenance."
notes: "THE FRIEND contradiction moment. Urgent chime. This is wow moment #3."
```
### Content Load Sequence (Server-Side)
```
PHASE 1: VOCABULARY LOAD (global/)
├── Load global/enums/*.yaml → build tag enum registries
├── Load global/facts/*.yaml → build FactId registry
├── Load global/factions/*.yaml → build faction definitions
├── Load global/entity-schema/attributes.yaml → build attribute key registry
└── Validate: all enum values, fact IDs, attribute keys are unique
PHASE 2: DISTRICT LOAD (districts/{id}/)
├── Load district.yaml → district metadata, NPC roster, location list
├── Load npcs/*.yaml → NPC profiles
│ ├── Validate canonical_ids unique
│ ├── Validate relationship targets exist
│ ├── Validate known_facts reference valid FactIds
│ └── Build canonical_id → StableId mapping (ContentRegistry)
├── Load locations/*.yaml → location spatial definitions
├── Load triangles/*.yaml → triangle NPC references + fork definitions
│ └── Validate all NPC refs exist in ContentRegistry
├── Load dialogue/**/*.yaml → line pool registry
│ └── Validate all tag values against enum registries
├── Load monologue/**/*.yaml → per-character line pool registry
│ └── Validate prerequisites reference valid FactIds + entity attributes
└── Load routines/schedules.yaml → NPC schedule data
PHASE 3: ENTITY SPAWN
├── For each NPC in roster:
│ ├── Spawn bevy_ecs Entity
│ ├── Insert Npc marker component
│ ├── Insert axis components (Want, Secret, Relationships, etc.)
│ ├── Insert KnowledgeGraph component (pre-populated from information.known_facts)
│ ├── Insert DailyRoutine component (from routine data)
│ ├── Register StableId ↔ Entity in EntityRegistry
│ └── If Tier 1 FRIEND: insert FriendArc component with phase data
├── For each location:
│ ├── Spawn location entity with spatial properties
│ └── Register in ContentRegistry
└── Build dialogue/monologue indices for fast runtime lookup
PHASE 4: READY
└── Content loaded, entities spawned, registries built → simulation can start
```
**Hot-reload path:** File watcher detects YAML change → re-parse affected file → validate → if NPC: update axis components in-place (no respawn needed for value changes). If dialogue/monologue: rebuild affected line pool index. If structural change (new NPC, removed NPC): log warning, require restart. Hot-reload is a development convenience, not a production feature.
---
## Topic 5: Technical Risk in the IN List
I'll tier these. Tier 1 = low risk. Tier 2 = medium, manageable. Tier 3 = hard, needs careful scoping. Tier 4 = this is where the schedule dies if we're not careful.
### Tier 1 — Low Risk (will work, standard engineering)
**WASD movement + collision.** Already have `movement.rs` with `TilePosition`. Collision is tile-based occupancy checking. 8-directional movement is in `PlayerAction` already. Z-level transitions are the only wrinkle — handle as tile properties (stairs, elevators). Estimate: done or nearly done.
**3 social sites (Terminal, Last Shift, Maintenance Corridors).** These are map content, not systems work. Server needs location entities with spatial bounds and properties (Meridian coverage, access restrictions). Client needs tile rendering. The hard part is art — which is explicitly "functional boxes with labels" for v0.1 (D-014). Estimate: location data loading is part of content loader; rendering is standard tile mapping.
**NPC routines (schedule-based movement).** Time system exists (D-031, `time.rs`). Day phases exist. Schedule format is defined. NPCs move to specified locations at phase boundaries. This is a state machine: `current_phase → lookup schedule → pathfind to target location → move`. Estimate: 2-3 dev-days for the schedule system. Content authoring for 17 NPC schedules is the longer pole.
### Tier 2 — Medium Risk (technically straightforward but integration-heavy)
**Knowledge graph.** D-041 is well-defined. Types exist in `types.rs`. Sprint 2 delivers core data structures + direct observation flow + basic decay. The risk isn't the knowledge graph itself — it's that **everything depends on it**. Monologue prerequisites query it. Dialogue filtering queries it. The FRIEND arc's contradiction detection queries it. Entity rendering uses `RelationshipState` from it. If knowledge graph delivery slips, everything downstream slips.
*Mitigation:* Knowledge graph Sprint 2 scope is intentionally narrow (direct observation + decay only). Sprint 3 adds the complex stuff. But Sprint 3 is also when monologue, dialogue, and FRIEND arc need to work. The dependency chain is tight.
**2 playable characters seeing same world differently.** Architecturally, this is already designed for (D-010 principle 3). The `ObserverSnapshot` is per-entity — two players get different snapshots. Knowledge graphs are per-entity — two PCs have different knowledge. The risk is **content volume and consistency**. Every piece of monologue content is written twice (one per character). Every NPC needs a smuggler-lens AND detective-lens. Every triangle fork needs to make sense from both perspectives.
*Mitigation:* The dual-lens requirement is a content team problem more than a server/client problem. But it doubles the content validation surface area — a monologue line that references a fact the detective can't learn is a content bug, not a code bug. Content validation tooling (Topic 3's schema validation) is the mitigation.
**Context-sensitive interaction (approach NPC → prompt → dialogue).** Server: proximity trigger → interaction state → dialogue pool query. Client: prompt rendering → dialogue display. The plumbing is standard. The risk is the **dialogue selection algorithm**. D-035 defines 6 structural tags + 3 selection tags. Filtering by access + trust + situation is a hard filter (combinatorial but finite). Selecting by topic + mood is a weighted selection (needs tuning). The algorithm itself is maybe 200 lines of Rust. The tuning to make it *feel good* is the unknown.
*Mitigation:* Build the line previewer CLI (already on my priority list) early. Let Mellanie and Paula test dialogue selection before it's in-game. Iterate on weights outside the game loop.
### Tier 3 — High Risk (technically complex, integration-dependent)
**Monologue system (tagged triggers, FactId prerequisites).** This is the feature that makes or breaks the vertical slice. Nine trigger types, each requiring different detection logic:
| Trigger | Detection Complexity | Server System Required |
|---|---|---|
| `enter_location` | Low | Location transition event |
| `observe_npc` | Medium | LOS + entity identification |
| `hear_sound` | Medium | Sound range model (D-018) |
| `observe_anomaly` | **High** | Routine deviation detection |
| `post_conversation` | Low | Dialogue end event |
| `discover_evidence` | Medium | Knowledge graph state change |
| `witness_interaction` | **High** | Two-entity observation in LOS |
| `time_idle` | Low | Timer on no-input |
| `return_visit` | Medium | Location visit history |
`observe_anomaly` and `witness_interaction` are the dangerous ones. `observe_anomaly` means "NPC is doing something outside their routine" — the server needs to know what "normal" looks like to detect "abnormal." This requires the routine system to track expected vs. actual behavior, which is a step beyond simple schedule execution.
`witness_interaction` means "I see NPC A talking to NPC B" — requires tracking NPC-to-NPC interactions AND checking whether those interactions are in the observer's LOS. This is a second-order perception query.
**Prerequisite evaluation** is the other risk. A prerequisite like:
```yaml
prerequisite:
entity:
target: "npc:kael-davan"
attribute: "routine_pattern"
condition: "deviation"
facts:
location.corridor_b7_restricted: KnowsOf
```
...is a small query language. The server needs to evaluate arbitrary combinations of entity attribute checks + fact confidence checks + potentially boolean logic (AND/OR). Keep this dead simple for v0.1 — AND-only, no nesting, explicit conditions. The temptation to build a general-purpose query engine is scope death.
*Estimate:* 8-12 dev-days for the full monologue pipeline (trigger detection + prerequisite evaluation + pool selection + pacing). The "pacing" part (how often monologue fires, cooldown between lines, priority when multiple lines qualify) is pure playtesting — budget 2-3 days of tuning time.
**THE FRIEND arc (Kael for smuggler, Sera for detective).** This is the integration test for EVERYTHING:
- Knowledge graph contradiction detection (Sprint 3)
- Monologue trigger system (all 9 types exercise)
- Tell system (behavioral observation accumulation over time)
- Multi-phase dialogue shifts (D-028 all 4 layers)
- Spatial staging (NPC in specific place at specific time)
- Relationship state transitions (Friendly → PersonOfInterest)
The risk isn't any individual system — it's the intersection. THE FRIEND arc requires all systems to work together correctly. A bug in knowledge decay timing means the contradiction window passes unnoticed. A bug in spatial staging means Kael is never in Corridor B-7 when the player is nearby. A bug in tell accumulation means the player has no behavioral evidence before the contradiction.
*Mitigation:* THE FRIEND arc needs its own integration test — a scripted scenario that walks through the full 5-phase arc and validates each system fires correctly. This is D-030's CauseChain paying off: every knowledge event, every monologue trigger, every relationship state change gets provenance tracking, and the integration test can verify the causal chain matches expectations.
*Estimate:* Server systems: 5-8 dev-days (contradiction detection + spatial staging + tell accumulation + FRIEND phase transitions). Content: probably the largest single content deliverable in v0.1 (70-100 lines per FRIEND, times 2 FRIENDs, all hand-authored). Client: relationship color shifts (D-033), dialogue phase UI cues.
### Tier 4 — Schedule Killers (needs aggressive scoping or it takes over)
**5 triangles with at least 1 fork each.** Each fork is a branching decision point. Each branch has consequences that ripple through NPCs, knowledge, and potentially other triangles.
The math: 5 triangles × 1 fork × 2 branches × N consequences per branch. If consequences cascade across triangles, N grows fast. If Triangle 1's fork outcome changes NPC attitudes in Triangle 3, then Triangle 3's fork depends on Triangle 1's resolution, and you have dependency chains.
*Scope control:* For v0.1, forks should be **terminal decisions** — they affect the triangle's own NPCs and change the player's knowledge, but they don't cascade into other triangles. Cross-triangle contamination is a v0.2 feature. This keeps each fork to 2-3 consequence entities, not 10-15.
*Estimate:* If forks are self-contained: 2-3 dev-days for the fork/consequence system + 3-5 dev-days for content authoring 5 fork scenarios. If forks cascade: 8-12 dev-days for cascade resolution + testing. **Strongly recommend self-contained forks for v0.1.**
**6 wow moments.** These aren't independent features — they're integration milestones. Each one is a "everything up to here works" gate:
| Wow Moment | Systems Required | Risk |
|---|---|---|
| #1 Arrival | Ambiance + routines + opening monologue | Low |
| #2 Character's Eye | Monologue trigger + routine deviation detection | **Medium-High** |
| #3 FRIEND Contradiction | Full FRIEND arc + spatial staging + contradiction detection | **High** |
| #4 Divergence Reveal | Dual-lens content + relationship colors + monologue partitioning | Medium |
| #5 News Ticker | Ticker system + dual monologue reactions | **Medium** (ticker is new UI element) |
| #6 Quiet Moment | time_idle trigger + reflective monologue | Low |
The dependency chain: #1 is achievable early. #6 is achievable early. #2 requires monologue system. #5 requires ticker + monologue. #4 requires knowledge graph + rendering. #3 requires everything.
**#3 is the critical path.** If THE FRIEND contradiction doesn't work, the demo's emotional peak is missing. Everything should be prioritized to unblock #3.
### Summary Risk Matrix
| Feature | Risk Level | Primary Risk Factor | Mitigation |
|---|---|---|---|
| WASD + collision | Low | None significant | Already built |
| 3 social sites | Low | Art (not scope concern at v0.1) | Functional boxes |
| NPC routines | Low-Medium | Content authoring time | Start schedules early |
| Knowledge graph | Medium | Downstream dependency chain | Sprint 2 narrow scope holds |
| 2 playable characters | Medium | Content volume doubling | Content validation tooling |
| Context-sensitive interaction | Medium | Dialogue selection tuning | Line previewer CLI |
| Monologue system | **High** | Trigger detection + prerequisite evaluation | Simple AND-only prerequisites, defer complex triggers |
| THE FRIEND arc | **High** | Integration of all systems | Dedicated integration test, prioritize for critical path |
| 5 triangle forks | **Medium-High** | Cascade complexity | Self-contained forks, no cross-triangle effects in v0.1 |
| 6 wow moments | Varies | #3 is the critical path | Prioritize everything that unblocks #3 |
**What will take longer than expected:**
1. **Monologue prerequisite tuning.** The gap between "prerequisites work" and "prerequisites feel right" is large. Content authors will write prerequisites that are too strict (nothing fires) or too loose (everything fires). Budget iteration time.
2. **Dialogue selection weighting.** Same tuning problem. Getting NPCs to say contextually appropriate things from a tagged pool requires weight iteration.
3. **Spatial staging for THE FRIEND.** Getting Kael into Corridor B-7 *when the player is nearby* without feeling scripted is a storyteller-level challenge compressed into one specific moment.
4. **Content conversion.** Transforming 17 NPC wiki profiles + 24 fact entries + 3 location descriptions + 5 triangles from prose markdown into structured YAML is manual labor. Each NPC file needs ~30 minutes of careful conversion. Budget 2-3 full days for the initial wiki → content conversion pass.
---
## Topic 6: Cross-Team Ticket Splits
The content pipeline creates work that spans all three teams (server, client, copy). Here's my proposed split for the major ticket categories. Each "ticket" below is a logical unit that should be one or two actual tickets.
### Content Infrastructure (Sprint 3)
| Ticket | Server | Client | Copy |
|---|---|---|---|
| Content directory structure | Create `content/` tree, `content.yaml` manifest | — | Populate initial files |
| Content loader (Phase 1-2) | `ContentRegistry`, YAML deserialization, entity spawn from content | — | — |
| Content loader (Phase 3-4) | Line pool indexing, hot-reload watcher | — | — |
| Content validation schemas | serde validation on load | — | JSON Schema files for YAML |
| Line previewer CLI | Build CLI: YAML → filtered line output | — | Test with real content |
### Wiki → Content Conversion (Sprint 3)
| Ticket | Server | Client | Copy |
|---|---|---|---|
| NPC profile conversion (17 NPCs) | Define `NpcProfile` serde struct | — | Convert wiki MD → YAML (17 files) |
| Location conversion (3 sites) | Define `LocationDef` serde struct | — | Convert wiki MD → YAML (3 files) |
| Fact catalog conversion | Already defined (`FactId`, `FactKnowledge`) | — | Split fact-catalog.md → 6 YAML files |
| Triangle definitions | Define `TriangleDef` serde struct | — | Write 5 triangle YAML files |
| Routine/schedule conversion | Define `ScheduleEntry` serde struct | — | Write schedules.yaml for 17 NPCs |
### Monologue System (Sprint 3)
| Ticket | Server | Client | Copy |
|---|---|---|---|
| Monologue trigger detection | 9 trigger type implementations | — | — |
| Monologue prerequisite evaluation | Knowledge graph query engine (simple AND-only) | — | — |
| Monologue line pool selection | Tag filtering + weighted selection | — | — |
| Monologue pacing/cooldown | Rate limiter, priority queue, cooldown timers | — | — |
| Monologue content authoring | — | — | Write monologue lines (2 chars × 3 locs + general) |
| Monologue display UI | — | Text panel, chime trigger, fade/scroll | — |
| Monologue chime audio | — | Audio event handler for monologue chime SFX | — |
### Dialogue System (Sprint 3)
| Ticket | Server | Client | Copy |
|---|---|---|---|
| Dialogue pool loader | YAML → indexed line pool, tag filtering | — | — |
| Dialogue selection algorithm | Access/trust hard filter + topic/mood weighted select | — | — |
| Dialogue content authoring | — | — | Write role-based dialogue (10+ roles × location) |
| Dialogue UI | — | Dialogue box, NPC name display, line rendering | — |
### Interaction Model (Sprint 3)
| Ticket | Server | Client | Copy |
|---|---|---|---|
| Proximity detection | Distance threshold check per tick | — | — |
| Interaction state machine | Idle → Prompt → InDialogue → Exit | — | — |
| Interaction prompt UI | — | "Press E to talk" / context-sensitive label | — |
### THE FRIEND Arc (Sprint 3-4, cross-team)
| Ticket | Server | Client | Copy |
|---|---|---|---|
| FRIEND phase transition system | Phase state machine, trigger evaluation | — | — |
| Contradiction detection | `Contradicted` KnowledgeState, spatial observation vs. expected location | — | — |
| Tell system accumulation | Behavior flag aggregation, tell detection events | — | — |
| FRIEND content (Kael) | — | — | 70-100 lines: dialogue + monologue + tells + contradiction |
| FRIEND content (Sera) | — | — | 70-100 lines: dialogue + monologue + tells + contradiction |
| Relationship color rendering | — | Entity color shifts per D-033 RelationshipState | — |
| FRIEND integration test | Test scenario: full 5-phase arc validation | — | Test content fixtures |
### NPC Rendering + Routines (Sprint 3)
| Ticket | Server | Client | Copy |
|---|---|---|---|
| NPC schedule execution | DayPhase → location lookup → pathfind → move | — | — |
| NPC routine deviation events | Expected vs. actual location tracking | — | — |
| NPC sprite/label rendering | — | Entity kind → sprite, name display from snapshot | — |
| NPC movement animation | — | Interpolated movement between tiles | — |
### Cross-Cutting
| Ticket | Server | Client | Copy |
|---|---|---|---|
| PC-as-NPC (other character exists) | NPC entity with PC profile data | NPC rendering (same as any NPC) | ~20-30 authored items |
| News ticker system | Ticker event generation | Ticker UI widget | Ticker text + dual monologue reactions |
| Smuggler lens parity | — | — | Smuggler attribute vocabulary + lens sections for all 17 NPCs |
| Hael → Naia Tamm rename | Update any hardcoded refs | — | Execute rename across all wiki + content files |
### Dependency Chain
```
Content directory structure
└── Content loader (Phase 1-2)
├── NPC profile conversion ──→ NPC schedule execution
├── Location conversion
├── Fact catalog conversion
└── Content loader (Phase 3-4)
├── Dialogue pool loader ──→ Dialogue selection ──→ Dialogue UI
├── Monologue trigger detection
│ └── Monologue prerequisite evaluation
│ └── Monologue line pool selection
│ └── Monologue pacing ──→ Monologue display UI
└── Triangle definitions ──→ Triangle fork system
Proximity detection ──→ Interaction state machine ──→ Interaction prompt UI ──→ Dialogue UI
Knowledge graph (Sprint 2) ──→ Contradiction detection ──→ FRIEND phase transitions
──→ Monologue prerequisite evaluation
──→ Tell system accumulation
FRIEND content (copy) ──→ FRIEND integration test
Monologue content (copy) ──→ Monologue pacing tuning
Dialogue content (copy) ──→ Dialogue selection tuning
```
**Critical path to wow moment #3 (THE FRIEND contradiction):**
Knowledge graph → Contradiction detection → FRIEND phase transitions → Spatial staging (routine deviation) → Monologue trigger (observe_npc with deviation condition) → Monologue display → FRIEND content authored and loaded.
Every block on this chain is either server or copy team work. Client only needs monologue display and relationship color rendering to support #3. **Server and copy are the bottleneck for the emotional peak of the demo.**
---
## Summary
1. **Format: YAML.** Content authors write it, serde reads it, generators produce it later.
2. **Structure: `global/` + `districts/`.** Vocabulary is global, instances are per-district. Generator-compatible from day one.
3. **Addressing: `canonical_id` in every file.** Maps to `StableId` at runtime via `ContentRegistry`. Deterministic assignment.
4. **Critical path: THE FRIEND arc.** Every technical risk converges on wow moment #3. Server-side systems (monologue triggers, prerequisite evaluation, contradiction detection, spatial staging) and copy-side content (FRIEND profiles, dialogue, monologue) are the two parallel tracks that must converge.
5. **Biggest schedule risk: content conversion + monologue tuning.** The system can be built, but making it *feel right* requires authored content and iteration time. Start the wiki → YAML conversion early so server engineers have real data to test against.
docs/workshops/v01-content-scoping/round2-dudley.md
-787
View File
@@ -1,787 +0,0 @@
# Round 2 — Dudley (Server Developer)
## 1. YAML Acceptance — Loader Adaptation
Accepted. YAML is the content format for v0.1. The lead has spoken and Tyre's rationale is sound — content authors (Mellanie, Paula) need to write and read these files, and `serde_yaml` is mature enough for our needs.
### What Changes in the Loader
Almost nothing structurally. The `serde` derive macros work identically across formats — the Rust structs stay the same, only the deserializer call changes:
```rust
// Round 1 (RON):
// let profile: NpcProfile = ron::from_str(&content)?;
// Round 2 (YAML):
let profile: NpcProfile = serde_yaml::from_str(&content)?;
```
The 6-phase load sequence from Round 1 is format-agnostic. All phase ordering, validation rules, and resource creation remain identical. Specific adaptations:
| Item | Round 1 (RON) | Round 2 (YAML) | Impact |
|------|---------------|----------------|--------|
| Manifest | `content/manifest.ron` | `content/content.yaml` | Filename only |
| NPC profiles | `.ron` files | `.yaml` files | Extension only |
| Dialogue/monologue | `.ron` files | `.yaml` files | Extension only |
| Multi-line text | Rust string escaping | YAML native `\|` / `>` blocks | Better for authors — no escaping |
| Validation | Serde-only | Serde + JSON Schema (Tyre's dual validation) | Strictly more validation |
| Dependency | `ron` crate | `serde_yaml` crate | Swap one dependency |
The one genuine improvement: YAML's native multi-line text support (`|` for literal blocks) means dialogue and monologue text will be cleaner in the content files. No escaped newlines, no awkward string concatenation. Content authors benefit directly.
### Cargo.toml Change
```toml
# Add:
serde_yaml = "0.9"
# The ron crate stays for potential future use (RON converter per lead's decision)
```
### RON Converter
Per the lead's decision, we build a RON converter. My recommendation:
- **Location:** `tooling/content-converter/` — a small Rust binary, not part of the server
- **Direction:** YAML → RON only (content files are authored in YAML; if we ever want RON for hot-path loading, the converter produces it)
- **When it runs:** Build-time, optional. Not load-time — the server loads YAML directly. The converter is insurance for a hypothetical future where YAML parse speed matters (it won't for v0.1)
- **Priority:** Low. Build it when someone asks for it, not proactively
---
## 2. Multi-Action Interaction Model
### The Architecture: N Actions, 1 Client Selection
The server computes ALL available actions for each nearby entity. The `InteractionOptions` struct from Round 1 already supports this. The v0.1 client selects the top-ranked action to display. The v0.2 client shows the full list.
```rust
/// Available interactions for a nearby entity.
/// Server computes all; client displays based on version.
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct EntityInteractions {
/// StableId of the target entity
pub entity_id: u64,
/// Display name (knowledge-filtered — "Dock Worker" or "Kael Davan")
pub display_name: String,
/// All available actions, ordered by priority (highest first).
/// v0.1 client shows actions[0] only.
/// v0.2+ client shows all (radial menu, list, etc.)
pub actions: Vec<AvailableAction>,
}
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct AvailableAction {
/// Action identifier used in PlayerAction::InteractWith
pub action_id: String,
/// What the action is
pub kind: ActionKind,
/// Display label for the client ("Talk", "Examine", "Ask about the schedule")
pub label: String,
/// Priority for v0.1 single-action selection (higher = shown first)
pub priority: u8,
/// Can this action be performed right now?
pub enabled: bool,
/// Why not? (shown as tooltip in v0.2+, ignored in v0.1)
pub disabled_reason: Option<String>,
}
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash, Serialize, Deserialize)]
pub enum ActionKind {
/// Study the entity without initiating contact.
/// Updates knowledge graph with behavioral observations.
Examine,
/// Initiate dialogue. Opens conversation state.
Talk,
/// Look at an environmental object. Returns description + knowledge grants.
ExamineObject,
/// Listen to a nearby NPC-NPC conversation. Passive — no social cost.
Overhear,
}
```
### Priority Ranking System
The server determines action priority per context. This is where the "single context-sensitive action" behavior lives:
```rust
/// Determine default action priority for a given entity and context.
/// Returns actions sorted by priority (highest first).
fn rank_actions(
target_kind: EntityKind,
observer_knowledge: &KnowledgeGraph,
target_stable_id: &StableId,
target_in_conversation: bool,
target_activity: &str,
) -> Vec<AvailableAction> {
let mut actions = Vec::new();
match target_kind {
EntityKind::Npc => {
// Examine is always available for NPCs in LOS
let examine_priority = if observer_knowledge
.entity_knowledge(target_stable_id)
.map(|ek| ek.known_attributes.contains_key("contradiction_flagged"))
.unwrap_or(false)
{
// Post-contradiction: Examine becomes high priority
// "Watch them more carefully"
90
} else {
// Default: Examine is secondary to Talk
40
};
actions.push(AvailableAction {
action_id: format!("examine_{}", target_stable_id.0),
kind: ActionKind::Examine,
label: "Observe".to_string(),
priority: examine_priority,
enabled: true,
disabled_reason: None,
});
// Talk: available if NPC is not sleeping, not in combat, not already
// in conversation with someone else
let talk_enabled = !target_in_conversation
&& target_activity != "sleeping";
actions.push(AvailableAction {
action_id: format!("talk_{}", target_stable_id.0),
kind: ActionKind::Talk,
label: "Talk".to_string(),
priority: if talk_enabled { 50 } else { 10 },
enabled: talk_enabled,
disabled_reason: if !talk_enabled {
Some("Busy".to_string())
} else {
None
},
});
// Overhear: available if NPC is in conversation with another NPC
if target_in_conversation {
actions.push(AvailableAction {
action_id: format!("overhear_{}", target_stable_id.0),
kind: ActionKind::Overhear,
label: "Listen".to_string(),
priority: 60,
enabled: true,
disabled_reason: None,
});
}
}
EntityKind::Object => {
actions.push(AvailableAction {
action_id: format!("examine_obj_{}", target_stable_id.0),
kind: ActionKind::ExamineObject,
label: "Examine".to_string(),
priority: 50,
enabled: true,
disabled_reason: None,
});
}
_ => {}
}
// Sort by priority descending
actions.sort_by(|a, b| b.priority.cmp(&a.priority));
actions
}
```
### How v0.1 and v0.2 Differ — Client Side Only
| Behavior | v0.1 | v0.2+ |
|----------|------|-------|
| Actions computed | ALL (server computes full list) | ALL (same) |
| Actions sent to client | ALL (via `EntityInteractions.actions`) | ALL (same) |
| Actions displayed | `actions[0]` only — single prompt | All enabled actions — menu/radial |
| Player input | `Interact` → server applies `actions[0]` | `InteractWith(action_id)` → server applies specific action |
| Architecture change needed for v0.2 | **None on server.** Client reads more of the existing data. | Client UI change only |
The key guarantee: **zero server-side changes for v0.2 multi-verb.** The server already sends everything. The client just reads more of what's already there.
### PlayerAction Extension
```rust
pub enum PlayerAction {
// ... existing movement variants ...
/// v0.1: interact with nearest entity, server picks top action.
Interact,
/// v0.2+: interact with specific entity using specific action.
/// Falls back to top action if action_id is None.
InteractWith {
target_id: u64, // StableId of target
action_id: Option<String>, // specific action, or None for default
},
/// Select a dialogue topic during active conversation.
DialogueSelect { topic: String },
/// End the active conversation.
DialogueEnd,
}
```
For v0.1, the client sends `Interact`. The server resolves to the nearest entity and applies `actions[0]`. When v0.2 introduces multi-verb UI, the client sends `InteractWith { target_id, action_id }`. The server handles both — `Interact` is syntactic sugar for "find nearest, pick top action."
### Stig's Question: IPC Message Format
Stig asked what the state update looks like. The answer: **full text in the message, not IDs for client-side lookup.** This keeps the client thin and prevents information leakage. The `ObserverSnapshot` already carries everything the client needs. Interaction data rides the same channel:
```rust
/// ObserverSnapshot v3 — adds interaction and dialogue data.
pub struct ObserverSnapshot {
pub version: u8, // 3
pub tick: u64,
pub game_time: GameTime,
pub player_facing: FacingDirection,
pub entities: Vec<VisibleEntity>,
pub visible_tiles: Vec<VisibleTile>,
// v3 additions:
/// Entities within interaction range with available actions.
/// Empty if no interactable entities are nearby.
pub nearby_interactions: Vec<EntityInteractions>,
/// Active dialogue state. None if not in conversation.
pub active_dialogue: Option<ActiveDialogue>,
/// Monologue lines triggered this tick. Usually 0 or 1.
pub monologue: Vec<MonologueDisplay>,
/// Overheard conversation fragments. Passive, proximity-based.
pub overheard: Vec<OverheardDisplay>,
/// Current simulation speed (1.0 = normal, 0.5 = overlay, 0.0 = paused).
/// Client uses this to adjust animation/interpolation rates.
pub sim_speed: f32,
}
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct ActiveDialogue {
pub npc_entity_id: u64,
pub npc_name: String,
pub npc_relationship_color: RelationshipState,
/// Current NPC line. None before first line / between lines.
pub current_line: Option<DialogueLineDisplay>,
/// Available topics the player can raise. Empty if conversation is NPC-led.
pub available_topics: Vec<TopicOption>,
}
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct DialogueLineDisplay {
pub line_id: String,
pub text: String,
pub mood: String,
}
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct TopicOption {
pub topic_id: String,
pub label: String,
pub enabled: bool,
}
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct MonologueDisplay {
pub line_id: String,
pub text: String,
pub trigger: String,
/// true = use urgent chime (observe_anomaly, discover_evidence)
pub urgent: bool,
}
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct OverheardDisplay {
pub speaker_id: u64,
pub speaker_name: String,
pub fragment: String,
}
```
Everything the client needs to render is in the snapshot. The client never queries content files. The server is the single source of truth.
---
## 3. Pause System — Tick Rate Modulation
### The Model: SimulationSpeed Resource
Currently `SimulationTime` has a boolean `paused` field. That's insufficient for 50% speed. I'll replace it with a speed multiplier model:
```rust
/// Simulation speed states.
/// Determines how many ticks advance per real-time frame.
#[derive(Debug, Clone, Copy, PartialEq, Serialize, Deserialize)]
pub enum SimSpeed {
/// Normal speed: 1 tick per frame at target TPS (10 tps per D-031).
Normal,
/// Reduced speed: tick every other frame (50% speed).
/// Used when UI overlays are active (knowledge panel, dialogue).
Overlay,
/// Full pause: no ticks advance.
/// Spacebar toggle. Always available.
Paused,
}
impl SimSpeed {
/// Returns the tick advance rate.
/// Normal = advance every frame.
/// Overlay = advance every 2nd frame.
/// Paused = never advance.
pub fn should_tick(&self, frame_counter: u64) -> bool {
match self {
SimSpeed::Normal => true,
SimSpeed::Overlay => frame_counter % 2 == 0,
SimSpeed::Paused => false,
}
}
/// Serialized speed for client animation adjustment.
pub fn as_f32(&self) -> f32 {
match self {
SimSpeed::Normal => 1.0,
SimSpeed::Overlay => 0.5,
SimSpeed::Paused => 0.0,
}
}
}
/// Resource tracking simulation speed and frame count.
#[derive(Resource, Debug, Clone)]
pub struct SimulationSpeed {
/// Current speed state.
pub speed: SimSpeed,
/// Frame counter for Overlay tick skipping.
pub frame_counter: u64,
/// Stack of speed modifiers. Highest priority wins.
/// When all modifiers are removed, returns to Normal.
speed_stack: Vec<SpeedModifier>,
}
#[derive(Debug, Clone)]
struct SpeedModifier {
source: SpeedSource,
speed: SimSpeed,
priority: u8,
}
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)]
pub enum SpeedSource {
/// Spacebar toggle — highest priority, always wins.
PlayerPause,
/// Knowledge panel open.
KnowledgePanel,
/// Active dialogue with NPC.
Dialogue,
}
```
### State Machine
```
┌──────────┐
┌──────→│ Normal │◄──────┐
│ │ (1.0x) │ │
│ └────┬─────┘ │
│ │ │
close overlay open overlay spacebar
│ │ │
│ ┌────▼─────┐ │
├──────→│ Overlay │──────→│
│ │ (0.5x) │ │
│ └────┬─────┘ │
│ │ │
│ spacebar │
│ │ │
│ ┌────▼─────┐ │
└───────│ Paused │───────┘
│ (0.0x) │
└──────────┘
```
Rules:
1. **Spacebar always toggles full pause.** From Normal → Paused. From Overlay → Paused. From Paused → returns to whatever state was active before pause (Normal or Overlay).
2. **Opening knowledge panel or dialogue → Overlay (50%).** Multiple overlays don't stack — it's 50% whether you have one or three open.
3. **Closing all overlays → Normal.** But only if not explicitly paused by spacebar.
4. **Spacebar overrides everything.** It's the master switch.
### Implementation: Modified advance_tick
```rust
/// System: advance tick based on current simulation speed.
/// Replaces the current boolean-paused advance_tick.
pub fn advance_tick(
mut time: ResMut<SimulationTime>,
mut speed: ResMut<SimulationSpeed>,
) {
speed.frame_counter += 1;
if speed.speed.should_tick(speed.frame_counter) {
time.tick += 1;
}
}
/// System: process pause/speed PlayerActions.
pub fn process_speed_input(
mut speed: ResMut<SimulationSpeed>,
input_events: Res<InputQueue>,
// ... other input handling
) {
// Spacebar pause toggle
// When paused by spacebar, restore previous speed on unpause
// Overlay open/close events modify the speed stack
}
```
### What the Client Needs to Know
The `sim_speed: f32` field in ObserverSnapshot v3 tells the client:
- `1.0` → normal animation/interpolation
- `0.5` → halve animation rates, entities move at half speed visually
- `0.0` → freeze all animation, UI stays responsive
The client doesn't manage pause state. It reads the speed from the snapshot and adjusts rendering accordingly. The server is authoritative.
### Dialogue-Specific Pause Behavior
When dialogue is active (player is talking to an NPC), simulation runs at Overlay speed (50%). This means:
- NPCs continue their routines at half speed — the world doesn't freeze when you talk
- Other NPCs can walk past during your conversation — you might miss something
- But it's slow enough that the player doesn't feel punished for engaging in dialogue
If the player hits spacebar during dialogue, full pause. They can read at their own pace. Spacebar again resumes to Overlay (because dialogue is still active).
---
## 4. FriendArc Phase Transitions — Triggers and Content Dependencies
### Phase Transition State Machine
```
WARMTH ──────→ TRUST ──────→ DOUBT ──────→ CONFLICT
│ │ │ │
│ auto (tick) │ knowledge │ observation │ knowledge +
│ │ threshold │ + monologue │ dialogue
│ │ │ │
▼ ▼ ▼ ▼
"We're good" "I trust you" "Something's "I know what
wrong" you did"
```
### Phase-by-Phase: Triggers, Content, and What the Server Needs
#### Phase 1: WARMTH → TRUST
**Trigger:** Interaction count threshold + time elapsed.
```rust
/// Transition from Warmth to Trust.
/// This is the "getting to know you" phase — automatic progression
/// as the player interacts with the FRIEND over time.
fn check_warmth_to_trust(
friend_arc: &FriendArc,
interaction_log: &InteractionLog,
time: &SimulationTime,
) -> bool {
let interactions_with_friend = interaction_log
.count_interactions(friend_arc.bonded_character, friend_arc.friend_entity);
let time_since_first = time.tick.saturating_sub(
interaction_log.first_interaction_tick(
friend_arc.bonded_character, friend_arc.friend_entity
).unwrap_or(time.tick)
);
// Require both: enough interactions AND enough time.
// Prevents rushing through the arc by spam-talking.
interactions_with_friend >= 3 && time_since_first >= 600 // 1 game-hour
}
```
**Content required:**
- 5-8 dialogue lines for Warmth phase (casual, friendly, establishing rapport)
- 3-5 monologue lines for Warmth (positive: "Kael's reliable. Good to have someone you can count on.")
- Trust transition is silent — no dramatic moment. The player just notices the FRIEND is warmer
**Server state change:** `FriendArc.phase = Trust`. No knowledge graph change. No visual change. The NPC's dialogue pool shifts to Trust-phase lines (gated by the `situation: [friend_trust]` tag).
#### Phase 2: TRUST → DOUBT
**Trigger:** Knowledge threshold — the player character learns specific facts that create tension.
```rust
/// Transition from Trust to Doubt.
/// Requires the bonded character to accumulate suspicious knowledge.
/// NOT a single event — it's a gradual shift.
fn check_trust_to_doubt(
friend_arc: &FriendArc,
observer_kg: &KnowledgeGraph,
) -> bool {
// The character must know at least ONE of the doubt-triggering facts
// at KnowsOf or higher confidence.
let doubt_facts = &friend_arc.doubt_trigger_facts;
doubt_facts.iter().any(|fact_id| {
observer_kg.fact_at_least(fact_id, KnowledgeConfidence::KnowsOf)
})
}
```
**Content required for Kael (smuggler's FRIEND):**
- Doubt-triggering facts (defined in NPC profile):
- `"kael.schedule_inconsistency"` — Kael's routine doesn't fully match the posted schedule
- `"ring.internal_pressure"` — the smuggler learns the ring is under strain
- 5-8 dialogue lines for Trust phase (deeper, more personal, sharing more)
- 3-5 monologue lines for Doubt phase (questioning: "Kael left early again. Third time this rotation. Where does he go?")
- Tell acceleration: Kael's tells become more frequent in Doubt phase. The `tell_stage` counter advances, making tells more visible
**Content required for Sera (detective's FRIEND):**
- Doubt-triggering facts:
- `"sera.avoidance_pattern"` — Sera consistently avoids Torek Lintar
- `"investigation.evidence_gap"` — evidence exists that should have been reported but wasn't
- Same line counts as Kael, detective-perspective
**Server state change:** `FriendArc.phase = Doubt`. Tell stage advances (`tell_stage += 1`). Monologue pool shifts. No visual change yet — the entity color stays green (Friendly). The player should feel uneasy but not alarmed.
#### Phase 3: DOUBT → CONFLICT
**Trigger:** Direct observation of the contradiction. This is the critical moment — wow moment #3.
```rust
/// Transition from Doubt to Conflict.
/// Requires DIRECT OBSERVATION of the contradiction.
/// This cannot be told to the player — they must SEE it.
fn check_doubt_to_conflict(
friend_arc: &FriendArc,
observer_kg: &KnowledgeGraph,
) -> bool {
// ALL contradiction facts must be known at KnowsDetails or higher.
// At least one must have source = DirectObservation.
let all_known = friend_arc.contradiction_facts.iter().all(|fact_id| {
observer_kg.fact_at_least(fact_id, KnowledgeConfidence::KnowsDetails)
});
// The discovery flag is set by the spatial staging system
// when the player observes the FRIEND in the wrong place.
all_known && friend_arc.contradiction_discovered
}
```
**How `contradiction_discovered` gets set — spatial staging:**
This is the hardest part. The server must arrange for the FRIEND to be in a specific place at a specific time, and the player must be able to observe it. The simulation can't script this — it must create the opportunity and let the player find it.
```rust
/// System: check if the bonded character observes the FRIEND
/// in a contradiction location during a contradiction window.
fn check_contradiction_observation(
friend_query: Query<(&FriendArc, &NpcRoutine, &TilePosition), With<Npc>>,
observer_query: Query<(&KnowledgeGraph, &TilePosition), With<PlayerCharacter>>,
location_map: Res<LocationMap>,
time: Res<SimulationTime>,
mut event_queue: ResMut<KnowledgeEventQueue>,
) {
for (arc, routine, npc_pos) in friend_query.iter() {
if arc.phase != FriendPhase::Doubt {
continue;
}
// Is the FRIEND currently at their contradiction location?
let at_contradiction = arc.contradiction_location.as_ref()
.map(|loc| location_map.contains_position(loc, npc_pos))
.unwrap_or(false);
// Is it the right time window?
let in_window = arc.contradiction_time_window.as_ref()
.map(|w| w.active_at(&time))
.unwrap_or(true); // no time window = always active
if !at_contradiction || !in_window {
continue;
}
// Is the bonded character observing?
// (They must have LOS to the FRIEND's current position)
// The perception system handles LOS. We check if the bonded
// character has Direct confidence on the FRIEND.
for (obs_kg, _obs_pos) in observer_query.iter() {
if let Some(entry) = obs_kg.entity_knowledge(&arc.friend_stable_id) {
if entry.confidence == KnowledgeConfidence::Direct {
// The player character is looking at their FRIEND
// in the wrong place at the wrong time.
// This is wow moment #3.
// Emit knowledge event for contradiction facts
// Emit monologue trigger (observe_npc with deviation)
// Set contradiction_discovered = true
}
}
}
}
}
```
**Content required for the contradiction moment:**
- **Kael:** Observed in Corridor B-7 (maintenance corridors) during shift transition, meeting unknown contact. The smuggler knows Kael has no reason to be there.
- Monologue line (urgent chime): "Kael? In Corridor B-7? During shift transition? He has no reason to be there. None that I know of." (`terminal_m_s_012` from Tyre's example)
- Knowledge grant: `"kael.secret_meetings": KnowsDetails`
- Knowledge grant: `"kael.restricted_corridor_visits": KnowsDetails`
- **Sera:** Observed avoiding Torek Lintar (turning away when he enters the bar). The detective recognizes the pattern.
- Monologue line (urgent chime): detective-equivalent — recognizing deliberate avoidance
- Knowledge grant: `"sera.avoidance_pattern": KnowsDetails`
**Server state change:** `FriendArc.phase = Conflict`. `FriendArc.contradiction_discovered = true`. **RelationshipState shifts: Friendly → PersonOfInterest.** Entity color shifts green → amber (D-033, 0.5s fade). Tell stage maxes out. Dialogue pool shifts to Conflict-phase lines.
This is the single most important moment in the vertical slice. State consistency requires:
1. Knowledge graph updated with contradiction facts
2. FriendArc phase advanced
3. RelationshipState changed
4. Monologue triggered (urgent)
5. Entity color change visible in next ObserverSnapshot
All five must happen atomically within the same tick. I need to verify the tick order handles this correctly — knowledge event processing must complete before snapshot generation.
#### Phase 4: CONFLICT (Terminal)
**Trigger:** None — this is the final phase. The player is in Conflict with their FRIEND.
**Content required:**
- 8-12 Conflict-phase dialogue lines (confrontation options, defensive NPC responses, the NPC's sympathetic motivation revealed)
- 5-8 Conflict-phase monologue lines (the character processing betrayal, re-evaluating past interactions)
- No clean resolution — D-034 mandates this. The conversation can happen, understanding can emerge, but the trust is broken
**Server state:** `FriendArc.phase = Conflict`. RelationshipState stays PersonOfInterest (or shifts to Hostile if the confrontation goes badly). The arc is complete.
### Revised FriendArc Component
```rust
#[derive(Component, Debug, Clone, Serialize, Deserialize)]
pub struct FriendArc {
/// Which character this FRIEND is bonded to (StableId).
pub bonded_character: StableId,
/// StableId of this FRIEND NPC (for knowledge graph lookups).
pub friend_stable_id: StableId,
/// Current phase.
pub phase: FriendPhase,
// --- Transition triggers ---
/// Facts that trigger Doubt phase (any one sufficient).
pub doubt_trigger_facts: Vec<FactId>,
/// Facts that constitute the full contradiction (all required for Conflict).
pub contradiction_facts: Vec<FactId>,
/// Location where the contradiction occurs.
pub contradiction_location: Option<String>, // canonical location ID
/// Time window for the contradiction (day phase + optional minute range).
pub contradiction_time_window: Option<TimeWindow>,
// --- State tracking ---
/// Tell visibility stage (0 = minimal, advances as phase progresses).
pub tell_stage: u8,
/// Has the bonded character directly observed the contradiction?
pub contradiction_discovered: bool,
}
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct TimeWindow {
pub phase: DayPhase,
pub start_minute: Option<u64>, // within the phase
pub end_minute: Option<u64>,
}
impl TimeWindow {
pub fn active_at(&self, time: &SimulationTime) -> bool {
if time.day_phase() != self.phase {
return false;
}
let tod = time.time_of_day_minutes();
let phase_start = match self.phase {
DayPhase::Morning => 0,
DayPhase::Afternoon => 360,
DayPhase::Evening => 720,
DayPhase::Night => 1080,
};
let start = phase_start + self.start_minute.unwrap_or(0);
let end = phase_start + self.end_minute.unwrap_or(360);
tod >= start && tod < end
}
}
```
### Content Summary — What I Need from Mellanie and Paula
| FRIEND NPC | Phase | Lines Needed | Type | Blocker? |
|-----------|-------|-------------|------|----------|
| **Kael** | Warmth | 5-8 | dialogue (casual, friendly) | No — generic enough to synthesize |
| **Kael** | Warmth | 3-5 | monologue (positive, routine) | No |
| **Kael** | Trust | 5-8 | dialogue (personal, deeper) | Yes — needs character voice |
| **Kael** | Trust | 3-5 | monologue (warming, comfortable) | Yes |
| **Kael** | Doubt | 5-8 | dialogue (evasive, stressed) | Yes |
| **Kael** | Doubt | 3-5 | monologue (questioning, uneasy) | Yes |
| **Kael** | Conflict | 8-12 | dialogue (confrontation, revelation) | Yes — most critical |
| **Kael** | Conflict | 5-8 | monologue (processing, betrayal) | Yes |
| **Kael** | Contradiction | 1 | monologue (urgent, wow moment #3) | **CRITICAL** |
| **Sera** | (same counts) | ~35-46 | (same breakdown) | Same blockers |
**Total per FRIEND NPC: ~35-46 authored lines minimum.**
**Total for both: ~70-92 lines.**
This aligns with D-034's estimate of 70-100 per FRIEND. The breakdown by phase is what I need to test each transition independently.
### Interaction Log Component
I need a lightweight interaction tracking component to support the Warmth → Trust transition:
```rust
/// Tracks interaction history between entities.
/// Used for FriendArc Warmth→Trust transition and future NOBODY promotion.
#[derive(Component, Debug, Clone, Serialize, Deserialize)]
pub struct InteractionLog {
/// (target_stable_id, tick) pairs.
/// BTreeMap for deterministic iteration.
pub interactions: BTreeMap<StableId, Vec<u64>>,
}
impl InteractionLog {
pub fn new() -> Self {
Self { interactions: BTreeMap::new() }
}
pub fn record(&mut self, target: StableId, tick: u64) {
self.interactions.entry(target).or_default().push(tick);
}
pub fn count(&self, target: &StableId) -> usize {
self.interactions.get(target).map(|v| v.len()).unwrap_or(0)
}
pub fn first_tick(&self, target: &StableId) -> Option<u64> {
self.interactions.get(target).and_then(|v| v.first().copied())
}
}
```
This also becomes the foundation for NOBODY tier promotion in v0.2 — the same interaction counter that drives FriendArc Warmth→Trust will drive NOBODY→NOTICED. Building it now means zero rework later.
---
## Summary of Round 2 Deliverables
| Decision | Resolution |
|----------|-----------|
| **YAML format** | Accepted. `serde_yaml` replaces `ron` for content loading. RON converter in `tooling/` as low-priority insurance. |
| **Multi-action model** | Server computes ALL available actions per entity, ranked by priority. v0.1 client shows `actions[0]`. v0.2 client shows all. Zero server changes needed for v0.2. |
| **Pause system** | `SimSpeed` enum: Normal (1.0x), Overlay (0.5x), Paused (0.0x). Spacebar always toggles full pause. UI overlays trigger Overlay speed. Speed stack with priority resolution. |
| **FriendArc transitions** | 4-phase state machine with explicit triggers: Warmth (interaction count + time) → Trust (knowledge threshold) → Doubt (specific facts) → Conflict (direct observation of contradiction). Contradiction detection requires spatial staging system. |
### Dependencies I'm Tracking
1. **ObserverSnapshot v3** — Tyre needs to sign off on the protocol extension. I've proposed the full struct. Stig needs the `sim_speed` field and `nearby_interactions` / `active_dialogue` / `monologue` / `overheard` fields.
2. **FRIEND content packs** — Mellanie needs to produce phase-tagged dialogue and monologue lines per the breakdown above. These unblock integration testing of the FriendArc state machine.
3. **Contradiction spatial data** — Paula needs to specify the exact contradiction setup for Kael and Sera in the NPC profiles: which location, which time window, what the contradiction looks like when observed.
4. **FactId catalog** — Still the #1 blocker. I need the machine-readable fact vocabulary before I can build prerequisite evaluation. Gestalt and Paula produce this.
docs/workshops/v01-content-scoping/round2-gestalt.md
-422
View File
@@ -1,422 +0,0 @@
# Round 2 — Gestalt (Systems Design)
*cracks knuckles*
Four resolution tasks. Let me be honest about each.
---
## Task 1: Canonical NPC Mapping (Definitive)
The lead confirmed my mechanical mapping wins for v0.1. Paula's emotional/narrative reads become v0.2 annotations. But "winning" doesn't mean refusing to learn from the disagreements. I reviewed all 10 and changed my mind on 6 of them.
### Changes from Round 1 (Where Paula Was Right)
Let me be transparent about what I got wrong and why:
| NPC | My R1 | Paula's R1 | Final R2 | Who Was Right | Why I Changed |
|-----|-------|-----------|----------|---------------|---------------|
| **Maret** (pattern) | SYSTEM | WITNESS | **WITNESS** | Paula | Maret's v0.1 function is defined by what she SAW, not her institutional role. The player (both characters) approaches Maret because she carries information. SYSTEM describes her job; WITNESS describes her story function. |
| **Maret** (motivation) | WITNESS | SKEPTIC | **SKEPTIC** | Paula | If pattern is WITNESS and motivation is WITNESS, there's no compositional tension. WITNESS+SKEPTIC = "she saw something AND she doubts" — the doubt makes her dangerous because she might ACT. Data-driven doubt IS skepticism. |
| **Resha** (motivation) | SKEPTIC | CIVILIAN | **CIVILIAN** | Paula | CATALYST+SKEPTIC implies deliberate questioning. CATALYST+CIVILIAN = "innocent disruption" — Resha doesn't INTEND to cause problems. The accidental quality makes the disruption more realistic and more dangerous (you can't negotiate with curiosity). |
| **Harek** (pattern) | GHOST | ANCHOR | **ANCHOR** | Paula | Harek is PHYSICALLY PRESENT. GHOST means absent power; Harek is at the bar playing cards. His leverage on Drin is indirect, but HE isn't absent. Paula's read: Harek embodies complacent contentment whose comfort accidentally creates a tool for others. The "unconscious lever" is more interesting than "invisible puppeteer." |
| **Drin** (pattern) | REMNANT | SYSTEM | **SYSTEM** | Paula | Paula nailed this: "The dock inspector IS the inspection system. His compromise means the system itself is corrupted." REMNANT requires historical depth a 40-year-old station doesn't have. Drin doesn't remember centuries of tradition — he remembers 5 years ago. That's not REMNANT-scale. SYSTEM+TURNCOAT = institutional rot. |
| **Sabel** (pattern) | THRESHOLD | GHOST | **GHOST** | Paula | Sabel is off-station with 1-2 brief visits. The player doesn't interact with Sabel enough for THRESHOLD mechanics (getting past a gatekeeper). The player learns about Sabel through others' references. That's GHOST — absent power shaping events through supply chain influence. |
| **Olin** (motivation) | SKEPTIC (dual) | CIVILIAN | **CIVILIAN** | Paula | Dropped dual designation. At Tier 3, Olin has 10-15 lines. Not enough content for SKEPTIC function. CIVILIAN is the safe tag — if Olin gets promoted to T2 in v0.2, the hidden motivation can be revealed. 1 pattern + 1 motivation per NPC, no exceptions. |
### What I Kept (Where My Mechanical Read Holds)
| NPC | Disagreement | My R1 | Final R2 | Why I'm Keeping It |
|-----|-------------|-------|----------|-------------------|
| **Voss** (motivation) | OPERATOR vs HANDLER | OPERATOR | **OPERATOR** | Voss RUNS the schedule. That's operating, not handling. HANDLER implies top-down pressure — Devra and Harek do that. Voss is middle management: competent, procedural, operating the machinery. The schedule IS his operation. |
| **Devra** (motivation) | HANDLER vs OPERATOR | HANDLER | **HANDLER** | Devra conveys Nils's strategy, manages external contacts, delivers escalation demands. That's pressure from above. She doesn't run day-to-day operations (Kael, Renn, Voss do). She manages the people who run things. |
| **Sess** (pattern) | ANCHOR vs NOBODY | ANCHOR | **ANCHOR** | NOBODY is deferred to v0.2. Tagging Sess as NOBODY means the tag does nothing in v0.1. ANCHOR at T3 = contentment as atmospheric texture. The bartender who sees everything and says nothing because his life is fine. v0.2 note: Sess could be retagged NOBODY if dynamic tier promotion activates. |
### The Definitive v0.1 NPC Mapping
| # | Name | Tier | Pattern | Motivation | Composition Read |
|---|------|------|---------|-----------|-----------------|
| 1 | **Kael Davan** | **T1** | **FRIEND** | **OPERATOR** | Trust anchor running ring cargo. Identity betrayal: "I was your friend AND your co-conspirator." |
| 2 | **Sera Venn** | **T1** | **FRIEND** | **WITNESS** | Trust anchor carrying unreported evidence. Concealment betrayal: "I was your friend AND I was hiding evidence." |
| 3 | **Naia Tamm** | **T1*** | **MIRROR** | **CIVILIAN** | Honest transparency, no secrets, uninvolved. "The one person not lying — surrounded by liars." |
| 4 | **Voss** | T2 | **SYSTEM** | **OPERATOR** | Institutional authority operating the schedule that enables smuggling. Corrupted machinery: "The system works — for the wrong people." |
| 5 | **Lera Sessik** | T2 | **ANCHOR** | **OPERATOR** | Contentment embodied, running a bar on willful ignorance. Profitable blindness: "Is this enough? Yes — if I don't look." |
| 6 | **Torek Lintar** | T2 | **CATALYST** | **CIVILIAN** | Spending disrupts equilibrium. Uninvolved, just living visibly. Accidental signal: "He doesn't know he's a liability." |
| 7 | **Devra** | T2 | **THRESHOLD** | **HANDLER** | Ring gatekeeper, manages operations from above. Obstacle with authority: "You go through her or you don't go." |
| 8 | **Maret Korr** | T2 | **WITNESS** | **SKEPTIC** | Accidentally observed discrepancies, doubts the numbers. Dangerous knowledge: "She saw something and she can't stop questioning it." |
| 9 | **Resha** | T2 | **CATALYST** | **CIVILIAN** | New hire forcing defensiveness with innocent questions. Accidental disruption: "She just asked. Everyone flinched." |
| 10 | **Drin** | **T2** | **SYSTEM** | **TURNCOAT** | Inspector whose compromise corrupts the institution. Loyalty shifting under coercion. Institutional rot: "The inspection system is broken because the inspector is broken." |
| 11 | **Renn** | T2 | **THRESHOLD** | **OPERATOR** | Courier controlling cargo flow. Physical gatekeeper: "Renn moves the product. Trace Renn, find the route." |
| 12 | **Pell** | T2 | **CATALYST** | **TURNCOAT** | Wavering member forcing potential crisis. Maximum instability: "When Pell breaks, everything moves." |
| 13 | **Harek** | T2 | **ANCHOR** | **HANDLER** | Complacent contentment whose comfort creates a tool. Unconscious lever: "Harek doesn't know his card games built a weapon." |
| 14 | **Sess** | T3 | **ANCHOR** | **CIVILIAN** | Quiet contentment behind the bar. Social wallpaper: "Sees everything, says nothing — because nothing's wrong with HIS life." |
| 15 | **Olin** | T3 | **CATALYST** | **CIVILIAN** | New arrival forcing evaluation. Ambiguous intent: "Friend or threat? The question IS the disruption." |
| 16 | **Sabel** | T3 | **GHOST** | **OPERATOR** | Off-station absent power running the supply chain. Distant machinery: "Sabel shapes events from elsewhere." |
| 17 | **Tav** | T3 | **SYSTEM** | **CIVILIAN** | Ring lookout following procedure. Lowest rung: "Tav watches the door. That's the whole job." |
*Off-stage:*
| NPC | Pattern | Motivation | Notes |
|-----|---------|-----------|-------|
| **Nils Davan** | **GHOST** | **HANDLER** | Absent authority applying pressure through intermediaries. |
### Pattern Distribution (Final)
| Pattern | Count | NPCs | Coverage |
|---------|-------|------|----------|
| FRIEND | 2 | Kael, Sera | Full (D-034 production level) |
| MIRROR | 1 | Naia Tamm | Full (T1 emotional depth) |
| ANCHOR | 3 | Lera, Harek, Sess | Full + sketch. Three versions of "is this enough?" |
| SYSTEM | 3 | Voss, Drin, Tav | Full + sketch. Institutional machinery (legit + criminal) |
| CATALYST | 3 | Torek, Resha, Pell | Full. Three disruption modes (accidental, innocent, deliberate) |
| THRESHOLD | 2 | Devra, Renn | Full. Access gatekeepers (organizational + physical) |
| WITNESS | 1 | Maret | Full. Data-driven information carrier |
| GHOST | 1+1 | Sabel (+Nils off-stage) | Light. Absent power through supply/authority |
| REMNANT | 0 | — | Correctly absent. 40-year station lacks historical depth. |
| NOBODY | 0 | — | Deferred to v0.2. Data ships (hidden fields in content). |
8 of 9 patterns present. All 6 motivations present.
### Motivation Distribution (Final)
| Motivation | Count | NPCs |
|-----------|-------|------|
| OPERATOR | 5 | Kael, Voss, Lera, Renn, Sabel |
| CIVILIAN | 6 | Naia Tamm, Torek, Resha, Olin, Sess, Tav |
| HANDLER | 2+1 | Devra, Harek (+Nils off-stage) |
| WITNESS | 1 | Sera |
| TURNCOAT | 2 | Drin, Pell |
| SKEPTIC | 1 | Maret |
CIVILIAN at 6/17 (35%) — matches D-029's noise floor requirement (~30% flat). OPERATOR at 5 reflects a logistics hub where everyone is RUNNING something. All 6 motivations represented.
### Why This Mapping Creates Interesting Decisions
**ANCHOR saturation (3):** Three different answers to "is this enough?" Lera: "Yes, if I don't look." Harek: "Yes, absolutely — pass me the cards." Sess: "Yes, and I'd rather you didn't disturb it." This isn't redundancy — it's the thematic floor the investigation disrupts. The player walks through contentment before contamination touches it.
**SYSTEM × TURNCOAT (Drin):** The most mechanically productive composition in the set. The institution IS the character AND the character is betraying the institution. For the detective: crack the inspector, crack the system. For the smuggler: keep the inspector quiet, keep the system working for you. Same NPC, inverted interactions. That's the dual-lens proof.
**CATALYST diversity (3 types):** Torek disrupts through SPENDING (accidental, financial signal). Resha disrupts through ASKING (innocent, social signal). Pell disrupts through WAVERING (deliberate, operational signal). Three types of disruption, three types of player assessment. The smuggler reads them as threats with different urgency levels. The detective reads them as leads with different reliability levels.
---
## Task 2: Generic Key Architecture (The Bloat Question)
The lead asks: *"If the original EntityKnowledge set was incomplete for the smuggler, are we doing this again for the administrator or the corporate tycoon?"*
The answer is **no — if we design the keys correctly now.**
### The Problem with Per-Archetype Keys
My Round 1 proposal: 4 smuggler-specific keys (`exposure_risk`, `loyalty_assessment`, `cover_integrity`, `moral_weight`). If we repeat this for 8 archetypes:
```
8 archetypes × 4 unique keys = 32 archetype-specific keys
+ 14 shared keys
= 46 total keys (unsustainable)
```
Administrator needs `bureaucratic_leverage`, `regulatory_compliance`...
Merchant needs `market_position`, `asset_vulnerability`...
Every archetype spawns its own vocabulary. That's schema bloat AND content bloat (every NPC profile must have 46 fields).
### The Solution: 4 Generic Perspective Keys
Look at what my 4 smuggler keys actually represent at the ABSTRACT level:
| Smuggler Key | Abstract Question |
|-------------|-------------------|
| `exposure_risk` | "How does this NPC threaten MY operational position?" |
| `loyalty_assessment` | "How reliably will this NPC act in MY interest?" |
| `cover_integrity` | "How well is the relevant deception holding?" |
| `moral_weight` | "How morally culpable is this NPC in MY judgment?" |
These questions are UNIVERSAL. Every archetype asks them — just with different words:
| Abstract Question | Smuggler | Detective | Administrator | Merchant |
|------------------|----------|-----------|--------------|----------|
| "How does this NPC threaten my position?" | "Will they expose the ring?" | "Will they obstruct my investigation?" | "Will they expose my corruption?" | "Will they undercut my deal?" |
| "How reliably will this NPC serve my interests?" | "Can I count on them in operations?" | "Will they testify/cooperate?" | "Will they vote with me?" | "Will they honor the contract?" |
| "How well is the deception holding?" | "Is their cover solid?" | "Is my informant still believable?" | "Does the public still buy it?" | "Does the competitor still trust me?" |
| "How culpable is this NPC?" | "How deep in the ring?" | "How guilty?" | "How corrupt?" | "How honest?" |
**Same 4 questions. Same 4 keys. 8 archetypes.**
### Proposed Generic Keys
| Key Name | Value Enum | What It Stores |
|----------|-----------|---------------|
| `threat_to_position` | `"none"`, `"low"`, `"moderate"`, `"high"`, `"critical"` | Observer's assessment of how this NPC threatens the observer's operational security, institutional standing, or strategic position. |
| `reliability` | `"solid"`, `"dependable"`, `"uncertain"`, `"wavering"`, `"hostile"` | Observer's assessment of how predictably this NPC will serve the observer's interests. |
| `facade_status` | `"solid"`, `"thin"`, `"cracking"`, `"blown"`, `"N/A"` | Status of any active deception involving this NPC (their cover, the observer's cover, a shared front). N/A if no deception in play. |
| `moral_standing` | `"innocent"`, `"peripheral"`, `"complicit"`, `"compromised"`, `"willing"` | Observer's subjective moral assessment of this NPC within the observer's ethical framework. |
### How Interpretation Works
The key stores GENERIC data. The monologue system provides CHARACTER-SPECIFIC interpretation through D-032's hard partition (separate pools per character).
**Same NPC, same keys, different character pools:**
```yaml
# Smuggler monologue about Maret
- id: hub_m_031
text: "Maret's been checking manifests again. She's going to notice something she can't un-notice."
character: smuggler
trigger: observe_npc
prerequisite:
target.known_attributes.threat_to_position: "high"
target.known_attributes.name: "Maret Korr"
# Detective monologue about Maret
- id: hub_m_032
text: "Korr looks worried. She processes manifests — if the numbers are off, she'd know."
character: detective
trigger: observe_npc
prerequisite:
target.known_attributes.threat_to_position: "high"
target.known_attributes.name: "Maret Korr"
```
Same key (`threat_to_position: "high"`), same NPC — but the smuggler reads it as "she's a risk to the operation" while the detective reads it as "she's a potential witness at risk." The interpretation lives in the monologue text, not in the key schema.
### Why This Scales to 8 Archetypes Without Bloat
| Archetype | threat_to_position means... | reliability means... | facade_status means... | moral_standing means... |
|-----------|---------------------------|---------------------|----------------------|------------------------|
| Smuggler | Exposure risk to the ring | Operational loyalty | Cover integrity | Innocent vs. complicit |
| Detective | Obstruction to investigation | Cooperation likelihood | Informant/cover status | Guilt level |
| Administrator | Political liability | Voting alignment | Public image coherence | Corruption level |
| Merchant | Competitive threat | Contract reliability | Deal integrity | Business ethics |
| Newcomer | Social danger | Friendliness | Acceptance facade | Community trustworthiness |
| Operator | Operations disruption | Team dependability | Mission cover | Professional ethics |
| Exile | Personal danger | Alliance reliability | Identity concealment | Threat vs. ally |
| Fixer | Client risk | Job reliability | Operation facade | How dirty |
**Total EntityKnowledge keys: 18.** 14 shared + 4 generic perspective. Works for all 8 archetypes. No additional keys needed at v1.0.
### Value Enum Design
The enums are deliberately archetype-neutral:
- `"solid"` / `"dependable"` / `"uncertain"` / `"wavering"` / `"hostile"` — these words work in ANY context. A smuggler reads "wavering" as "might turn on us." A detective reads "wavering" as "might cooperate if pressured." Same word, different operational meaning.
- `"innocent"` / `"peripheral"` / `"complicit"` / `"compromised"` / `"willing"` — these work for any moral framework. A smuggler uses them to track guilt distance from the ring. An administrator uses them to track corruption distance from a scandal. The progression is the same.
### How Content Authors Use This
NPC profiles get a SINGLE set of character-perspective attributes, not per-archetype sections:
```yaml
# In kael-davan.yaml, perspective section
perspectives:
smuggler:
threat_to_position: "low" # Kael is reliable (pre-contradiction)
reliability: "solid" # Trusted colleague
facade_status: "solid" # Cover holds (pre-contradiction)
moral_standing: "willing" # Fully committed ring member
detective:
threat_to_position: "moderate" # Kael handles cargo on suspicious shifts
reliability: "uncertain" # Unknown cooperativeness
facade_status: "solid" # Appears to be a normal dock worker
moral_standing: "complicit" # Connected to discrepancies (if known)
```
Content authors populate perspective values per character in the NPC YAML. The server loads these as initial `known_attributes` values for each character's knowledge graph. Values update through gameplay (Kael's `facade_status` shifts from `"solid"` to `"cracking"` when tells accumulate).
### Addressing Paula's 8-Key Proposal
Paula proposed all 8 smuggler attributes as new keys. My generic architecture maps her proposal:
| Paula's Key | Maps To | Notes |
|-------------|---------|-------|
| `trust_read` | `trust_level` (existing) | Same key, context-dependent interpretation. Already works. |
| `exposure_risk` | `threat_to_position` (generic) | Renamed for archetype-neutrality. |
| `loyalty_assessment` | `reliability` (generic) | Renamed. |
| `leverage_held` | `secret_held` (existing) | Leverage IS secret knowledge. Same storage. |
| `social_debt` | Deferred to v0.2 | 30-minute session doesn't develop favor economy. |
| `moral_weight` | `moral_standing` (generic) | Renamed. |
| `cover_integrity` | `facade_status` (generic) | Renamed. |
| `loyalty_conflict` | Deferred to v0.2 | Inferable from `behavior_flags` + `reliability`. |
**Result:** 2 existing keys reused + 4 generic keys created + 2 deferred. Total schema: 18 keys. Works for 8 archetypes.
---
## Task 3: Self-Contained Triangle Forks (Confirmed)
**I agree with Tyre's recommendation: self-contained forks for v0.1, no cross-triangle cascade.**
But "self-contained" needs a precise definition, because there's a trap:
### The Shared-NPC Problem
Voss appears in BOTH Triangle 1 (Hub Power) and Triangle 2 (Worried Knowledge). If the smuggler escalates in Triangle 1, Voss gets more anxious. That anxiety is part of Voss's ENTITY STATE — it's stored in `behavior_flags`, `routine_pattern`, etc. If Triangle 2's fork reads Voss's entity state, then Triangle 1's decision HAS cascaded into Triangle 2.
Is that a cross-triangle cascade? Technically yes. Should we prevent it? **No — that would require NPCs to have separate states per triangle, which is absurd.**
### What "Self-Contained" Actually Means
**Self-contained forks = independent decision state machines, shared NPC state.**
| Allowed (v0.1) | Not Allowed (v0.2+) |
|----------------|---------------------|
| Each triangle has its own fork with its own trigger, decision, and outcome | Triangle 1's OUTCOME directly gates Triangle 2's FORK (if T1 escalates, T2 fork changes) |
| NPCs carry behavioral state across triangles (Voss's anxiety is visible everywhere) | Triangle forks modify other triangles' state machines (T1 pushes T2 from state A to state B) |
| Players OBSERVE cross-triangle effects through NPC behavior | Fork resolution in one triangle REQUIRES resolution of another |
| Monologue can reference NPC state from any source | The storyteller sequences forks based on other forks' outcomes |
**In implementation:**
```
Triangle 1 Fork:
trigger: Devra delivers Nils's escalation demand
decision: smuggler chooses escalate/stabilize/mediate
outcome: modifies Voss.behavior_flags, Kael.behavior_flags
DOES NOT: modify Triangle 2's fork state
Triangle 2 Fork:
trigger: detective notices Maret's manifest re-checking pattern
decision: detective approaches Maret or pressures Drin
outcome: modifies Maret.trust_level, Drin.cover_integrity
DOES NOT: depend on Triangle 1's resolution
Shared state visible to both:
Voss.behavior_flags may contain "nervous" from T1 AND "overworked" from T2
The player sees ALL of Voss's behavioral state regardless of which triangle produced it
Cross-triangle OBSERVATION is emergent — it's systems interacting, not scripted cascade
```
**Why this is right for v0.1:**
1. **Testing scope**: Self-contained forks can be tested independently. Each triangle fork is a unit test. Cross-triangle cascade requires integration tests across all 5 triangles.
2. **Content scope**: Each fork needs its own decision content (dialogue, monologue, consequences). 3 active forks × 3 choices each = 9 content branches. Adding cascade dependencies multiplies this combinatorially.
3. **The emergent observation IS the payoff**: The player noticing that Voss is anxious in BOTH the hub (Triangle 1) and during manifest processing (Triangle 2) is an emergent connection. They're doing investigation — connecting dots across contexts. That's MORE interesting than scripted cascade, and it comes for free from shared NPC state.
4. **v0.2 cascade path**: If we want Triangle 1's escalation to gate Triangle 2's timing in v0.2, the architecture supports it. The fork state machines are independent now; adding dependencies later is an additive change, not a rewrite.
### Triangle Fork Summary (Final)
| Triangle | Fork Type | Decision | Self-Contained? |
|----------|-----------|----------|-----------------|
| T1: Hub Power | **Active** | Smuggler: escalate/stabilize/mediate | YES — modifies Voss+Kael state, no T2 gate |
| T2: Worried Knowledge | **Active** | Detective: approach Maret / pressure Drin / wait | YES — modifies Maret+Drin state, no T1 gate |
| T3: Bar Tensions | **Passive** | No fork — ambiguity is permanent | N/A |
| T4: Worried Partner | **Active** | Both PCs: FRIEND contradiction paths A/B/C | YES — modifies Kael/Sera state, no other triangle gate |
| T5: Informant Question | **Passive** | No fork — tension observable, resolution post-session | N/A |
---
## Task 4: Knowledge Panel Pause — Sim Speed Architecture
**Lead decision: 50% sim speed when panel is open. Spacebar always pauses from anywhere.**
### Why 50% Is Correct (Not 10%, Not Full Pause)
Stig proposed 10%. Lead overruled to 50%. Here's the mechanical reasoning:
| Speed | Effect | Problem |
|-------|--------|---------|
| 100% (no slow) | World runs at full speed while you read the knowledge panel | NPCs walk away while you're cross-referencing. Punishes information gathering. |
| 50% (lead's choice) | World runs at half speed | You can SEE NPCs moving slowly while you think. Creates tension: "Do I keep reading or close and follow?" That's an INTERESTING DECISION. |
| 10% (Stig's proposal) | World barely moves | No tension. Functionally equivalent to pause. If you're going to pause, just pause. 10% is a nothing-state. |
| 0% (full pause) | World stops | No tension. The knowledge panel becomes a reference tool, not a strategic moment. Removes the feeling of time pressure that makes investigation feel real. |
**50% creates a micro-decision every time you open the panel:** "Is the information worth the time?" That's asymmetric information AS MECHANIC — even the player's attention is a scarce resource.
### Sim Speed State Machine
Two independent toggles, multiplicative:
```
effective_speed = if pause_override { 0.0 } else { base_speed × ui_modifier }
```
| Toggle | Controls | Values |
|--------|----------|--------|
| `ui_modifier` | Whether a UI overlay is open | `1.0` (no overlay) or `0.5` (knowledge panel open) |
| `pause_override` | Spacebar | `false` (not paused) or `true` (paused) |
**State combinations:**
| State | ui_modifier | pause_override | Effective Speed | Player Experience |
|-------|------------|---------------|----------------|-------------------|
| Normal play | 1.0 | false | **100%** | Full speed. NPCs move, routines advance. |
| Panel open | 0.5 | false | **50%** | Slow motion. NPCs drift. Time passes. Tension. |
| Paused (from normal) | 1.0 | true | **0%** | Full stop. World frozen. Read, think, plan. |
| Paused (from panel) | 0.5 | true | **0%** | Full stop. Panel still visible. No time pressure. |
**Key behaviors:**
- **Spacebar always pauses.** From any state. No exceptions. This is accessibility AND good design.
- **Spacebar resumes to previous state.** If you paused from panel-open (50%), unpausing returns to 50%, not 100%. If you paused from normal play, unpausing returns to 100%.
- **Tab toggles panel.** Opening panel sets `ui_modifier = 0.5`. Closing panel sets `ui_modifier = 1.0`. Independent of pause state.
- **Dialogue: also 50%.** When dialogue is active (Talk interaction), the same `ui_modifier = 0.5` applies. NPCs who aren't in the conversation continue moving at half speed. This means other events can happen WHILE you're talking — the world doesn't freeze for your conversation. That's immersive sim design.
### v0.2 Extension
The multiplicative model is composable. Future UI states can define their own modifiers:
| UI State | Modifier | Combined |
|----------|----------|----------|
| Knowledge panel | 0.5 | 0.5 |
| Dialogue | 0.5 | 0.5 |
| Panel + Dialogue? | 0.5 × 0.5 = 0.25 | 25% (both open simultaneously) |
| Cutscene | 0.0 | Full freeze (storyteller controls) |
For v0.1, only panel and dialogue use 0.5. The system supports future states without redesign.
### Implementation Note for Dudley
The server tick rate doesn't change. The CLIENT requests a sim speed modifier. The server processes ticks at variable intervals:
- Normal: 1 tick per 50ms (20 ticks/sec)
- 50%: 1 tick per 100ms (10 ticks/sec)
- Paused: 0 ticks (server queues but doesn't process)
The server's tick processing is deterministic regardless of interval. Changing the interval changes PACING, not LOGIC. All systems (NPC routines, monologue triggers, tell accumulation) operate on tick count, not wall-clock time. A 50% slowdown means the same events happen — they just take twice as long in wall-clock time.
---
## Cross-Reference: Addressing Tracking Doc Items
A few items from Qatux's tracking that directly involve my assignments:
### A-17: Self-contained triangle forks
**Confirmed.** See Task 3. Independent decision state machines, shared NPC state. Tyre was right.
### D-04: Examine vs Talk
**Lead decided: conceptually separate, v0.1 ships single action.** I accept this. My 7-interaction model stands as the DESIGN TARGET. v0.1 implements it as context-sensitive single action (server knows about multiple actions per entity, client surfaces the best one). v0.2 adds multi-verb UI. The architecture must support both — that's Tyre and Dudley's task.
### D-05: Knowledge Panel Pause
**Resolved.** See Task 4. 50% sim speed, spacebar override to full pause. Multiplicative model.
### A-10: Dialogue files by location + role
**I validate this.** It aligns with D-035 (role-based, not NPC-based line assignment) and the generator model (templates define roles, NPCs fill roles). The file organization should be:
```
districts/sova-transit/dialogue/
hub-dock-worker.yaml # Role: dock worker, Location: hub
hub-supervisor.yaml # Role: supervisor, Location: hub
bar-owner.yaml # Role: bar owner, Location: bar
bar-regular.yaml # Role: bar regular, Location: bar
...
```
NPCs are assigned to roles at content load time. A line tagged `role: dock_worker` + `access: insider` fires for Kael (if smuggler has insider access to Kael) regardless of which NPC fills the dock_worker role. This is generator-compatible.
---
## Summary of Changes from Round 1
| Item | Round 1 | Round 2 | Change Reason |
|------|---------|---------|---------------|
| Maret pattern | SYSTEM | **WITNESS** | Story function > job description |
| Maret motivation | WITNESS | **SKEPTIC** | Compositional tension (WITNESS+SKEPTIC > WITNESS+WITNESS) |
| Resha motivation | SKEPTIC | **CIVILIAN** | Innocent disruption > deliberate questioning |
| Harek pattern | GHOST | **ANCHOR** | Present contentment > absent power |
| Drin pattern | REMNANT | **SYSTEM** | Institutional role > nostalgia (station too young for REMNANT) |
| Sabel pattern | THRESHOLD | **GHOST** | Absent influence > present gatekeeper |
| Olin motivation | SKEPTIC (dual) | **CIVILIAN** | Dropped dual designation. 1 per NPC. |
| Smuggler keys | 4 smuggler-specific | **4 generic perspective** | `threat_to_position`, `reliability`, `facade_status`, `moral_standing` — works for all 8 archetypes |
| EntityKnowledge total | 18 (14+4) | **18 (14+4)** | Same count, generic names |
| Triangle forks | Self-contained (tentative) | **Self-contained (confirmed)** | Independent state machines, shared NPC state |
| Panel pause | Not addressed | **50% sim speed, spacebar override** | Multiplicative toggle model |
docs/workshops/v01-content-scoping/round2-mellanie.md
-461
View File
@@ -1,461 +0,0 @@
# Round 2 — Mellanie (Copywriter)
## v0.1 Content Scoping Workshop
---
## Task 1: Canonical PC Voice Registers
These are authoring specs, not narrative documents. Every monologue line I write gets checked against these parameters. If a line doesn't match the register, it gets cut.
---
### Smuggler — Internal Voice Register
**One-line summary:** Watches people, not systems. Thinks in fragments. Worries about friends the way a dock worker worries — practically, physically, with the knot in the stomach, not the word for it.
#### Voice Parameters
| Parameter | Value | Example |
|---|---|---|
| **Sentence length** | Short. Fragments welcome. Rarely more than 2 sentences per monologue fire. | "Kael's here. Good." |
| **Vocabulary** | Concrete, physical, sensory. Uses trade jargon (containers, manifests, shifts, routes) without explaining it. No institutional language. | "Recycled air and cargo lubricant." Not: "Standard atmospheric recycling." |
| **Emotional register** | Feeling-first, analysis second. Names the gut before the brain catches up. | "Starting to worry" before "something's off." |
| **Relationship mode** | First-name basis with everyone. Thinks relationally — people are defined by connection, not role. | "Kael" not "Davan." "Voss is tense" not "the shift supervisor seems agitated." |
| **Observation priority** | People > environment > objects. Notices body language before noticing cargo. | "Kael keeps checking his lattice" before "Container 4471 is still in temp." |
| **Operational thinking** | Present when thinking about the job. Time-aware, route-aware, schedule-aware. But always filtered through "is this safe for my people?" | "Transition window opens in fifty minutes. After that, twenty minutes of reduced oversight." |
| **Self-reference** | Rare. The smuggler thinks about others, not herself. When self-reference occurs, it's through physical sensation. | "My stomach dropped" not "I feel betrayed." |
| **Humor** | Dry, situational, understated. Dark when stressed. Never witty — that's a different register. | "Home sweet home" about a cargo bay. |
| **What she doesn't do** | Doesn't analyze systems. Doesn't use institutional vocabulary. Doesn't explain things to herself that she already knows. Doesn't monologue in paragraphs. |
#### Voice Anchors (Reference Lines)
These 5 lines define the boundaries. Every smuggler monologue line should feel like it could sit next to these without register collision.
1. **Baseline warm:** *"Kael's already at the dock. Good. The day's better when he's on shift."*
— Short. Personal. Physical presence matters.
2. **Operational:** *"Shift transition in thirty minutes. If Voss kept the schedule thin, the route's clear."*
— Time-specific. Practical. Other people's actions determine safety.
3. **Concerned:** *"Kael keeps checking his lattice. Waiting for a message? Not like him to be jumpy."*
— Observation leads to interpretation. Interpretation is relational ("not like him"), not clinical.
4. **Hurt:** *"He looked left. He always looks left when he's making something up. Two years I've known that tell. Kael is lying to me."*
— Personal history weaponized. The "two years" is the knife. Ends with a flat declaration, not a question.
5. **Atmospheric:** *"Morning shift. Recycled air and cargo lubricant. Home sweet home."*
— Three fragments. Sensory detail. Irony through understatement.
#### Anti-Patterns (What the Smuggler Does NOT Sound Like)
- "I should investigate this anomaly further." (Too clinical. She'd think: "That's not right.")
- "The scheduling irregularity suggests systemic manipulation." (Institutional vocabulary. She'd think: "Voss changed the rotation again.")
- "I need to consider the implications of Kael's behavior for our operational security." (Analytical distance. She'd think: "What the hell is Kael doing?")
- "According to the manifest, container 4471 should weigh 240 kilograms." (Explaining what she already knows. She'd think: "4471's heavy. Too heavy.")
---
### Detective — Internal Voice Register
**One-line summary:** Categorizes first, feels second. Thinks in complete sentences. The institutional training runs in the background like an operating system — it never turns off, but sometimes the human overrides it.
#### Voice Parameters
| Parameter | Value | Example |
|---|---|---|
| **Sentence length** | Complete sentences, but not long ones. More structured than the smuggler. Occasional fragments for emphasis or snap judgments. | "Standard prefab, heavy foot traffic. Let's see what the shift change tells me." |
| **Vocabulary** | Institutional layer over plain speech. Professional terms leak in: "case file," "filing it," "noted," "flagged." Not technical jargon — investigative habit. | "Dock worker. Davan, K. Unremarkable on paper." The surname-comma-initial is institutional reflex. |
| **Emotional register** | Analysis-first, personal second. When personal breaks through, it's notable — a crack in the professional surface that signals emotional weight. | "She's not lying. But she's not telling me everything. Sera, what do you know?" — The first-name appeal at the end IS the emotion. |
| **Relationship mode** | Surname-first for targets and unknowns. First-name for allies and people he trusts. The shift from surname to first-name (or back) IS a relationship marker. | "Davan, K." early → "Kael" never (smuggler's FRIEND, not detective's). "Sera" always (detective's FRIEND). |
| **Observation priority** | Patterns > people > environment. Notices deviations from expected behavior before noticing the person. | "That's twice now" before "Sera leaves." The count matters more than the actor. |
| **Analytical thinking** | Automatic. Counts things, tracks frequencies, flags inconsistencies. Self-directs: "filing it," "noted," "coincidence?" These are internal bookkeeping prompts. | "Three times. Three excuses. That's data." |
| **Self-reference** | More common than the smuggler, but always through the professional lens. The detective monitors his own state as evidence. | "I'm reading too much into this" — self-aware about analytical bias. |
| **Humor** | Wry, observational. Appreciates irony at a distance. Can laugh at himself. Never cruel. | "Only place in this district that doesn't smell like freight lubricant." |
| **What he doesn't do** | Doesn't think in fragments (that's the smuggler). Doesn't use trade jargon he hasn't learned. Doesn't name-drop relationships he doesn't have. Doesn't express vulnerability directly — it leaks, he doesn't pour. |
#### Voice Anchors (Reference Lines)
1. **Clinical baseline:** *"Logistics hub. Standard prefab, heavy foot traffic. Let's see what the shift change tells me."*
— Categorize. Evaluate. Self-direct. Three operations in three sentences.
2. **Pattern recognition:** *"That's the third time. Sera leaves when Torek arrives. Three different excuses, same result. That's not coincidence."*
— Counting is automatic. Conclusion is flat and declarative. No hedging.
3. **Personal leak:** *"Good to see Sera. She always was the reliable one. At least someone in this district speaks my language."*
— First-name. Past tense ("always was") implies shared history. "My language" is institutional belonging.
4. **Conflicted:** *"Same booth. Same warm smile. Same offer to buy me a drink. ...Everything except whatever she's not saying."*
— Repetition builds the pattern. The ellipsis is the human catching up to the analyst. The final clause is the knife.
5. **Atmospheric:** *"Grain spirit and low conversation. Only place in this district that doesn't smell like freight lubricant."*
— Sensory but evaluative. The detective doesn't just notice smells — he catalogs them as data points.
#### Anti-Patterns (What the Detective Does NOT Sound Like)
- "Kael's here. Good." (Too terse. That's the smuggler. The detective would think: "Davan's on shift. Standard.")
- "I feel uneasy about Sera's behavior." (Direct emotional vocabulary. He'd think: "Something's off with Sera. Can't place it yet.")
- "This container has been tampered with, indicating smuggling activity." (Explaining the obvious. He'd think: "Weight's wrong. Noted.")
- "My heart sank when I saw the evidence." (Physical emotion — that's the smuggler's register. The detective: "Didn't want to see that. But there it is.")
---
### Voice Register Comparison — Same Observation, Two Characters
**Trigger: Seeing a container in temp storage overnight.**
- **Smuggler:** *"That container's been in temp since yesterday. Someone forgot to process it, or someone's stalling."*
— Concrete. Two explanations, both practical. No judgment yet.
- **Detective:** *"Container in overnight temp. Unusual for a hub this size — turnaround is normally sub-eight hours. Flag it."*
— Categorical. Quantified deviation. Self-directed action.
**Trigger: Entering the bar.**
- **Smuggler:** *"Lera's. Grain spirit and noise. Could use both right now."*
— Informal name. Sensory. Personal need.
- **Detective:** *"The Last Shift. Same crowd as yesterday. Let's see who's NOT here tonight."*
— Official name. Pattern comparison. Investigative frame.
**Trigger: Noticing Naia Tamm is upset.**
- **Smuggler:** *"Naia looks rough today. Should check on her later."*
— First-name. Immediate concern. Plans to act.
- **Detective:** *"Tamm seems distressed. Not her baseline. Something at home, or something she's heard?"*
— Surname. Clinical assessment. Hypothesizes cause.
**Trigger: Hearing raised voices behind a door.**
- **Smuggler:** *"Raised voices from the back room. Devra's in there. That's not a brokering call."*
— Identifies the person. Interprets through operational knowledge.
- **Detective:** *"Arguing behind that door. The bartender didn't flinch. Either she's used to it or she knows what it is."*
— Notes the non-reaction. Third-party behavior is data.
---
### Display Constraints (per Stig's R1 proposal)
Adopting Stig's parameters as authoring constraints:
| Constraint | Value | Implication for Writing |
|---|---|---|
| Max length | ~160 characters | Hard ceiling. Most lines should be 80-120. |
| Max visual lines | 2 | No three-line monologue. If it wraps to 3, cut it. |
| Display time | 4-6 seconds (length-adjusted) | Player reads at ~250 WPM = ~20-25 words in 5 seconds. Target: 15-25 words per line. |
| Fade behavior | Fade in/out | No abrupt text pops. Lines must read cleanly mid-fade. |
| Character tint | Smuggler: amber-white `#f0e0c8`, Detective: blue-white `#c8d8f0` | Voice must be distinguishable WITHOUT color — color confirms, doesn't create. |
**The 25-word rule:** If a monologue line exceeds 25 words, it better be the most important line in the pool. Most lines should be 10-18 words. The authoring guide examples average 14 words. That's the target.
---
## Task 2: THE FRIEND Content Pack — Kael Davan (Structure)
### What's In the Pack
The Kael Davan content pack is a single deliverable containing everything the engine needs to run THE FRIEND arc for the smuggler's path. It's also the benchmark — if this pack validates against the tag taxonomy, loads correctly, triggers appropriately, and sounds right, every subsequent content pack follows the same structure.
### Pack Contents
```
content/
districts/
sova-transit/
terminal/
dialogue.yaml # Kael's dialogue lines at The Terminal (shared pool)
monologue-smuggler.yaml # Smuggler monologue at Terminal (includes Kael observations)
monologue-detective.yaml # Detective monologue at Terminal (includes Kael observations)
bar/
dialogue.yaml # Kael's dialogue lines at The Last Shift
monologue-smuggler.yaml
monologue-detective.yaml
corridor/
dialogue.yaml # Kael's dialogue lines in Corridor B-7
monologue-smuggler.yaml
monologue-detective.yaml
```
**Note:** Kael's content lives inside location files, not a per-NPC file. Per D-035 and Tyre's directory design, dialogue is organized by location. Kael's lines appear in `terminal/dialogue.yaml` alongside other NPCs who speak at the Terminal. The `role: dock_worker` tag identifies which lines belong to Kael's template role.
The pack is authored as a single document, then split into location files during content conversion. For authoring purposes, I'll write it as one file with location headers and deliver the split files.
### Line Budget (Kael Davan)
| Content Type | Lines | Location Split |
|---|---|---|
| **Kael dialogue** | | |
| Greetings (5 access tiers) | 5 | Terminal: 3, Bar: 2 |
| Shift/work talk (insider, peer) | 8 | Terminal: 6, Bar: 2 |
| Bar casual (peer) | 4 | Bar: 4 |
| Ring coordination (insider) | 6 | Terminal: 3, Corridor: 3 |
| Deflection/evasion (post-contradiction) | 6 | Terminal: 3, Bar: 2, Corridor: 1 |
| Confrontation responses | 4 | Terminal: 1, Bar: 1, Corridor: 2 |
| Hael references (casual, unprompted) | 3 | Terminal: 1, Bar: 2 |
| **Dialogue subtotal** | **36** | |
| | | |
| **Smuggler monologue about Kael** | | |
| Phase 1 — Comfort (warmth, baseline) | 4 | Terminal: 2, Bar: 2 |
| Phase 2 — First Crack (concern, tells) | 4 | Terminal: 3, Bar: 1 |
| Phase 3 — Contradiction (alarm, shock) | 3 | Corridor: 2, Terminal: 1 |
| Phase 4 — Confrontation aftermath (hurt, conflict) | 3 | Terminal: 1, Bar: 1, Corridor: 1 |
| Phase 5 — Contaminated trust (doubt over warmth) | 4 | Terminal: 2, Bar: 1, Corridor: 1 |
| **Smuggler monologue subtotal** | **18** | |
| | | |
| **Detective monologue about Kael** | | |
| Identification / first observation | 2 | Terminal: 2 |
| Behavioral observation (tells noted) | 3 | Terminal: 2, Bar: 1 |
| Suspicion / analytical escalation | 3 | Terminal: 2, Corridor: 1 |
| Informant potential assessment | 2 | Terminal: 1, Bar: 1 |
| **Detective monologue subtotal** | **10** | |
| | | |
| **Tell observation lines** | | |
| Lattice checking (first + repeat) | 2 | Terminal: 2 |
| Shortened interactions / evasive | 2 | Terminal: 1, Bar: 1 |
| Looks-left tell (casual + confirmation) | 2 | Bar: 1, Corridor: 1 |
| Spatial deviation (Corridor B-7) | 2 | Corridor: 2 |
| **Tell subtotal** | **8** | |
| | | |
| **Trust-gated lines** (Kael's deeper dialogue) | | |
| Insider: ring operational talk | 6 | Terminal: 4, Corridor: 2 |
| Insider: close colleague warmth | 4 | Terminal: 2, Bar: 2 |
| Secret: hints about wanting out (pre-contradiction, rare) | 3 | Bar: 2, Corridor: 1 |
| **Trust-gated subtotal** | **13** | |
| | | |
| **Unprompted lines** (Kael volunteers) | | |
| Early: offers information, warmth | 3 | Terminal: 2, Bar: 1 |
| Late: warnings, deflections | 3 | Terminal: 1, Bar: 1, Corridor: 1 |
| **Unprompted subtotal** | **6** | |
| | | |
| **PACK TOTAL** | **91** | |
91 lines. Within the 70-100 range from D-034. The slight overcount gives me room to cut — better to write 91 and kill 10 weak ones than write 70 and wish I had more coverage.
### Arc Phase Mapping to Triggers + Prerequisites
This is the structural skeleton. Every line in the pack maps to one of these slots.
#### Phase 1: Comfort (0-10 min, RelationshipState: Friendly)
| Trigger | Prerequisite | Content Type | Count |
|---|---|---|---|
| `observe_npc` | `relationship_state: Friendly, subject: kael_davan` | Smuggler monologue: warmth | 2 |
| `observe_npc` | `relationship_state: Friendly, subject: kael_davan` | Smuggler monologue: routine fondness | 2 |
| `post_conversation` | `relationship_state: Friendly, subject: kael_davan` | Smuggler monologue: social comfort | 1 |
| NPC dialogue | `access: [insider, peer], trust: surface` | Kael greetings, shift talk | 8 |
| NPC dialogue | `access: [insider], trust: real` | Kael ring talk, colleague warmth | 6 |
| NPC dialogue (unprompted) | `access: [insider]` | Kael volunteers info | 2 |
**Phase 1 total: ~21 lines.** Heavy on dialogue (establish Kael's voice), lighter on monologue (smuggler's comfortable, not reflective).
#### Phase 2: First Crack (10-15 min, still Friendly, flags accumulating)
| Trigger | Prerequisite | Content Type | Count |
|---|---|---|---|
| `observe_anomaly` | `behavior_flags: lattice_checking` | Smuggler monologue: mild concern | 2 |
| `post_conversation` | `behavior_flags: evasive` | Smuggler monologue: worry | 2 |
| `observe_npc` (detective) | `relationship_state: Known, subject: kael_davan` | Detective monologue: behavioral note | 2 |
| NPC dialogue | `access: [insider, peer], trust: surface` | Kael: shorter, deflective | 4 |
| Tell observation | `behavior_flags` gates | Tells: lattice, shortened interactions | 3 |
**Phase 2 total: ~13 lines.** Tell observations ramp up. Dialogue gets clipped. Smuggler monologue shifts from fond to concerned.
#### Phase 3: The Contradiction (15-20 min, Friendly -> PersonOfInterest)
| Trigger | Prerequisite | Content Type | Count |
|---|---|---|---|
| `witness_interaction` | `relationship_state: Friendly, subject: kael_davan` | Smuggler monologue: shock/alarm (THE moment) | 2 |
| `observe_anomaly` | `contradiction_flagged: meeting_unknown_contact` | Smuggler monologue: processing | 1 |
| `observe_npc` (detective) | behavioral flags accumulating | Detective monologue: suspicion spike | 2 |
| Tell observation | `contradiction_flagged` | Spatial deviation tell | 2 |
**Phase 3 total: ~7 lines.** Fewest lines, highest stakes. Every word carries maximum weight. The contradiction monologue is the most important line in the pack.
#### Phase 4: Confrontation (20-25 min, PersonOfInterest)
| Trigger | Prerequisite | Content Type | Count |
|---|---|---|---|
| `post_conversation` | `tell_observed: looks_left_when_lying` | Smuggler monologue: the tell confirmation | 2 |
| `post_conversation` | `relationship_state: PersonOfInterest` | Smuggler monologue: hurt/conflict | 1 |
| NPC dialogue | `access: [insider], trust: surface` | Kael: deflection, evasion | 6 |
| NPC dialogue | `access: [insider]` | Kael: confrontation responses | 4 |
| NPC dialogue (unprompted) | `access: [insider]` | Kael: warnings | 2 |
| Tell observation | `tell_observed` gate | Looks-left confirmation | 1 |
**Phase 4 total: ~16 lines.** Dialogue-heavy — the confrontation is a conversation. Kael's evasion lines are the hardest to write because they must be plausible without being convincing.
#### Phase 5: Contaminated Trust (25-30 min, PersonOfInterest, new equilibrium)
| Trigger | Prerequisite | Content Type | Count |
|---|---|---|---|
| `observe_npc` | `relationship_state: PersonOfInterest, subject: kael_davan` + `contradiction_flagged` | Smuggler monologue: doubt over warmth | 3 |
| `return_visit` | `relationship_state: PersonOfInterest` | Smuggler monologue: location contamination | 1 |
| `time_idle` | `relationship_state: PersonOfInterest, subject: kael_davan` | Smuggler monologue: rumination | 1 |
| `observe_npc` (detective) | `secret_confidence: confirmed/suspected` | Detective monologue: informant potential | 2 |
| NPC dialogue | `access: [public], trust: surface` | Kael: surface normal (warmth locked out) | 4 |
| NPC dialogue | `access: [insider], trust: real` (if smuggler chose understanding path) | Kael: confession hints | 3 |
| Trust-gated: secret | Path A only | Kael: deeper truth | 2 |
**Phase 5 total: ~16 lines.** The contamination lines are the ones where voice discipline matters most — same warmth, new subtext. "Same old Kael" lines where the smuggler hears what used to be comfort and now hears a question.
### Cross-Phase Lines (Not Phase-Specific)
| Content Type | Count | Notes |
|---|---|---|
| Detective identification/first observation | 2 | Fires before detective has context on Kael |
| Kael Hael references (casual, any phase) | 3 | Establish relationship before it's load-bearing |
| Kael bar casual (not phase-gated) | 4 | Social texture |
| Detective pattern-forming observations | 3 | Cumulative, phase-independent |
| Kael insider ring coordination | 4 | Operational dialogue, pre-contradiction |
**Cross-phase total: ~16 lines.**
### Phase Total Reconciliation
| Phase | Lines | % of Pack |
|---|---|---|
| Phase 1: Comfort | 21 | 23% |
| Phase 2: First Crack | 13 | 14% |
| Phase 3: Contradiction | 7 | 8% |
| Phase 4: Confrontation | 16 | 18% |
| Phase 5: Contaminated Trust | 16 | 18% |
| Cross-phase | 16 | 18% |
| **Total** | **89** | ~98% (rounding) |
Close to the 91 estimate. The 2-line gap is margin for lines that emerge during writing — there's always one observation or reaction that only becomes obvious while you're in the character's head.
### Format (Sample YAML)
Each line in the pack looks like this. Showing one per phase to demonstrate prerequisite progression:
```yaml
# Phase 1: Comfort — smuggler sees Kael, no concerns
- id: terminal_m_010
character: smuggler
trigger: observe_npc
prerequisite:
relationship_state: Friendly
subject: kael_davan
text: "Kael's already at the dock. Good. The day's better when he's on shift."
mood: [fond]
topic: [colleague]
situation: [shift_start]
access: [insider, peer]
trust: surface
tags: [kael, baseline, pre_contradiction]
notes: "Phase 1 warmth. Establishes the bond."
# Phase 2: First Crack — smuggler notices tell
- id: terminal_m_011
character: smuggler
trigger: observe_anomaly
prerequisite:
all:
- relationship_state: Friendly
subject: kael_davan
- known_attributes:
subject: kael_davan
key: behavior_flags
value_contains: lattice_checking
text: "Kael keeps checking his lattice. Waiting for a message? Not like him to be jumpy."
mood: [concerned]
topic: [colleague]
situation: [routine]
access: [insider]
trust: real
tags: [kael, tell, first_crack]
# Phase 3: Contradiction — the moment
- id: corridor_m_010
character: smuggler
trigger: witness_interaction
prerequisite:
relationship_state: Friendly
subject: kael_davan
text: "Kael? Down here? And that's — I don't know them. Not crew, not ring. Who the hell is that?"
mood: [concerned]
topic: [colleague]
situation: [observation]
access: [insider]
trust: real
tags: [the_friend, contradiction, kael, critical_moment]
notes: "THE CONTRADICTION. Sets contradiction_flagged. Green -> amber."
# Phase 4: Tell confirmation — the knife
- id: corridor_m_011
character: smuggler
trigger: post_conversation
prerequisite:
all:
- relationship_state: PersonOfInterest
subject: kael_davan
- known_attributes:
subject: kael_davan
key: tell_observed
value: looks_left_when_lying
text: "He looked left. Always looks left when he's making something up. Two years, Kael. I know your tells."
mood: [conflicted]
topic: [trust]
situation: [confrontation]
access: [insider]
trust: real
tags: [the_friend, kael, tell_confirmation]
# Phase 5: Contaminated trust — the new normal
- id: terminal_m_015
character: smuggler
trigger: observe_npc
prerequisite:
all:
- relationship_state: PersonOfInterest
subject: kael_davan
- known_attributes:
subject: kael_davan
key: contradiction_flagged
value: meeting_unknown_contact
text: "Same old Kael. Same jokes, same routine. ...What are you not telling me?"
mood: [conflicted]
topic: [colleague]
situation: [routine]
access: [insider]
trust: real
tags: [kael, the_friend, contaminated_trust]
```
### Dependencies Before I Can Write the Full Pack
| Dependency | Owner | Status | Impact if Missing |
|---|---|---|---|
| Content directory structure confirmed | Tyre | Round 2 (expected) | I write the pack as a single doc and split later — not blocking |
| FactId catalog (smuggler path entries) | Gestalt / Paula | Gap 5 from tracking | I use authoring-guide FactIds as placeholders, replace when catalog lands |
| EntityKnowledge key resolution (4 vs 8 keys) | Gestalt / Paula | D-03 disagreement | I write prerequisites using the Round 1 key names, adapt to winner |
| Monologue display constraints | Stig | R1 proposal: ~160 char, 2-line, 4-6 sec | Adopted. Writing to these constraints now. |
| NPC pattern/motivation mapping finalized | Gestalt | Round 2 (lead awarded to Gestalt) | Doesn't change Kael's content — he's FRIEND+OPERATOR regardless |
**None of these are hard blockers.** The biggest risk is FactId placeholder drift — if the final catalog changes `contraband.ring_exists` to `smuggling.ring_confirmed`, I have to search-replace across the pack. Manageable, but annoying at scale. I'd rather the catalog stabilizes before I author all 695 items.
### Authoring Timeline
**Kael pack (91 lines):** I can draft the full pack once this workshop closes. Dialogue lines require the most iteration (Kael's voice under pressure is tricky — evasive without sounding scripted). Monologue lines are faster (I've been living in both character registers for two workshops now). Tell lines are mechanical — they map directly to the wiki's tell system table.
Estimate: full draft in one session. Review pass in a second. Revision after Gestalt validates tags and Dudley confirms prerequisites fire correctly.
**Sera pack follows immediately.** Different contradiction mechanics (cumulative pattern vs. single observation), different voice (Sera's precision vs. Kael's brevity), same structure. Lessons from Kael's pack inform Sera's.
---
### Note on the 695 Number
Round 1 tracking (A-06) flags my 695 total as "needs validation from others." Let me be clear about what it is and isn't:
- **695 is the authored floor.** Below this, the 30-minute session has gaps — locations without environmental text, NPCs without enough dialogue variation, monologue pools that repeat.
- **695 is not the generation-expanded total.** D-028 specifies a 4x generation pass for dialogue ("write 10, generate 40"). If we apply that to the ~350 dialogue lines, the engine sees ~1,400 dialogue lines. But the 350 are what I hand-write.
- **695 doesn't include content the engine generates.** Routine greetings, time-of-day variations, personality-trait transformations — those are generation-pass output, not authored input.
The number to track is **695 authored items.** That's the scope. That's what I deliver.
---
*Mellanie, Round 2. Voice registers defined, pack structure mapped, dependencies identified. Ready to write the benchmark.*
docs/workshops/v01-content-scoping/round2-paula.md
-367
View File
@@ -1,367 +0,0 @@
# Round 2 — Paula (Narrative & Political Depth)
## Task 1: NPC Pattern/Motivation Mapping — v0.2 Emotional Layer
Gestalt's mechanical mapping is canonical for v0.1. Accepted.
But the versioned approach creates something valuable: **two analytical lenses on the same NPCs.** Gestalt maps from function ("What does this NPC do in the system?"). I map from meaning ("What does this NPC mean to the story?"). For v0.1, function drives implementation. For v0.2, meaning drives emotional depth expansion.
Here's every disagreement annotated with what the v0.2 emotional layer adds:
### Disagreement Resolution + v0.2 Notes
| NPC | v0.1 (Gestalt) | v0.2 Layer (Paula) | What the v0.2 Layer Adds |
|-----|----------------|-------------------|--------------------------|
| **Voss** | SYSTEM + OPERATOR | SYSTEM + HANDLER | v0.1 Voss runs schedules (OPERATOR). v0.2 Voss manages people through scheduling authority — the resentment, the fear, the performative competence hiding real vulnerability. HANDLER unlocks Voss-specific monologue about being trapped between institutional role and criminal obligation. "I manage people. They just don't know who I'm managing them for." |
| **Devra** | THRESHOLD + HANDLER | THRESHOLD + OPERATOR | v0.1 Devra manages from above (HANDLER). v0.2 Devra runs the operation's machinery — she's the most competent person in the ring and knows it. OPERATOR unlocks content about Devra's ambition, her quiet belief she could run this better than Nils, her frustration at being the brain behind someone else's decisions. |
| **Maret** | SYSTEM + WITNESS | WITNESS + SKEPTIC | v0.1 Maret is the institutional scheduler who saw something (SYSTEM+WITNESS). v0.2 Maret doubts — not just "the numbers are off" but "the entire system I trusted is corrupt, and I'm complicit by filing clean reports." SKEPTIC unlocks Maret's crisis of institutional faith, the thing that makes her more than a data point for the detective. |
| **Resha** | CATALYST + SKEPTIC | CATALYST + CIVILIAN | v0.1 treats Resha's questions as genuine skepticism (SKEPTIC). v0.2 adds the tragedy: Resha is a CIVILIAN who accidentally became a CATALYST. She's not questioning the system — she's trying to learn it. The system is so broken that LEARNING it is disruptive. CIVILIAN unlocks content about Resha's bewilderment when people react to her innocent questions with fear. |
| **Harek** | GHOST + HANDLER | ANCHOR + HANDLER | v0.1 Harek shapes events through debt leverage (GHOST+HANDLER). v0.2 adds: Harek embodies contentment. He's the man who has enough, wants nothing more, and whose comfortable complacency created a tool for others without him meaning to. ANCHOR unlocks content about unconscious complicity — the "Is this enough?" question answered by someone who never thought to ask it, whose answer is "yes" while his comfort enables harm. |
| **Drin** | REMNANT + TURNCOAT | SYSTEM + TURNCOAT | v0.1 Drin remembers simpler times (REMNANT). v0.2 adds: Drin IS the inspection system. His compromise doesn't just corrupt a person — it corrupts the institutional process itself. SYSTEM unlocks content about institutional rot as metaphor: when the inspector is compromised, what does "inspection" even mean? |
| **Sess** | ANCHOR + CIVILIAN | NOBODY + CIVILIAN | v0.1 Sess embodies quiet contentment (ANCHOR). v0.2 adds: Sess is invisible — social wallpaper that the player walks past twenty times before realizing the bartender has seen everything. NOBODY unlocks dynamic tier promotion content for v0.2: the moment the player invests in Sess, the quiet contentment reveals itself as an observation post. |
| **Olin** | CATALYST + SKEPTIC | CATALYST + CIVILIAN | v0.1 gives Olin dual motivation (ambiguity). v0.2 resolves the ambiguity per playthrough: some seeds, Olin IS a skeptic (asking questions because they're probing). Other seeds, Olin is a civilian (asking questions because they genuinely need work). The randomized motivation resolution is a v0.2 generator feature. |
| **Sabel** | THRESHOLD + OPERATOR | GHOST + OPERATOR | v0.1 Sabel is the off-station gatekeeper (THRESHOLD). v0.2 adds: Sabel is absent power — the upstream force shaping local events. GHOST unlocks content about Sabel's indifference: Sabel doesn't care about Sova's people, only about the supply chain. If the operation burns, Sabel moves on. That coldness is narrative content for v0.2 (the player discovers the ring is disposable to its supplier). |
| **Tav** | SYSTEM + CIVILIAN | NOBODY + OPERATOR | v0.1 Tav follows ring lookout procedure (SYSTEM+CIVILIAN). v0.2 adds: Tav is peripheral, barely visible, the lowest rung. NOBODY unlocks tier promotion content — the player who notices Tav discovers a young person trapped in a role they barely understand, doing dangerous work because someone told them it mattered. |
### What the v0.2 layer means for content planning
The v0.2 layer adds **~30-50 authored lines per NPC** of emotional-depth content: expanded monologue pools, deeper dialogue gating, and pattern-specific interaction triggers (e.g., ANCHOR contentment dialogues, NOBODY promotion paths, GHOST influence chains). This is the "write 10, generate 40" Tier 2 expansion target.
For now, Gestalt's v0.1 mapping governs implementation. My mapping governs the content roadmap. Both are correct — they describe different layers of the same characters.
---
## Task 2: The Key Bloat Question — Generic Assessment Architecture
The lead asks: "If the original EntityKnowledge set was incomplete for the smuggler, are we doing this again for the administrator or the corporate tycoon?"
**The honest truth: No, but only if we name the keys correctly.**
### The Problem With "Smuggler-Specific" Keys
Gestalt proposed 4 new keys: `exposure_risk`, `loyalty_assessment`, `cover_integrity`, `moral_weight`. These are described as "smuggler-specific." But look at what they actually capture:
| Key | What It Really Measures | Is This Smuggler-Specific? |
|-----|------------------------|---------------------------|
| `exposure_risk` | "How much does this NPC's behavior threaten my current interests?" | No. An administrator assesses exposure risk too — but it's political exposure, not operational. |
| `loyalty_assessment` | "Where does this NPC's loyalty lie relative to me?" | No. Every archetype navigates loyalty networks. |
| `cover_integrity` | "Is my position/identity intact around this person?" | No. An administrator's "cover" is their public reputation. A newcomer's "cover" is their attempt to blend in. |
| `moral_weight` | "How much moral cost do I carry in this relationship?" | No. Already generic. Every human feels guilt, complicity, or indifference. |
These aren't smuggler keys. They're **role-perspective assessment keys** that every archetype uses with different semantics.
### The Generic Architecture
**Proposal: 6 role-perspective keys that work for all 8 archetypes.** Same keys, archetype-specific interpretation, zero per-archetype schema bloat.
| Generic Key | Smuggler Interpretation | Detective Interpretation | Administrator | Newcomer | Merchant |
|------------|------------------------|------------------------|---------------|----------|----------|
| `risk_assessment` | Exposure of ring operations | Exposure of investigation | Exposure of political position | Vulnerability as an outsider | Exposure of trade relationships |
| `loyalty_assessment` | Loyal to the ring? | Cooperative with investigation? | Aligned with my faction? | Willing to help a newcomer? | Reliable trade partner? |
| `position_integrity` | Is my cover identity holding? | Is my authority respected? | Is my reputation intact? | Am I blending in? | Is my business relationship secure? |
| `moral_weight` | Guilt about complicity | Guilt about using people | Guilt about political compromises | Guilt about disrupting others | Guilt about exploiting information |
| `tell_observed` | Behavioral tell suggesting ring exposure | Behavioral tell suggesting concealment | Political tell (nervous in meetings) | Social tell (who's welcoming, who's not) | Commercial tell (price sensitivity, evasion) |
| `contradiction_flagged` | Behavior contradicts ring loyalty | Behavior contradicts claimed innocence | Behavior contradicts public stance | Behavior contradicts stated welcome | Behavior contradicts stated terms |
**The values use the same enums.** `risk_assessment: "high"` means different things to different archetypes, but the schema is identical. The content authoring guide (the archetype brief, the voice register, the monologue prerequisite rules) provides the interpretation. The knowledge graph stores data; the content layer provides meaning.
### Why This Works
Let me complicate this by testing it against the hardest case. The **Insider** archetype (the community member, the person embedded in the social fabric). Does `risk_assessment` work?
- Insider's `risk_assessment` of Kael: "How much does Kael's behavior threaten the community I'm part of?" Value: `"moderate"` — Kael's nervousness is unsettling but hasn't caused concrete harm yet.
- Insider's `loyalty_assessment` of Voss: "Where does Voss's loyalty lie — with the shift crew or with whoever's pressuring him?" Value: `"uncertain"` — Voss seems stressed but still functional.
- Insider's `position_integrity` assessment of themselves near the detective: "Does the detective's presence threaten my standing in the community?" Value: `"stressed"` — people are nervous, the community is pulling inward, and the insider's position as a trusted neighbor is complicated by anyone who cooperates with authorities.
It works. Same keys. Different lens. Zero schema change.
### What IS Archetype-Specific
The archetype-specific content lives in three places, none of which are EntityKnowledge keys:
1. **Monologue prerequisite interpretation.** The prerequisite `risk_assessment == "high"` triggers different monologue lines per archetype. The smuggler thinks: "Torek's spending is going to get us caught." The administrator thinks: "Torek's spending is drawing Commission attention to the district." Same trigger, different pool, same key.
2. **Dual-lens section in NPC profiles.** Every NPC profile already has per-character lens sections. For 8 archetypes, this becomes an archetype-lens section per NPC — but that's content authoring, not schema work. And at 300-world scale, the generator produces these from archetype brief + NPC profile + composition rules.
3. **Voice register.** The smuggler's internal voice is operational and terse. The detective's is analytical and institutional. An administrator's would be political and strategic. A newcomer's would be uncertain and observational. These registers shape how the same knowledge is expressed, not what knowledge exists.
### The Practical Answer
**For v0.1:** Rename Gestalt's 4 keys to the generic versions:
| Current (Gestalt's v0.1) | Renamed (Generic) | Change Required |
|--------------------------|-------------------|-----------------|
| `exposure_risk` | `risk_assessment` | Rename in schema + content |
| `loyalty_assessment` | `loyalty_assessment` | No change — already generic |
| `cover_integrity` | `position_integrity` | Rename in schema + content |
| `moral_weight` | `moral_weight` | No change — already generic |
2 renames. That's it. The v0.1 smuggler and detective content is authored against the generic keys. When v0.2 adds the Newcomer archetype, the Newcomer's knowledge graph uses the same 6 role-perspective keys with Newcomer-specific content. Zero schema changes. Zero key bloat.
**For v0.2+:** `social_debt` and `loyalty_conflict` (Gestalt's deferred keys) should also be evaluated against this lens. `social_debt` generalizes cleanly (every archetype navigates obligations). `loyalty_conflict` may fold into `loyalty_assessment` + `behavior_flags` as Gestalt argued. That's a v0.2 decision.
**Total key count per archetype: 20** (14 shared + 6 role-perspective). Same for smuggler, detective, administrator, merchant, newcomer, insider, fixer, exile. No per-archetype keys. No bloat. The schema scales to 8 archetypes without modification.
### What SUSTAINS This Across 8 Archetypes
The keys are the skeleton. The archetype brief is the muscle. Each archetype needs:
1. A **voice register** (how their monologue sounds)
2. An **assessment framework** (what "risk" means to them, what "loyalty" means)
3. A **moral arc** (what their version of Comfort → Doubt → Reckoning → Compromise looks like)
These are content documents, not schema changes. They live in the authoring guide, not the codebase. Mellanie writes them; Paula designs them; Gestalt validates that the mechanical triggers work.
The smuggler moral arc (Comfort → Doubt → Reckoning → Compromise) is the prototype. Every archetype gets a 4-phase arc with the same structure and different content. The administrator's arc might be: Authority → Doubt → Reckoning → Adaptation. The newcomer's: Wonder → Doubt → Reckoning → Belonging-or-Departure.
But the keys don't change. The keys are the infrastructure. The content is the building.
---
## Task 3: Wiki Fix Execution Plan
### Prioritized Execution Order
The changes are ordered by dependency — later items reference earlier items' outputs.
| Priority | Change | Files Affected | Content Status | Estimated Effort |
|----------|--------|---------------|----------------|-----------------|
| **P0-1** | Naia Tamm rename | 16 files | Cascade plan ready (Round 1). Content changes specified per-file. | ~2 hours (mechanical, but must be thorough) |
| **P0-2** | Nils Davan stub page | 1 new file + 3 cross-ref updates | Full draft ready (Round 1). | ~30 min |
| **P0-3** | Drin Tier 2 expansion | 1 file rewrite + index update | Full draft ready (Round 1). 7 new axes, voice sample, tell system. | ~1 hour |
| **P1-1** | Canonical name application | 10 NPC profile headers + index | Name table ready (Round 1). 3 names need Miri validation. | ~1 hour |
| **P1-2** | Triangle 1 escalation fork | index.md triangle section + Kael/Voss notes | 5-beat sequence designed (Round 1). Self-contained per D-INTERACT. | ~1 hour |
| **P2-1** | Smuggler-lens sections (all 17 NPCs) | 17 NPC profile files | Template designed (Round 1). Per-NPC content requires authoring. | ~8-10 hours |
| **P2-2** | PC-as-NPC profiles | 2 new files | Gap identified (Round 1). Content not yet drafted. | ~3-4 hours |
| **P2-3** | FactId catalog — smuggler entries | 1 file | Gap identified (Round 1). Entries not yet drafted. | ~2 hours |
### P0-1: Naia Tamm Rename — Execution-Ready Content
Below is the exact content change needed for each file. I'm specifying what to find and what to replace so this can be executed mechanically.
#### File 1: `wiki/npcs/hael.md` → rename to `wiki/npcs/naia-tamm.md`
Full rewrite of the file header and all internal references. Key structural changes:
**Old header:**
```markdown
# Hael
**Tier 2 NPC** | The Last Shift (Bar) | Mundane
```
**New header:**
```markdown
# Naia Tamm — THE MIRROR
**Tier 1 (MIRROR) NPC** | The Last Shift (Bar) | Mundane
```
**Core Identity section changes:**
- `**Name**: Hael` → `**Name**: Naia Tamm`
- Add: `**Canonical ID**: krenn.naia-tamm`
- Add: `**Pattern**: MIRROR (no contradiction arc, no secret)`
- Add: `**Motivation**: CIVILIAN (v0.1 mechanical mapping)`
**All internal "Hael" references** → "Naia Tamm" (formal) or "Naia" (casual/dialogue). The Krenn convention (D-036) is first-name-primary in social contexts, so dialogue and monologue use "Naia." Profile text and cross-references use "Naia Tamm."
**Secret/Vulnerability section** — must be reframed for MIRROR pattern:
```markdown
### 2. Secret / Vulnerability
**Surface secret**: None. Naia has no secrets. This is THE MIRROR's
defining trait.
**Deep secret**: None. Naia Tamm is the one person in the district who
is exactly what she appears to be — a teacher worried about her partner.
The MIRROR's power is simplicity. When events drag Naia into the
conspiracy (through Kael's ring involvement, through Sera's concealment),
the damage is devastating precisely because Naia was genuine.
**Vulnerability**: Emotional exposure. Naia's worry about Kael is visible,
exploitable, and honest. She has no defenses because she has no agenda.
The detective can cultivate Naia as a source without guilt — until the
consequences of that cultivation become apparent.
```
**Content requirements section** — update for MIRROR-specific depth:
```markdown
## Content Requirements (MIRROR — Tier 1 Emotional Depth)
**~50-70 authored lines total** (no generation expansion):
- **20-25 dialogue lines**: Bar greetings (3), Kael-related conversation
(8-10), Sera interaction (4-5), school/community (3-4), response to
bad news (3-5)
- **8-12 trust-gated lines**: Honest disclosures about Kael's behavior
changes, emotional confessions about the relationship, what Naia has
told Sera
- **5-8 unprompted lines**: Naia volunteers worry about Kael, asks
about Kael if the player has seen him, mentions school events
- **8-12 monologue lines per character**:
- Smuggler monologue about Naia: guilt (4-5 — "She doesn't know.
She can never know."), protectiveness (3-4), moral weight (2-3)
- Detective monologue about Naia: sympathy (3-4 — "The partner.
Worried. Doesn't know what I know."), source assessment (2-3),
moral cost of using her (3-4)
- **3-5 tell observation lines**: Visible stress, checking for Kael,
increased bar presence, confiding in Sera
- **NO contradiction discovery lines** — THE MIRROR has no contradiction.
The emotional payload comes from what happens TO Naia, not what Naia
hides.
```
**Cross-reference links at bottom:**
```markdown
**Cross-References:** [Kael Davan](kael-davan.md), [Sera Venn](sera-venn.md),
[Lera Sessik](lera-sessik.md)
```
#### File 2: `wiki/npcs/index.md`
**Roster table row 9:**
- Old: `| 9 | Hael | Teacher (Kael's Partner) | Bar | Tier 2 | Mundane | Worried Partner |`
- New: `| 9 | **Naia Tamm** | Teacher (Kael's Partner) | Bar | **Tier 1 (MIRROR)** | Mundane | Worried Partner |`
**Triangle 4 diagram (3 label changes):**
```
Naia Tamm (Teacher, Kael's Partner)
/ \
worried about confides in friend
Kael's late nights, |
evasive answers |
| |
Kael (Dock Worker) <--friendship--> Sera (Commission Field Tech)
```
**Triangle 4 description text** — every "Hael" → "Naia Tamm" (formal) or "Naia" (in-character). Approximately 8 replacements.
**Social site listing — The Last Shift:**
- Old: `- Hael (Teacher) — Kael's partner, worried`
- New: `- Naia Tamm (Teacher) — Kael's partner, worried`
**Content Deliverables section:**
- Move Naia Tamm from "Tier 2" list to a new "Tier 1 (MIRROR)" subsection, or note the tier change explicitly.
#### File 3: `wiki/index.md`
**NPC listing:**
- Old: `- [Hael](npcs/hael.md) — Kael's partner (referenced)`
- New: `- [Naia Tamm](npcs/naia-tamm.md) — Kael's partner, THE MIRROR`
Also move from "Tier 2" to a new bullet under Tier 1:
```markdown
- **Tier 1 (MIRROR):**
- [Naia Tamm](npcs/naia-tamm.md) — Kael's partner, teacher
```
#### File 4: `wiki/npcs/kael-davan.md` (~20+ replacements)
This is the heaviest file. Every "Hael" becomes "Naia" in dialogue/monologue contexts and "Naia Tamm" in descriptive/profile contexts. Key sections:
- **Axis 1 (Want), Secondary**: "Protect Hael (partner)" → "Protect Naia (partner)"
- **Axis 2 (Secret)**: "Hael doesn't know about the smuggling" → "Naia doesn't know about the smuggling"
- **Relationship 2 header**: "Hael (partner, teacher, civilian)" → "Naia Tamm (partner, teacher, civilian)"
- **Relationship 2 body**: All "Hael" → "Naia" (casual reference in relationship description)
- **Axis 4 (Tolerance)**: "Hael's increasing worry" → "Naia's increasing worry"
- **Axis 5 (Routine)**: "Home with Hael" → "Home with Naia"
- **Axis 6 (Information)**: "Hael's worry" → "Naia's worry", "Hael talked to Sera" → "Naia talked to Sera"
- **Axis 7 (Contentment)**: "guilt about lying to Hael" → "guilt about lying to Naia"
- **Voice sample**: "I'm fine, Hael" → "I'm fine, Naia" (Mood: Protective line)
- **Dual-lens notes**: All Hael references
- **Triangle 4 role notes**: All Hael references
- **Secret section**: All Hael references
- **Contradiction arc**: Multiple references throughout all 5 phases
- **Authoring notes**: "Hael references" → "Naia references"
File link in cross-references:
- Old: `[Hael](hael.md)` (if present)
- New: `[Naia Tamm](naia-tamm.md)`
#### File 5: `wiki/npcs/sera-venn.md` (~15 replacements)
Same pattern as Kael. Key sections:
- **Axis 1 (Want), Secondary**: "Protect Hael" → "Protect Naia Tamm"
- **Relationship 2**: Full section rewrite — "Hael" → "Naia" / "Naia Tamm"
- **Axis 4, 5, 6, 7**: All Hael references
- **Tell system**: References to Hael observing Sera's avoidance
- **Voice sample**: "Hael was here earlier" → "Naia was here earlier"
- **Triangle 4 role notes**: All Hael references
- **Secret section**: All Hael references
- **Contradiction arc**: Hael references throughout
- **Authoring notes**: "Hael references" → "Naia references"
#### Files 6-16: Lighter touch changes
| File | Changes |
|------|---------|
| `wiki/npcs/lera-sessik.md` | Axis 6 info inventory: "Hael's worry about Kael" → "Naia Tamm's worry about Kael" |
| `wiki/npcs/maret-korr.md` | Axis 5 routine: "goes for Hael's company" → "goes for Naia's company" |
| `wiki/authoring/monologue-guide.md` | Any monologue examples referencing Hael |
| `wiki/locations/krenn-system/the-last-shift.md` | NPC presence list, social dynamics |
| `wiki/world/sova-transit-district.md` | NPC references |
| `wiki/factions/the-ring.md` | Kael vulnerability references |
| `wiki/knowledge/relationship-states.md` | Example entries |
| `wiki/knowledge/entity-attributes.md` | Example entries |
| `wiki/knowledge/fact-catalog.md` | FactId entries: `npc.hael.*` → `npc.naia_tamm.*`, `relationship.kael.hael` → `relationship.kael.naia_tamm` |
| `wiki/world/krenn-system.md` | Naming examples list: "Hael" → keep (it's a valid Krenn first name), but add "Naia" to the list if not present |
| `decisions/content.md` | D-034: "partner Hael" → "partner Naia Tamm". D-036: naming examples list update. |
### P0-2: Nils Davan Stub — Execution-Ready Content
The full stub page draft was provided in my Round 1 response. It's ready to write to `wiki/npcs/nils-davan.md`.
**Cross-reference updates needed after creation:**
| File | Change |
|------|--------|
| `wiki/npcs/index.md` | Add Nils to the Smuggling Ring social site listing. Add to roster table as off-stage NPC. |
| `wiki/index.md` | Add `[Nils Davan](npcs/nils-davan.md) — Ring coordinator (off-stage)` to NPC listing. |
| `wiki/npcs/kael-davan.md` | Add cross-reference link at bottom: `[Nils Davan](nils-davan.md)` |
| `wiki/npcs/voss.md` | Add cross-reference link |
| `wiki/npcs/devra.md` | Add cross-reference link |
| `wiki/npcs/renn.md` | Add cross-reference link |
### P0-3: Drin Tier 2 Expansion
Full 7-axis draft provided in Round 1. Gestalt confirms promotion (A-01 consensus). Execution:
1. Rewrite `wiki/npcs/drin.md` from Tier 3 format to Tier 2 format using my Round 1 draft
2. Update `wiki/npcs/index.md` roster table: Tier 3 → Tier 2, update entanglement
3. Update `wiki/index.md`: Move Drin from Tier 3 listing to Tier 2
4. Add Gestalt's v0.1 mapping to header: `**Pattern**: REMNANT | **Motivation**: TURNCOAT`
### P1-1: Canonical Names
Apply the name table from Round 1. **Three names need Miri validation** before applying: Drin Vassar, Sess Torin, Tav Lenn. Olin deliberately omits surname (narrative choice). Sabel deliberately omits surname (off-station character).
### P1-2: Triangle 1 Escalation Fork
**Important: Self-contained per Tyre's recommendation (confirmed by lead as D-INTERACT).** My Round 1 design included cross-triangle cascade (Path B feeding Triangle 2 via Maret). For v0.1, the fork must be self-contained.
Revised Triangle 1 fork — self-contained version:
The 5-beat structure stays the same, but Beat 5 consequences are resolved WITHIN Triangle 1:
| Path | Self-Contained Consequence | What Does NOT Cascade |
|------|---------------------------|----------------------|
| **A (Back Voss)** | Nils is angry at Kael. Kael is frightened. Smuggler feels responsible. | Nils's anger does not trigger Pell's crisis (Triangle 5). |
| **B (Back Nils)** | Voss capitulates but is visibly rattled. Fourth manifest revision happens. | The manifest revision does NOT trigger Maret's discovery (Triangle 2). Maret discovers independently. |
| **C (Stay neutral)** | Nils acts unilaterally. Operation is sloppier. Smuggler's standing drops. | The sloppy operation does NOT make the detective's investigation easier. Detective's timeline is independent. |
This keeps Triangle 1 testable in isolation while preserving the emotional weight of each choice. Cross-triangle cascade becomes a v0.2 feature when the storyteller can manage multi-triangle state.
### Execution Dependencies
```
P0-1 (Naia Tamm rename) ─── no dependencies, start immediately
P0-2 (Nils stub) ─── no dependencies, start immediately
P0-3 (Drin expansion) ─── blocked by A-01 formalization (consensus confirmed)
P1-1 (Canonical names) ─── blocked by Miri validation (3 names)
P1-2 (Triangle 1 fork) ─── depends on P0-2 (Nils stub must exist first)
P2-1 (Smuggler-lens) ─── depends on key bloat resolution (Task 2 above)
P2-2 (PC-as-NPC) ─── depends on P2-1 (smuggler-lens template establishes format)
P2-3 (Smuggler FactIds) ─── depends on P2-1
```
**P0-1 and P0-2 can start immediately and run in parallel.** I recommend these as the first Sprint 3 copy team commits.
docs/workshops/v01-content-scoping/round2-si.md
-290
View File
@@ -1,290 +0,0 @@
# Round 2 — SI (Project Manager)
## Finalized Ticket List for v0.1 Content Scoping
Incorporates: all 7 Round 1 responses, Qatux tracking doc, lead decisions (D-NPC, D-FORMAT, D-INTERACT, D-PAUSE).
---
## 1. Lead Decisions — Impact on Tickets
| Decision | Ticket Impact |
|----------|---------------|
| **D-NPC:** Gestalt's mechanical mapping wins for v0.1 | NEW-1 simplified: "apply Gestalt's mapping" (not resolve disagreements). Paula's emotional layer becomes v0.2 annotation. |
| **D-FORMAT:** YAML for content, RON converter available | Confirms C-series as YAML. Adds NEW-8: RON converter tool. |
| **D-INTERACT:** Single action for v0.1, multi-verb architecture underneath | NEW-7 reframed. Adds NEW-9 (server: InteractionOptions) + NEW-10 (client: extensible prompt). |
| **D-PAUSE:** Spacebar always pauses, overlays = 50% sim speed | Adds NEW-11 (server: tick rate scaling) + NEW-12 (client: pause state machine). |
---
## 2. Round 1 Consensus — Impact on Tickets
| Consensus Item | Ticket Impact |
|----------------|---------------|
| **A-01:** Drin promoted to Tier 2 | NEW-2 changes from "evaluation" to "execute promotion" — expand profile. |
| **A-02:** NOBODY deferred to v0.2 | No v0.1 ticket. Hidden data ships in NPC YAML files (handled by C-series). |
| **A-05:** ~200 monologue lines | Sizes NEW-4 at ~200 lines (~100 per character). |
| **A-06:** ~695 total authored items | Overall content scope validation. No new ticket, but informs sprint capacity. |
| **A-07:** 3 active + 2 passive triangles | Confirms A11 scope (Triangle 1 only needs fixing). T3/T5 need less work. |
| **A-11:** THE FRIEND is critical path | Confirms #261 → #297/#298 chain is the highest-priority dependency. |
| **A-12:** Client receives text from server | No client-side content loading tickets needed. Simplifies client scope. |
| **A-14:** PC-as-NPC confirmed for v0.1 | Validates B3, B5, NEW-6. |
| **A-15:** News ticker confirmed for v0.1 | #306 confirmed. Scope: ~20 headlines. |
| **A-17:** Self-contained triangle forks | Reduces C8 complexity (no cross-triangle cascade logic). |
| **Tyre: Line previewer CLI** | Adds NEW-13. |
| **Paula: 7 additional wiki gaps** | Gaps 1-5 already covered by existing tickets. Gap 6 (location smuggler detail) → folded into content conversion. Gap 7 (Harek triangle membership) → folded into NEW-1 mapping. |
---
## 3. Existing Ticket Updates (Revised)
| ID | Title | Action | Sprint Target |
|----|-------|--------|---------------|
| #368 | Knowledge vocabulary for v0.1 content | **Close** — wiki at `wiki/` is the delivered output | Sprint 2 (done) |
| #369 | Wiki Review Workshop Outputs (epic) | **Repurpose** as parent epic for all v0.1 content scoping tickets. Update description. | — |
| #301 | Wiki taxonomy and structure | **Assign to copy.** Downscope: Sova district structure only for v0.1. Full 500+ world taxonomy is generator-era. | Sprint 3 |
| #319 | Krenn System wiki entry | **Merge with A3.** Expanded: wiki page + seed.yaml reference implementation. Assign to copy. | Sprint 4 |
| #261 | Dual Lens Authoring Guide | **CRITICAL PATH ROOT.** Assign to copy. Owner: Paula. Blocks 9 downstream tickets. | Sprint 3 (P0) |
| #310 | Character voice speech patterns | **Subsume into B4** (smuggler voice card + moral arc). B4 is the larger ticket. Close #310 when B4 lands. | Sprint 3 (via B4) |
| #306 | News ticker / Meridian feed content | **Confirm scope:** ~20 dual-lens headlines. Assign to copy. | Sprint 4 |
| #326 | YAML content loader | **Assign to server.** Blocked by C1 + C2. | Sprint 4 |
| #86 | Core NPC components | **Already Sprint 3 server.** Dudley's ECS component list from Round 1 informs this. | Sprint 3 |
| #88 | Daily routine system | **Already Sprint 3 server.** Needs NPC routine YAML from content conversion. | Sprint 3 |
---
## 4. Finalized New Ticket Proposals
### Group A: Wiki Content Fixes (copy team)
| ID | Title | Type | Priority | Sprint | Blocked By | Description |
|----|-------|------|----------|--------|------------|-------------|
| A1 | Apply canonical full names to all NPC wiki pages | task | medium | 3 | — | Apply Miri's 12 full names to NPC wiki pages. Update Core Identity blocks, environmental text references. |
| A2 | Rename Hael → Naia Tamm across all wiki files | task | medium | 3 | — | Find-and-replace across ~8 wiki files. Triangle 4 becomes Naia-Kael-Sera. |
| A6 | Add smuggler-perspective FactId progression text | task | high | 4 | B4 | Add smuggler-path text for all FactIds where smuggler starts at KnowsDetails or has different knowledge path. |
| A7 | Add smuggler-specific entity attributes to entity-attributes.md | task | high | 3 | — | Scope depends on Round 2 resolution of D-03 (Gestalt's 4 new + 2 repurposed vs Paula's 8 new). Add to wiki/knowledge/entity-attributes.md. |
| A8 | Standardize location shortcodes in monologue-guide.md | task | medium | 3 | — | Fix hub_m_ → terminal_m_ inconsistency. Add shortcode reference table. |
| A10 | Stub NPC profile for Nils Davan | task | medium | 3 | — | Off-stage profile: Core Identity, relationship to Kael, role in ring, known attributes. |
| A11 | Fix Triangle 1 (Hub Power) — Volume Escalation decision | story | high | 3 | A10 | Add smuggler decision fork: side with Nils (louder signal), side with Voss (tension), or split route (exposure). Self-contained — no cross-triangle cascade per A-17. |
| A12 | Create environmental text examples file | task | medium | 4 | A3/#319 | Bar menu, safety notice, news ticker cycle, corridor graffiti. Krenn-voiced. Needed for wow moment #1 (Arrival). |
### Group B: Style Guides & Specs (copy team)
| ID | Title | Type | Priority | Sprint | Blocked By | Description |
|----|-------|------|----------|--------|------------|-------------|
| B1 | NPC Authoring Style Guide | story | critical | 5 | A3, A4, A7, B2, B4 | Combined document: tier templates, authoring rules, regional culture, content pipeline. Reframed as generator specification — this IS the NPC generator input format. Most complex ticket; many blockers. |
| B2 | THE MIRROR pattern spec | story | high | 3 | — | Define honest-character NPC pattern. No contradiction arc, no secret. Tier 1 emotional depth. Naia Tamm is first instance. Output becomes generator template. |
| B3 | PC-as-NPC unified spec | story | high | 3 | A7 | Unified spec: starting knowledge graph, starting relationship map, reverse knowledge (bidirectional), orientation monologue, agency boundaries, authored relationship stubs, tell inversion. 9-step conversion checklist. |
| B4 | Smuggler voice card + moral arc spec | story | high | 3 | A7 | Two deliverables: (1) Smuggler voice card — paired examples with detective showing dual-lens register differences. (2) Smuggler moral arc — 4 phases (Comfort→Doubt→Reckoning→Compromise), smuggler-specific FactIds, monologue triggers. Subsumes #310 scope. |
| B5 | NPC-format briefs for both PCs — Concept A v0.1 | story | high | 4 | B3 | NPC-mode behavior scripts (5-7 routine entries each), reverse dual-lens notes, observation monologue (3-5 lines per character). ~20-30 authored items total. |
### Group C: Content Directory & Schema (split teams)
| ID | Title | Type | Priority | Sprint | Team | Blocked By | Description |
|----|-------|------|----------|--------|------|------------|-------------|
| C1 | Content directory structure design doc | story | high | 3 | copy | — | Document converged structure: `_meta/` + `_schema/` (infrastructure), `global/` + `districts/` (content). Canonical_id format. Mod overlay mechanics. District as atomic pack unit. Informs all content implementation. |
| C2 | Create content/ directory skeleton | task | high | 3 | server | C1 | Create directory tree with empty YAML stubs. `_meta/`, `_schema/`, `global/` (factions, technology, contraband, knowledge, enums, regions), `districts/sova-transit/` (district.yaml, npcs/, locations/, templates/, triangles/, lines/). |
| C3 | Content schema definitions (YAML Schema files) | story | high | 3 | server | C1 | Create `_schema/` with validation schemas: npc.schema.yaml (tier-conditional), location, faction, template, fact, dialogue, monologue, district, pool. |
| C4 | Create global/enums/ YAML files from D-035 | task | medium | 4 | server | C2 | Populate enums: situations (13), topics (9), moods (8), triggers (9), access-tiers (5), activities (new). |
| C5 | Create global/knowledge/entity-attributes.yaml | task | medium | 4 | server | C2 | Machine-readable entity attribute definitions. 14 detective + smuggler keys (count depends on D-03 resolution). |
| C6 | Create pools.yaml for v0.1 seed-time selection | task | medium | 4 | server | C2 | Sova single-candidate pools: friend_smuggler, friend_detective, bar_regulars, compromised_inspector, primary_contraband. Architecture supports N candidates. |
| C7 | Create template YAML files with role slot definitions | task | medium | 4 | server | C2 | 3 social sites: logistics-hub.yaml, bar.yaml, smuggling-ring.yaml. Role slots with count ranges, required flags, pool references, triangle constraints. |
| C8 | Create triangle YAML files for 5 v0.1 triangles | task | medium | 4 | server | C2 | 5 triangles. Self-contained forks (no cross-triangle cascade per A-17). Includes updated T1 with Volume Escalation. |
| C9 | Implement make validate-content CLI | story | high | 4 | server | C3 | Structural + tier-conditional validation. Reads _schema/, validates all YAML. v0.2: cross-reference validation. |
| C10 | Pre-commit FactId typo check | task | medium | 4 | ci | — | Grep-based pre-commit check validating FactId references against canonical facts.yaml. |
### Group D: Design Specs
| ID | Title | Type | Priority | Sprint | Team | Blocked By | Description |
|----|-------|------|----------|--------|------|------------|-------------|
| D2 | Seed configuration schema design | story | medium | 4 | server | — | Schema for what the randomizer produces at game-start: FRIEND selections, social site population, compromised NPC, contraband type. v0.1 has single-candidate pools but architecture must support N. |
| D4 | News ticker headline pool | task | medium | 4 | copy | — | ~20 dual-lens headlines for Meridian feed at Lera's. Freight data, politics, local infrastructure, sports, Commission advisories. Each works as dual-lens monologue trigger. |
### Group NEW: Tickets from Round 1 + Round 2
| ID | Title | Type | Priority | Sprint | Team | Blocked By | Description |
|----|-------|------|----------|--------|------|------------|-------------|
| NEW-1 | Apply Gestalt's NPC pattern/motivation mapping | task | high | 3 | copy | — | Apply the canonical v0.1 mapping (Gestalt's Round 2 finalized table) to wiki and content files. 17 NPCs × (pattern + motivation). Includes Harek's structural role per Paula Gap 7. |
| NEW-2 | Drin Tier 2 profile expansion | task | medium | 3 | copy | NEW-1 | Drin confirmed Tier 2 (A-01). Expand wiki profile to full Tier 2 depth: all 10 profile axes, smuggler lens section, triangle membership formalized. |
| NEW-3 | Wiki → YAML content conversion (Sova NPCs) | story | high | 4 | copy | C1, C2, C3 | Convert 17 NPC wiki profiles to engine-readable YAML. Includes routine YAML layer (Paula Gap 3), triangle fork decision points (Gap 4), location smuggler detail (Gap 6). Tyre estimates 2-3 days. |
| NEW-4 | Monologue content pool — minimum viable (~200 lines) | story | high | 4 | copy | #261, B4 | ~100 lines per character. Categories: arrival observations, NPC routine commentary, environmental flavor, contradiction hints, idle reflections, tutorial/orientation. Follows Mellanie's authoring order (FRIEND packs first, then fill). |
| NEW-5 | v0.1 wow moment content checklist | task | high | 3 | copy | — | Map D-039's 6 wow moments to specific content deliverables + implementation tickets. Track completion. Acceptance: every moment has identified content + code backing it. |
| NEW-6 | PC-as-NPC content authoring | story | high | 5 | copy | B3, B5 | Author the actual lines: 5-7 routine entries per character, 3-5 observation monologue lines, reverse dual-lens notes. ~25 authored items (Mellanie's budget). |
| NEW-7 | v0.1 interaction verb spec | task | medium | 3 | copy | — | Document the 7 interaction types (A-04: Move, Look, Monologue, Examine Object, Examine NPC, Talk, Overhear). Define triggers, UI needs, server events per type. v0.1 surfaces single context-sensitive action; architecture supports N verbs. |
### Group NEW-R2: Tickets from Lead's Round 2 Decisions
| ID | Title | Type | Priority | Sprint | Team | Blocked By | Description |
|----|-------|------|----------|--------|------|------------|-------------|
| NEW-8 | YAML → RON converter tool | task | medium | 4 | server | C1 | Build-time converter: reads content YAML, emits RON. Lives in `tooling/`. Runs as make target (`make content-ron`). Not on critical path — engine consumes YAML in v0.1; RON is future-proofing. |
| NEW-9 | Multi-verb interaction architecture — server InteractionOptions | story | high | 3 | server | — | Server models N available actions per entity via `InteractionOptions` component. v0.1 client picks first/best; v0.2 client shows menu. Must not be throwaway. Includes ObserverSnapshot v3 extension for interaction data. |
| NEW-10 | Multi-verb interaction architecture — client extensible prompt | story | high | 3 | client | NEW-9 | Client-side interaction prompt designed for extensibility. v0.1: single context-sensitive E prompt. Architecture supports v0.2 multi-verb menu. Prompt system reads InteractionOptions from server state. |
| NEW-11 | Pause system — server tick rate scaling | story | medium | 3 | server | — | Tick rate supports 3 states: full speed (normal play), 50% speed (UI overlay open), 0% (spacebar pause). Server receives pause/speed commands from client. |
| NEW-12 | Pause system — client state machine | story | medium | 3 | client | NEW-11 | Client pause state machine: Normal → Overlay (50% speed, triggered by knowledge panel / dialogue) → Paused (spacebar from any state). Spacebar always overrides to full pause. |
| NEW-13 | Line previewer CLI | task | medium | 4 | server | C3, C9 | CLI tool to preview monologue/dialogue line selection for a given game state. Tyre's recommendation for content tuning. Lives in `tooling/`. Helps content authors test prerequisite logic without running the full game. |
---
## 5. Sprint Plan
### Sprint 3: Know (Copy Team — Content Foundation)
**Goal:** Deliver the content specs and wiki fixes that unblock server implementation and content authoring.
| Priority | Ticket | Title | Owner Hint | Effort |
|----------|--------|-------|------------|--------|
| **P0** | **#261** | **Dual Lens Authoring Guide** | **Paula** | **Large** |
| **P0** | **C1** | **Content directory structure design** | **Tyre/Gestalt** | **Medium** |
| P0 | A1 | Apply canonical full names | Paula | Small |
| P0 | A2 | Hael → Naia Tamm rename | Paula | Small |
| P0 | A7 | Smuggler entity attributes | Paula | Small |
| P1 | B2 | MIRROR pattern spec | Gestalt/Gore | Medium |
| P1 | B4 | Smuggler voice + moral arc (subsumes #310) | Gore/Mellanie | Medium |
| P1 | NEW-1 | Apply Gestalt's NPC pattern mapping | Gestalt | Small |
| P1 | NEW-5 | Wow moment content checklist | SI | Small |
| P1 | A10 | Nils Davan stub | Paula | Small |
| P1 | A11 | Triangle 1 fix | Gestalt/Paula | Medium |
| P2 | B3 | PC-as-NPC spec | Gestalt/Paula | Medium |
| P2 | A8 | Shortcode fix | Mellanie | Small |
| P2 | NEW-2 | Drin Tier 2 profile expansion | Paula | Small |
| P2 | NEW-7 | Interaction verb spec | Gestalt | Small |
**Sprint 3 copy total: 15 tickets (2 P0, 6 P1, 5 P2, 2 small enough to parallelize)**
### Sprint 3: Know (Server Team — Content-Adjacent, Proposed Additions)
| Priority | Ticket | Title | Effort |
|----------|--------|-------|--------|
| P1 | C2 | Create content/ directory skeleton | Small |
| P1 | C3 | Content schema definitions | Medium |
| P1 | NEW-9 | Multi-verb interaction architecture — InteractionOptions | Medium |
| P2 | NEW-11 | Pause system — tick rate scaling | Small |
### Sprint 3: Know (Client Team — Proposed Additions)
| Priority | Ticket | Title | Effort |
|----------|--------|-------|--------|
| P1 | NEW-10 | Multi-verb interaction — extensible prompt | Medium |
| P2 | NEW-12 | Pause system — client state machine | Small |
### Sprint 4 (Content Conversion + Authoring Begins)
| Ticket | Title | Team | Blocked By |
|--------|-------|------|------------|
| NEW-3 | Wiki → YAML conversion (17 NPCs) | copy | C1, C2, C3 |
| C4 | Enum YAMLs from D-035 | server | C2 |
| C5 | Entity-attributes YAML | server | C2 |
| C6 | Pools YAML | server | C2 |
| C7 | Social site template YAMLs | server | C2 |
| C8 | Triangle YAMLs | server | C2 |
| C9 | validate-content CLI | server | C3 |
| C10 | Pre-commit FactId check | ci | — |
| A6 | Smuggler FactId progression text | copy | B4 |
| A12 | Environmental text examples | copy | A3/#319 |
| B5 | PC NPC-format briefs | copy | B3 |
| D4 | News ticker headlines (~20) | copy | — |
| #306 | News ticker content (align with D4) | copy | — |
| D2 | Seed configuration schema | server | — |
| NEW-8 | YAML → RON converter | server | C1 |
| NEW-13 | Line previewer CLI | server | C3, C9 |
| #326 | YAML content loader | server | C1, C2 |
| A3/#319 | Krenn brief + seed.yaml reference | copy | — |
### Sprint 5+ (Content at Scale)
| Ticket | Title | Team | Blocked By |
|--------|-------|------|------------|
| NEW-4 | Monologue content pool (~200 lines) | copy | #261, B4 |
| NEW-6 | PC-as-NPC content authoring (~25 items) | copy | B3, B5 |
| B1 | NPC Authoring Style Guide (generator spec) | copy | A3, A4, A7, B2, B4 |
| A4 | Regional style guide / seed.yaml template | copy | — |
| A9 | Thematic Question field (Tier 1 profiles) | copy | B2 |
| #297 | THE FRIEND: Kael content pack | copy | #261 |
| #298 | THE FRIEND: Sera content pack | copy | #261 |
| #190 | Workplace content pack | copy | #261 |
| #191 | Bar content pack | copy | #261 |
| #192 | Smuggling ring content pack | copy | #261 |
---
## 6. Revised Dependency Chain
```
SPRINT 3 — Two Parallel Critical Chains
========================================
Chain 1: Content Authoring Pipeline
------------------------------------
#261 (Dual Lens Guide) [P0, CRITICAL PATH ROOT]
├── blocks B4 (Smuggler voice + moral arc) [Sprint 3]
│ ├── blocks A6 (Smuggler FactId text) [Sprint 4]
│ └── blocks NEW-4 (Monologue pool) [Sprint 5]
├── blocks #297 (FRIEND: Kael) [Sprint 5]
├── blocks #298 (FRIEND: Sera) [Sprint 5]
├── blocks #299 (Opening hook: smuggler) [Sprint 5]
├── blocks #300 (Opening hook: detective) [Sprint 5]
└── blocks #190, #191, #192 (Content packs) [Sprint 5]
A7 (Smuggler attributes) [P0, Sprint 3]
├── blocks B4 (Smuggler voice) [Sprint 3]
└── blocks B3 (PC-as-NPC spec) [Sprint 3]
└── blocks B5 (PC briefs) [Sprint 4]
└── blocks NEW-6 (PC-as-NPC authoring) [Sprint 5]
Chain 2: Content Architecture Pipeline
---------------------------------------
C1 (Content dir design) [P0, Sprint 3]
├── blocks C2 (skeleton) [Sprint 3, server]
│ ├── blocks C4 (enums) [Sprint 4]
│ ├── blocks C5 (entity attrs) [Sprint 4]
│ ├── blocks C6 (pools) [Sprint 4]
│ ├── blocks C7 (templates) [Sprint 4]
│ ├── blocks C8 (triangles) [Sprint 4]
│ ├── blocks NEW-3 (wiki→YAML) [Sprint 4]
│ └── blocks #326 (YAML loader) [Sprint 4]
├── blocks C3 (schemas) [Sprint 3, server]
│ ├── blocks C9 (validator) [Sprint 4]
│ ├── blocks NEW-3 (wiki→YAML) [Sprint 4]
│ └── blocks NEW-13 (line previewer) [Sprint 4]
└── blocks NEW-8 (RON converter) [Sprint 4]
Independent Chains (Sprint 3)
------------------------------
B2 (MIRROR spec) → A9 (Thematic Question) [Sprint 4]
A10 (Nils stub) → A11 (Triangle 1 fix) [Sprint 3]
NEW-9 (InteractionOptions, server) → NEW-10 (Extensible prompt, client) [Sprint 3]
NEW-11 (Tick rate scaling, server) → NEW-12 (Pause state machine, client) [Sprint 3]
```
---
## 7. Ticket Count Summary
| Category | Count | Teams |
|----------|-------|-------|
| Wiki fixes (A-series) | 8 | copy |
| Style guides & specs (B-series) | 5 | copy |
| Content directory & schema (C-series) | 10 | copy (1), server (8), ci (1) |
| Design specs (D-series) | 2 | server (1), copy (1) |
| Round 1 new tickets (NEW 1-7) | 7 | copy |
| Round 2 new tickets (NEW 8-13) | 6 | server (4), client (2) |
| **Total new tickets** | **38** | copy (21), server (13), client (2), ci (1), + 1 epic update |
| Existing ticket updates | 10 | — |
**Delta from Round 1:** +6 tickets (NEW-8 through NEW-13 from lead decisions), +2 server Sprint 3 additions (NEW-9, NEW-11), +2 client Sprint 3 additions (NEW-10, NEW-12). Removed: D3 (killed), A5 (deferred), D1 (deferred). Merged: A3 into #319, #310 into B4.
---
## 8. Risks & Recommendations
**Risk 1: #261 is still the critical path root.** Every content authoring ticket flows through it. If it slips even one sprint, the entire content pipeline delays. Recommend: assign Paula immediately, time-box to 5 working days, accept "good enough" over "perfect."
**Risk 2: Sprint 3 copy team has 15 tickets.** That's a lot. But 7 are small tasks (A1, A2, A7, A8, A10, NEW-1, NEW-2) that can be parallelized. The real load is #261, C1, B2, B4, and A11. Recommend: Paula owns #261 + wiki fixes (A1, A2, A7, A10, NEW-2). Gestalt owns C1, NEW-1, B2, A11, NEW-7. Mellanie owns A8, B4. SI owns NEW-5.
**Risk 3: Server team Sprint 3 is already heavy** (10 existing tickets). Adding C2, C3, NEW-9, NEW-11 is +4. Recommend: C2 and C3 are blocked by C1 anyway — they can start mid-sprint when C1 lands. NEW-9 and NEW-11 are independent and can begin immediately.
**Risk 4: Content conversion (NEW-3) is a Sprint 4 bottleneck.** Tyre estimates 2-3 full days for 17 NPC conversions. This blocks the server from testing with real data. Recommend: start with the 3 Tier 1 NPCs (Kael, Sera, Naia) as soon as C2 lands, don't wait for all 17.
---
*Proposals only — no tickets created. Awaiting lead approval.*
*Compiled by SI. Source: Round 1 tracking doc (Qatux), all 7 Round 1 responses, lead Round 2 decisions.*
docs/workshops/v01-content-scoping/round2-stig.md
-375
View File
@@ -1,375 +0,0 @@
# Round 2 Response: Stig (UI Developer)
## v0.1 Content Scoping Workshop
---
## Task 1: Single-Action Prompt Designed for Multi-Verb Extension
The lead confirmed: v0.1 ships single-action. Multi-verb is v0.2. I need to design the prompt system so the upgrade path is clean — no throwaway architecture.
### How it works in v0.1
The server sends an `InteractionOptions` payload per entity when the player enters interaction range. v0.1 format:
```
InteractionOptions {
entity_id: "kael_davan",
display_name: "Kael Davan",
primary: { verb: "Talk", keybind: "E" },
secondary: null
}
```
The client renders:
```
[E] Talk
Kael Davan
[====]
```
One prompt. One key. The player approaches, reads, presses. Done.
**For objects:**
```
InteractionOptions {
entity_id: "manifest_terminal_03",
display_name: "Manifest Terminal",
primary: { verb: "Examine", keybind: "E" },
secondary: null
}
```
Renders as:
```
[E] Examine
Manifest Terminal
[====]
```
Same pattern. The verb changes. The keybind stays the same. The player learns one input: "E means interact."
### How it extends to v0.2 (multi-verb)
The server payload grows:
```
InteractionOptions {
entity_id: "kael_davan",
display_name: "Kael Davan",
primary: { verb: "Talk", keybind: "E" },
secondary: { verb: "Observe", keybind: "F" },
actions: [
{ verb: "Talk", keybind: "E" },
{ verb: "Observe", keybind: "F" }
]
}
```
The client renders both:
```
[E] Talk [F] Observe
Kael Davan
[====]
```
**What changes in the client:**
- The prompt renderer reads `actions[]` instead of just `primary`
- Layout goes from single-label to horizontal label row
- Keybind display pluralizes
**What does NOT change:**
- The prompt's position (world-space, entity-tracked)
- The fade behavior (proximity-triggered)
- The input routing (keybind → server action request)
- The overall visual language (bracket-key + verb)
**The v0.1 client code:**
```gdscript
# InteractionPrompt.gd
func update_prompt(options: InteractionOptions) -> void:
if options == null:
hide()
return
# v0.1: show primary action only
# v0.2: iterate options.actions[] for multi-label
_label.text = "[%s] %s" % [options.primary.keybind, options.primary.verb]
_name_label.text = options.display_name
_target_entity = options.entity_id
show()
```
The `options.actions[]` field exists in the protocol from day one. The v0.1 client ignores it. The v0.2 client reads it. No protocol change needed.
### Architectural notes for Dudley/Tyre
The `InteractionOptions` should be part of the `ObserverSnapshot` update — not a separate message. When the player is near an entity, the snapshot includes the interaction payload. When they move away, it's `null`. The client never requests interaction options — they arrive passively as part of perception.
This means the server's `InteractionResolver` system evaluates available actions every tick for entities in the player's interaction radius. In v0.1 that's a simple lookup (NPC → Talk, Object → Examine). In v0.2 it evaluates relationship state, knowledge, and context to determine the full action set.
**For Gestalt's Examine-vs-Talk question:** The server models both verbs internally from v0.1 onward. It just surfaces only the primary one to the client. If the server determines that "Observe" is more relevant than "Talk" at a given moment (e.g., player has already talked to this NPC this shift, or NPC is currently in an anomalous state), the server can swap the primary. Single-action doesn't mean single-verb-forever — it means the server picks the best one.
---
## Task 2: Pause System State Machine
Three states. Clean transitions. No ambiguity.
### States
```
RUNNING ← normal gameplay, full sim speed
OVERLAY_ACTIVE ← UI overlay open (knowledge panel, dialogue), 50% sim speed
PAUSED ← spacebar pause, 0% sim speed
```
### Transitions
```
[Tab] [Space]
RUNNING ──────────────> OVERLAY_ACTIVE ──────────────> PAUSED
^ | |
| [Tab] | [Space] |
+────────────────────────+ | |
| | |
+─────────────────────────────────────+ |
| [Space] |
+─────────────────────────────────────────────────────+
```
### Rules
| Input | From RUNNING | From OVERLAY_ACTIVE | From PAUSED |
|-------|-------------|--------------------|-|
| **[Space]** | → PAUSED | → PAUSED | → previous state (RUNNING or OVERLAY_ACTIVE) |
| **[Tab]** (knowledge panel) | → OVERLAY_ACTIVE | → RUNNING (closes panel) | → PAUSED + OVERLAY_ACTIVE (panel opens, stays paused) |
| **[E]** (interaction/dialogue) | → OVERLAY_ACTIVE (if dialogue starts) | stays OVERLAY_ACTIVE | no effect |
| **[Esc]** | no effect | → RUNNING (closes overlay) | → previous state |
**Key behaviors:**
1. **Spacebar is king.** It always toggles to/from PAUSED. Period. No other input overrides spacebar. If the player is in dialogue and hits space, the game pauses with the dialogue still visible.
2. **Overlay = 50% speed, not 0%.** When the knowledge panel is open, the world still breathes. NPCs still move (slowly). Time still passes (slowly). This prevents the knowledge panel from becoming a freeze-frame intelligence tool. The player can check their notes, but the world doesn't wait.
3. **Spacebar from OVERLAY_ACTIVE goes to PAUSED, not RUNNING.** If I'm reading my knowledge panel and I want the world to stop completely, I hit space. I don't have to close the panel first. Conversely, hitting space from PAUSED with an overlay open returns to OVERLAY_ACTIVE (50% speed with panel still visible), not RUNNING.
4. **Dialogue is an overlay.** When in conversation, sim runs at 50%. NPCs outside the conversation keep moving. This means: while you're talking to Kael, Sera might leave the bar. You could miss it. That's the game. If you want to freeze everything, pause.
5. **Multiple overlays don't stack speed reductions.** If dialogue is active (50%) and the player opens the knowledge panel (also 50%), sim stays at 50%. Not 25%.
### Implementation (client-side)
```gdscript
# PauseManager.gd
enum SimState { RUNNING, OVERLAY_ACTIVE, PAUSED }
var _state: SimState = SimState.RUNNING
var _pre_pause_state: SimState = SimState.RUNNING
var _active_overlays: int = 0 # count of open overlays
func _input(event: InputEvent) -> void:
if event.is_action_pressed("pause"): # spacebar
_toggle_pause()
elif event.is_action_pressed("knowledge_panel"): # tab
_toggle_knowledge_panel()
func _toggle_pause() -> void:
if _state == SimState.PAUSED:
_set_state(_pre_pause_state)
else:
_pre_pause_state = _state
_set_state(SimState.PAUSED)
func _toggle_knowledge_panel() -> void:
if _knowledge_panel_open:
_close_knowledge_panel()
else:
_open_knowledge_panel()
func _open_knowledge_panel() -> void:
_knowledge_panel_open = true
_active_overlays += 1
if _state == SimState.RUNNING:
_set_state(SimState.OVERLAY_ACTIVE)
# if PAUSED, stay PAUSED — panel opens visually but sim doesn't resume
func _close_knowledge_panel() -> void:
_knowledge_panel_open = false
_active_overlays -= 1
if _active_overlays == 0 and _state == SimState.OVERLAY_ACTIVE:
_set_state(SimState.RUNNING)
func _set_state(new_state: SimState) -> void:
_state = new_state
match new_state:
SimState.RUNNING:
Engine.time_scale = 1.0
SimState.OVERLAY_ACTIVE:
Engine.time_scale = 0.5
SimState.PAUSED:
Engine.time_scale = 0.0
```
### Question for Dudley
Does the server need to know about pause state? If the client sets `Engine.time_scale = 0.0`, does the server keep ticking and the client just stops rendering? Or does the client need to signal the server to pause its tick loop?
For single-player (v0.1), I think the client controls this entirely. The server runs as a subprocess — if the client freezes its consumption of server ticks, the server's output buffer fills and it naturally stalls. But this depends on the IPC design. Dudley should confirm.
For the 50% overlay speed: does the client request half-speed ticks from the server, or does it receive full-speed ticks and render every other one? I lean toward the client setting the tick request rate. Cleaner.
---
## Task 3: Monologue Display Constraints (Confirmed)
Mellanie needs hard numbers. Here they are.
### Display constraints
| Parameter | Value | Rationale |
|-----------|-------|-----------|
| **Max characters** | 160 | Two lines at ~80 chars/line at reference font size. Fits 40% viewport width. |
| **Max lines** | 2 | One breath. Monologue competes with gameplay — the player is moving, looking, deciding. Two lines is a glance. Three is a paragraph. |
| **Display duration (base)** | 4.0 seconds | Long enough to read 160 characters at comfortable pace (~40 chars/sec reading speed for on-screen text). |
| **Display duration (short, <80 chars)** | 3.0 seconds | Short lines don't need 4 seconds. Scale linearly. |
| **Display duration (urgent chime)** | 5.0 seconds | Anomaly observations deserve an extra beat. The player needs time to register that something changed. |
| **Fade in** | 0.3 seconds | Fast enough to not feel laggy. Slow enough to not pop. |
| **Fade out** | 0.5 seconds | Slightly slower than fade-in. The thought lingers. |
| **Interruption fade** | 0.15 seconds | When a new monologue replaces the current one, the old one exits fast. No collision. |
| **Cooldown between lines** | 2.0 seconds minimum | Two monologues back-to-back feel like a data dump. The gap is where the player absorbs. |
| **Max queue depth** | 1 | If two triggers fire simultaneously, the higher-priority one displays and the other is dropped. No stacking, no scroll-back. The character's mind moves on. |
### Priority ordering (when two triggers fire at once)
```
1. observe_anomaly ← the game is telling you something important
2. witness_interaction ← the game is telling you something happened
3. discover_evidence ← you found something
4. post_conversation ← reaction to what just happened
5. hear_sound ← environmental awareness
6. observe_npc ← identification / emotional reaction
7. enter_location ← atmospheric
8. return_visit ← atmospheric
9. time_idle ← lowest — reflective, only when nothing else is happening
```
`observe_anomaly` always wins. If THE FRIEND's contradiction fires at the same time as an `enter_location` line, the contradiction shows. The atmospheric line is gone. The player will never know it existed. That's fine — the important thing happened.
### What Mellanie should write to
**Target:** 80-120 characters for most lines. 160 is the hard maximum — use it rarely. The best monologue lines are 40-80 characters. One punchy thought.
Examples from the authoring guide, with character counts:
- `"Morning shift. Recycled air and cargo lubricant. Home sweet home."` — 66 chars. Perfect. One line, one breath.
- `"Kael's here. Good — I was starting to worry."` — 47 chars. Even better. Fast, emotional.
- `"Dock worker Davan — lattice activity spiked. Three pings in two minutes. Expecting a message? Or checking for surveillance?"` — 124 chars. This pushes into line 2 but earns it — the detective's analytical voice needs the full thought.
- `"He looked left. He always looks left when he's making something up. Two years I've known that tell. Kael is lying to me."` — 121 chars. This is a climax moment. Two lines justified.
**Rule of thumb:** If it fits on one line (~80 chars), it should be one line. Two lines are for moments that matter.
### Font specification (for reference)
Monologue text at reference resolution (1920x1080):
- **Font:** Clean sans-serif (Godot default or a custom face — Araminta's call)
- **Size:** 18-20px equivalent
- **Line height:** 1.4x
- **Max width:** 40% of viewport = ~768px at 1920 wide
- **At 18px, ~80 characters fit in 768px** with standard proportional font metrics
This gives comfortable readability at typical viewing distance. Not tiny, not shouting. The text whispers.
### Monologue during dialogue
When a dialogue panel is active, monologue can still fire (e.g., `observe_anomaly` while in conversation). The monologue display shifts up to sit above the dialogue panel:
```
Normal state:
+------------------------------------------------------------------+
| |
| GAME WORLD |
| |
| +--monologue----------------------------+ |
| | Kael's here. Good. | |
| +----------------------------------------+ |
| |
+------------------------------------------------------------------+
During dialogue:
+------------------------------------------------------------------+
| |
| GAME WORLD |
| |
| +--monologue----------------------------+ |
| | That's not anyone from our rotation. | |
| +----------------------------------------+ |
+------------------------------------------------------------------+
| KAEL DAVAN |
| "Just a friend. Don't worry about it." |
| [Continue] [End] |
+------------------------------------------------------------------+
```
The monologue sits in the world layer. The dialogue sits in the HUD layer. They don't overlap. The player reads dialogue first (larger, centered, paneled), catches monologue peripherally (smaller, left, ghostly). Two voices — one external, one internal — simultaneously.
This is critical for Wow Moment #3. The contradiction fires monologue WHILE the player might be in conversation. The internal "What the hell?" happens at the same moment as the external smooth deflection. The UI must support both without making the player choose which to read.
---
## Responses to Round 1 Open Questions (Answered by Lead Decisions)
### D-04 (Examine vs Talk) — Resolved
Lead decision: conceptually separate, v0.1 ships single-action. Covered in Task 1 above. The server models both verbs; the client surfaces one. Extensible to multi-verb in v0.2 without protocol changes.
### D-05 (Knowledge Panel Pause) — Resolved
Lead decision: 50% sim speed for overlays, spacebar always pauses. Covered in Task 2 above.
### Client text delivery — Resolved (A-12, proposed D-048)
Server sends full text, client renders. Confirmed by lead and tracking doc. No local content loading on the client.
---
## Updated UI Bill of Materials (incorporating Round 2 decisions)
| System | Scenes | Scripts | Shaders | Priority | Notes |
|--------|--------|---------|---------|----------|-------|
| **Monologue renderer** | 1 | 1 | 0 | P0 | Fade, timing, priority queue, character tint |
| **Interaction prompt** | 1 | 1 | 0 | P0 | World-space tracking, single-action (extensible to multi) |
| **Dialogue panel** | 1 | 1 | 0 | P0 | Semi-transparent, text advance, exit handling |
| **Entity color system** | 0 | 1 | 1 | P0 | D-033 palette, 0.5s fade transitions |
| **Pause manager** | 0 | 1 | 0 | P0 | State machine: RUNNING / OVERLAY / PAUSED |
| **HUD bar** | 1 | 1 | 0 | P1 | Location + time phase. Placeholder text in v0.1 |
| **Minimap** | 1 | 1 | 1 | P1 | Insert-style, player dot + area bounds |
| **Knowledge panel** | 1 | 1 | 0 | P1 | Right-side overlay, People/Places/Observations |
| **News ticker** | 1 | 1 | 0 | P1 | World-space scrolling text on bar display entity |
| **Fog rendering** | 0 | 0 | 1 | P0 | Shared with server team (shadowcast → visual) |
| **TOTAL** | **7** | **9** | **3** | | |
Reduced from 9 scenes to 7 (pause manager and entity colors don't need dedicated scenes). Added 1 shader (fog rendering confirmed as client-side).
---
## Dependencies I'm Waiting On
| From | What I Need | Blocks |
|------|-------------|--------|
| **Dudley** | IPC message format — specifically `ObserverSnapshot` structure for interaction options, monologue payloads, dialogue payloads. | Interaction prompt, dialogue panel, monologue renderer |
| **Dudley** | Pause architecture — does client control sim speed, or does it signal the server? | Pause manager |
| **Tyre** | `ObserverSnapshot` v3 protocol spec (Round 2 task for Tyre). | Everything that reads server state |
| **Araminta** | Font selection, diegetic styling direction for knowledge panel. | Knowledge panel visual treatment |
| **Mellanie** | First monologue content (even 5-10 lines) for integration testing. | Monologue renderer testing |
I can build all UI scaffolding with mock data. But integration testing needs real payloads from the server and real text from Mellanie. The sooner those arrive, the sooner we know if the display constraints actually feel right at runtime.
---
*Spacebar always pauses. Everything else fades in when needed and disappears when it's done.*
docs/workshops/v01-content-scoping/round2-tracking.md
-594
View File
@@ -1,594 +0,0 @@
# Round 2 Tracking — Qatux (Documenter)
## v0.1 Content Scoping Workshop — CLOSING ROUND
**Status:** All 7 responses received (Gestalt, Paula, Tyre, Dudley, Stig, Mellanie, SI). Workshop complete.
**Date:** 2026-02-12
---
## 1. Lead Decisions (Round 2 Brief)
Four lead decisions were issued at the start of Round 2, resolving the major disagreements from Round 1:
| ID | Decision | Round 1 Disagreement Resolved |
|----|----------|-------------------------------|
| **D-NPC** | Gestalt's mechanical mapping is canonical for v0.1. Paula's emotional/narrative layer becomes v0.2 annotations. | D-02 (10 of 17 NPC mapping disagreements) |
| **D-FORMAT** | YAML for content files. RON converter available as optional build-time tool. | D-01 (YAML vs RON) |
| **D-INTERACT** | Single context-sensitive action for v0.1. Multi-verb architecture modeled underneath from day one. | D-04 (Examine vs Talk: separate or combined) |
| **D-PAUSE** | Spacebar always pauses (0% speed). UI overlays (knowledge panel, dialogue) trigger 50% sim speed. 3-state system. | D-05 (Knowledge panel pause behavior) |
**Additionally resolved by lead direction:**
- **D-03 (EntityKnowledge keys):** 16 total keys. 4 new generic role-perspective keys. `trust_read` merged into existing `trust_level`. `leverage_held` absorbs `secret_held`. `secret_confidence` renamed to `leverage_confidence`. (See Section 5.)
- **R2-06 (PC voice registers):** Assigned to Mellanie as Round 2 task.
- **R2-07 (Triangle fork cascade):** Self-contained forks confirmed.
- **R2-09 (ObserverSnapshot v3):** Assigned to Tyre as Round 2 task.
**Closing round additions (post-Round 2 responses):**
- **Q-012 resolved:** 16 EntityKnowledge keys finalized (see Section 5).
- **Q-013 resolved:** Server-authoritative pause. Client is a dumb renderer. NEW-12 (client pause state machine) killed.
- **Q-016 resolved:** `actions[]` → `verbs[]` rename confirmed across server code, client code, YAML content, wiki docs, decision files. Folded into NEW-7.
- **Process rule:** No ticket merges across domain teams. Shared epics are fine; each team gets its own ticket with its own definition of done.
---
## 2. Round 1 Disagreement Resolutions
### D-02 Resolved: NPC Pattern/Motivation Mapping
Gestalt reviewed all 10 disagreements from Round 1 and **changed his position on 6 of 10**, adopting Paula's reads. Both agents converged on a single canonical mapping.
| NPC | Round 1 Gestalt | Round 1 Paula | Round 2 Final | Who Prevailed | Gestalt's Rationale for Change |
|-----|----------------|--------------|---------------|---------------|-------------------------------|
| **Maret** (pattern) | SYSTEM | WITNESS | **WITNESS** | Paula | Story function > job description |
| **Maret** (motivation) | WITNESS | SKEPTIC | **SKEPTIC** | Paula | WITNESS+SKEPTIC creates compositional tension |
| **Resha** (motivation) | SKEPTIC | CIVILIAN | **CIVILIAN** | Paula | Innocent disruption > deliberate questioning |
| **Harek** (pattern) | GHOST | ANCHOR | **ANCHOR** | Paula | Harek is physically present; contentment, not absent power |
| **Drin** (pattern) | REMNANT | SYSTEM | **SYSTEM** | Paula | Station too young for REMNANT; SYSTEM+TURNCOAT = institutional rot |
| **Sabel** (pattern) | THRESHOLD | GHOST | **GHOST** | Paula | Off-station = absent power, not gatekeeper |
| **Olin** (motivation) | SKEPTIC (dual) | CIVILIAN | **CIVILIAN** | Paula | Dropped dual designation; 1 pattern + 1 motivation per NPC |
| **Voss** (motivation) | OPERATOR | HANDLER | **OPERATOR** | Gestalt | Voss RUNS the schedule; middle management operating machinery |
| **Devra** (motivation) | HANDLER | OPERATOR | **HANDLER** | Gestalt | Devra conveys Nils's strategy; pressure from above |
| **Sess** (pattern) | ANCHOR | NOBODY | **ANCHOR** | Gestalt | NOBODY deferred to v0.2; ANCHOR at T3 = contentment as texture |
**Paula's response:** Accepted the versioned approach. Annotated all 10 disagreement NPCs with v0.2 emotional layer descriptions. Each annotation specifies what content the v0.2 motivation/pattern unlocks (~30-50 lines per NPC).
### D-01 Resolved: YAML Format
**Dudley accepts YAML.** One-line change: `serde_yaml::from_str()` replaces `ron::from_str()`. Multi-line YAML blocks (`|`) improve author experience. RON crate retained for potential future use.
### D-04 Resolved: Examine vs Talk
**Converged on: conceptually separate, v0.1 ships single action.** The server models both verbs internally; priority resolution determines which surfaces as the `[E]` prompt. Post-contradiction, Examine can become primary (detective investigating a flagged NPC). The v0.2 client reads the full action list — no server changes needed.
### D-05 Resolved: Pause System
**3-state system adopted by all respondents.** Gestalt, Stig, and Dudley each independently designed compatible state machines.
---
## 3. Definitive v0.1 NPC Mapping
The canonical mapping, produced by Gestalt with 6 changes from Paula's input:
| # | Name | Tier | Pattern | Motivation | Composition Read |
|---|------|------|---------|-----------|-----------------|
| 1 | **Kael Davan** | **T1** | **FRIEND** | **OPERATOR** | Trust anchor running ring cargo |
| 2 | **Sera Venn** | **T1** | **FRIEND** | **WITNESS** | Trust anchor carrying unreported evidence |
| 3 | **Naia Tamm** | **T1*** | **MIRROR** | **CIVILIAN** | Honest transparency, no secrets |
| 4 | **Voss** | T2 | **SYSTEM** | **OPERATOR** | Institutional authority operating the schedule |
| 5 | **Lera Sessik** | T2 | **ANCHOR** | **OPERATOR** | Contentment embodied, running a bar on willful ignorance |
| 6 | **Torek Lintar** | T2 | **CATALYST** | **CIVILIAN** | Spending disrupts equilibrium |
| 7 | **Devra** | T2 | **THRESHOLD** | **HANDLER** | Ring gatekeeper, manages operations from above |
| 8 | **Maret Korr** | T2 | **WITNESS** | **SKEPTIC** | Accidentally observed discrepancies, doubts the numbers |
| 9 | **Resha** | T2 | **CATALYST** | **CIVILIAN** | New hire forcing defensiveness with innocent questions |
| 10 | **Drin** | **T2** | **SYSTEM** | **TURNCOAT** | Inspector whose compromise corrupts the institution |
| 11 | **Renn** | T2 | **THRESHOLD** | **OPERATOR** | Courier controlling cargo flow |
| 12 | **Pell** | T2 | **CATALYST** | **TURNCOAT** | Wavering member forcing potential crisis |
| 13 | **Harek** | T2 | **ANCHOR** | **HANDLER** | Complacent contentment whose comfort creates a tool |
| 14 | **Sess** | T3 | **ANCHOR** | **CIVILIAN** | Quiet contentment behind the bar |
| 15 | **Olin** | T3 | **CATALYST** | **CIVILIAN** | New arrival forcing evaluation |
| 16 | **Sabel** | T3 | **GHOST** | **OPERATOR** | Off-station absent power running the supply chain |
| 17 | **Tav** | T3 | **SYSTEM** | **CIVILIAN** | Ring lookout following procedure |
**Off-stage:** Nils Davan — GHOST + HANDLER
**Distribution:** 8 of 9 patterns present (REMNANT correctly absent; NOBODY deferred to v0.2). All 6 motivations present. CIVILIAN at 6/17 (35%) matches D-029 noise floor (~30%).
---
## 4. Key Architecture Convergences
### 4.1 Multi-Verb Interaction Architecture
Tyre, Dudley, and Stig independently produced compatible designs:
| Agent | Contribution | Compatible? |
|-------|-------------|-------------|
| **Tyre** | `AvailableActions` per entity with priority-sorted `ActionOption` list; `ActionKind` enum; `InteractPrimary` vs `InteractWith` PlayerAction variants | Canonical design |
| **Dudley** | `EntityInteractions` with `AvailableAction` list; server-side `rank_actions()` priority system; `PlayerAction::InteractWith` for v0.2 | Compatible — naming differs, structure identical |
| **Stig** | `InteractionOptions` with `primary`/`secondary` fields; v0.2 extension reads `actions[]` array; world-space prompt renderer | Client-side compatible |
**Minor naming divergence:** Tyre uses `AvailableActions`/`ActionOption`, Dudley uses `EntityInteractions`/`AvailableAction`. These are the same concept.
**Lead confirmation (closing round):** `actions[]` → `verbs[]` rename confirmed. Scope: server code, client code, YAML content files, wiki docs, decision files. Folded into NEW-7 ticket description.
**Key design principles (unanimous):**
- Server computes N available verbs per entity every tick
- v0.1 client shows only priority-0 verb (single `[E]` prompt)
- v0.2 client renders full list — no server changes needed
- Context-sensitive priority (post-contradiction: Examine rises above Talk)
- `InteractionOptions`/`AvailableActions` embedded in ObserverSnapshot, not separate message
- Server is authoritative; client never queries content files
### 4.2 Pause System (3-State)
| State | Speed | Trigger | All 3 Agree? |
|-------|-------|---------|-------------|
| **Normal** | 100% (1.0) | Default | Yes |
| **Overlay** | 50% (0.5) | Knowledge panel, dialogue | Yes |
| **Paused** | 0% (0.0) | Spacebar (always) | Yes |
**Gestalt:** Multiplicative toggle model (`effective_speed = if pause_override { 0.0 } else { base_speed * ui_modifier }`). Multiple overlays don't stack (50% stays 50%). v0.2 extension: panel + dialogue could = 25%.
**Stig:** GDScript `PauseManager` with `SimState` enum, `_pre_pause_state` tracking for resume, overlay count tracking. Spacebar from OVERLAY_ACTIVE goes to PAUSED (not RUNNING). Questions for Dudley: does server need pause signals, or does client control?
**Dudley:** `SimSpeed` enum resource with `speed_stack` (priority-based). `SimSpeed::Overlay` ticks every 2nd frame. Server is authoritative over tick advancement. `sim_speed: f32` field in ObserverSnapshot tells client the current rate.
**Resolved (closing round):** Server-authoritative pause. Tick rate is a server simulation concern. Client is a dumb renderer — it renders ObserverSnapshots at whatever rate the server sends them. Client sends a pause IPC command to the server; that's it. Stig's `PauseManager` GDScript is reduced to sending IPC commands and reading `sim_speed` from the snapshot for visual feedback. **NEW-12 (client pause state machine) killed** — client doesn't manage time.
### 4.3 ObserverSnapshot v3
Tyre and Dudley independently produced v3 definitions. They are structurally identical:
| Field | Tyre's Proposal | Dudley's Proposal | Status |
|-------|----------------|-------------------|--------|
| `sim_speed: f32` | Yes (default 1.0) | Yes | Agreed |
| `nearby_interactions` | `Vec<NearbyInteraction>` | `Vec<EntityInteractions>` | Agreed (naming differs) |
| `active_dialogue` | `Option<ActiveDialogue>` | `Option<ActiveDialogue>` | Agreed |
| `monologue` | `Vec<MonologueDisplay>` | `Vec<MonologueDisplay>` | Agreed |
| `overheard` | `Vec<OverheardFragment>` | `Vec<OverheardDisplay>` | Agreed (naming differs) |
| `knowledge_updates` | `Vec<KnowledgeUpdate>` | Not in Dudley's R2 snapshot | Tyre adds delta updates |
| `examine_result` | `Option<ExamineResult>` | Not in Dudley's R2 snapshot | Tyre adds |
| `ticker_headlines` | `Vec<TickerHeadline>` | Not in Dudley's R2 snapshot | Tyre adds |
**Wire size estimate (Tyre):** v3 adds ~50-1500 bytes per tick on top of v2's 2-8 KB. Total: ~2-10 KB/tick at 10 tps = 20-100 KB/s. Well within IPC budget.
**Backward compatibility:** MessagePack serializes by field name. New fields use `#[serde(default)]`. v2 client reading v3 snapshot ignores unknown fields. v3 client reading v2 snapshot gets empty defaults.
### 4.4 Content Directory + Schema
Tyre produced the definitive directory tree and JSON Schema definitions:
**Directory structure:** `content/content.yaml` (manifest) + `content/schema/` (JSON Schema files) + `content/global/` (facts, factions, enums, entity-schema) + `content/districts/sova-transit/` (npcs/, locations/, triangles/, dialogue/, monologue/, routines/).
**Schemas defined:**
- `npc-profile.schema.json` — Full NPC profile with tier-conditional fields, pattern/motivation enums, axes, tells, access tiers, trust levels, friend_arc, triangle membership
- `dialogue-pool.schema.json` — Tagged dialogue lines per D-028/D-035. Role + location based, with access/trust/situation gating and knowledge_grants
- `monologue-pool.schema.json` — Character-partitioned (D-032). Trigger + prerequisite (AND-only) + priority + cooldown. 160 char max per Stig
**Validation pipeline (3-tier):**
1. Authoring time: IDE with JSON Schema autocomplete
2. Build time (`make content-validate`): JSON Schema + cross-reference validation
3. Load time: serde_yaml deserialization + semantic validation (StableId assignment, relationship wiring)
### 4.5 YAML + RON Converter
| Aspect | Tyre | Dudley | Status |
|--------|------|--------|--------|
| Content format | YAML | YAML (accepted) | Agreed |
| RON converter location | `tooling/content-tools/` | `tooling/content-converter/` | Minor naming difference |
| When converter runs | Build-time optional | Build-time optional, low priority | Agreed |
| Development loading | YAML direct | YAML direct | Agreed |
| Production loading | RON cache preferred, YAML fallback | YAML (RON is insurance) | Agreed — YAML in v0.1, RON as future optimization |
Tyre provides dual-format loader (~20 lines) with `load_with_cache()` fallback pattern. `content/.cache/` is gitignored.
---
## 5. EntityKnowledge Keys — RESOLVED: 16 Keys
Both Gestalt and Paula independently arrived at the same conclusion: **generic perspective keys, not per-archetype keys.** This resolves D-03 from Round 1.
### Convergence (Round 2 Responses)
| Point | Gestalt | Paula | Converged? |
|-------|---------|-------|-----------|
| Per-archetype keys are unsustainable | Yes (32 archetype-specific + 14 shared = 46 total) | Yes (same conclusion) | **Yes** |
| Generic keys work for all 8 archetypes | Yes | Yes | **Yes** |
| Interpretation lives in content, not schema | Yes (monologue pools provide character-specific meaning) | Yes (archetype brief + voice register + moral arc) | **Yes** |
| `social_debt` deferred to v0.2 | Yes | Accepts | **Yes** |
| `loyalty_conflict` deferred to v0.2 | Yes (inferable from `behavior_flags` + `reliability`) | Accepts | **Yes** |
### Final Resolution (Closing Round Lead Decision)
**16 total EntityKnowledge keys.** 12 existing shared keys + 4 new generic role-perspective keys. Key merges and renames applied:
#### 4 New Role-Perspective Keys (observer→target, all archetypes)
| Key | Value Enum | What It Stores |
|-----|-----------|---------------|
| `risk_assessment` | `none`, `low`, `moderate`, `high`, `critical` | How this NPC threatens the observer's position (exposure, obstruction, liability, competition — archetype-dependent) |
| `loyalty_assessment` | `solid`, `dependable`, `uncertain`, `wavering`, `hostile` | How predictably this NPC serves the observer's interests |
| `position_integrity` | `solid`, `thin`, `cracking`, `blown`, `N/A` | Status of active deception involving this NPC (cover, reputation, facade) |
| `moral_weight` | `innocent`, `peripheral`, `complicit`, `compromised`, `willing` | Observer's subjective moral assessment within their ethical framework |
**Key names adopt Paula's naming** (`risk_assessment` over `threat_to_position`, `position_integrity` over `facade_status`). **Value enums adopt Gestalt's archetype-neutral vocabulary.**
#### Key Merges and Renames
| Action | Old | New | Rationale |
|--------|-----|-----|-----------|
| **Merge** | `trust_read` | `trust_level` (existing) | "Read is the action, level is the end state." Same key, per-character interpretation. |
| **Absorb** | `secret_held` | `leverage_held` (existing, renamed) | "Secret is a subtype of leverage." Value space expanded: secrets, debts, promises, obligations, compromising positions. |
| **Rename** | `secret_confidence` | `leverage_confidence` | Follows `secret_held` → `leverage_held` rename. |
| **Defer** | `social_debt` | v0.2 | 30-minute session doesn't develop favor economy. |
| **Defer** | `loyalty_conflict` | v0.2 | Inferable from `behavior_flags` + `loyalty_assessment`. |
| **Not added** | `tell_observed`, `contradiction_flagged` | — | Tracked in `behavior_flags` (existing). No 7th key needed. |
#### Final Key Inventory (16 total)
| # | Key | Category | New/Existing |
|---|-----|----------|-------------|
| 1 | `name` | Identity | Existing |
| 2 | `role` | Identity | Existing |
| 3 | `faction` | Identity | Existing |
| 4 | `species` | Identity | Existing |
| 5 | `location` | Spatial | Existing |
| 6 | `routine_pattern` | Behavioral | Existing |
| 7 | `trust_level` | Relational | Existing (absorbs `trust_read`) |
| 8 | `leverage_held` | Relational | Existing (renamed from `secret_held`, expanded value space) |
| 9 | `leverage_confidence` | Relational | Existing (renamed from `secret_confidence`) |
| 10 | `relationship_state` | Relational | Existing |
| 11 | `behavior_flags` | Behavioral | Existing (tracks tells + contradictions) |
| 12 | `known_associates` | Social | Existing |
| 13 | `risk_assessment` | **Role-perspective** | **NEW** |
| 14 | `loyalty_assessment` | **Role-perspective** | **NEW** |
| 15 | `position_integrity` | **Role-perspective** | **NEW** |
| 16 | `moral_weight` | **Role-perspective** | **NEW** |
**This scales to all 8 archetypes without modification.** Interpretation lives in content (monologue pools, voice registers, archetype briefs), not schema. The smuggler reads `risk_assessment: "high"` as exposure risk; the detective reads it as obstruction risk; the administrator reads it as political liability. Same key, same enum, different meaning.
---
## 6. FriendArc Phase Transitions (Dudley)
Dudley produced the definitive 4-phase state machine with explicit trigger code:
| Phase Transition | Trigger | Content Dependency |
|-----------------|---------|-------------------|
| **Warmth → Trust** | Interaction count (>=3) + time elapsed (>=600 ticks / 1 game-hour) | 5-8 casual dialogue + 3-5 positive monologue |
| **Trust → Doubt** | Knowledge threshold — observer learns a doubt-triggering fact at KnowsOf+ | 5-8 deeper dialogue + 3-5 questioning monologue |
| **Doubt → Conflict** | Direct observation of contradiction (`contradiction_discovered` flag) | **1 critical monologue line** (wow moment #3) + 8-12 confrontation dialogue |
**Contradiction spatial staging:** Server schedules NPC routine deviation (Kael in Corridor B-7 during shift transition). The `check_contradiction_observation` system checks: (1) FRIEND at contradiction location, (2) within time window, (3) bonded character has Direct confidence (LOS). All 5 state changes must happen atomically within one tick: knowledge graph updated, FriendArc phase advanced, RelationshipState changed (Friendly → PersonOfInterest), monologue triggered (urgent), entity color shifted (green → amber).
**Content required per FRIEND NPC:** ~35-46 authored lines minimum. Both FRIEND NPCs: ~70-92 lines. Aligns with D-034 estimate.
**New component:** `InteractionLog` — BTreeMap tracking (target_stable_id, tick) pairs. Supports Warmth→Trust transition and future NOBODY tier promotion.
---
## 7. PC Voice Registers (Mellanie)
Mellanie produced canonical voice register specifications for both playable characters:
### Smuggler — Internal Voice Register
**One-line summary:** Watches people, not systems. Thinks in fragments. Worries about friends practically, physically, with the knot in the stomach.
| Parameter | Value |
|-----------|-------|
| Sentence length | Short. Fragments welcome. Rarely >2 sentences. |
| Vocabulary | Concrete, physical, sensory. Trade jargon without explanation. |
| Emotional register | Feeling-first, analysis second. |
| Relationship mode | First-name basis. People defined by connection, not role. |
| Observation priority | People > environment > objects. |
| Self-reference | Rare. Through physical sensation, not emotional vocabulary. |
| Humor | Dry, situational, understated. Dark when stressed. |
**5 voice anchors provided:** Baseline warm, Operational, Concerned, Hurt, Atmospheric.
**4 anti-patterns defined:** Too clinical, institutional vocabulary, analytical distance, explaining known facts.
### Detective — Internal Voice Register
**One-line summary:** Categorizes first, feels second. Thinks in complete sentences. Institutional training runs in the background.
| Parameter | Value |
|-----------|-------|
| Sentence length | Complete but not long. More structured than smuggler. |
| Vocabulary | Institutional layer over plain speech. "Noted," "flagged," "filed it." |
| Emotional register | Analysis-first. Personal breaks through as notable cracks. |
| Relationship mode | Surname-first for targets. First-name for allies. The shift IS a marker. |
| Observation priority | Patterns > people > environment. Counts things, tracks frequencies. |
| Self-reference | More common, always through professional lens. |
| Humor | Wry, observational. Appreciates irony at a distance. |
**5 voice anchors provided.** 4 comparison examples (same trigger, two characters) demonstrating voice distinctness.
### Display Constraints (Mellanie confirms Stig's R1 proposal)
| Constraint | Value |
|-----------|-------|
| Max length | ~160 characters (hard ceiling) |
| Target range | 80-120 characters (most lines), 40-80 (ideal) |
| Max visual lines | 2 |
| Word target | 10-18 words (14 average) |
| Display time | 4-6 seconds (length-adjusted) |
| Character tint | Smuggler: amber-white `#f0e0c8`, Detective: blue-white `#c8d8f0` |
---
## 8. THE FRIEND Content Pack — Kael Davan (Mellanie)
Mellanie mapped the complete Kael Davan content pack structure:
| Content Type | Lines | Phase Distribution |
|-------------|-------|-------------------|
| Kael dialogue | 36 | Terminal: 17, Bar: 13, Corridor: 6 |
| Smuggler monologue about Kael | 18 | 5 phases (Comfort 4, First Crack 4, Contradiction 3, Confrontation 3, Contaminated Trust 4) |
| Detective monologue about Kael | 10 | Identification 2, Behavioral 3, Suspicion 3, Informant 2 |
| Tell observation lines | 8 | Lattice 2, Shortened 2, Looks-left 2, Spatial 2 |
| Trust-gated lines | 13 | Insider 6, Close colleague 4, Secret hints 3 |
| Unprompted lines | 6 | Early warmth 3, Late warnings 3 |
| **PACK TOTAL** | **91** | Within D-034 range (70-100) |
**Phase distribution analysis:**
- Phase 1 (Comfort): 21 lines (23%) — heavy on dialogue, light on monologue
- Phase 2 (First Crack): 13 lines (14%) — tells ramp up
- Phase 3 (Contradiction): 7 lines (8%) — fewest lines, highest stakes
- Phase 4 (Confrontation): 16 lines (18%) — dialogue-heavy
- Phase 5 (Contaminated Trust): 16 lines (18%) — voice discipline critical
- Cross-phase: 16 lines (18%)
**Sample YAML lines provided** for each phase demonstrating prerequisite progression. Format aligns with Tyre's `monologue-pool.schema.json`.
**695 total validation (Mellanie clarifies):** 695 is the authored floor. Does not include generation-expanded output (D-028: "write 10, generate 40" for dialogue). Does not include engine-generated content (routine greetings, time-of-day variations).
---
## 9. UI Specifications Confirmed (Stig)
### Updated Bill of Materials
| System | Scenes | Scripts | Shaders | Priority |
|--------|--------|---------|---------|----------|
| Monologue renderer | 1 | 1 | 0 | P0 |
| Interaction prompt | 1 | 1 | 0 | P0 |
| Dialogue panel | 1 | 1 | 0 | P0 |
| Entity color system | 0 | 1 | 1 | P0 |
| Pause manager | 0 | 1 | 0 | P0 |
| HUD bar | 1 | 1 | 0 | P1 |
| Minimap | 1 | 1 | 1 | P1 |
| Knowledge panel | 1 | 1 | 0 | P1 |
| News ticker | 1 | 1 | 0 | P1 |
| Fog rendering | 0 | 0 | 1 | P0 |
| **TOTAL** | **7** | **9** | **3** | |
**Changes from Round 1:** Reduced from 9 scenes to 7. Added 1 shader (fog rendering). Pause manager added (P0, new in R2).
### Monologue Display Parameters (Stig, confirmed by Mellanie)
| Parameter | Value |
|-----------|-------|
| Max characters | 160 |
| Max lines | 2 |
| Base duration | 4.0s |
| Short duration (<80 chars) | 3.0s |
| Urgent chime duration | 5.0s |
| Fade in | 0.3s |
| Fade out | 0.5s |
| Interruption fade | 0.15s |
| Cooldown between lines | 2.0s minimum |
| Max queue depth | 1 (drop lower-priority) |
**Priority ordering:** observe_anomaly (1) > witness_interaction (2) > discover_evidence (3) > post_conversation (4) > hear_sound (5) > observe_npc (6) > enter_location (7) > return_visit (8) > time_idle (9).
**Critical UI interaction:** Monologue fires during dialogue (for wow moment #3). Monologue sits in world layer; dialogue sits in HUD layer. Two voices simultaneously — one external, one internal.
### Interaction Prompt — Single-Action Extensible
v0.1: `[E] Talk` / `[E] Examine` — single keybind, context-sensitive verb.
v0.2: `[E] Talk [F] Observe` — horizontal label row, same prompt position.
The `verbs[]` field (renamed from `actions[]` per D-060) exists in the protocol from day one. The v0.1 client ignores it. The v0.2 client reads it. No protocol change needed.
---
## 10. Ticket Analysis — Finalized (SI)
### Lead Decision Impact on Tickets
| Decision | Ticket Impact |
|----------|---------------|
| D-NPC | NEW-1 simplified to "apply Gestalt's mapping." Paula's layer → v0.2 annotation. |
| D-FORMAT | Confirms C-series as YAML. Adds NEW-8 (RON converter). |
| D-INTERACT | NEW-7 reframed. Adds NEW-9 (server InteractionOptions) + NEW-10 (client extensible prompt). |
| D-PAUSE | Adds NEW-11 (server tick rate scaling). ~~NEW-12 (client pause state machine)~~ **killed in closing round** — client is a dumb renderer. |
### Final Ticket Count
| Category | Count | Teams |
|----------|-------|-------|
| Wiki fixes (A-series) | 8 | copy |
| Style guides & specs (B-series) | 5 | copy |
| Content directory & schema (C-series) | 10 | copy (1), server (8), ci (1) |
| Design specs (D-series) | 2 | server (1), copy (1) |
| Round 1 new tickets (NEW 1-7) | 7 | copy |
| Round 2 new tickets (NEW 8-13) | 5 | server (4), client (1) |
| **Total new tickets** | **37** | **copy (21), server (13), client (1), ci (1)** |
| Existing ticket updates | 10 | — |
**Delta from Round 1:** +5 tickets (NEW-8 through NEW-13 from lead decisions, minus NEW-12 killed in closing round). Removed: D3 (killed), A5 (deferred), D1 (deferred), NEW-12 (killed — client doesn't manage time). Merged: A3 into #319, #310 into B4.
### Sprint 3 Allocation
**Copy team (15 tickets):**
- P0: #261 (Dual Lens Guide, **critical path root**), C1 (Content directory design), A1 (canonical names), A2 (Naia Tamm rename), A7 (smuggler attributes)
- P1: B2 (MIRROR spec), B4 (smuggler voice + moral arc), NEW-1 (NPC mapping), NEW-5 (wow moment checklist), A10 (Nils stub), A11 (Triangle 1 fix)
- P2: B3 (PC-as-NPC), A8 (shortcode fix), NEW-2 (Drin expansion), NEW-7 (interaction verb spec)
**Server team (4 additions):** C2 (directory skeleton), C3 (schemas), NEW-9 (InteractionOptions), NEW-11 (tick rate scaling)
**Client team (1 addition):** NEW-10 (extensible prompt). ~~NEW-12 killed~~ — client sends pause IPC command; server manages tick rate.
### Critical Path (Revised)
Two parallel chains:
**Chain 1 — Content Authoring:**
```
#261 (Dual Lens Guide) [P0, ROOT]
-> B4 (Smuggler voice + moral arc)
-> A6 (Smuggler FactId text) [Sprint 4]
-> NEW-4 (Monologue pool ~200 lines) [Sprint 5]
-> #297 (FRIEND: Kael) [Sprint 5]
-> #298 (FRIEND: Sera) [Sprint 5]
-> #190, #191, #192 (Content packs) [Sprint 5]
```
**Chain 2 — Content Architecture:**
```
C1 (Content dir design) [P0]
-> C2 (skeleton) + C3 (schemas) [Sprint 3]
-> C4-C8 (YAML population) [Sprint 4]
-> NEW-3 (wiki->YAML conversion) [Sprint 4]
-> #326 (YAML loader) [Sprint 4]
-> C9 (validator) [Sprint 4]
```
**Independent chains (Sprint 3):**
- A10 (Nils stub) → A11 (Triangle 1 fix)
- NEW-9 (InteractionOptions, server) → NEW-10 (extensible prompt, client)
- NEW-11 (tick rate scaling, server) — no client counterpart (client reads `sim_speed` from snapshot)
### Risks (SI)
1. **#261 remains critical path root.** Every content authoring ticket flows through it. Recommended: assign Paula, time-box 5 days.
2. **Sprint 3 copy team has 15 tickets.** 7 are small/parallelizable. Real load: #261, C1, B2, B4, A11.
3. **Server Sprint 3 already heavy** (10 existing + 4 new). C2/C3 blocked by C1 anyway.
4. **Content conversion (NEW-3) is Sprint 4 bottleneck.** Start with 3 Tier 1 NPCs as soon as C2 lands.
---
## 11. Wiki Fix Execution Plan (Paula)
Paula produced execution-ready content changes for each priority level:
| Priority | Change | Files | Status | Effort |
|----------|--------|-------|--------|--------|
| P0-1 | Naia Tamm rename | 16 files | Exact per-file changes specified | ~2 hours |
| P0-2 | Nils Davan stub | 1 new + 3 cross-ref | Full draft ready | ~30 min |
| P0-3 | Drin Tier 2 expansion | 1 rewrite + index | Full draft ready | ~1 hour |
| P1-1 | Canonical names | 10 headers + index | Name table ready; 3 need Miri validation | ~1 hour |
| P1-2 | Triangle 1 escalation fork | index + 2 NPC notes | Self-contained version (v0.1) | ~1 hour |
| P2-1 | Smuggler-lens sections (17 NPCs) | 17 profiles | Template ready; per-NPC content needed | ~8-10 hours |
| P2-2 | PC-as-NPC profiles | 2 new files | Gap identified; not yet drafted | ~3-4 hours |
| P2-3 | FactId catalog smuggler entries | 1 file | Gap identified; not yet drafted | ~2 hours |
**P0-1 and P0-2 can start immediately.** P0-3 blocked by A-01 formalization (consensus confirmed). P1-1 blocked by Miri validation (3 names). P1-2 depends on P0-2.
**P1-2 (Triangle 1) — self-contained revision:** Cross-triangle cascade removed per D-INTERACT. Path B no longer triggers Maret's discovery. Path C no longer makes detective investigation easier. Emotional weight preserved within Triangle 1.
---
## 12. Dependencies Matrix
| Agent | Waiting On | From | Blocks | Status |
|-------|-----------|------|--------|--------|
| **Stig** | IPC message format (ObserverSnapshot v3 struct) | Dudley/Tyre | All client UI | Open |
| ~~**Stig**~~ | ~~Pause architecture decision~~ | ~~Dudley~~ | ~~Pause manager~~ | **Resolved** — server-authoritative |
| **Stig** | Font selection, diegetic styling | Araminta | Knowledge panel visual | Open |
| **Stig** | First monologue content (5-10 lines) | Mellanie | Monologue renderer testing | Open |
| **Dudley** | ObserverSnapshot v3 sign-off | Tyre | Protocol implementation | Open |
| **Dudley** | FactId catalog (machine-readable) | Gestalt/Paula | Prerequisite evaluation | Open |
| **Dudley** | FRIEND content packs (phase-tagged) | Mellanie | FriendArc integration testing | Open |
| **Dudley** | Contradiction spatial data (location, time window) | Paula | Spatial staging system | Open |
| **Mellanie** | Content directory confirmed | Tyre | File structure for packs | Open |
| **Mellanie** | FactId catalog stabilized | Gestalt/Paula | Prerequisite placeholders | Open |
| ~~**Mellanie**~~ | ~~EntityKnowledge key resolution~~ | ~~Lead~~ | ~~Prerequisite vocabulary~~ | **Resolved** — 16 keys, 4 role-perspective |
| **Paula** | Miri validation (3 NPC surnames) | Miri | Canonical name application | Open |
---
## 13. Decisions Ready to Formalize
### From Lead's Round 2 Decisions
| Proposed ID | Decision | Source |
|-------------|----------|--------|
| D-049 | **YAML is the content file format for v0.1.** RON converter available as optional build-time tool in `tooling/`. Server loads YAML directly in development; RON cache is a production optimization. | D-FORMAT lead decision; Tyre design; Dudley acceptance |
| D-050 | **Gestalt's NPC pattern/motivation mapping is canonical for v0.1.** Paula's emotional/narrative layer becomes v0.2 annotations. Version-toggle approach: same NPCs, different analytical depth per version. | D-NPC lead decision; Gestalt definitive table; Paula versioned layer |
| D-051 | **v0.1 ships single context-sensitive action; multi-verb architecture modeled underneath.** Server computes N available actions per entity. v0.1 client shows priority-0 only. v0.2 client reads full list. No server changes for v0.2 multi-verb. | D-INTERACT lead decision; Tyre architecture; Dudley implementation; Stig client design |
| D-052 | **3-state pause system: Normal (100%), Overlay (50%), Paused (0%). Server-authoritative.** Spacebar always pauses from any state. UI overlays (knowledge panel, dialogue) trigger 50% speed. Multiple overlays don't stack below 50%. Spacebar resumes to pre-pause state. **Server controls tick rate; client is a dumb renderer.** Client sends pause IPC command to server. Client reads `sim_speed` from ObserverSnapshot for visual feedback. NEW-12 (client pause state machine) killed. | D-PAUSE lead decision + closing round resolution; Gestalt mechanical design; Dudley server SimSpeed authoritative |
| D-053 | **Self-contained triangle forks for v0.1.** Independent decision state machines, shared NPC state. No cross-triangle cascade. Players observe cross-triangle effects emergently through NPC behavior. v0.2 adds storyteller-managed cascade. | Gestalt confirmation; Tyre recommendation (R1); Paula revised Triangle 1 |
| D-054 | **ObserverSnapshot v3 protocol.** Extends v2 with: sim_speed, nearby_interactions, active_dialogue, monologue, overheard, knowledge_updates, examine_result, ticker_headlines. Backward compatible via serde defaults. Wire overhead ~50-1500 bytes/tick. | Tyre full definition; Dudley compatible definition |
| D-055 | **16 EntityKnowledge keys total. 4 new generic role-perspective keys: `risk_assessment`, `loyalty_assessment`, `position_integrity`, `moral_weight`.** All observer→target. `trust_read` merged into existing `trust_level`. `secret_held` renamed to `leverage_held` with expanded value space (secrets, debts, promises, obligations, compromising positions). `secret_confidence` renamed to `leverage_confidence`. `social_debt` and `loyalty_conflict` deferred to v0.2. `tell_observed` and `contradiction_flagged` tracked in existing `behavior_flags` — no dedicated keys. Scales to all 8 archetypes without schema changes. | Gestalt generic architecture; Paula generic architecture; closing round lead resolution |
| D-056 | **PC voice registers defined.** Smuggler: feeling-first, fragments, concrete/physical, first-name basis. Detective: analysis-first, complete sentences, institutional vocabulary, surname-first for targets. Both characters have 5 voice anchors, 4 anti-patterns, and 4 comparison examples. | Mellanie canonical specifications |
| D-057 | **Content directory structure: `content/` with `schema/`, `global/`, `districts/` top-level split.** JSON Schema validation at build time. Dialogue by location + role (not NPC). Monologue partitioned by character. `canonical_id` format: `npc:{slug}`, `loc:{district}:{location}`. | Tyre finalized tree + schema definitions |
| D-058 | **THE FRIEND content pack template: Kael Davan.** 91 lines across 5 arc phases + cross-phase. Pack validates tag taxonomy, load correctness, trigger appropriateness. Structure becomes template for all subsequent content packs. | Mellanie pack structure + sample YAML |
| D-059 | **Monologue display constraints.** 160 char max, 2-line max, 4-6s display time, 2s cooldown, queue depth 1 (drop lower priority), 9-level priority ordering with observe_anomaly highest. | Stig constraints; Mellanie adoption |
| D-060 | **`actions[]` renamed to `verbs[]` across all surfaces.** Scope: server code, client code, YAML content files, wiki docs, decision files. Folded into NEW-7 ticket description. | Closing round lead decision |
| D-061 | **No ticket merges across domain teams.** Shared epics are fine, but each team gets its own ticket with its own definition of done. | Closing round lead decision (process rule) |
### From Round 1 (Carried Forward — Unchanged)
| Proposed ID | Decision | Source |
|-------------|----------|--------|
| D-042 | Drin promoted from Tier 3 to Tier 2 | Round 1 consensus (A-01) |
| D-043 | THE NOBODY mechanic deferred to v0.2; hidden data ships in v0.1 | Round 1 consensus (A-02) |
| D-044 | v0.1 interaction model: 7 interactions (Move, Look, Monologue, Examine Object, Examine NPC, Talk, Overhear) | Round 1 consensus (A-04) |
| D-045 | v0.1 scope: add News ticker, PC-as-NPC, Time progression, Relationship state transitions to IN list | Round 1 consensus (A-14, A-15, A-16) |
| D-046 | v0.1 scope: add Inventory, Stealth, Combat, Player-facing save/load, Lattice modification to explicit OUT list | Gestalt (Round 1) |
| D-047 | v0.1 triangles: 3 active forks (T1, T2, T4), 2 passive tensions (T3, T5) | Round 1 consensus (A-07) |
| D-048 | Client receives all text from server via state updates; client does not load or evaluate content files | Round 1 consensus (A-12) |
---
## 14. Open Items
### Resolved in Closing Round
| # | Item | Resolution | Decision |
|---|------|-----------|----------|
| Q-012 | EntityKnowledge generic key count: 4 vs 6 | **16 total keys.** 4 new role-perspective (`risk_assessment`, `loyalty_assessment`, `position_integrity`, `moral_weight`). `trust_read` → `trust_level` (merge). `secret_held` → `leverage_held` (absorb + expand). `secret_confidence` → `leverage_confidence` (rename). `tell_observed`/`contradiction_flagged` tracked in `behavior_flags`. No 7th key. | D-055 |
| Q-013 | Pause authority: client vs server | **Server-authoritative.** Client is a dumb renderer. Sends pause IPC command. Reads `sim_speed` from snapshot. NEW-12 killed. | D-052 (updated) |
| Q-016 | `actions[]` → `verbs[]` scope | **Confirmed across all surfaces:** server code, client code, YAML content, wiki docs, decision files. Folded into NEW-7. | D-060 |
### Still Open
| # | Item | Owner | Status | Priority |
|---|------|-------|--------|----------|
| Q-014 | 3 NPC surnames awaiting Miri validation: Drin Vassar, Sess Torin, Tav Lenn. | Miri | Blocked on world-building | Low |
| Q-015 | Interaction struct naming: `AvailableActions`/`ActionOption` (Tyre) vs `EntityInteractions`/`AvailableAction` (Dudley). Trivial — needs one canonical choice. | Tyre/Dudley | Sprint 3 implementation | Low |
| Q-017 | Mellanie's 695 authored items — validated by SI as scope input but not independently verified by other agents. | SI/Mellanie | Informational | Low |
---
## 15. Workshop Summary
### What This Workshop Produced
1. **Canonical NPC mapping** — 17 NPCs with pattern + motivation, through collaborative resolution (Gestalt changed 6 of 10 positions based on Paula's arguments)
2. **Content architecture** — Full directory tree, 3 JSON Schema definitions, 3-tier validation pipeline, dual-format loader
3. **Interaction architecture** — Multi-verb server model with single-action client filter, extensible without server changes
4. **Pause system** — 3-state model with unanimous design convergence across 3 agents
5. **ObserverSnapshot v3** — Full protocol definition with backward compatibility, produced independently by 2 agents with structural agreement
6. **PC voice registers** — Canonical specifications for both characters with voice anchors, anti-patterns, and comparison examples
7. **FRIEND content pack template** — 91-line Kael Davan pack with phase-by-phase structure, prerequisite progression, and sample YAML
8. **FriendArc state machine** — 4-phase transitions with explicit trigger code and content dependencies
9. **Wiki fix execution plan** — 8 prioritized changes with per-file specifications for top-priority items
10. **37 new tickets + 10 updates** — Full Sprint 3-5 roadmap across copy, server, client, and CI teams (NEW-12 killed in closing round)
### What Remains Unresolved
- 3 NPC surnames awaiting Miri validation (Q-014)
- Interaction struct naming — trivial, resolved at implementation time (Q-015)
- 695 authored items scope validation (Q-017, informational)
### Critical Path Unchanged
**#261 (Dual Lens Authoring Guide) remains the single biggest blocker.** Blocks 9 downstream tickets. Recommended: assign Paula, Sprint 3 P0, time-box 5 days.
---
*Qatux, Round 2 tracking (updated with closing round resolutions). For the record: all 7 Round 2 responses cataloged. 4 lead decisions implemented + 3 closing round resolutions (Q-012: 16 keys, Q-013: server-authoritative pause, Q-016: verbs[] rename confirmed). 10 Round 1 disagreements resolved (6 changed to Paula, 3 kept Gestalt, 1 deferred by design). 20 decisions ready to formalize (D-042 through D-061: 13 new from Round 2 + closing, 7 carried from Round 1). 37 new tickets proposed + 10 updates (NEW-12 killed). 3 minor items remain open. Workshop complete.*
docs/workshops/v01-content-scoping/round2-tyre.md
-1154
View File
File diff suppressed because it is too large Load Diff
docs/workshops/v01-content-scoping/si-ticket-changes.md
-295
View File
@@ -1,295 +0,0 @@
# v0.1 Content Scoping — Ticket List (Final)
**Author:** SI (Project Manager)
**Source:** v0.1 Content Scoping Workshop (Rounds 1-2), Wiki Review Workshop (Round 2 ticket list superseded)
**Status:** Proposals only — awaiting lead approval before database creation
**Corrections applied (closing round):**
1. C9 → Sprint 3 (same crate as C3)
2. #326 split into Phase 1 (Sprint 3) + Phase 2 (Sprint 4)
3. NEW-9 expanded: proximity detection + `verbs[]`
4. NEW-12 killed (pause is server-only; client sends IPC command)
5. NEW-10 stays separate from #240 (one ticket per team, no shared tickets)
6. NEW-14 added: UI microcopy
7. `verbs[]` rename folded into NEW-7
8. #237 → #88 dependency added
9. A2 file count: ~16 files (Paula's full cascade)
10. A7 description: specific 4 new keys + 2 renames, 16 total
11. B2 acceptance criteria added
12. NEW-1: Gestalt-Paula synthesis (not Gestalt-only)
13. C1: mod-compatible conventions (no overlay implementation)
14. #86 ECS component list updated to workshop output
---
## Existing Ticket Updates
| ID | Title | Action | Sprint |
|----|-------|--------|--------|
| #368 | Knowledge vocabulary for v0.1 content | **Close** — wiki at `wiki/` is the delivered output. | Sprint 2 (done) |
| #369 | Wiki Review Workshop Outputs (epic) | **Repurpose** as parent epic for all v0.1 content scoping tickets. Update description to reflect this workshop's scope. | — |
| #301 | Wiki taxonomy and structure | **Assign to copy.** Downscope: Sova district structure only for v0.1. | Sprint 3 |
| #319 | Krenn System wiki entry | **Merge with A3.** Expanded: wiki page + seed.yaml reference implementation. Assign to copy. | Sprint 4 |
| #261 | Dual Lens Authoring Guide | **CRITICAL PATH ROOT.** Assign to copy, owner Paula. Blocks 9 downstream tickets. | Sprint 3 (P0) |
| #310 | Character voice speech patterns | **Subsume into B4.** Close #310 when B4 lands. | Sprint 3 (via B4) |
| #306 | News ticker / Meridian feed content | **Confirm scope:** ~20 dual-lens headlines. Assign to copy. | Sprint 4 |
| #326 | YAML content loader | **Split into two tickets.** Phase 1: loader skeleton + fixture data (Sprint 3, server, blocked by C1+C2+C3). Phase 2: real content loading (Sprint 4, server, blocked by C4-C8 + NEW-3). | Sprint 3 / 4 |
| #86 | Core NPC components | **Update ECS component list** to workshop output: ThematicPattern, FunctionalMotivation, FriendArc, ContentTier, AccessTierMap, TrustLevels, NpcRoutine, MoodState, TriangleMembership, InteractionLog. | Sprint 3 |
| #88 | Daily routine system | **Add dependency:** blocked by #237 (A* pathfinding). Needs NPC routine YAML from content conversion. | Sprint 3 |
---
## New Tickets
### A. Wiki Content Fixes (copy team)
| ID | Title | Type | Pri | Sprint | Blocked By | Description |
|----|-------|------|-----|--------|------------|-------------|
| A1 | Apply canonical full names to all NPC wiki pages | task | med | 3 | — | Apply Miri's 12 full names to NPC wiki pages. Update Core Identity blocks, environmental text references (manifests, shift rosters, Commission kiosk). |
| A2 | Rename Hael → Naia Tamm across all wiki files | task | med | 3 | — | Phonetic collision fix (Kael/Hael). Find-and-replace across ~16 files (Paula's full cascade). Triangle 4 becomes Naia-Kael-Sera. Update all relationship references, triangle diagrams, cross-references. |
| A6 | Add smuggler-perspective FactId progression text | task | high | 4 | B4 | Add smuggler-path text for all FactIds where smuggler starts at KnowsDetails or has different knowledge path than detective. |
| A7 | Update entity-attributes.md — smuggler role-perspective keys | task | high | 3 | — | Add 4 new role-perspective keys: `risk_assessment`, `loyalty_assessment`, `position_integrity`, `moral_weight`. Rename `secret_held` → `leverage_held` (broader scope: secrets, debts, promises, obligations). Rename `secret_confidence` → `leverage_confidence`. Update `trust_level` description to absorb `trust_read` scope. All keys are observer→target. Total after update: 16 canonical keys. |
| A8 | Standardize location shortcodes in monologue-guide.md | task | med | 3 | — | Fix hub_m_ → terminal_m_ inconsistency. Canonical shortcodes: terminal, bar, corridor. Add shortcode reference table. Add situation overlap rules and mood exclusivity rules. |
| A10 | Stub NPC profile for Nils Davan (off-stage) | task | med | 3 | — | Minimal off-stage profile: Core Identity, relationship to Kael (siblings), role in ring (upstream pressure), known attributes by other NPCs. |
| A11 | Fix Triangle 1 (Hub Power) — Volume Escalation decision | story | high | 3 | A10 | Add smuggler decision fork: side with Nils (louder signal), side with Voss (internal tension), or split the route (new exposure surface). Each option cascades within T1 only — self-contained, no cross-triangle cascade (A-17). Includes Nils partial presence via lattice message (~5-8 lines). |
| A12 | Create environmental text examples file | task | med | 4 | A3/#319 | Create wiki/authoring/environmental-text-examples.md. 4 text types: bar menu, safety notice, news ticker cycle, corridor graffiti. Krenn-voiced with cultural notes + monologue pairings (smuggler + detective). Needed for wow moment #1 (Arrival). |
### B. Style Guides & Specs (copy team)
| ID | Title | Type | Pri | Sprint | Blocked By | Description |
|----|-------|------|-----|--------|------------|-------------|
| B1 | NPC Authoring Style Guide | story | crit | 5 | A3, A4, A7, B2, B4 | Combined document: tier templates (Paula), authoring rules (Mellanie conventions, Gestalt constraints, Ozzie anchor line), regional culture (Miri), content pipeline (Tyre). Reframed as generator specification — this IS the NPC generator input format. Most complex ticket; many blockers. |
| B2 | THE MIRROR pattern spec | story | high | 3 | — | Define honest-character NPC pattern. No contradiction arc, no secret, no tell. Tier 1 emotional depth. **v0.1 acceptance criteria:** Pattern definition with mechanical rules, content requirements (50-70 lines, 10-axis profile), tell system rules (MIRROR has none), Naia Tamm as reference implementation. Output becomes generator template. |
| B3 | PC-as-NPC unified spec | story | high | 3 | A7 | Unified spec: starting knowledge graph, starting relationship map, reverse knowledge (bidirectional — Gestalt's critical insight), orientation monologue (Ozzie's first 60 seconds), agency boundaries, authored relationship stubs (Gore's requirement), tell inversion. 9-step conversion checklist for content authors. v0.1 scope: 2 PC briefs (smuggler, detective). |
| B4 | Smuggler voice card + moral arc spec | story | high | 3 | A7 | Two deliverables: (1) Smuggler voice card — paired examples with detective showing dual-lens register differences. Thinks in people vs data, first names vs surnames, fragments vs complete sentences, Krenn substrate vocabulary. (2) Smuggler moral arc — 4 phases (Comfort→Doubt→Reckoning→Compromise), smuggler-specific FactIds, monologue triggers. Subsumes #310 (Character voice speech patterns). |
| B5 | NPC-format briefs for both PCs — Concept A v0.1 | story | high | 4 | B3 | When you play the smuggler, the detective exists as an NPC (and vice versa). NPC-mode behavior scripts (5-7 routine entries each), reverse dual-lens notes, observation monologue for PC seeing other-PC-as-NPC (3-5 lines per character). ~20-30 authored items total. |
### C. Content Directory & Schema (split teams)
| ID | Title | Type | Pri | Sprint | Team | Blocked By | Description |
|----|-------|------|-----|--------|------|------------|-------------|
| C1 | Content directory structure design doc | story | high | 3 | copy | — | Document converged structure: `_meta/` + `_schema/` (infrastructure, underscore prefix), `global/` + `districts/` (game content). Canonical_id format (`{system}.{station}.{district}.{type}.{slug}`). Mod-compatible directory conventions (no overlay implementation). District as atomic pack unit. Informs all content implementation. |
| C2 | Create content/ directory skeleton | task | high | 3 | server | C1 | Create directory tree with empty YAML stubs. `_meta/`, `_schema/`, `global/` (factions, technology, contraband, knowledge, enums, regions), `districts/sova-transit/` (district.yaml, npcs/, locations/, templates/, triangles/, lines/). |
| C3 | Content schema definitions (YAML Schema files) | story | high | 3 | server | C1 | Create `_schema/` with validation schemas: npc.schema.yaml (tier-conditional rules), location.schema.yaml, faction.schema.yaml, template.schema.yaml, fact.schema.yaml, dialogue.schema.yaml, monologue.schema.yaml, district.schema.yaml, pool.schema.yaml. |
| C4 | Create global/enums/ YAML files from D-035 | task | med | 4 | server | C2 | Populate enums: situations (13), topics (9), moods (8), triggers (9), access-tiers (5), activities (new — from Gestalt routine format + Miri cultural patterns). |
| C5 | Create global/knowledge/entity-attributes.yaml | task | med | 4 | server | C2 | Machine-readable entity attribute definitions. 16 canonical keys after A7 update (14 original, 4 new, 2 renamed). |
| C6 | Create pools.yaml for v0.1 seed-time selection | task | med | 4 | server | C2 | Sova single-candidate pools: friend_smuggler (kael-davan), friend_detective (sera-venn), bar_regulars, compromised_inspector, primary_contraband. Architecture supports N candidates; v0.1 has 1 each. |
| C7 | Create template YAML files with role slot definitions | task | med | 4 | server | C2 | 3 social sites: logistics-hub.yaml, bar.yaml, smuggling-ring.yaml. Each declares named role slots with count ranges, required flags, pool references, triangle constraints. |
| C8 | Create triangle YAML files for 5 v0.1 triangles | task | med | 4 | server | C2 | 5 triangles: hub-power (T1, active fork), worried-knowledge (T2, active fork), bar-tensions (T3, passive), worried-partner (T4, active fork), informant-question (T5, passive). Self-contained forks — no cross-triangle cascade (A-17). |
| C9 | Implement make validate-content CLI | story | high | 3 | server | C3 | Structural + tier-conditional content validation. Same crate as C3 schemas. Reads `_schema/` definitions, validates all YAML in `content/`. v0.1 scope: structural validation (required fields, type checks, enum matching) + tier-conditional rules. v0.2: cross-reference validation (FactId existence, NPC slug resolution). |
| C10 | Pre-commit FactId typo check | task | med | 4 | ci | — | Grep-based pre-commit check validating FactId references in YAML content files against canonical facts.yaml. Cheap v0.1 bridge until full cross-reference validation lands in C9 v0.2. |
### D. Design Specs
| ID | Title | Type | Pri | Sprint | Team | Blocked By | Description |
|----|-------|------|-----|--------|------|------------|-------------|
| D2 | Seed configuration schema design | story | med | 4 | server | — | Schema for what the randomizer produces at game-start: FRIEND selections, social site population, compromised NPC, contraband type, entanglement overrides. v0.1 has single-candidate pools but architecture must support N. Saved with game state. Location: runtime/ (not content/). Constrained by D-029 ratio (30/50/20). |
| D4 | News ticker headline pool | task | med | 4 | copy | — | ~20 dual-lens headlines for Meridian feed at Lera's. Mix: freight/commodity data, Assembly politics, local infrastructure, sports, Commission advisories. Each headline works as a dual-lens monologue trigger. |
### NEW. Tickets from Workshop Rounds 1-2
| ID | Title | Type | Pri | Sprint | Team | Blocked By | Description |
|----|-------|------|-----|--------|------|------------|-------------|
| NEW-1 | Apply Round 2 NPC pattern/motivation mapping | task | high | 3 | copy | — | Apply the Round 2 finalized NPC pattern/motivation mapping (Gestalt-Paula synthesis) to wiki and content files. 17 NPCs × (pattern + motivation). Includes Harek's structural role formalization (Paula Gap 7). |
| NEW-2 | Drin Tier 2 profile expansion | task | med | 3 | copy | NEW-1 | Drin confirmed promoted to Tier 2 (A-01 consensus). Expand wiki profile to full Tier 2 depth: all 10 profile axes, smuggler lens section, triangle membership formalized for T2 and T5. |
| NEW-3 | Wiki → YAML content conversion (Sova NPCs) | story | high | 4 | copy | C1, C2, C3 | Convert 17 NPC wiki profiles to engine-readable YAML in content/districts/sova-transit/npcs/. Includes routine YAML layer (Paula Gap 3), triangle fork decision points (Gap 4), location smuggler detail (Gap 6). Must match schemas from C3. Tyre estimates 2-3 full days. |
| NEW-4 | Monologue content pool — minimum viable (~200 lines) | story | high | 4 | copy | #261, B4 | ~100 lines per character. Categories: arrival observations, NPC routine commentary, environmental flavor, contradiction hints, idle reflections, tutorial/orientation. Follows Mellanie's authoring order (FRIEND packs first, then fill to ~200). |
| NEW-5 | v0.1 wow moment content checklist | task | high | 3 | copy | — | Map D-039's 6 wow moments to specific content deliverables + implementation tickets. Track completion. Acceptance: every moment has identified content + code backing it. |
| NEW-6 | PC-as-NPC content authoring | story | high | 5 | copy | B3, B5, #297, #298 | Author the actual PC-as-NPC lines: 5-7 routine entries per character, 3-5 observation monologue lines, reverse dual-lens notes. ~25 authored items (Mellanie's budget). Blocked by FRIEND packs — must know who the characters ARE before writing how they appear as NPCs. |
| NEW-7 | v0.1 interaction verb spec + `verbs[]` terminology | task | med | 3 | copy | — | Document the 7 interaction types (A-04: Move, Look, Monologue, Examine Object, Examine NPC, Talk, Overhear). Define triggers, UI needs, server events per type. v0.1 surfaces single context-sensitive action; architecture supports N verbs via `verbs[]`. Includes wiki + decisions rename: "interaction" → "`verbs[]`" terminology where appropriate. Soft dependency for NEW-9. |
### NEW-R2. Tickets from Lead Round 2 Decisions
| ID | Title | Type | Pri | Sprint | Team | Blocked By | Description |
|----|-------|------|-----|--------|------|------------|-------------|
| NEW-8 | YAML → RON converter tool | task | med | 4 | server | C1 | Build-time converter: reads content YAML, emits RON. Lives in `tooling/`. Runs as make target (`make content-ron`). Not on critical path — engine consumes YAML in v0.1; RON is future-proofing for engine performance if needed. |
| NEW-9 | Proximity detection + multi-verb InteractionOptions (`verbs[]`) | story | high | 3 | server | — | Proximity detection system + server-side `InteractionOptions` component modeling N available actions per entity via `verbs[]`. Without proximity, InteractionOptions has no trigger. v0.1 client picks first/best verb; v0.2 client shows menu. Must not be throwaway. Includes ObserverSnapshot v2 → v3 protocol extension for interaction data. Soft dependency on NEW-7 (verb definitions). |
| NEW-10 | Interaction prompt — client extensible prompt system | story | high | 3 | client | NEW-9 | Client-side interaction prompt designed for extensibility. v0.1: single context-sensitive E prompt. Architecture supports v0.2 multi-verb menu. Prompt system reads `InteractionOptions` from server state. Separate from #240 (Player interaction system and dispatcher) — different team, different definition of done. |
| NEW-11 | Pause system — server tick rate scaling | story | med | 3 | server | — | Tick rate supports 3 states: full speed (normal play), 50% speed (UI overlay open — knowledge panel, dialogue), 0% (spacebar pause). Server receives pause/speed commands from client via IPC. |
| NEW-13 | Line previewer CLI | task | med | 4 | server | C3, C9 | CLI tool to preview monologue/dialogue line selection for a given game state. Lives in `tooling/`. Helps content authors test prerequisite logic without running the full game. Tyre's recommendation for content tuning. |
| NEW-14 | UI microcopy | task | med | 5 | client | Stig UI spec | ~50 strings: interaction prompt labels, knowledge panel labels, relationship state descriptors, HUD labels, tutorial text. Blocked by Stig's UI element specs from Sprint 3. |
---
## Sprint Plan
### Sprint 3: Know — Copy Team (Content Foundation)
**Goal:** Deliver content specs and wiki fixes that unblock server implementation and content authoring.
| Pri | Ticket | Title | Owner Hint | Effort |
|-----|--------|-------|------------|--------|
| **P0** | **#261** | **Dual Lens Authoring Guide** | **Paula** | **Large** |
| **P0** | **C1** | **Content directory structure design** | **Tyre/Gestalt** | **Medium** |
| P0 | A1 | Apply canonical full names | Paula | Small |
| P0 | A2 | Hael → Naia Tamm rename (~16 files) | Paula | Small |
| P0 | A7 | Smuggler role-perspective keys (16 total) | Paula | Small |
| P1 | B2 | MIRROR pattern spec + Naia reference impl | Gestalt/Gore | Medium |
| P1 | B4 | Smuggler voice + moral arc (subsumes #310) | Gore/Mellanie | Medium |
| P1 | NEW-1 | NPC pattern/motivation mapping (Gestalt-Paula synthesis) | Gestalt | Small |
| P1 | NEW-5 | Wow moment content checklist | SI | Small |
| P1 | A10 | Nils Davan stub | Paula | Small |
| P1 | A11 | Triangle 1 fix (Volume Escalation) | Gestalt/Paula | Medium |
| P2 | B3 | PC-as-NPC spec | Gestalt/Paula | Medium |
| P2 | A8 | Shortcode fix | Mellanie | Small |
| P2 | NEW-2 | Drin Tier 2 profile expansion | Paula | Small |
| P2 | NEW-7 | Interaction verb spec + `verbs[]` terminology | Gestalt | Small |
**Copy Sprint 3 total: 15 tickets (5 P0, 6 P1, 4 P2)**
### Sprint 3: Know — Server Team (Content-Adjacent Additions)
| Pri | Ticket | Title | Effort |
|-----|--------|-------|--------|
| P1 | C2 | Content/ directory skeleton | Small |
| P1 | C3 | Content schema definitions | Medium |
| P1 | C9 | validate-content CLI (same crate as C3) | Medium |
| P1 | NEW-9 | Proximity detection + InteractionOptions (`verbs[]`) | Medium |
| P1 | #326-P1 | Content loader Phase 1 — skeleton + fixtures | Medium |
| P2 | NEW-11 | Pause system — tick rate scaling | Small |
**Server Sprint 3 additions: 6 tickets (in addition to existing 10)**
### Sprint 3: Know — Client Team (Additions)
| Pri | Ticket | Title | Effort |
|-----|--------|-------|--------|
| P1 | NEW-10 | Interaction prompt — extensible prompt system | Medium |
**Client Sprint 3 addition: 1 ticket**
### Sprint 4: Content Conversion + Authoring Begins
| Ticket | Title | Team | Blocked By |
|--------|-------|------|------------|
| NEW-3 | Wiki → YAML conversion (17 NPCs) | copy | C1, C2, C3 |
| C4 | Enum YAMLs from D-035 | server | C2 |
| C5 | Entity-attributes YAML | server | C2 |
| C6 | Pools YAML | server | C2 |
| C7 | Social site template YAMLs | server | C2 |
| C8 | Triangle YAMLs | server | C2 |
| C10 | Pre-commit FactId check | ci | — |
| A6 | Smuggler FactId progression text | copy | B4 |
| A12 | Environmental text examples | copy | A3/#319 |
| B5 | PC NPC-format briefs | copy | B3 |
| D4 | News ticker headlines (~20) | copy | — |
| #306 | News ticker content (align with D4) | copy | — |
| D2 | Seed configuration schema | server | — |
| NEW-4 | Monologue content pool (~200 lines) | copy | #261, B4 |
| NEW-8 | YAML → RON converter | server | C1 |
| NEW-13 | Line previewer CLI | server | C3, C9 |
| #326-P2 | Content loader Phase 2 — real content | server | C4-C8, NEW-3 |
| A3/#319 | Krenn brief + seed.yaml reference | copy | — |
### Sprint 5+ (Content at Scale)
| Ticket | Title | Team | Blocked By |
|--------|-------|------|------------|
| NEW-6 | PC-as-NPC content authoring (~25 items) | copy | B3, B5, #297, #298 |
| NEW-14 | UI microcopy (~50 strings) | client | Stig UI spec |
| B1 | NPC Authoring Style Guide (generator spec) | copy | A3, A4, A7, B2, B4 |
| A4 | Regional style guide / seed.yaml template | copy | — |
| A9 | Thematic Question field (Tier 1 profiles) | copy | B2 |
| #297 | THE FRIEND: Kael content pack | copy | #261 |
| #298 | THE FRIEND: Sera content pack | copy | #261 |
| #190 | Workplace content pack | copy | #261 |
| #191 | Bar content pack | copy | #261 |
| #192 | Smuggling ring content pack | copy | #261 |
---
## Dependency Graph
```
SPRINT 3 — Three Parallel Chains
==================================
Chain 1: Content Authoring Pipeline (copy)
-------------------------------------------
#261 (Dual Lens Guide) [P0, CRITICAL PATH ROOT]
├─► B4 (Smuggler voice + moral arc) [Sprint 3]
│ ├─► A6 (Smuggler FactId text) [Sprint 4]
│ └─► NEW-4 (Monologue pool) [Sprint 4]
├─► #297 (FRIEND: Kael) [Sprint 5]
│ └─► NEW-6 (PC-as-NPC authoring) [Sprint 5]
├─► #298 (FRIEND: Sera) [Sprint 5]
│ └─► NEW-6 (PC-as-NPC authoring) [Sprint 5]
├─► #299 (Opening hook: smuggler) [Sprint 5]
├─► #300 (Opening hook: detective) [Sprint 5]
└─► #190, #191, #192 (Content packs) [Sprint 5]
A7 (Smuggler attributes) [P0, Sprint 3]
├─► B4 (Smuggler voice) [Sprint 3]
└─► B3 (PC-as-NPC spec) [Sprint 3]
└─► B5 (PC briefs) [Sprint 4]
└─► NEW-6 (PC-as-NPC authoring) [Sprint 5]
Chain 2: Content Architecture Pipeline (server)
-------------------------------------------------
C1 (Content dir design) [P0, Sprint 3, copy]
├─► C2 (skeleton) [Sprint 3, server]
│ ├─► C4 (enums) [Sprint 4]
│ ├─► C5 (entity attrs) [Sprint 4]
│ ├─► C6 (pools) [Sprint 4]
│ ├─► C7 (templates) [Sprint 4]
│ ├─► C8 (triangles) [Sprint 4]
│ ├─► NEW-3 (wiki→YAML) [Sprint 4, copy]
│ └─► #326-P2 (loader Phase 2) [Sprint 4]
├─► C3 (schemas) [Sprint 3, server]
│ ├─► C9 (validator) [Sprint 3, server]
│ ├─► NEW-3 (wiki→YAML) [Sprint 4, copy]
│ └─► NEW-13 (line previewer) [Sprint 4]
├─► #326-P1 (loader Phase 1) [Sprint 3, server]
└─► NEW-8 (RON converter) [Sprint 4]
Chain 3: Interaction Pipeline (server + client)
-------------------------------------------------
NEW-7 (Verb spec) [Sprint 3, copy] ···soft···> NEW-9
NEW-9 (Proximity + InteractionOptions) [Sprint 3, server]
└─► NEW-10 (Extensible prompt) [Sprint 3, client]
Independent (Sprint 3)
------------------------
B2 (MIRROR spec) ─► A9 (Thematic Question) [Sprint 4]
A10 (Nils stub) ─► A11 (Triangle 1 fix) [Sprint 3]
NEW-11 (Tick rate scaling) [Sprint 3, server] — no downstream blockers
Existing Server Dependencies
------------------------------
#237 (A* pathfinding) ─► #88 (Daily routine system) [both Sprint 3]
```
---
## Ticket Count
| Category | Count | Teams |
|----------|-------|-------|
| Wiki fixes (A-series) | 8 | copy |
| Style guides & specs (B-series) | 5 | copy |
| Content directory & schema (C-series) | 10 | copy (1), server (8), ci (1) |
| Design specs (D-series) | 2 | server (1), copy (1) |
| Workshop tickets (NEW 1-7) | 7 | copy |
| Lead decision tickets (NEW 8-14, excl. killed NEW-12) | 6 | server (4), client (2) |
| **Total new tickets** | **38** | **copy (21), server (13), client (2), ci (1)** |
| Existing ticket updates | 10 | — |
| **Killed from Round 2** | **1** | NEW-12 (client pause — not a ticket) |
*Note: count is 38, not 37 — NEW-14 (UI microcopy) was added in closing corrections. 38 original − 1 killed (NEW-12) + 1 added (NEW-14) = 38.*
---
## Risks
1. **#261 is the critical path root.** Blocks 9 tickets directly. If it slips one sprint, the entire content authoring pipeline delays into Sprint 5+. Recommend: assign Paula immediately, time-box to 5 working days.
2. **Sprint 3 server team is heavy.** 10 existing tickets + 6 new content-adjacent additions = 16. Mitigation: C2, C3, C9, #326-P1 are all blocked by C1 (copy team) — they start mid-sprint. NEW-9 and NEW-11 are independent and can begin immediately.
3. **Content conversion (NEW-3) is a Sprint 4 bottleneck.** Tyre estimates 2-3 full days for 17 NPC conversions. Blocks server from testing with real data. Recommend: start with 3 Tier 1 NPCs (Kael, Sera, Naia) as soon as C2 lands; don't wait for all 17.
4. **#237 → #88 server dependency.** Pathfinding must land before routines. Both are Sprint 3. If #237 slips, NPC routines slip, which delays routine deviation detection (#243), which delays wow moment #2 (The Character's Eye).
---
*Proposals only — no tickets created in database. Awaiting lead approval.*
*Compiled by SI. Source: v0.1 Content Scoping Workshop Rounds 1-2, lead closing corrections, Qatux tracking doc.*
docs/workshops/v01-content-scoping/v01-content-scoping-workshop-brief.md
-227
View File
@@ -1,227 +0,0 @@
# Workshop Brief: v0.1 Content Scoping
## What Actually Ships in the Vertical Slice?
**Project:** The Settled Reach (D-021)
**Date:** 2026-02-12
**Called by:** Jeroen
**Prerequisite:** Wiki Review workshop established long-term content strategy (300-world generator model, cultural ingredients menu, three-system NPC architecture, Sacred/Profane/Middle Kingdom). This workshop applies that strategy to v0.1.
**Participants:** GESTALT, PAULA, TYRE, MELLANIE, STIG, DUDLEY + SI (tickets) + QATUX (documenter)
---
## Context
The Wiki Review workshop (4 rounds + lead interview) produced a comprehensive long-term content strategy documented in `docs/workshops/wiki-review/SUMMARY.md`. The key outcome: the full game targets 300 worlds populated by generators fed by style briefs. But **v0.1 is NOT a generator test. v0.1 is proof of the interaction model** — 1 district, hand-authored, proving that the player can touch the world and the world can touch back.
The existing wiki (`wiki/`, 45 files, ticket #368) contains the content for Sova Transit District: 17 NPCs across 3 tiers, 5 triangles, 3 social sites, knowledge vocabulary (FactIds, entity attributes, relationship states), and an authoring guide. This content has known gaps and issues identified in Rounds 1-2 of the Wiki Review.
**This workshop scopes and prioritizes the content work needed to ship v0.1.**
**Key constraint:** v0.1 must be architecturally compatible with the 300-world future. Hand-authored Sova content becomes the benchmark output that generators must match. Every structure we create now is a generator template later. Don't build anything that only works for 1 district.
**Design constraints from existing decisions:**
- D-005: Single-character perspective
- D-020: Godot 4 client + Rust/bevy_ecs server
- D-027: Smuggler + detective vertical slice, two-character proof
- D-034: THE FRIEND production-level NPC pattern (Kael, Sera)
- D-035: Monologue system with tagged prerequisites
- D-036: Krenn System / Sova Transit District setting
- D-037: Contraband types
- D-039: 6 wow moments in a 30-minute session
- D-041: Knowledge graph architecture
- Wiki Review: WASD direct control, context-sensitive interaction
---
## Required Reading
Before responding, read:
1. `docs/workshops/wiki-review/SUMMARY.md` — the long-term content strategy (essential context)
2. `docs/workshops/wiki-review/lead-interview.md` — lead's decisions on cultural ingredients, NPC composition, archetypes, randomization, scale
3. `wiki/index.md` — current wiki structure
4. `wiki/npcs/index.md` — NPC roster and triangles
5. `decisions/content.md` — D-028, D-034, D-035, D-036, D-037
6. `decisions/scope.md` — D-027, D-039
---
## Topic 1: Wiki Fixes — Known Issues from Rounds 1-2
**What needs fixing in the existing wiki before it can drive implementation?**
The Wiki Review identified these specific issues:
### 1a. Hael → Naia Tamm rename
Unanimous decision. Resolves Kael/Hael sonic collision (T-03). Hael becomes Naia Tamm, following Krenn naming conventions. This NPC is also the first instance of THE MIRROR pattern — honest, no contradiction arc, no secret.
- **Paula:** Execute the rename across all wiki files. Update relationship references, triangle diagrams, cross-references.
- **Mellanie:** Review Naia Tamm's voice — does she need voice samples now that she's a MIRROR (Tier 1 emotional depth)?
### 1b. Smuggler lens parity
The wiki is detective-shaped. The smuggler perspective needs equal depth:
- Smuggler-specific NPC attributes: `trust_read`, `exposure_risk`, `loyalty_assessment`, `leverage_held`, `social_debt`, `moral_weight`, `cover_integrity`, `loyalty_conflict`
- Moral arc phases for smuggler: Comfort → Doubt → Reckoning → Compromise
- Every NPC profile needs a smuggler-lens section with the same depth as the detective-lens section
- **Paula:** Propose the smuggler attribute vocabulary and add smuggler-lens sections to all NPC profiles.
- **Gestalt:** How do smuggler attributes map to EntityKnowledge keys in the knowledge graph?
### 1c. Triangle 1 (Hub Power) strengthening
Weakest triangle. Smuggler role is passive. Needs a concrete fork — the Nils-vs-Voss escalation decision.
- Nils needs a stub wiki page at minimum
- The player needs a decision point, not just observation
- **Gestalt:** Design the Triangle 1 fork. What does the smuggler decide? What does the detective observe?
- **Paula:** Write the Nils stub page. Define Triangle 1's escalation sequence.
### 1d. Drin tier promotion
Drin is doing Tier 2 work (Triangle 2, Triangle 5, compromised by Harek) in a Tier 3 profile.
- **Gestalt:** Should Drin be promoted to Tier 2? What are the mechanical implications?
- **Paula:** If promoted, expand the profile to full Tier 2 depth.
### 1e. Full canonical names
Miri generated 12 Krenn-style names in Round 1. Apply them to NPCs currently using single names.
- **Paula:** Apply Miri's names where appropriate. Check naming consistency.
**Questions:**
1. **Paula:** Are there other wiki gaps not listed above? What did you discover during Round 1-2 review that still needs fixing?
2. **Gestalt:** Do any triangles need restructuring beyond Triangle 1?
3. **Mellanie:** Are the voice samples in Tier 1 profiles (Kael, Sera) distinct enough for monologue authoring?
---
## Topic 2: v0.1 NPC Architecture
**Which subset of the three-system NPC model ships in v0.1?**
The long-term strategy defines three NPC systems:
- **System A:** 9 thematic patterns (FRIEND, MIRROR, ANCHOR, GHOST, CATALYST, THRESHOLD, REMNANT, SYSTEM, NOBODY)
- **System B:** 6 functional motivations (HANDLER, WITNESS, TURNCOAT, CIVILIAN, OPERATOR, SKEPTIC)
- **System C:** Composition rules (pattern x motivation per NPC)
v0.1 has 17 NPCs across 3 tiers. Not all patterns and motivations need to be present.
**Questions:**
1. **Gestalt:** Which patterns and motivations are REQUIRED for v0.1? Which can be deferred? Map the existing 17 NPCs to pattern + motivation assignments.
2. **Paula:** Do the existing NPC profiles already implicitly match patterns/motivations? Make the mapping explicit.
3. **Gestalt:** Does THE NOBODY ship in v0.1, or is dynamic tier promotion a v0.2 feature? If v0.1, which NPCs are NOBODYs?
4. **Dudley:** What server-side entity data does each pattern/motivation require? What's the ECS component design?
---
## Topic 3: v0.1 Content Directory Structure
**How does wiki content become engine-readable data?**
The wiki (`wiki/`) is the authoring source. The engine needs content in a structured format the server can load. The directory structure must:
- Support the v0.1 content (1 district, hand-authored)
- Be architecturally compatible with the 300-world generator output (same schema, same addressing)
- Allow hot-reloading during development
- Support content validation
**Questions:**
1. **Tyre:** Propose the `content/` directory structure for v0.1. What format — YAML? RON? How does it mirror the wiki structure?
2. **Tyre:** How does content addressing work? `canonical_id` per entity? How do wiki pages map to content files?
3. **Dudley:** What does the server content loader need? What's the load sequence? How does an NPC profile become a spawned entity?
4. **Gestalt:** What's per-district vs. global? Where does the FactId catalog live? Where do NPC profiles live? Where do triangle definitions live?
5. **Stig:** What does the client need from content files? NPC display names? Dialogue text? Location descriptions? What format makes client loading simple?
---
## Topic 4: Interaction Model Basics for v0.1
**What's the minimum viable interaction for the vertical slice?**
The Control & Interaction workshop will design the full system. But v0.1 needs SOMETHING — the player must be able to:
- Walk up to an NPC and initiate dialogue
- Receive monologue observations
- Examine objects/environment
- Overhear conversations (proximity-based)
This topic scopes the v0.1 minimum, not the full design.
**Questions:**
1. **Gestalt:** What's the minimum interaction set that proves the core loop? Walk + talk + observe + monologue? Or does v0.1 need more?
2. **Stig:** What UI elements does the minimum interaction model need? Interaction prompt? Dialogue box? Monologue display? Knowledge panel?
3. **Dudley:** What server events support the minimum interaction? Proximity triggers? Interaction requests? Dialogue state?
4. **Mellanie:** How much monologue content does v0.1 need? What's the minimum pool size before it feels repetitive?
---
## Topic 5: v0.1 Scope Boundary
**What's IN v0.1 and what's explicitly OUT?**
v0.1 proves the interaction model. It does NOT prove generators, randomization, or cultural variety. Be ruthless about scope.
**Candidates for IN:**
- WASD movement + collision
- Context-sensitive interaction (approach NPC → prompt → dialogue)
- Monologue system (tagged triggers, FactId prerequisites)
- Knowledge graph (player learns facts, relationships change)
- 2 playable characters (smuggler, detective) seeing same world differently
- THE FRIEND arc (Kael for smuggler, Sera for detective)
- 5 triangles with at least 1 fork each
- 6 wow moments (D-039)
- 3 social sites (Terminal, Last Shift, Maintenance Corridors)
- NPC routines (schedule-based movement)
**Candidates for OUT (v0.2+):**
- THE NOBODY / dynamic tier promotion
- Archetype transitions
- Multiple FRIEND candidates per character
- Secondary contraband variation
- Gate network / multi-world
- Content generation / randomization
- Modding support
**Questions:**
1. **Gestalt:** Is this IN/OUT split correct? Anything missing from IN that's essential for the 30-minute session? Anything in IN that's scope creep?
2. **Tyre:** What's the technical risk in the IN list? What might take longer than expected?
3. **Dudley:** What server features are blocked by content that doesn't exist yet?
4. **SI:** Map the IN list to tickets. What already has tickets? What needs new ones?
---
## Topic 6: Ticket Generation
**What implementation tickets come out of this workshop?**
SI had a preliminary list of 28 tickets from Wiki Review Round 2, but the 300-world reframe makes some obsolete and creates new ones.
**Expected ticket categories:**
- Wiki fixes (rename, smuggler lens, triangle strengthening, Drin promotion, canonical names)
- Content file creation (wiki → YAML/RON conversion for engine)
- Content directory structure setup
- Content loader implementation (server-side)
- Content validation schema
- Minimum interaction model (client UI elements)
- Monologue content pool (minimum viable)
- PC-as-NPC content (the other character exists as an NPC)
**Questions:**
1. **SI:** Review the Round 2 ticket list (`docs/workshops/wiki-review/si-ticket-changes.md`). Which survive? Which are obsolete? What's new?
2. **SI:** Which tickets belong to Sprint 3 (Know) vs. later sprints? What's the dependency chain?
3. **Tyre:** What tickets should be split between server/client/copy teams?
---
## Workshop Format
**1-2 rounds.**
**Round 1:** Topic responses. Each participant addresses their assigned questions with concrete proposals. Wiki fixes should include actual content (not just "we should fix this"). Directory structures should be actual file trees. Ticket proposals should have title, description, and team assignment.
**Round 2:** Integration + ticket finalization. Resolve disagreements, finalize the IN/OUT boundary, produce the ticket list. SI creates tickets. Qatux documents decisions.
## Expected Outputs
- **Wiki fix list** with assignments and content ready to apply
- **NPC pattern/motivation mapping** for all 17 v0.1 NPCs
- **Content directory structure** with schema proposal
- **v0.1 interaction model minimum** — enough for Stig/Dudley to implement
- **Scope boundary document** — clear IN/OUT with rationale
- **Ticket list** — implementation tickets with team assignments and sprint targets
- **Decision amendments** — updates to existing decisions based on scoping
docs/workshops/v01-content-scoping/workshop-outcomes.md
-116
View File
@@ -1,116 +0,0 @@
# Workshop Outcomes: v0.1 Content Scoping
**Workshop:** v0.1 Content Scoping
**Date:** 2026-02-12
**Rounds:** 2 + closing round (lead resolutions)
**Participants:** Gestalt, Paula, Tyre, Mellanie, Stig, Dudley, Si, Qatux
**Facilitator:** Jeroen
**Documenter:** Qatux
**Status:** CLOSED — all recoverable decisions filed, tickets created
**Full notes:** `docs/workshops/v01-content-scoping/SUMMARY.md`, `si-ticket-changes.md`
---
## What the Workshop Accomplished
Applied the Wiki Review's long-term generator strategy to the immediate v0.1 hand-authored proof. Produced 20 decisions (D-042 through D-061), 38 new tickets, canonical NPC mapping for 17 characters, the 16-key EntityKnowledge specification, full content directory architecture, and a Sprint 3-5 roadmap. Tyre and Dudley independently produced structurally identical ObserverSnapshot v3 definitions without coordination — confirmed the architecture was sound. Lead issued 4 decisions resolving the major Round 1 disagreements between rounds, then resolved 3 remaining questions in a closing round.
**Note on decision IDs:** Several IDs assigned at this workshop collided with later numbering. Genuinely new decisions identified in retrospect were filed as D-087 (content directory structure), D-089 (NPC canonical mapping method), D-091 (EntityKnowledge 16-key canonical set), Q-031 through Q-034.
---
## Decisions Produced
### From Round 1 Consensus (7)
| ID | Decision | Domain |
|----|----------|--------|
| D-042 | Drin promoted from Tier 3 to Tier 2 | content.md |
| D-043 | THE NOBODY mechanic deferred to v0.2; hidden data ships in v0.1 content | scope.md |
| D-044 | v0.1 interaction model: 7 verbs (Move, Look, Monologue, Examine Object, Examine NPC, Talk, Overhear) | scope.md |
| D-045 | v0.1 scope IN: news ticker, PC-as-NPC, time progression, relationship state transitions | scope.md |
| D-046 | v0.1 scope OUT: inventory, stealth, combat, save/load, lattice modification | scope.md |
| D-047 | v0.1 triangles: 3 active forks (T1, T2, T4), 2 passive tensions (T3, T5) | content.md |
| D-048 | Client receives all text from server via state updates; client does not load content files | architecture.md |
### From Round 2 + Closing (13)
| ID | Decision | Domain |
|----|----------|--------|
| D-049 | YAML is the content file format for v0.1; RON is optional build-time optimization | architecture.md |
| D-050 | Gestalt's NPC pattern/motivation mapping canonical for v0.1; Paula's emotional layer becomes v0.2 annotations | content.md |
| D-051 | v0.1 ships single context-sensitive verb; multi-verb architecture modeled underneath | architecture.md |
| D-052 | 3-state pause: Normal (100%), Overlay (50%), Paused (0%); server-authoritative | architecture.md |
| D-053 | Self-contained triangle forks for v0.1; no cross-triangle cascade (v0.2) | content.md |
| D-054 | ObserverSnapshot v3: adds sim_speed, nearby_interactions, active_dialogue, monologue, overheard, knowledge_updates, examine_result, ticker_headlines | architecture.md |
| D-055 | 16 EntityKnowledge keys; 4 new role-perspective keys; trust_read merged into trust_level; secret_held → leverage_held | architecture.md |
| D-056 | PC voice registers: smuggler (feeling-first, fragments, physical); detective (analysis-first, complete sentences, institutional) | content.md |
| D-057 | Content directory: content/ with _schema/, global/, districts/ top-level split; JSON Schema validation at build time | process.md |
| D-058 | THE FRIEND content pack template: Kael Davan, 91 lines across 5 arc phases | content.md |
| D-059 | Monologue display: 160 char max, 2-line max, 4-6s display, 2s cooldown, queue depth 1, 9-level priority | architecture.md |
| D-060 | actions[] renamed to verbs[] across all surfaces | architecture.md |
| D-061 | No ticket merges across domain teams | process.md |
### Retrospective Filings (ID collisions resolved)
| ID | Decision | Domain |
|----|----------|--------|
| D-087 | Content directory structure (content/ split) | process.md |
| D-089 | Canonical NPC pattern/motivation mapping method | content.md |
| D-091 | EntityKnowledge 16-key canonical specification | architecture.md |
---
## Open Questions Carried Forward
| ID | Question | Status |
|----|----------|--------|
| Q-031 | NPC surnames for Drin, Sess, Tav awaiting Miri validation | Informational |
| Q-032 | Interaction struct naming: AvailableActions (Tyre) vs EntityInteractions (Dudley) | Resolved at implementation |
| Q-033 | 695 authored items: validated as scope input but not independently verified | Informational |
| Q-034 | Dialogue max-width: pixel value for 20% height / max-width constraint | Pending lead call |
None blocked Sprint 3.
---
## Tickets Created
38 new tickets + 10 existing ticket updates. See `si-ticket-changes.md` for full list.
**Teams:** copy (21), server (13), client (2), ci (1).
**Critical path:** #261 (Dual Lens Authoring Guide) is the single biggest blocker — directly blocks 9 downstream tickets across the content pipeline. Five-day time-box recommended.
| Series | Count | Domain |
|--------|-------|--------|
| A (Wiki content fixes) | 8 | copy |
| B (Style guides + specs) | 5 | copy |
| C (Content directory + schemas) | 10 | copy/server/ci |
| D (Design specs) | 2 | server/copy |
| NEW 1-7 (Workshop rounds) | 7 | copy |
| NEW 8-14 (Lead decisions, excl. killed NEW-12) | 6 | server/client |
**Killed:** NEW-12 (client pause state machine — pause is server-authoritative, client sends IPC command only).
**Sprint allocation:** Sprint 3 — foundations and specs. Sprint 4 — content conversion and authoring begins. Sprint 5+ — content at scale.
---
## NPC Canonical Mapping (17 NPCs)
The Gestalt-Paula synthesis produced the v0.1 canonical pattern/motivation mapping for all 17 Sova NPCs. This is the authoritative reference for content authoring.
| Name | Tier | Pattern | Motivation |
|------|------|---------|-----------|
| Kael Davan | T1 | FRIEND | OPERATOR |
| Sera Venn | T1 | FRIEND | WITNESS |
| Naia Tamm | T1* | MIRROR | CIVILIAN |
| Voss, Lera, Torek, Devra, Maret, Resha, Drin, Renn, Pell, Harek | T2 | (varied) | (varied) |
| Sess, Olin, Sabel, Tav | T3 | (varied) | (varied) |
Off-stage: Nils Davan — GHOST + HANDLER.
---
*Compiled by Qatux. Source: `docs/workshops/v01-content-scoping/SUMMARY.md`, `si-ticket-changes.md`. Decisions in relevant `decisions/` domain files (D-042 through D-061, D-087, D-089, D-091). Open questions in `decisions/questions.md` (Q-031 through Q-034).*