settled-reach/docs/workshops/wheres-the-fun/round1-gestalt.md

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

title	description	type	status	workshop	agent	round	created
Round 1: GESTALT Interview Questions	Gestalt's systems design diagnosis on asymmetric information as core mechanic	workshop	archived	wheres-the-fun	gestalt	1	2026-03-05

Round 1: GESTALT Interview Questions

Workshop: Where's the Fun? — Diagnosis Round

Agent: GESTALT (Systems Design) Focus: Is "asymmetric information detective" the right core mechanic? Where is the gap between the 7-verb system design and the confused playtest experience?

---

Pre-Question Framing

Let me break down what I actually found mechanically. Three tensions in the source docs that I think are load-bearing:

1. The verb priority spec (Section 4, interaction-verbs-v0.1.md) says Talk has higher priority than Examine NPC at close range — pre-contradiction. The detective's stated loop is "Examine first, Talk later." These directly contradict each other. The player approaching an NPC to watch them gets offered [E] Talk.

2. The "not a tutorial" philosophy assumes the player will correctly attribute cause to effect: "monologue fired, therefore my action registered." But that only works if the player trusts the feedback loop. If monologue feels contextless, the calibration chain breaks — and the tutorial breaks with it.

3. Asymmetric information as a mechanic requires the player to feel the asymmetry — to know they're missing something specific. "I don't know what I don't know" is not asymmetric information, it's confusion. The two states feel identical from outside but require completely different design responses.

---

Question 1: Did the system fight the detective loop?

The question: When you were playing the detective and wanted to watch an NPC before talking to them — did you try to do that, and did the system let you? Or did you end up in dialogue anyway because [E] Talk was what the button said?

Why this matters mechanically: The verb priority spec puts Talk above Examine NPC at close range. To get [E] Observe instead of [E] Talk, the player has to be at mid range, not close range. But this is invisible — nothing tells you that backing up 2 tiles switches the verb. If the detective's core loop is "accumulate behavioral tells through observation, then confront," but the input system defaults to the social verb at close range, the loop never teaches itself. The player keeps getting pushed toward dialogue before they're ready.

This isn't a bug. It's a design decision. But it may be the wrong one — or it may be correct and we just need the verb label to communicate it. I want to know if this actually broke in play.

---

Question 2: Was the confusion "I know something is here" or "I have no idea what I'm looking at"?

The question: During the playtest, when things weren't working — was the experience closer to "I can feel there's something here, I just can't figure out how to reach it" or "I have no idea what I'm supposed to be paying attention to or why"?

Why this matters mechanically: These are different failure modes requiring different fixes.

• Good mystery confusion ("I know something is here"): The mechanic is working, the player is engaged, but they need better tools or legibility to act on their curiosity. Fix: UI/UX, verb transparency, monologue specificity.
• Bad confusion ("I don't know what I don't know"): The mechanic is not registering at all. The player isn't feeling asymmetric information — they're feeling uniform opacity. The game is a black box, not a puzzle box. Fix: potentially redesign the core loop entry point.

Asymmetric information is only interesting when you know you're missing something specific. If Kael's behavioral tells are firing in the knowledge graph and the monologue is flagging them, but the player still feels like nothing is happening — I want to know which failure that is. Because the answer determines whether this is a polish problem or a design problem.

---

Question 3: At minute 2, what did you think you were supposed to be doing?

The question: Two minutes in, with no objectives, no markers, and your character in the world — what did you actually think the goal was? Not in retrospect, not as the designer. What did the game communicate to you in that moment about what success looked like?

Why this matters mechanically: The "no objectives, pure observation" philosophy only works if the player has a mental model for what progress looks like. The first-5-minutes design doc identifies clear beats (enter location, see FRIEND, operational texture, first hairline crack) — but all of those are design intentions, not player experiences. If the player at minute 2 has no sense of purpose, progress, or priority — not because the systems aren't working, but because nothing has communicated what the systems are for — then the "not a tutorial" philosophy isn't succeeding at teaching through play. It's succeeding at not teaching.

The question isn't whether the player understood the detective puzzle. It's whether they had any question to answer, any thread to pull, any thing they were curious about that felt like it came from inside the game rather than from designer goodwill.

---

GESTALT — Round 1 complete. Waiting for interview responses before Round 3 proposals.