settled-reach/docs/workshops/wheres-the-fun/wheres-the-fun-workshop-brief.md

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

title	description	type	status	workshop	agent	round	created
Workshop Brief: Where's the Fun?	Workshop brief and agenda for the v0.1 playtest reckoning	workshop	archived	wheres-the-fun		0	2026-03-05

Workshop Brief: Where's the Fun?

v0.1 Playtest Reckoning

Project: The Settled Reach Date: 2026-03-05 Called by: Jeroen (first playtest of v0.1) Format: Interview — agents ask Jeroen questions, facilitator coordinates

Participants: GESTALT, OZZIE, PAULA, GORE, NIGEL, MIRI, TYRE, ARAMINTA, MELLANIE Always-present: QATUX (documenter), SI (sprint prep)

---

The Problem

The first playtest of v0.1 hit a wall. The engine works. The world simulates. NPCs move on routines. Fog reveals. Monologue fires. The technical foundation is solid.

The game isn't fun. The player doesn't know what to do, why they should care, or how to engage. The detective puzzle — the core framing of the vertical slice — may be a conceptual error.

This workshop exists to diagnose the fun problem and propose directions. Nothing is sacred. The asymmetric information mechanic, the detective/smuggler framing, the monologue-as-primary-feedback approach, the "no tutorial, no objectives" philosophy — all of these can be challenged.

Two-Layer Onboarding Gap

The playtest revealed that "onboarding" is failing on two levels:

1. Narrative onboarding — "Who am I? Why am I here?" There is no briefing, dossier, or context given to the player about their character, their mission, or their relationship to this place.

2. Mechanical onboarding — "How do I play? What should I pay attention to?" The game teaches nothing. The "not a tutorial" philosophy (see Reference Materials) assumes the player will naturally discover the verbs and loops through play. In practice, the player discovers confusion.

Layer 2 supersedes Layer 1. Even if the player knew their character's motivation, they still wouldn't know how to act on it.

---

Playtest Evidence

What Works

• The simulation engine is functional — NPCs on routines, fog/LOS, perception pipeline
• World atmosphere is present even in placeholder art — the space feels occupied
• The graphics need to invent themselves, but the concept reads through the placeholder
• Fog, perception, monologue systems all fire correctly at the technical level

What Doesn't Work (14-item playtest log)

#	Issue	Severity	Category
1	Monologue display duration too long	UX	Feedback timing
2	Monologue feels scattered and contextless — "why am I having these thoughts about chalk marks?"	Design	Information architecture
3	Fog edge transparency still visually broken	Visual	Rendering
4	Stance indicator UX makes no sense — should be icon + keybind attached to minimap or dialogue window	UX	HUD layout
5	HUD has debug clutter in top-left	Polish	Cleanup
6	HUD visual polish needed (low priority)	Polish	Visual identity
7	Interaction prompt ("[E] Talk") is vague — should float above NPC with obfuscated names until identity is resolved	UX	Interaction clarity
8	Right-click context menu is floating text, needs chrome/panel styling	UX	Visual treatment
9	Monologue observations disconnected from visual source — chalk mark observation appears in wildly different location with no visual cue where it came from	Design	Spatial anchoring
10	Signal-to-noise problem — too many things beeping, flashing, moving, competing for attention without clarity on what they mean or how much to care	Design	Attention management
11	Unpleasant sense of urgency/pressure to "keep up" — possibly related to message timeouts	Design	Pacing
12	Concern about how v0.1 will break open into v0.2+ playstyles	Design	Extensibility
13	Testing wall — cannot progress due to accumulated UX/clarity issues, don't know what to do in-game	Critical	Core loop
14	Two-layer onboarding gap — narrative (who/why) AND mechanical (how)	Critical	Core loop

The Testing Wall (Item 13)

This is the critical finding. The player — who designed the game — could not figure out how to play it. Not because the systems are broken, but because:

• There is no sense of purpose (what am I trying to do?)
• There is no sense of progress (am I getting closer to something?)
• There is no sense of feedback priority (which of these 5 simultaneous signals matters?)
• The monologue system, designed as the primary feedback mechanism, feels like noise rather than guidance

If the designer can't play it, no one can.

---

The Core Questions

For Each Agent

Read the playtest log above, read the Reference Materials, and prepare 2-3 questions to ask Jeroen during the interview round. Your questions should probe your domain expertise.

Gestalt (Systems Design & Fun Factor):

• Seed question: Is "asymmetric information detective" the right core mechanic, or should the fun come from something else? The 7-verb system is architecturally elegant but produces confusion in practice. Where is the gap between the design and the experience?
• Read: docs/design/interaction-verbs-v0.1.md, docs/design/first-5-minutes-experience.md

Ozzie (Player Experience & Wow Factor):

• Seed question: When you imagine this game being fun, what does that moment feel like? The 6 wow moments (D-039) are beautifully designed on paper. None of them landed in the playtest. What's the gap between the design intent and the first-run experience?
• Read: docs/design/v0.1-wow-moments-checklist.md

Paula (Narrative & Political Depth):

• Seed question: Does the narrative framework — complicity, moral compromise, the smuggler's 4-phase arc — translate into moment-to-moment engagement? Or is it too cerebral for a player who doesn't yet know how to move through the world?
• Read: docs/design/smuggler-moral-arc.md, decisions/content.md

Gore (Themes & Endgame Design):

• Seed question: Is the thematic ambition (complicity, information asymmetry as master mechanic, "characters as lenses") getting in the way of accessible fun? When you zoom all the way out — what is this game ABOUT at the moment-to-moment level, not the essay level?
• Read: decisions/scope.md (D-005, D-027, D-091)

