Files
settled-reach/docs/sprints/sprint-17/copy.md
T
jpmschweitzerandClaude Opus 4.6 abff69a632 chore(meta): Sprint 17 planning — briefings, workshop brief, close Q-025
- Write sprint 17 briefings for server, client, copy, visual, joint
- Add Knowledge Flow & NPC Boundaries workshop brief
- Close Q-025 (KG cap/eviction not needed at current scale)
- Assign 9 tickets to Sprint 17: Tell

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-23 23:25:08 +01:00

3.1 KiB

Sprint 17: Tell — Copy Tasks

Goal: NPCs volunteer information unprompted and express personality through delivery; the player can read time and orientation at a glance from the insert HUD; POI infrastructure lands on the server.

Branch: copy Agents: Mellanie (author), Paula (narrative), Gestalt (systems)

Carry-over from Sprint 16

None. Sprint 16 copy ticket (#542, line ID migration) will close before Sprint 17.

New Tickets

# Title Blocked by
#330 Diegetic tutorial monologue lines — per character — (blockers #299, #300 done)

Use db/connectors/ticket show <id> for full details.

Key Decisions

  • decisions/content.md — D-035 (tag taxonomy, monologue prerequisites), D-028 (dialogue architecture)
  • decisions/perception.md — D-019 (camera and perception), D-011 (fog of perception)

Notes

#330 — Diegetic tutorial monologue lines — per character

What exists: Monologue pools at content/campaigns/main/systems/krenn/stations/sova/districts/transit/monologue/detective/ and .../smuggler/ contain character-specific internal monologue. Opening monologue files exist (opening.yaml for both characters). The monologue system in server/src/simulation/monologue.rs fires lines based on triggers and prerequisites.

What to deliver: 8-10 monologue lines per character (smuggler + detective) that teach core mechanics diegetically:

  • Movement and exploration ("These corridors all look the same. Mental note: check the signage.")
  • Fog of perception ("Can't see past that corner. Might be worth checking.")
  • Sound model ("Voices down the hall. Can't make out the words from here.")
  • NPC interaction ("Could ask around. People talk if you give them reason to.")
  • Insert/HUD usage ("Check the overlay. Should show the time and nearby contacts.")

Lines fire on first-time events (first move, first fog encounter, first sound heard, first NPC proximity, first insert open). Use trigger: first_time_event with appropriate event tags.

Voice consistency: Smuggler lines should be observational, street-smart, practical. Detective lines should be analytical, procedure-oriented, careful. Both stay in-character — tutorials are disguised as natural inner thoughts, not fourth-wall-breaking instructions.

Prerequisite format: Per D-035:

- id: pc-smuggler_m_s_tut_001
  text: "Voices. Down the corridor. Can't tell how many."
  trigger: first_sound_heard
  priority: tutorial
  cooldown: -1

Use _tut_ in IDs to distinguish tutorial lines from narrative monologue.

Note on PC monologue ID collision (Q-028): The review of PR #59 flagged that PC monologue IDs collide across location files. Use the _tut_ discriminator for tutorial lines. Q-028 will resolve the broader scheme.

Dependency Chain

#330 (Tutorial monologue) → standalone, no deps

PR Workflow

When ready to submit, create a PR with tea CLI:

tea pr create --repo jpmschweitzer/settled-reach --login schweitz --title "feat(content): sprint 17 description" --description "body" --base main --head copy