settled-reach/docs/workshops/wheres-the-fun/round4-araminta.md

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

title	description	type	status	workshop	agent	round	created
Round 4: Araminta — Cross-Review and Refinement	Araminta's cross-review and refinement of round 3 proposals	workshop	archived	wheres-the-fun	araminta	4	2026-03-05

Round 4: Araminta — Cross-Review and Refinement

Where's the Fun? Workshop | 2026-03-05

---

Reactions to Other Agents' Proposals

Tyre — Strong Agreement, Unblocks Everything

"NPC legibility data in ObserverSnapshot is easy. The data exists. We just need to send it." This is the most important sentence in all of Round 3 for visual design. The knowledge-gated reveal system I proposed in Round 3 — where visual information tracks knowledge-graph state — depends entirely on the snapshot carrying display name, activity label, emotional state, and relationship summary. If that ships in Phase 1, every visual layer I build on top of it has a real foundation. If it doesn't, I'm designing character legibility on top of nothing.

Tyre's Phase 1 and my character archetype work are directly coupled. The sprint order needs to reflect this: server NPC legibility data and client archetype visual system must ship together. One without the other delivers no value to the player.

Miri — Natural Collaboration, One Dependency

"Sova Transit place identity document" and "NPC archetype visual spec (collaborative Araminta/Miri)" are flagged as two separate deliverables. I'd push to design these as one document in two sections. Place identity and character archetype legibility are not independent — dock workers dressed and moving like dock workers IN a dock area is more legible than either element alone. The visual language of a place and the visual language of the people in it reinforce each other or they fight each other. One document, co-authored, is cleaner than two documents that need to be reconciled later.

Ozzie — Redesigned Wow Moments Define My Visual Roadmap

Ozzie's six redesigned moments aren't just emotional targets — they're visual design specifications I didn't realize I needed:

• First Day: supervisor NPC with a distinct visual identity (authority readable without a label)
• The Asymmetric Lens: career-tagged ticker visual design — 15 lines that need to LOOK like they belong to three different interpretive frameworks
• The Ownership Moment: property UI visual design — what does "mine" look like on a tile map?
• The Enemy: NPC attitude degradation visible in their behavioral state indicator — this feeds directly into my behavioral state read system

Round 3 Araminta described the three-tier signal system in the abstract. Ozzie's moments give me concrete design targets. I'm treating these as my visual specification list for v0.2.

Mellanie — Co-Design Required on Insert Grammar

Mellanie notes: "copy needed for the entire diegetic tool suite — each tool has a distinct voice register per career." My career insert grammar document and her voice register work need to be designed simultaneously, not sequentially. If I design a law enforcement insert that looks like Commission blue + case-file aesthetic, and Mellanie writes law enforcement tool copy in a different register, they'll feel like two different designers had the same brief. The visual register and the voice register of each insert need to be defined in the same room, at the same time.

Recommendation: the career insert grammar document should be a joint deliverable — one column for visual register, one column for voice register, one per career. Co-authored by Araminta and Mellanie.

Paula + Gore — Phase Zero Depends on Character Legibility, Not the Other Way Around

Paula's Phase Zero (earn warmth with Kael before the arc can erode it) and Gore's reframe from "complicity" to "consequence" are both correct — but both are gated on character legibility. You can't feel warmth for Kael if Kael reads as a dot. You can't feel consequence if you can't tell which dot did what to which other dot. Paula says "add Phase Zero before the arc." I'd say "add character legibility before Phase Zero." They agree in spirit — Phase Zero is the earned warmth, and the player can only earn warmth for visible people. But the visual work comes first in the sequence.

Gestalt — Verb System Has a Visual Surface I Didn't Address

The VerbPriorityProfile refactor (job-aware verb priority) has a visual dimension I missed in Round 3: the on-screen verb prompt ([E] label) needs a visual treatment that matches the career context. Law enforcement's primary verb might visually signal authority — a different prompt color or icon set than a smuggler's social-network verb or a hacker's remote-access verb. The insert grammar document needs to include verb prompt visual treatment per career, not just the HUD overlay. This is a gap in my Round 3 proposal; adding it to the scope.

---

Three Questions for Jeroen

Q1: Character appearance customization — how deep?

CK3-style character creation (culture, family, skill budget) implies the player is defining who their character IS, not just what they can do. Does that extend to visual appearance? And do NPCs reflect cultural variation in their visual presentation?

This matters because it's the difference between two completely different design tasks:

• Option A (appearance system): Player-defined hair, clothing, cultural dress markers. NPCs with culture-specific appearance variation. I'm designing a layered costume/appearance grammar that works at tile scale. This is achievable but requires deliberate constraints — top-down tiles have a readability floor where CK3-level detail becomes noise.

• Option B (archetype palette): Character appearance is archetype-anchored. Cultural variation exists in the world but expresses through architectural and environmental detail, not individual NPC appearance variation. I'm designing 3-5 legible archetype silhouettes that can be palette-swapped for career/faction.

I have a strong visual design preference for Option B — archetype silhouettes are more legible at tile scale, and cultural richness communicates better through place and behavior than through individual character detail at this resolution. But if Jeroen's vision includes the player seeing their character as their created person, Option A is the right answer and we need to design for it from the start.

Q2: "Uncaring world" generates first — does that change what visual design deliverables I should be building?

The two-phase sequencing (world runs and feels natural → authored content injected) changes what kind of visual design work belongs in Phase 1. If the generator produces geography → infrastructure → zones → population → routines procedurally, then the visual palette system I design needs to be a SET OF RULES the generator applies, not a set of hand-crafted assets for Sova Transit specifically.

Concretely: should I be designing "Sova Transit's dock zone is cool industrial blue-grey" OR "any logistics zone in any generated location uses cool industrial palette because logistics zones have this visual grammar"? The first is world-specific art direction. The second is a generative visual grammar — reusable, scalable, but harder to make feel authored and specific.

The supplement says "world first, then content." I want to know which mode of visual design work supports that sequencing better. My instinct is that we design Sova Transit FIRST as a proof of the grammar, then extract the rules for the generator — but I want to confirm that ordering.

Q3: What's the visual near-miss you most want to avoid?

I have an obvious wrong turn I want to name and have you react to: designing character archetypes that are optimized for the detective/smuggler binary — suit-and-trenchcoat investigator, dockworker/smuggler type — which then read as "finished" placeholder art even after the life-sim pivot. If I design archetypes that only make sense in the context of a detective mystery, we'll have technically delivered on character legibility but painted ourselves into a visual corner that's hard to undo.

More broadly: given that the game is a single-character life sim where the player creates their character and picks from multiple career paths, what visual pattern would most undermine that promise? I'd rather hear the near-miss from you directly than design confidently toward it.

---

My Single Most Important Recommendation

The career bookmark list is a visual design blocker.

Q-WTF-005 (confirm the career bookmark list) is listed as an open question blocking Mellanie, Gestalt, Nigel, and me. I want to add weight to this blocker from the visual design side specifically.

The career insert grammar document — defining the visual HUD language for each career — is the document that lets every other visual deliverable in Phase 2 proceed coherently. Without a confirmed bookmark list, I don't know how many inserts to design, what information architectures they need to support, or what visual register each one should inhabit. Designing inserts for an unknown list risks designing for careers that get cut, or having no insert design for a career that gets added.

This isn't a large decision — it's confirming which 1-3 career paths get designed for v0.2. But it needs to happen before the career insert grammar sprint, and ideally before the NPC archetype visual spec work (so the archetypes are tuned to the careers that will be visible in v0.2).

Confirm the bookmark list. Everything downstream of it can move fast once it's settled.