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

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

title	description	type	status	workshop	agent	round	created
Round 5: Araminta — Visual Design Reaction to 15 Decisions	Araminta's visual design reactions to the 15 locked decisions	workshop	archived	wheres-the-fun	araminta	5	2026-03-05

Round 5: Araminta — Visual Design Reaction to 15 Decisions

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

---

Overview

The 15 decisions land well conceptually. The generator-first approach, full character customization, and generated NPCs are all correct directions. But three of these decisions create compounding visual design problems that aren't solved by "we'll use outline/highlight." This round is my full technical accounting of those problems, plus per-decision reactions for completeness.

---

Decision-by-Decision Reactions

Decision 1: Proof-of-life = generator + graphics, not hand-built slice

Strong agreement — and it fundamentally changes my design task.

I was planning to design "Sova Transit's visual identity." That's the wrong output. The generator doesn't produce Sova Transit specifically — it produces locations with characteristics, and Sova Transit is one instance of a location that has certain zone types. My output needs to be a visual grammar the generator can apply: rules that say "a logistics zone has this color temperature, this prop vocabulary, these NPC archetype expectations." Sova Transit is the PROOF of that grammar, not the deliverable.

This means the style guide I write isn't world art direction for a specific place. It's a parameterized visual grammar with zone type as the input and palette + prop vocabulary + NPC silhouette expectations as the output. The generator reads from this grammar to dress any location it produces.

Implication for sprint planning: the style guide draft needs to be written BEFORE any sprite or tile work begins, because it defines the rules that all other visual production follows.

Decision 2: Skills + bookmark only for character creation (family/culture deferred)

Noted with a visual design subtlety.

Skills and bookmarks are the creation axes. Culture selection is deferred. But Decision 6 says culture is PRIMARY for voice — culture-driven, job modifies. This creates a gap: if the player doesn't select culture at creation time, where does their cultural identity come from for visual purposes?

Options:

• Implicit from starting location: the generated starting apartment and neighborhood express the cultural context the character is embedded in, even if not selected
• Bookmark implies culture: the tycoon bookmark implies a certain cultural-economic position, and the generated world populates the relevant cultural visual context around them
• Character appearance choices ARE the cultural signal: the player picks hair, clothing, colors — and those choices encode cultural belonging implicitly, without a culture dropdown

I'm operating under the assumption that the player's appearance choices (Decision 11) are the cultural expression in character creation, and that the world around them reflects generated cultural context. But this should be confirmed before designing the character creation screen.

Decision 3: Religion is NOT a game system

Clean scope removal. No visual design implications.

Decision 4: Tycoon is the v0.2 bookmark

Sets my visual priority sequence.

The tycoon bookmark gets the first career insert design. Visually this means:

• Insert aesthetic: financial dashboard. Warmer palette than law enforcement's institutional blue. Market data feeds, asset position summaries, economic opportunity indicators. The Settled Reach equivalent of Bloomberg Terminal meets a person's neural HUD.
• Tycoon verb visual treatment: economic verbs (Buy/Invest/Negotiate/Contract) need visual weight that communicates stakes. These aren't investigation verbs that reward patience — they're decision verbs with visible consequence speed.
• World overlay priority: property ownership markers, business contact availability indicators, economic zone legibility.

The tycoon insert will be the template that the other career inserts are designed against. Getting the tycoon design right establishes the grammar that law enforcement and other bookmarks follow in v0.3+.

Decision 5: Skills affect outcome, not verb availability

Outcome feedback becomes a visual design problem I hadn't fully addressed.

If everyone sees the same verbs but skill determines quality of outcome, then the POST-verb feedback (what happens after you act) needs to communicate outcome quality. A skilled negotiation vs a fumbled one produce different results — that difference needs visual representation.

Options for outcome quality signal:

• Feedback animation quality: a skilled action resolves cleanly; a poor skill action has a visual stumble (brief flash of incorrect/off-center feedback)
• Outcome descriptor in the signal: the ambient tier feedback line says "Negotiation: strong position" vs "Negotiation: they noticed your hesitation" — the text carries the quality signal
• NPC behavioral response: the NPC's behavioral state indicator shifts based on outcome quality — still moves to neutral after a stumble, but to warm after a confident interaction

