Files
Dolon (Agent) 35a6c40188
BetterLeaks / scan (push) Successful in 55s
Expand Setting Portability: applies to ALL NPCs, not just courtesans
Universal capability: any character + any setting.
Add general NPC examples: tavern keeper in forge, guild meeting in throne room.
Build reusable setting library for entire campaign.
2026-03-25 10:08:03 +00:00

7.1 KiB

Setting Portability — Cross-Scene Rendering

Discovered: 2026-03-25 (accidental identity swap during Cillian TransitionScene generation)

Scope: Universal — applies to all NPCs, not just courtesans. Any character identity can be rendered in any setting.

What it is: Character identities and setting descriptions are completely independent — you can render any NPC in any described setting, regardless of their "original" scene or intended location.


Discovery Story

While generating TransitionScene images for Cillian (sauna setting), accidentally used Eiríkur's identity description instead of Cillian's. Result:

  • ✅ Setting matched perfectly (Cillian's stone sauna with tiered benches, firelight)
  • ✅ Person rendered perfectly (Eiríkur with ash-blond hair, pale blue eyes)
  • ✅ No "scene ownership" lock — the model had no problem putting Eiríkur in Cillian's room

Implication: NPCs are not caged to their original settings. Settings are portable descriptions that can be combined with any character identity.


The Formula

NPC_A_identity + NPC_B_setting_description = NPC_A in NPC_B's location

Components:

  • Identity block: Physical description anchors WHO is in the scene
  • Setting block: Architectural/decor description anchors WHERE they are
  • Model treats them independently: No validation that they "belong" together

Universal applicability:

  • Courtesan in tavern keeper's inn
  • Blacksmith in noble's study
  • Guard captain in merchant's warehouse
  • Any NPC in any location

Use Cases

1. Cross-Scene Variants

Example (courtesan): "Show Kara in Eira's sauna instead of her bathhouse" Example (general NPC): "Show the tavern keeper in the blacksmith's forge"

  • Extract setting description from one NPC's scene
  • Apply different NPC's identity
  • Generate → NPC_A in NPC_B's location

Why: Creative variety, narrative flexibility, testing different atmospheres for same character.

2. New Location Testing

Example: Want to try a "firelit library" setting before committing?

  • Write setting description for library
  • Test with one courtesan's identity
  • Review results before applying to full tier

Why: Validate new settings without generating full cohort.

3. Guest Appearances

Example (courtesan): "Show the trio (Eira/Milla/Freya) in Kara's lanternlounge" Example (general NPC): "Show the merchant guild masters meeting in the jarl's throne room"

  • Extract setting from one location
  • Apply multiple NPC identities
  • Generate → Group in shared location

Why: Narrative flexibility (meetings, shared spaces, visiting arrangements, social scenes).

4. Setting Reuse

Example (courtesan): Cillian's sauna description works great → reuse for Eiríkur, Milla, etc. Example (general NPC): Medieval tavern interior → reuse for innkeeper, bard, regular patron, traveling merchant

  • One good setting description = portable asset
  • No need to extract setting from every NPC individually
  • Mix-and-match library of validated settings

Why: Efficiency. Once you have 10-20 good setting descriptions (tavern, forge, market stall, throne room, etc.), you can combine them with any NPCs.


Practical Workflow

Standard (Original Scene)

# Extract setting from courtesan's own Undressed image
vision_extract(cillian_undressed) → "stone sauna with benches..."
generate(cillian_identity + cillian_setting) → Cillian in his sauna

Portable (Cross-Scene)

# Use another courtesan's setting
vision_extract(cillian_undressed) → "stone sauna with benches..."
generate(eirikur_identity + cillian_setting) → Eiríkur in Cillian's sauna

Library Approach (Reusable Settings)

settings_library = {
    "stone_sauna": "traditional stone-walled sauna with...",
    "bathhouse_tiles": "polished bathhouse with tiled pool...",
    "lantern_lounge": "lantern-lit salon with silk cushions...",
    "fireplace_furs": "stone-walled lounge with fieldstone fireplace...",
}

# Generate any courtesan in any setting
generate(kara_identity + settings_library["stone_sauna"])
generate(cillian_identity + settings_library["lantern_lounge"])

Constraints & Gotchas

✅ What Works

  • Any courtesan in any setting (no scene ownership locks)
  • Multiple courtesans in same setting (shared space)
  • Same courtesan in multiple settings (alternate locations)

⚠️ Watch Out For

  • Tier mismatch: Putting Poor courtesan in Elite setting may feel incongruous (though technically works)
  • Gender-coded spaces: Some settings may read as male/female-coded (sauna vs boudoir); cross-gender may feel off
  • Setting continuity: If using for TransitionScene workflow, must match the courtesan's actual Undressed room for narrative coherence

❌ Doesn't Work

  • Reference-based portability: This discovery is text-only generation. Reference images anchor both identity AND setting, so portability doesn't apply when using composite references.

TransitionScene Implications

Original workflow:

  1. Extract setting from courtesan's Undressed image
  2. Generate TransitionScene using same courtesan + same setting

Flexible workflow:

  1. Build library of validated settings (one per tier/style)
  2. For each courtesan, pick the closest setting from library
  3. Generate TransitionScene without individual vision extraction

Trade-off:

  • Library approach: Faster, reusable, but less personalized
  • Extraction approach: Perfect match per courtesan, but more work

Recommendation: Use extraction for first batch to build library, then reuse settings for similar courtesans.


Future Experiments

Multi-Courtesan Scenes

  • Can we render pair/trio Undressed by combining identities + shared setting?
  • Formula: identity_A + identity_B + setting_shared → both in same scene
  • Already validated for Dressed/Topless (reference-based); text-only pairs/trios untested

Cross-Tier Settings

  • Render Modest courtesan in Wealthy setting (aspiration/fantasy framing?)
  • Render Wealthy courtesan in Poor setting (incognito/disguise narrative?)

Setting-Only Generation

  • Can we generate empty room by omitting identity entirely?
  • Test: prompt = setting_description_only + "no people"
  • Use case: Establish location before adding courtesans

Technical Note: Why This Works

Text-to-image models separate semantic concepts:

  • Subject tokens: Person, face, body, hair, eyes → WHO
  • Scene tokens: Walls, furniture, lighting, atmosphere → WHERE
  • Pose tokens: Standing, walking, sitting → WHAT DOING

The model composes these independently. As long as you provide clear tokens for each, it doesn't enforce "canonical" pairings. Identity + setting are modular.


Summary

Setting portability unlocks creative flexibility. Courtesans can appear in any setting you can describe. No scene ownership locks exist in text-only generation. Build a library of validated settings and mix-and-match with any identities.

Key insight: The accidental Cillian/Eiríkur swap wasn't a failure — it was a proof of portability. Embrace it.