Nigel (Sandbox & Replayability):

• Seed question: Can this game be replayable if the first playthrough doesn't hook? The dual-lens divergence reveal (wow moment #4) is a second-playthrough payoff. But if the player quits at minute 8 of the first playthrough because they don't know what to do, the second playthrough never happens.
• Read: docs/design/first-5-minutes-experience.md (seed variants section)

Miri (Worldbuilder & Setting Designer):

• Seed question: Does the world sell itself in 30 seconds, or does the player need to be told why they should care? Sova Transit is designed as a working-class station district with rich internal logic. In the playtest, none of that landed — the player saw tiles, NPCs, and fog, but not a place.
• Read: decisions/content.md (D-025, D-027)

Tyre (Technical Architecture & Feasibility):

• Seed question: What's technically feasible to change about the core loop without rebuilding the engine? If the workshop concludes that the "no objectives, pure observation" approach needs modification, what can the existing architecture support?
• Read: decisions/architecture.md, docs/design/interaction-verbs-v0.1.md

Araminta (Visual Designer):

• Seed question: How much of the "not fun" problem is visual vs mechanical? The placeholder art creates a readability floor — you can see what's happening. But there's no visual hierarchy, no focal points, no "this is where you should look." Would strong art direction mask or fix the issue?
• Read: The playtest log above (items 3, 4, 6, 8, 10)

Mellanie (Copywriter):

• Seed question: Is the monologue system working as a content delivery mechanism, or is it just noise? The monologue is designed as the primary bridge between the top-down camera and the character's subjective experience. In the playtest, it felt like scattered thoughts without context. Is this a content problem (wrong lines) or a system problem (wrong delivery)?
• Read: docs/design/first-5-minutes-experience.md (voice rules section), docs/design/smuggler-moral-arc.md (monologue trigger rules)

---

Interview Protocol

Round 1: Diagnosis (agents prepare questions)

Each agent reads:

1. This brief (the playtest log and their seed question)
2. The Reference Materials assigned to them
3. Any additional design docs they feel are relevant

Then writes 2-3 interview questions for Jeroen with reasoning for why each question matters. Questions should:

• Probe the gap between design intent and playtest experience
• Challenge assumptions if warranted — nothing is sacred
• Be specific enough to produce actionable answers

Output: docs/workshops/wheres-the-fun/round1-{agent}.md

Round 2: Interview

The facilitator collects all questions from Round 1 and presents them to Jeroen as a consolidated interview. Jeroen answers. Answers are distributed back to all agents.

Output: docs/workshops/wheres-the-fun/lead-interview.md

Round 3: Proposals

Each agent reads Jeroen's interview answers and all other agents' Round 1 questions. Then writes a concrete proposal for their domain:

• What to keep (working, just needs polish)
• What to change (design intent is right, execution is wrong)
• What to kill (design intent itself is wrong)
• Where does the fun come from? (the positive vision, not just the diagnosis)

Output: docs/workshops/wheres-the-fun/round3-{agent}.md

Round 4: Synthesis

Agents read each other's Round 3 proposals. Each agent writes a response identifying:

• Agreements and reinforcing ideas across domains
• Conflicts that need resolution
• Their single most important recommendation

Output: docs/workshops/wheres-the-fun/round4-{agent}.md

---

Reference Materials

Design Documents

• docs/design/first-5-minutes-experience.md — Beat-by-beat opening design, "not a tutorial" philosophy
• docs/design/smuggler-moral-arc.md — 4-phase moral trajectory, FactId gates, monologue trigger rules
• docs/design/interaction-verbs-v0.1.md — 7 verbs, single context key, verb priority system
• docs/design/v0.1-wow-moments-checklist.md — 6 wow moments, 1/23 content deliverables complete

Decision Files

• decisions/scope.md — D-005 (single character perspective), D-027 (vertical slice proof), D-091 (complicity as thematic core)
• decisions/content.md — D-028 (tagged line pool dialogue), D-029 (entanglement ratio), D-032 (separate monologue pools), D-035 (tag taxonomy)
• decisions/architecture.md — D-041 (knowledge graph), D-048 (dumb client), D-054 (ObserverSnapshot v3)
• decisions/perception.md — D-011 (shadowcasting LOS), D-015 (vision cone), D-016 (monologue as perception bridge)

Key Design Principles Under Review

• "Not a tutorial" — The game teaches through play, not instruction. Is this viable?
• "Monologue is the primary feedback mechanism" — Character voice bridges top-down camera to subjective experience. Is this working?
• "No objectives, no markers" — The player discovers purpose through observation. Does this produce discovery or confusion?
• "Asymmetric information as master mechanic" — Different knowledge creates different games. But does it create fun?
• "Complicity" — The thematic core. Beautiful in essays. Does it play?

---

Expected Outputs

1. Diagnosis — What specifically is causing the fun gap? (UX? content? core mechanic? pacing? all of the above?)
2. Direction — Keep/pivot/evolve the detective puzzle framing and the asymmetric information approach
3. Proposals — Concrete per-domain recommendations for making v0.1 engaging
4. Ticket candidates — Actionable items for Sprint 25 (Si captures these)

---

A Note on Scope

This workshop is about what the game needs to be fun, not about what's technically feasible or what's already been decided. If the answer is "the detective puzzle is wrong and we need a different core loop," that's a valid conclusion. If the answer is "the core loop is right but the first 10 minutes are catastrophically failing to teach it," that's also valid.

The cost of protecting past decisions is lower than the cost of shipping a game nobody can play.