I favor the third option for life-sim feel — the feedback is social/behavioral, not scored. You read the room, not a number. But this needs NPC behavioral state indicators to be designed and live in the client before it works.

Decision 6: Culture-driven voice, job modifies

Sets the NPC visual character design priority.

NPCs are generated with cultural identity as the primary dimension, job as modifier. Visually this means:

• Silhouette/posture = role/job (the dock worker stands differently than the business contact)
• Palette and detail = culture (the same dock worker from culture A vs culture B has the same body posture but different clothing palette and cultural detail)

The risk: if I design the archetype system with ONLY role as the organizing axis, I'll produce archetypes that look culturally flat — everyone's a generic type, not a person from somewhere. The visual grammar needs culture as a modifier layer on top of role as the structural layer.

This is a component-asset design question (see Deep Dive 2 below).

Decision 7: ALL NPCs are generated, no named characters

The biggest visual design scope change in the 15 decisions.

I was planning to design visual identities for Kael, Naia, Maret. Those characters don't exist. The visual system needs to produce emergent character identity from generated components without hand-authored personality designs.

The key insight from Jeroen's answer: "The Sims and Rimworld are perfectly capable of generating interesting characters that come alive and create attachments." The Sims achieves this through:

1. Distinct visual appearance (generated unique combination of features)
2. Behavior that expresses personality consistently
3. Player investment through relationship mechanics

The visual design task: create a component-assembly system that reliably produces characters that feel DISTINCT from each other (not all looking like variants of the same template) and LEGIBLE in role/relationship (not visually indistinguishable chaos).

See Deep Dive 2 for the full technical breakdown.

Decision 8: Generative AI for NPC content templating

Noted — not directly a visual design task, but has one implication.

The AI templating is for content (dialogue, tone). Not for sprite generation. My component-asset system produces sprites; AI assists with the personality/dialogue layer. The two pipelines are parallel, not coupled.

The implication: eventually, the AI-generated personality of an NPC (their cultural tone, their speech patterns) should INFORM what kind of visual variation they receive from the component system. A character generated as "reserved, formal, high-status" should visually read as such — formal clothing set, upright posture, muted palette. This mapping from personality/culture dimensions to visual components needs to be in the style guide.

Decision 9: Possible in-game ollama for live NPC dialogue

Deferred — one future visual design consideration.

If NPCs have live AI dialogue, there may be a moment where the NPC is "thinking" (generating a response). A visual treatment for this state — subtle, not breaking the diegetic fiction — would be needed. Something like a brief attentive posture hold, a minimal insert-style processing indicator in the dialogue panel. Not a spinner. Something that feels like a person collecting their thoughts rather than a machine processing.

Flagging for later; no immediate visual design action needed.

Decision 10: Quietly responsive world, gradient of caring by social proximity

The behavioral state indicator system needs a relationship axis.

My Round 3 behavioral state indicators were designed for three states: stress, suspicion, routine comfort. That's a world-state axis. Decision 10 adds a RELATIONSHIP axis: this NPC notices you, cares about you to varying degrees.

The relationship gradient (stranger → acquaintance → colleague → friend) needs visual expression. My proposal:

Relationship level	Behavioral indicator treatment
Stranger	No indicator (world doesn't know you exist)
Acquaintance	Ambient tier indicator on close approach (grey, low-weight)
Colleague/neighbor	Relevant tier indicator when active (amber, present but not demanding)
Primary social contact	Relationship state visible (warm/stressed/concerned — behavioral reads now include relationship reads)
Hostile	Danger tier signal (red, avoiding/tracking you)

This is still consistent with the three-tier system. The tier isn't just about urgency — it also maps to social proximity. Strangers live in ambient-or-invisible. Friends are legible at the relevant tier unless they're in crisis, which promotes to danger.

Decision 11: Full character customization (hair, clothing, colors)

The hardest unsolved visual design problem. Deep dive below.

Acknowledged as a real problem. Outline/highlight is the proposed solution. I have significant concerns about how this plays out at tile scale. See Deep Dive 1 for the full breakdown.

Decision 12: Setting delivery: both layers (visual + insert)

Confirms the parallel production structure.

The visual layer shows place identity through palette, props, and NPC behavior. The insert layer names and contextualizes. These need to be designed together — the insert copy for a zone should reference the VISUAL elements the player is already seeing, not introduce information the world hasn't shown. "The docks" is named by the insert after the player has already read the space as industrial/logistical from its visual grammar.

Practical implication: Mellanie and I need to co-draft the tycoon insert copy AFTER the zone visual grammar is established, so the copy can reference the visual context accurately.

Decision 13: First Settled Reach moment: apartment + insert activation

Two designed visual sequences, each deserving their own spec.

The Apartment Wake-Up:

The apartment is auto-generated to reflect economic starting position. For the tycoon bookmark with a decent skill budget: a mid-to-upper apartment. But "mid-to-upper" needs visual specifications the generator can apply:

• Wealthy apartment signals: larger window viewport (more of the exterior visible), furniture density higher, decor items present (art, plants, personal objects), cleaner color palette (less wear-and-tear textures)
• Modest apartment signals: tighter viewport, fewer furniture pieces, more utilitarian props (a single chair, a small screen), slightly worn palette

These aren't just size differences — they're VISUAL GRAMMAR signals that communicate economic status without explicit text labels. A player who picked a skill-heavy starting budget (less starting capital) should wake up in a space that visually reads as "I'm building toward something, not there yet."

The apartment is also the player's first glimpse of the Settled Reach's visual technology — insert hardware on the wall or bedside, ambient smart-building elements, the window showing the generated exterior. The Settled Reach reads as advanced-but-human through the apartment's tech-texture, not through a lore drop.

Insert Activation:

The neural insert powering on is a DESIGNED BEAT. Visually I'd propose:

1. Apartment view is clean (no HUD overlay)
2. Insert activates: a subtle warmth blooms across the vision periphery (edge vignette in insert accent color, very brief)
3. UI elements phase in sequentially: world overlay layer first (you can now "read" zone labels), then the financial feeds, then notification panel — each appearing as the insert calibrates
4. The tycoon insert's dashboard assembles itself — empty at first, populating with starting data

This sequence teaches the player what the tycoon insert shows WITHOUT a tutorial. They watch it come online and see what it surfaces. The insert IS the onboarding.

The visual register for insert activation should feel intimate and sensory — not technical UI appearing. The neural connection is a felt experience, not just a screen appearing. Blur-to-clarity transition. Sound design partners with this heavily (Gore/GORE's domain but the visual sequence needs to be audio-aware).

Decision 14: Groundhog Day alarm clock homage

Specified in audio, implied visually.

The click pa-pa pa-pa is audio. The visual analog: the alarm clock device in the apartment (whatever form that takes in the Settled Reach) transitions from "idle/sleeping" state to "active" state as the sound fires. Then cut short — the device returns to idle as the player is "already awake" before the full sequence plays out.

The cut-short visual: the device's glow/indicator starts its wake-up pattern, then snaps off as the player's perspective says "I'm already up." This is subtle and fast. It shouldn't demand the player's attention — it's a background wink, not a front-and-center animation.

The "first game day only" constraint is important. On subsequent days, the alarm is ordinary (different, understated). This wink exists to establish the tone of the whole game from the very first second: this world is lived-in and wry, not earnest and serious.

Decision 15: Player choices ARE the content (Rimworld model)

Changes the insert's visual job description.

The insert can't be organized as a quest tracker — there are no quests. It's organized as a WINDOW ONTO OPPORTUNITY. The tycoon insert shows:

• Current market positions (what's moving, what's stable, what's vulnerable)
• Social contacts and their availability status
• Property and business asset summary (what you own, what state it's in)
• Economic events and news (filtered through the tycoon's knowledge/network)

This is a DASHBOARD, not a briefing. The visual design challenge: a dashboard can easily become overwhelming (too much data) or sparse (nothing to read). The 3-tier signal hierarchy applies here too. The insert surfaces:

• Danger tier: something you own or control is threatened, a deal is going bad
• Relevant tier: a contact is available, a market opportunity is open, a decision is pending
• Ambient tier: background world data, the economic texture the player reads over time

The dashboard design should feel like the player is reading the temperature of their situation at a glance. Not: "here's your objective." More: "here's the state of your world; what do you want to engage with?"

---

Deep Dive 1: Full Customization at Tile Scale

The Core Tension

The creation screen is an emotional investment moment. The player has chosen their character's hair color, clothing style, palette. They've invested in who this person IS visually. Then they enter the game — and their character is a 16-32 pixel sprite that needs to be readable at a glance during active gameplay.

These two modes of seeing the same character have fundamentally different readability requirements. Creation-screen fidelity and tile-scale gameplay fidelity are not on the same spectrum — they're different problems.

The Outline/Highlight Approach — What It Actually Solves

Outline/highlight solves one specific problem: separating the player character from the background and other NPCs at tile scale. A consistent 2px outline in a high-contrast color means the player's character doesn't visually merge with the tile floor or NPC crowd.

What it does NOT solve:

• Whether the player's customized hair color reads differently from an NPC's hair color at 16 pixels
• Whether a player who chose "red jacket" looks meaningfully different from a player who chose "dark jacket" in a crowd
• Whether the emotional investment of the creation screen translates to a feeling of "that's MY character" during gameplay

The Actual Solution: Identity Tokens, Not Pixel-Fidelity

The answer is not to make tile sprites represent creation choices at high fidelity. The answer is to make the impression of creation choices survive into tile scale.

What survives tile-scale reduction:

• Color temperature (warm vs cool palette)
• Value contrast (light vs dark clothing overall)
• Silhouette (slim vs broad, fitted vs loose clothing)
• Hair color read (dark/light/vivid — three distinguishable reads at 16px)

What doesn't survive:

• Specific haircut shapes
• Clothing detail (pockets, collars, material texture)
• Facial features

Proposed approach: Creation choices map to tile-scale token sets.

The creation screen offers full-fidelity selection. Each selection maps to a tile-scale token that represents the impression of that choice:

• "Deep red jacket" → tile sprite uses the warm-red jacket asset in the relevant body type layer
• "Ashen short hair" → tile sprite uses the dark-hair-short asset in the hair layer
• "Lean build" → tile sprite uses the slim silhouette body layer

The player sees their character in full fidelity during the creation screen and in portrait/close-up contexts. During tile-scale gameplay, they see an impressionistic representation that carries the COLOR TEMPERATURE and SILHOUETTE of their choices without the detail.

This is what The Sims does: the Sim looks like their creation at full zoom, like a colored impression at distant zoom. The player's brain fills in the detail because they know what they chose.

Identity lock: the player character outline color is theirs.

The player's character has a consistent outline color that is chosen during creation or assigned at generation and never duplicated in the local scene. This is not the avatar's clothing — it's a subtle but consistent visual marker. During gameplay: you always know which sprite is yours because of the outline treatment. No cognitive load.

The NPC Variant

NPCs are generated. They have the same component-assembly system but no specific player investment in their appearance. Their tile-scale impression needs to communicate role first (archetype silhouette), culture-context second (palette), and individual distinctness third (within-type variation).

The risk: if NPC generation produces too much within-type variation, the archetypes stop reading. If it produces too little, everyone in the same role looks identical.

Proposed constraint: archetype silhouette is fixed per role. Palette is variable within cultural range. Detail (hair, accessory) is variable within cultural range.

A dock worker's POSTURE and BODY TYPE silhouette doesn't vary. What varies is the color of their work gear (culture-influenced) and their hair. At tile scale, they still read immediately as a dock worker — but they look like THEIR dock worker from wherever they're from.

What Needs Confirmed Before I Can Design This

1. Creation screen fidelity target: is the creation screen a full-character render (like CK3's portrait) or a top-down tile-scale preview? If CK3-style, I'm designing two character representations — portrait and tile. If tile-only, the creation screen shows the impressionistic version and full fidelity is never the goal.
2. Component granularity: how many distinct options does the player choose from in each category? The granularity determines how many tile-scale token assets I need to produce. 10 hair colors × 8 clothing styles × 4 silhouette types = 320 sprite combinations per archetype. At tycoon-only scope, this is manageable. At all-careers scope, it scales fast.

---

Deep Dive 2: Generated NPC Visual Variety Without Visual Noise

The Problem

All NPCs are generated. The generator produces:

• Role (dock worker, colleague, business contact, neighbor)
• Cultural background (which culture's visual grammar applies)
• Personality dimensions (reserved vs. expressive, formal vs. casual, high-status vs. low-status)
• Relationship to the player (stranger, acquaintance, contact, rival)

The visual system needs to express all of these dimensions while keeping any NPC legible at a glance for ROLE. A player looking at a crowd needs to instantly parse: "dock workers over there, two business contacts near the entrance, a supervisor at the desk." They don't need to consciously read this — the visual grammar communicates it before the player's conscious attention engages.

The Legibility Hierarchy

Rule: role legibility must survive ALL cultural variation. Two dock workers from different cultures must both instantly read as dock workers. Cultural variation lives in dimensions that don't obscure the role signal.

Dimensions that carry ROLE signal (fixed per role, not culturally variable):

• Body posture / silhouette shape
• Clothing TYPE (working gear vs. business wear vs. casual)
• Behavioral default (what they're doing when idle)

Dimensions that carry CULTURE signal (variable within cultural grammar):

• Color palette of clothing (same clothing type, different cultural palette)
• Cultural detail markers (cultural accessories, style flourishes)
• Hair treatment (cultural norms vary)

Dimensions that carry INDIVIDUAL signal (variable within cultural range):

• Specific palette choice within cultural range
• Hair color/type selection
• Minor accessory presence

This hierarchy means: at tile scale, you read posture+clothing type → role. Then you read palette → cultural context. Then, if you're paying close attention, you read individual variation. Role is always the first signal; individual distinctness is the last signal.

The Component System Architecture

Each NPC sprite is assembled from four layers:

1. Body layer (fixed per role category): 3-5 distinct role silhouettes (service worker, professional, manual worker, authority figure, specialist/technical). This layer doesn't vary within a role.

2. Clothing layer (variable per cultural grammar): each role has a clothing type (work gear, business wear, etc.) with 4-8 cultural palette variants. The clothing type is fixed; the palette is culture-selected.

3. Hair layer (variable within cultural range): 3-4 hair type options per body layer, palette variants within cultural range.

4. Detail layer (optional, culturally significant markers): small cultural detail elements (a specific type of jacket closure, a cultural marking, an accessory associated with cultural background). Present or absent based on cultural generation rules.

Total sprites at v0.2 scope (tycoon bookmark, 3 role types, 3 cultural variants, 3 hair options): 3 body types × 3 cultural clothing palettes × 3 hair options × 2 detail states = 54 tile sprites per direction × 4 directions = 216 total sprite assets for NPC variety. This is a manageable production run. Scales with role types and cultural breadth as the game grows.

The Distinctness Problem in Crowds

Even with the hierarchy above, a crowd of same-role NPCs (all dock workers) risks visual repetition that undermines the "these are distinct people" reading. The Sims solves this with aggressive HAIR COLOR variation — even if body and clothing read similarly, distinct hair colors make individuals visually separable at a glance.

Proposed rule: within any scene, no two NPCs share the same combination of clothing palette + hair color. The generator tracks this during scene population and prevents duplicate combinations. Players can learn to tell individuals apart by their color combination even before knowing their name, which is how you start to form "that's the one who..." recognition before a name is revealed.

This is the visual equivalent of the knowledge-gated name reveal: you recognize the COMBINATION before you know the person.

---

Deep Dive 3: Auto-Generated Apartment Visual Variety

The Problem

The apartment reflects economic starting position. This is meaningful as a first impression — your apartment tells you something true about who your character is starting as. But "wealthy" and "poor" are mechanical designations; the visual system needs to translate them into spatial and atmospheric signals without explicit labels.

The Visual Grammar of Economic Status in the Settled Reach

What communicates wealth in a near-future working-class-to-middle-class range (the likely tycoon starting range)?

Wealthy signals (in Settled Reach aesthetic):

• Larger viewport — the window shows more of the exterior, implying more floor space
• Furniture density — more objects, each with finer detail
• Color palette — cleaner, less worn. Neutral-warm tones, intentional decor choices
• Technology presence — visible insert station, ambient-smart-building elements (lighting that responds, wall panels that indicate rather than just existing)
• View quality — the window looks out on a better slice of the generated exterior (elevated, park-adjacent, not directly onto another building face)

Modest signals:

• Tighter viewport — implied smaller space
• Fewer furniture pieces — one chair, a bed, a screen. Utilitarian
• Color palette — slightly warmer from use, worn textures visible
• Technology presence — insert hardware present (everyone has inserts) but less polished; the wall unit is clearly third-party or older model
• View quality — street level, another building face close, less natural light implied

Critical rule: both apartments must feel INHABITED, not empty or depressing. This is not Kenshi-indifference — the world quietly cares. Even a modest apartment has one personal object that communicates this is someone's home. A cheap screen with something playing, a plant that's doing okay, a jacket hung by the door. The emotional register is: "this person is making something of what they have" across the full wealth range, not "poor people have sad apartments."

Generator Parameters

For the generator to produce apartments with these visual reads, it needs parameters it can read from the character's starting state:

• wealth_tier (1-5 or similar) → selects furniture density level + palette set + viewport size
• cultural_context → selects which cultural visual grammar applies to the apartment's design language (furniture style, decor type, personal objects)
• bookmark → potentially adds career-specific personal objects (a tycoon even at starting wealth has one business-related item visible — a small screen showing market data, a leather planner-equivalent, something that says "this person thinks about money")

The personal objects are the richest legibility signal. They're small, but they're the thing that makes the apartment feel like a CHARACTER'S APARTMENT rather than a generated space that happens to belong to whoever plays it.

---

Cross-References to Other Agents' Round 4 Work

Miri (Round 4) — Zone Identity Spec is My Direct Upstream Dependency

Miri identifies the same chain I identified in Round 3: Miri writes the zone identity spec → Araminta produces tile palettes → Tyre exposes zone-type data in snapshot → generator applies visual grammar. Miri calls the zone identity spec "the first worldbuilding deliverable in the v0.2 roadmap." I agree completely. I cannot author the generative zone visual grammar (Decision 1's actual deliverable) until Miri's spec defines what zone types mean in the Settled Reach's social vocabulary.

The apartment visual grammar is a subset of this: "residential zone, lower economic tier" is a zone type with a social meaning. Miri and I should design these together — one document with a worldbuilding section and a visual expression section, not two documents that need reconciling.

Tyre (Round 4) — Archetype Taxonomy Is a Joint Design Task

Tyre's dependency mapping shows the server-side data (NPC legibility in ObserverSnapshot) can only expose what Miri defines as existing archetype types. My visual system can only render what the snapshot exposes. These three tracks fan out from Miri's archetype definitions.

Critically: Tyre's dependency chart shows "Miri's archetype definitions (what types exist)" as the bottleneck that everything fans out from. But the visual grammar needs to INFORM those definitions too — some archetype distinctions only exist because there's a meaningful visual difference. If two archetypes look identical at tile scale, they should be one archetype. The design flow needs to be: Miri/Araminta co-design the archetype taxonomy → Tyre implements it in the snapshot. Not: Miri designs, Tyre implements, Araminta adapts.

Gestalt (Round 4) — Verb Prompt Icon Set Confirmed In Scope

Gestalt's VerbPriorityProfile visual surface comment from Round 3 is still unaddressed in Round 4. I flagged it in my Round 4 output and it's now formally in my deliverable list (item 8: "Verb prompt icon set per career"). The icon set is small work with high consistency value — the icon inside the [E] bracket signals career register before any text appears. This is the visual layer underneath Gestalt's career-aware verb ordering.

Ozzie (Round 4) — Wow Moments Still My Visual Spec List, Now Tycoon-Filtered

Ozzie's six redesigned wow moments remain my visual specification list. They're now read through the tycoon lens:

• "First Day" = arriving at the tycoon's business for the first time — the Ownership Moment's antecedent
• "The Ownership Moment" = the tycoon's primary emotional peak — property tile with ownership indicator, business health state visible
• "The Consequence" = an economic decision's downstream effect becomes visible on the insert (a deal you made three days ago collapsed someone else's margin)
• "The Asymmetric Lens" = the market data ticker filtered through the tycoon's network and investment position — what they see that others don't

These are concrete design targets. I need Ozzie's final wow moment list (post-Round 5) before the insert grammar document can be written.

Paula + Gore (Round 4) — Phase Zero and Consequence Require NPC Legibility First

Both Paula's Phase Zero warmth model and Gore's consequence-as-theme require the player to emotionally invest in generated NPCs before any arc can fire. Both are gated on the visual system producing legible, distinct, relationship-aware NPC representations. My deliverable ordering (NPC legibility rules first, everything downstream of it) is the visual prerequisite for their content to land.

Mellanie (Round 4) — Tycoon Insert Grammar Is a Joint Deliverable

My Round 4 recommendation stands: the career insert grammar document should be co-authored (visual register column: me; voice register column: Mellanie; one per career). With tycoon confirmed as the v0.2 bookmark, the tycoon insert grammar document is the first output. The tycoon's visual register (financial dashboard, market data, amber-warm palette) needs to be designed in the same session as the tycoon's voice register. If I design first and Mellanie adapts, or vice versa, they'll feel like two designers on the same brief who never spoke. Short joint session, single document, one visual register and one voice register per section.

---

Questions for Jeroen (Visual Design Near-Misses)

Q1: Creation screen fidelity — portrait or tile preview?

The emotional investment of character creation depends on the player seeing their character at a fidelity that makes them care. At tile scale (16-32px), no character looks emotionally distinctive enough to invest in. CK3 uses full portraits. The Sims uses a fully-rendered 3D character viewer.

The near-miss: we design a creation screen that shows a tile-scale preview of the character — a technically accurate view of what they'll look like in gameplay — and the player can't tell the difference between their customization choices because everything is 20 pixels tall. The identity investment moment fails because the creation screen didn't make them care.

Question: Is the character creation screen a full-fidelity portrait/render moment, or is it tile-scale? And connected: when the player sees their character in the apartment wake-up sequence (their first in-world moment), is that a close-up portrait view or a tile-scale view? The answer determines whether I'm designing two character art styles or one.

Q2: How many cultures exist in the generated world, and what's their visual distinguishability priority?

Culture is primary for voice (Decision 6). Culture presumably affects apartment design, NPC appearance, and world texture. But we deferred culture selection from character creation — which implies culture is a WORLD property (what culture is this location's dominant culture) rather than a character property the player selects.

The near-miss: I design 2-3 cultural visual variants (enough for a prototype), and the world generates 6-8 cultural contexts because the Settled Reach's setting has established several distinct cultures. I've under-built the system; the generator exposes how incomplete the component library is.

Question: How many distinct cultural visual contexts should I be designing for at v0.2 scope? And is cultural visual grammar something the world generator applies to LOCATIONS (this location has a dominant cultural context) or to INDIVIDUAL NPCS (each NPC has a cultural background that may differ from the location's dominant culture)? The answer changes the combinatoric complexity significantly.

Q3: The apartment as identity anchor — how personal is it?

Jeroen described the apartment as part of the "First Settled Reach moment" alongside insert activation. The apartment is auto-generated but should reflect economic position. My deep dive above proposes that bookmark also affects personal objects (a tycoon's apartment has tycoon-relevant items). But how personal is it, really?

The near-miss: the apartment is generated to reflect wealth level but feels like a hotel room — correctly affluent or modest, but not YOURS. The player doesn't see themselves in it. They wake up in a room that is objectively appropriate but subjectively empty. The identity investment moment of character creation doesn't carry into the apartment because the apartment has no visual relationship to the choices the player made.

Question: Should the character's creation choices (appearance selections, skill emphasis) leave any trace in the apartment's visual generation? For example, a physically-skilled starting character might have equipment visible; a social-skill emphasis might have more relationship memorabilia visible. Or is the apartment purely economic position + cultural context, and the player's specific creation choices aren't expressed there?

---

My Single Most Important Concern

"Outline/highlight solves readability" is a hypothesis, not a solution.

Jeroen's answer to the full customization question was: "Readability solved through outline/highlight, not by limiting customization." I understand this and I'm not arguing against full customization. But outline/highlight is a disambiguation tool — it separates figures from backgrounds and from each other. It does not make a 16-pixel sprite communicate "this is the character I spent 15 minutes designing."

The emotional continuity between creation screen and gameplay is the design problem that needs solving before we commit to what "full customization" means in implementation. If the creation screen shows a tile-scale preview, the player knows what they're getting and invests at that level. If the creation screen shows a high-fidelity portrait, the player invests at portrait level and then needs to FIND that investment in gameplay — which means the tile sprite needs to carry the impression of the portrait, not be a separate, lower-fidelity thing.

I need to know what the creation screen fidelity target is before I can design the character component system with confidence. Everything downstream — how many components, what tile sprite resolution, whether to use portrait close-ups in apartment and dialogue contexts — depends on that answer.

This isn't blocking sprint work immediately. The zone palette grammar and NPC archetype silhouettes don't depend on it. But before any character creation screen or PC sprite production begins, this question needs a confirmed answer.