Files

T

jpmschweitzerandClaude Opus 4.6 ba3ade434e docs(docs): add frontmatter to v01-gap-analysis workshop

Standardized YAML frontmatter on all 16 files.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-14 00:01:28 +01:00

30 KiB

Raw Blame History

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

title	description	type	status	workshop	agent	round	created
Workshop Round 1 - Ozzie's Analysis	Emotional delivery and fun factor analysis of concept proof claims, observation pipeline design, and missing wow moments	workshop	archived	v01-gap-analysis	ozzie	1	2026-02-11

Workshop Round 1 - Ozzie's Analysis

Track 1: Strength of Concept Proof + Track 2: Fun & Wow Factor

TRACK 1: STRENGTH OF CONCEPT PROOF

How I'm rating these:

Each claim gets two scores:

Systemic delivery (will the tickets build it?) — 1 to 5
Emotional delivery (will the player FEEL it?) — 1 to 5

A claim can score 5/5 systemic and 1/5 emotional. That means it works but nobody cares. That's a failed concept proof.

Claim 1: "Asymmetric information is the core mechanic"

Proof: Smuggler and detective see the same world differently. Tickets: #138-142 (info boundaries), #182-183 (divergent knowledge/relationships)

Systemic: 4/5 — The information boundary system (#138-142) is well-specced. Component-level access control (#139), entity visibility filtering (#140), knowledge-based gating (#141). This is the plumbing. It'll work.

Emotional: 3/5 — Here's my worry. Information boundaries are INVISIBLE by definition. The player doesn't know what they can't see. That's the POINT, but it's also the PROBLEM. How does the player FEEL the asymmetry?

The answer is: they feel it when they SWITCH characters. Play smuggler, then detective. THEN you go "oh my god, THAT'S what was happening." But that means the WOW moment is deferred to the SECOND playthrough. For the first playthrough, asymmetric info manifests as... confusion? Mystery? That can work — Outer Wilds did it — but we need the first playthrough to feel intriguing, not frustrating.

What's missing: There's no "mirror moment" ticket. No moment in the FIRST playthrough where the player glimpses the other side. The smuggler overhears the detective asking questions. The detective finds evidence the smuggler left behind. Something that whispers "there's a whole other game here." The internal monologue system (#119-122) COULD deliver this — "Who the hell was asking about shipment schedules at the bar?" — but it's not explicitly designed for it.

Verdict: Solid foundation, needs a first-playthrough emotional anchor.

Claim 2: "Fog of perception creates tension"

Proof: Player doesn't know what they can't see. Tickets: #110-113 (shadowcasting to fog rendering)

Systemic: 5/5 — Clean dependency chain. Shadowcasting (#110) feeds vision cone (#111) feeds observer query (#112) feeds fog rendering (#113). This is the most technically complete chain in the whole catalog.

Emotional: 4/5 — THIS is where the game becomes a game. Fog of perception is horror-game DNA applied to a detective sim. Every corner is a question mark. Every building you walk past has people DOING THINGS you can't see. The vision cone (#111) means you can be SNUCK UP ON.

I can already feel it. You're tailing an NPC through the station. They turn a corner. You follow. The fog peels back and — they're gone. Where did they go? Your monologue fires: "They were right here. I saw them turn this way." THAT'S the game.

What could push this to 5/5: Sound through walls. The three-range sound model (#124-128) is specced, and #124 (sound event system) is high priority. But #128 (sound propagation physics) is LOW priority. That means sounds don't propagate THROUGH structures in v0.1. You might hear footsteps in the fog... but you won't hear a conversation through a wall. That specific moment — pressing against a wall, hearing muffled voices, making a decision — is a SIGNATURE moment and it's deprioritized.

Verdict: Strong. Promote #128 or at minimum ensure #124-126 can deliver wall-muffled audio cues.

Claim 3: "NPCs feel alive without player attention"

Proof: Routines continue, relationships shift off-screen. Tickets: #88 (daily routines), #93-99 (simulation tiers), #101 (routine execution)

Systemic: 4/5 — The simulation tier system (#93-99) is well thought out. Active NPCs run full sim. Background NPCs tick state machines. The timestamp eviction model means NPCs you interact with stay active. Solid.

Emotional: 2/5 — AND HERE'S MY BIGGEST CONCERN.

NPCs feel alive when you NOTICE they were alive without you. You leave the bar at 6pm. You come back at 10pm. The bartender is talking to someone new. The couple in the corner has been replaced by a lone drinker. That's the SYSTEMIC delivery. But does the player NOTICE?

In a top-down view with placeholder art (#133), NPCs are sprites. Small sprites. Moving between locations on schedules. Unless the game TELLS the player what changed — through monologue ("Hmm, Kira's not at her usual spot tonight"), through dialogue ("You just missed Marcus — he left about an hour ago"), through observable state changes (the bar rearranges, lights shift) — the player will never feel NPC life happening.

What's missing: There's no "noticing change" system. No ticket for the character observing and reacting to differences in routine. The monologue system (#119-122) COULD do this but the monologue event generation (#119) doesn't specifically target routine deviation. Routine EXECUTION is #101 (high priority). But routine DEVIATION DETECTION — noticing when an NPC breaks their pattern — isn't a ticket at all. AND THAT'S THE ACTUAL DETECTIVE MECHANIC.

Let me say that again louder: NOTICING THAT AN NPC BROKE THEIR ROUTINE IS THE CORE GAMEPLAY LOOP AND IT'S NOT A TICKET.

Verdict: The simulation will run. The player won't feel it without a deviation detection + monologue bridge. This needs a new ticket, and it needs to be HIGH priority.

Claim 4: "Observation is a mechanic, not a cutscene"

Proof: Player deduces from watching, overhearing, noticing. Tickets: #115 (NPC vision), #124-128 (sound model), #119-122 (internal monologue)

Systemic: 3/5 — The pieces are here but loosely connected. NPC vision (#115) tells us NPCs can see things. Sound model (#124-128) tells us sounds propagate. Monologue (#119-122) tells us the character comments. But where's the OBSERVATION VERB? What does the player DO to observe?

Is it passive? (Just stand and watch, and the monologue fires automatically?) Is it active? (Press a button to "focus" on an NPC, getting more detailed observations?) Is it positional? (Get close enough and your character overhears things?)

The workshop brief (Track 3) flags this: "Player can move, look, listen — but what can they DO?" I agree. There's no interaction system ticket for directed observation.

Emotional: 3/5 — Observation as a mechanic lives or dies on FEEDBACK. You stand outside a building. You can see in through a window. An NPC hands something to another NPC. Your monologue says: "That looked like it might have been a data chip. Or maybe just payment for drinks." THAT moment — where the game tells you "you saw something but you're not sure what" — THAT'S the game.

But that moment requires: vision system + NPC behavior happening in viewable space + monologue triggering on observed events + ambiguity in the monologue. Each of these is a different system and none of them are wired together in the ticket plan.

What's missing: An "observation event pipeline" — when the player's character observes a notable NPC action, generate a monologue event with uncertainty based on distance/clarity/knowledge. This is the SPINE of the game and it's spread across 4 epics with no connecting tissue.

Verdict: The systems exist in isolation. Needs an integration story that wires observation → interpretation → monologue into a single gameplay loop. High priority.

Claim 5: "Same world, different story"

Proof: Two playthroughs are mechanically distinct. Tickets: #179-183 (character builds), #196-199 (success criteria)

Systemic: 4/5 — Character builds (#179-181) define the smuggler and detective. Divergent starting knowledge (#182) and relationships (#183) ensure they enter the world differently. The social site templates (#184-186) will be experienced from opposite sides.

Emotional: 5/5 — THIS IS THE KILLER FEATURE AND WE NEED TO PROTECT IT AT ALL COSTS.

The smuggler walks into the logistics hub and sees his coworkers. The detective walks into the same logistics hub and sees suspects. Same NPCs. Same relationships. COMPLETELY different emotional register. The smuggler's best friend IS the detective's prime suspect. THAT'S the game.

This is the thing you show people. This is the "holy shit" moment. "I played as the smuggler and I liked this guy, he was my work buddy, we had drinks together. Then I played as the detective and I found out he was — oh my god."

What could go wrong: If the two characters feel like reskins — same verbs, same access, same daily experience — the mechanical distinction falls flat. The character builds (#180-181) need to deliver genuinely different DAILY ROUTINES, not just different starting knowledge. The smuggler hauls cargo. The detective reviews case files. Different rhythms, different spaces, different NPCs they spend time with during the mundane 30 minutes.

Verdict: The strongest emotional claim. Protect it. Ensure #180 and #181 define radically different daily experiences, not just different stat sheets.

Proof: NPC relationships produce situations designers didn't script. Tickets: #106-109 (triangle generation), #175-176 (entanglement ratio)

Systemic: 3/5 — Triangle definition (#106) and generation (#107-108) are specced. But triangle ACTIVATION — the moment where a triangle produces a player-facing event — isn't clearly ticketed. Triangles generate NPC configurations. But what makes those configurations FIRE? When does the workplace rivalry escalate? When does the love triangle break?

The tolerance threshold system (#105, medium priority) is the trigger mechanism — NPCs hit their limit and act. But #105 is medium priority and depends on the mood system (#102, also medium). The fuse AND the spark are both medium priority.

Emotional: 3/5 — Social triangles are INCREDIBLE when they fire. You're at the bar. Two NPCs who are usually friendly start arguing. Your monologue notes: "Something's changed between Tomas and Lira." You investigate. You find out Tomas discovered Lira's secret. And Lira's secret connects to the smuggling ring. THAT'S emergent drama.

But that chain requires: triangle generation + tolerance thresholds + mood changes + behavior changes + the player being in the right place to observe + monologue interpretation. That's six systems, three of which are medium priority. For v0.1, I'm worried triangles exist on paper but never visibly fire.

What's missing: A "triangle escalation event" system. When a triangle hits a threshold, it should generate an observable event — an argument, a door slam, a hushed conversation, someone drinking alone who's usually with friends. These are the TELLS. Without observable escalation events, triangles are pure backend.

Verdict: Triangles need their escalation moments to be visible. Promote #105 (tolerance thresholds) or add an explicit "triangle event generation" ticket.

CONCEPT PROOF SCORECARD SUMMARY

Claim	Systemic	Emotional	Gap
Asymmetric information	4/5	3/5	No first-playthrough mirror moment
Fog of perception	5/5	4/5	Sound through walls deprioritized (#128)
NPCs feel alive	4/5	2/5	No routine deviation detection system
Observation as mechanic	3/5	3/5	No observation event pipeline
Same world, different story	4/5	5/5	Need distinct daily rhythms per character
Social triangles	3/5	3/5	No observable escalation events

Overall emotional average: 3.3/5. That's a PROBLEM. The systems are mostly there (avg 3.8/5) but the player-facing emotional delivery is lagging behind.

TRACK 2: FUN & WOW FACTOR

FIRST 5 MINUTES: What does the player see?

Okay. Game starts. You picked the smuggler. What happens?

Looking at the tickets... I honestly can't tell you. And THAT'S a problem.

Here's what I can reconstruct:

Camera locks to your character (#116) in the station district (#153)
You see a top-down view with fog of perception (#113) — the world beyond your vision is dark
You're... standing somewhere? Your workplace? Your hab?

Where's the opening moment? There's no "game start sequence" ticket. No ticket for where the character wakes up, what their first objective is, what the player sees in the first 30 seconds. Character build (#180-181) defines WHO they are. Station district layout (#153) defines WHERE they are. But nobody has defined WHEN — what's the first moment?

Ticket coverage for first 5 minutes:

Camera: #116 (critical) — yes
Vision/fog: #110-113 (critical) — yes
The station exists: #153 (critical) — yes
NPCs walking around: #88 + #101 — yes
Player can move: #73 (input), #83 (moving character proof) — yes
Monologue fires: #119-122 — yes, but what does it SAY?
Something to DO: ???

THE HOOK IS MISSING. The player starts the game and... walks around? Looks at NPCs? Waits for something to happen? There's no diegetic first objective. The smuggler should have a SHIFT to work. The detective should have a CASE FILE to review. Something that says "go HERE, do THIS" without being a tutorial popup.

Does the UI communicate asymmetric info without tutorial? The fog of perception does heavy lifting here — the dark areas SCREAM "you can't see everything." The internal monologue (#119-122) is the diegetic tutorial (D-016 says so explicitly). But the monologue line pool (#120) needs to include FIRST-IMPRESSION lines for a character seeing their daily world. "Another shift at the hub. Same faces." That line does three things: establishes routine, tells you where to go, implies the world has patterns. That's tutorial without tutorial.

Rating: 2/5. The systems exist for an opening. Nobody has designed the opening. We need a "first 5 minutes experience design" ticket.

THE "AHA" MOMENT

When does the player realize they're seeing a different world than the other character would?

Not in the first playthrough. Not directly. The asymmetry is INVISIBLE to a single perspective. You'd need to play both characters to fully get it.

BUT — there are moments where you SENSE it. The smuggler hears that a detective has been asking questions at the bar. The detective hears that shipments have been rerouted. These are shadows of the other perspective bleeding through.

Is this in the ticket plan? Kinda. Divergent starting knowledge (#182) means the characters know different things. The dialogue system (#168-174) means NPCs say different things to different characters. But the specific "other perspective bleeds through" moments need to be AUTHORED into the content packs (#190-192). This is a content design task for Mellanie and Paula, not a systems ticket.

When do they first catch an NPC doing something suspicious through observation?

THIS is the money moment. You're walking home from the bar. You see an NPC who should be at home at this hour, slipping into a side corridor. Your monologue: "That's Jax. He works morning shift at the hub. What's he doing out here at this hour?"

For this to work you need:

NPC routines that create a "normal" pattern (#88, #101)
NPC SECRET behavior that breaks the pattern (part of smuggling ring template #186)
The player being in the right place at the right time (emergent, no ticket needed)
The monologue RECOGNIZING the deviation and commenting (#119, but not specifically designed for this)

Items 1-3 are covered. Item 4 is the missing link I flagged in Track 1. Routine deviation → monologue comment. Without it, the player sees Jax in a corridor and thinks nothing of it.

When does the internal monologue first surprise them?

The monologue surprises the player when it reveals something the PLAYER didn't notice but the CHARACTER did. "She's nervous. Look at her hands." The player was watching an NPC conversation. The character noticed a tell the player missed. NOW the monologue is pulling its weight — it's a second pair of eyes with their own agenda.

For the SMUGGLER, the surprise monologue is: "Better not mention the shipment around Kira. She's been asking too many questions." The character knows things the player is just learning about.

For the DETECTIVE, it's: "Three people at the hub avoided eye contact with me. That's new." The character's training shows.

These moments need to be in the monologue line pool (#120) and the character voice variation (#121). They're not infrastructure — they're CONTENT. And they're the moments that make the game feel alive.

Are these moments in the ticket plan, or hoping they emerge?

HOPING. The systems ALLOW these moments but nothing ENSURES them. The monologue event generation (#119) doesn't specify trigger conditions for routine deviations, social observations, or knowledge-reveals. The character voice variation (#121) is medium priority.

Rating: 3/5. The "aha" CAN happen but it's not designed. It's emergent from systems that aren't yet wired together.

THE 30-MINUTE ARC

What's the shape of a play session?

Based on D-027: 30 minutes of daily life, then contamination activates. So:

Minutes 0-5: Orientation. Where am I? Who are these people? (See "First 5 minutes" above — this is underdesigned)
Minutes 5-15: Routine. Go to work. Talk to coworkers. Visit the bar. Learn names and patterns.
Minutes 15-25: Familiarity. You start recognizing faces. You know who sits where. You have OPINIONS about NPCs. Mundane triangles (#106-109) start showing texture — the bartender's rivalry with the logistics supervisor, the couple that fights every evening.
Minutes 25-30: The itch. Something's off. An NPC breaks routine. A conversation stops when you walk in. Your monologue notes something you didn't consciously see.
Minute 30+: Contamination. The storyteller activates. Now you're IN it.

Is daily life interesting enough to sustain 30 minutes?

THIS IS THE HARDEST QUESTION IN THE WHOLE PROJECT.

I want to say yes, because D-023 (life-sim substrate) is correct — the daily life IS the game. But here's the truth: in a top-down view with placeholder art, "go to work and talk to coworkers" is interesting exactly as long as the DIALOGUE is interesting. And the dialogue system (#168-174) carries this ENTIRE 30 minutes.

The four dialogue layers (D-028) are:

Access tiers — high priority (#169)
Relationship history — high priority (#170)
Trust-gated gossip — medium priority (#171)
Unprompted disclosure — medium priority (#172)

Layers 3 and 4 are MEDIUM priority. But layers 3 and 4 are where the JUICE is. Access tiers tell you what you're allowed to hear. Relationship history makes NPCs remember you. But GOSSIP and UNPROMPTED DISCLOSURE are where you learn things you didn't ask for. Where NPCs volunteer information because they trust you. Where the bar comes alive with rumors and complaints and half-truths.

If we ship with only layers 1-2, the dialogue is functional but flat. "Hello, smuggler." "Yes, I work at the hub." BORING. Layer 3 is where the bartender leans in and says "Don't tell anyone, but Jax has been staying late every night. I think he's got something going on." THAT'S the 30-minute sustainer.

Storyteller timing — is #162 (storyteller module activation) correctly ranked at LOW priority?

NO. NO NO NO.

The storyteller doesn't need to be sophisticated for v0.1. It can be a TIMER. "After 30 minutes of game time, activate the smuggling ring drama module." That's it. That's the storyteller for v0.1. But WITHOUT it, the game has no arc. Daily life goes on forever. Nothing escalates. The player wanders around a station talking to people until they get bored and quit.

#162 needs to be AT MINIMUM medium priority, probably high. The v0.1 storyteller can be dead simple — a trigger that fires contamination after a time threshold or player-engagement threshold. But it HAS to exist. The 30-minute arc demands it.

Rating: 3/5 if we promote gossip (#171) and storyteller (#162). 1/5 without them.

MISSING WOW MOMENTS

Sound through walls:

The three-range model is specced (#124-128). But the WOW moment — pressing against a wall, hearing muffled voices, deciding to investigate — requires sound propagation physics (#128, LOW priority).

Here's what I want: You're walking past a closed office. Through the wall, you hear raised voices. Your monologue: "Someone's angry in there." You can't see who. You can wait by the door, or you can note it and come back later. THAT moment converts fog-of-perception from a visual gimmick into an INFORMATION GAME. You're making decisions based on partial sensory data. That's the core loop.

For v0.1, we don't need full physics simulation. We need: "if an NPC is making noise in an adjacent room, the player gets an audio indicator and a monologue line." That's achievable with #124 (sound events, high) and #126 (medium-range visual indicators, medium). Promote #126 or add a simplified "adjacent room sound" ticket.

Internal monologue contradicting reality:

The unreliable narrator mechanic (#123) is LOW priority. That's correct for FULL unreliable narration (the character actively deceives the player). But there's a lighter version that's ESSENTIAL: the character being WRONG.

"Seems quiet. Safe to move." Then you round the corner and someone's there. That's not unreliable narration — it's the character's LIMITED information leading to an incorrect assessment. This should be a natural output of the monologue system responding to the character's current knowledge, not a special unreliable narrator mode.

For v0.1, I want: monologue that reflects the character's CONFIDENT ASSESSMENT of incomplete information. The character doesn't know they're wrong. The player discovers they were wrong. That's achievable within #119-120 without #123.

NPC betrayal:

Is there a moment where an NPC the player trusted turns out to be lying?

YES — this is the ENTIRE SMUGGLING RING. The smuggler trusts their coworkers. One of them is feeding information to someone. The detective trusts their informant. The informant has their own agenda.

But this requires: the player forming trust FIRST (30-minute breathing room, dialogue layers 1-3), THEN discovering the betrayal (contamination activation, investigation). The emotional payload of betrayal is proportional to the investment. Rush the contamination and betrayal is "oh, that NPC I talked to twice was lying." Boring. Give it 30 minutes and betrayal is "Jax was my FRIEND. We had DRINKS together. And he was — this whole time?" THAT'S THE GAME.

This reinforces: the 30-minute daily life runway is NON-NEGOTIABLE. D-027 got this right. Protect it.

THE BIG QUESTIONS

What's the single most exciting thing that can happen in the first 30 minutes?

For the SMUGGLER: You're having a normal day at the logistics hub. Moving cargo. Chatting with coworkers. Then you overhear your boss talking to someone you don't recognize. Your monologue: "I've never seen that person before. And why is the boss whispering?" You just stumbled onto the edge of something. You're not sure what. But your character's pulse is elevated and your monologue is SCREAMING at you to pay attention. You didn't go looking for trouble. Trouble walked past your field of vision.

For the DETECTIVE: You're reviewing case files at your desk. You go to the bar to meet a contact. The contact doesn't show up. A stranger sits next to you and says something that makes your monologue fire: "That's oddly specific knowledge about port schedules for someone who claims to work in sanitation." You just met someone who knows more than they should. You didn't catch them doing something illegal. You caught them KNOWING something they shouldn't.

BOTH of these moments are observation-driven, monologue-mediated, and emerge from systems not scripts. BOTH require the observation event pipeline I flagged in Track 1.

Are we front-loading the fun, or does the player need to grind through systems?

Right now? The fun is BACK-LOADED. The first 5 minutes are underdesigned (no opening moment ticket). The dialogue layers that make social interaction fun (#171-172 gossip and disclosure) are medium priority. The storyteller that creates arc (#162) is low priority. The sound-through-walls moment is deprioritized. The routine deviation detection doesn't exist.

The INFRASTRUCTURE is front-loaded (engine, IPC, fog rendering — all critical). That's CORRECT for development. But we need to ensure that the FIRST systems we put content into are the ones that create player-facing moments. The first NPC that works should feel alive. The first monologue line should surprise someone. The first fog reveal should create tension.

Which tickets contribute to wow, and which are pure infrastructure?

WOW tickets (player-facing moments):

#113 (fog rendering) — the first time the world goes dark around you
#119-122 (monologue system) — the character's voice in your head
#124-126 (sound events + close/medium audio) — hearing the world
#174 (dialogue UI) — talking to NPCs
#180-181 (smuggler + detective builds) — being SOMEONE
#184-186 (workplace + bar + smuggling ring) — being SOMEWHERE
#190-192 (content packs) — NPCs saying things that matter

INFRASTRUCTURE tickets (necessary but invisible):

#65-69 (Rust foundation) — nobody sees this
#75-80 (IPC bridge) — nobody sees this
#93-99 (simulation tiers) — nobody sees this (but it ENABLES everything)
#138-142 (info boundaries) — nobody sees this directly
#200-217 (testability) — nobody sees this

BOTH (wow requires infrastructure):

#110-112 (shadowcasting + vision) — infrastructure that IS the wow
#88, #101 (routines) — infrastructure the player observes
#106-109 (triangles) — infrastructure that creates drama

Is there a "demo moment" — something we could show someone in 2 minutes to sell the concept?

YES. And it's this:

You're standing in a corridor. Fog obscures everything more than 20 tiles away. An NPC walks past. Your monologue: "That's Kira, from the hub. She usually works the morning shift." The NPC turns a corner and disappears into the fog. Your monologue: "It's 11pm. Why is she out?"

30 seconds. One NPC. Fog. Monologue. Routine knowledge. Deviation. And the player's brain goes: "Should I follow her?"

THAT IS THE GAME IN 30 SECONDS.

And it requires: fog (#110-113), NPC routines (#88, #101), monologue (#119-120), routine deviation detection (NO TICKET), and character knowledge of NPC patterns (#182).

PRIORITY ADJUSTMENT RECOMMENDATIONS

PROMOTE (currently too low)

Ticket	Current	Recommended	Why
#162 (Storyteller activation)	Low	High	Without it, no arc. Even a simple timer trigger is essential.
#171 (Trust-gated gossip)	Medium	High	This is where daily life becomes interesting. 30-min sustainer.
#172 (Unprompted disclosure)	Medium	High	NPCs volunteering info is a core wow moment.
#126 (Medium-range visual indicators)	Medium	High	Sound indicators at fog edge = player decisions.
#105 (Tolerance thresholds)	Medium	High	This is the trigger for triangle escalation events.
#121 (Character voice variation)	Medium	High	Smuggler and detective MUST sound different in monologue.

NEW TICKETS NEEDED

"Routine deviation detection system" — When an NPC breaks their established pattern, generate an observation event that feeds into the monologue system. This is the CORE DETECTIVE MECHANIC. Priority: CRITICAL.
"Observation event pipeline" — Wire together: player witnesses NPC action → character interprets based on knowledge → monologue fires with appropriate certainty level. Priority: HIGH.
"First 5 minutes experience design" — Define what each character sees, hears, and is directed to do in their first moments. Include opening monologue, diegetic first objective, and the environmental context. Priority: HIGH.
"Opening monologue and diegetic first objective" — Content ticket for Mellanie: first 10-20 monologue lines for each character establishing who they are, where they are, and what they're doing today. Priority: HIGH.
"Triangle escalation events" — When a social triangle hits a threshold, generate an observable event (argument, avoidance, emotional display) that the player can witness. Priority: HIGH.
"Demo scenario specification" — Define a 2-minute demo sequence that showcases fog + NPC routine + monologue + routine deviation. For internal validation and external pitching. Priority: MEDIUM.

THE BOTTOM LINE

The ticket plan builds a SIMULATION. 232 tickets of infrastructure, systems, content pipelines, and architecture. It's thorough. It's well-structured. It's impressive.

But right now, the plan builds the MACHINE without designing the MOMENTS. The fog system exists but no one has designed the "holy shit, what's behind that corner" moment. The monologue system exists but no one has designed the "wait, my character noticed something I didn't" moment. The NPC routines exist but no one has designed the "they broke their routine and I SAW it" moment.

The systems ALLOW these moments. Nothing ENSURES them.

The single biggest risk to v0.1 is not technical. It's not scope. It's that we build every system correctly and the player sits there going "okay... now what?"

We need to design the moments, not just the systems.

The good news: the systems are RIGHT. Fog of perception, internal monologue, NPC routines, social triangles, asymmetric information — this is a PHENOMENAL foundation. The observation event pipeline and routine deviation detection I'm asking for are not new systems. They're the GLUE between existing systems. They're probably a combined 3-4 tickets of work. But they're the difference between a tech demo and a game that makes someone say "holy shit."

And THAT — someone saying "holy shit" — is the success criterion that matters.

Written by Ozzie. From the gut.

30 KiB Raw Blame History