8.2 KiB
NPC Visualization Workflow (non-nudity)
1) Scope & triggers
Use this workflow for:
- Named/specific NPC portraits that need stable identity across rerenders.
- Pool NPC batches for fast at-table retrieval.
- Craft/trade rerenders where quality progression must be visible in sold goods.
Example triggers:
- “Create stable references for NPC X before scene renders.”
- “Rerender this profession pool with clearer tier progression.”
- “Fix in-flight prompts so higher tiers visibly look better.”
- “Promote this character to an Anchor NPC.”
- “Make an Anchor Location / room pack before rendering the scene.”
- “Render named NPCs in a reusable location without losing identity.”
2) Choose mode first
Mode A — Named/specific NPC (reference-first)
Use when continuity for one character matters most.
Mode B — Pool NPC batch (production-first)
Use when breadth and retrieval speed matter most.
- Focus on clear category/tier read, roster diversity, and in-shop player-facing utility.
- Full face/body reference staging is optional unless the user asks.
Mode C — Anchor NPC / Anchor Location scene workflow
Use when a named character must survive repeated renders or when a room/venue must stage repeated scenes.
- If the room matters, confirm the people-free Anchor Location first.
- If the character matters, use Anchor NPC references and a human keeper gate.
- Read
references/anchor-npc-location-workflow.md.
Locked progression terminology (2026-04-20)
Pool NPC(P1): generic roster visual.Scene NPC(P2): named in-context/location-bound visual.Anchor NPC(P3): full portable reference pack (tri-face + body + outfits).- Promotion language:
promote P1→P2,promote P2→P3, and optionalfast-track P1→P3.
3) Storage layout (current)
Root: ~/output/to-dnd-session-rclone/Reference Visuals/
-
Reference Visuals/Anchor NPCs/<Region or Bucket>/<NPC Name>/00-face.jpg— neutral face reference (left/front/right stitched in one 16:9 image)01-body.jpg— front/back neutral body reference (A-pose)02-marks/— close-ups of unique marksnpc.json— profile metadataOutfits/<Outfit Name>.jpg— front/back outfit reference
-
Reference Visuals/Anchor Locations/(location workflows, side-by-side with Anchor NPCs)
Keep run logs and manifest TSV/JSON/MD files in hidden .manifest/ folders whenever possible.
4) Named/specific NPC pipeline (required when Mode A)
- Collect brief (name, age, role, vibe, attire, setting).
- Generate reference set (face/body/outfit) under anti-modern constraints.
- Preserve asymmetry and identity details; do not mirror.
- Gate: human picks keeper references.
- Render finals with interaction framing and keeper-consistent materials/lighting.
5) Pool batch pipeline (Mode B)
- Lock category + tier matrix up front.
- Keep each scene clearly “in-shop visit”:
- for-sale inventory visible,
- repair intake visible,
- trade-specific tools/materials visible.
- Keep roster freshness (do not recycle same face/name sets across professions).
- Keep tier distinctions legible in <3 seconds.
6) Crafts/service progression lock (critical)
For craftsmanship-heavy renders, progression must be visible in:
- Goods themselves (not only decor),
- Tool/station sophistication,
- Display quality and quantity,
- Staffing and space scaling,
- Clothing/material progression.
Workshop-to-boutique progression rule (2026-04-03)
For craftsmanship-heavy scenes, composition should evolve with wealth tier:
- 10–40 (Village -> Comfortable): customer should feel like they are walking directly into the real workshop; active making, benches, tools, materials, and visible process are part of the trust signal and can sit comfortably in the foreground
- 50+ (Prosperous and above): customer-facing presentation begins to separate from fabrication; finished goods and curated selection space become increasingly prominent
- for higher-end weapons/arms (including armor) and many luxury-goods scenes, the customer-facing image should read more like a shop / boutique / atelier / gallery-fronted workshop than a raw workbench
- foreground priority at higher tiers: finished goods, display stands/racks/plinths, customer-facing comparison space
- background/side priority at higher tiers: fabrication benches, tools, repair clutter, active making zones
- this is a compositional default, not a replacement for trade-specific QA; still validate outputs visually before broad promotion
For service-heavy categories (e.g., Food & Drink, Hospitality; Healthcare), progression must be visible in:
- Goods/menu/remedy quality,
- Service/process discipline,
- Environment quality and trust signals.
Use:
references/craftsmen-progression-locks.md
7) Style constraints (always-on)
- Norse, medieval, photorealistic, 16:9.
- No electric/fluorescent lighting.
- No modern materials/furniture/signage/UI overlays.
- Final portraits should be interaction-facing (subject oriented to viewer/camera).
Lighting baseline policy (2026-04-03)
For pool NPCs outside Food & Drink, Hospitality, the current frozen baseline is the learned Recipe F lighting posture:
- prioritize strict medieval realism over decorative lighting,
- prefer daylight-only illumination,
- do not show visible ceiling lamps, wall sconces, pendants, chandeliers, desk lamps, shades, bulbs, or filaments,
- do not allow internal cabinet glow, backlit shelving, or under-shelf light,
- for 50–60, hardwood-primary display furniture is acceptable,
- for 70+, favor marble/stone-primary display surfaces with only sparse medieval leaded-glass framing.
Use this as the default production baseline for non-Food/Hospitality pool rerenders. Do not keep tweaking it casually; probe first, then promote only after visual QA.
For Food & Drink, Hospitality atmosphere-heavy interiors, use the Recipe H-family concise branch:
- keep prompts short and scene-first (avoid giant lock paragraphs),
- anchor on one clear action and one compact workspace description,
- always include: inventory-for-sale visible, repair/work queue visible, tools/materials visible,
- 10 Village + 20 Poor + 30 Modest: compact/small-scale scene and named NPC solo (no assistants/crew; optional single non-staff visitor only). Village (10) communal workshop is exception-only when explicitly justified,
- lighting should be practical medieval sources (hearth/candle/oil + limited window spill),
- keep anti-modern negatives focused and concrete (no electric/fluorescent/modern fixtures).
Do not rely on long “hard lock v2” text blocks for hospitality if outputs regress into oversized rooms, multi-staff drift, or electric-looking fixtures.
For specified people / named locations, use a stricter QA-gated branch rather than editing the pool baseline in place.
For jewelers / jewelcutters, treat the scene class as unresolved for now: current small-luxury-item recipes still attract task-light / desk-lamp regressions, so do not promote those recipes broadly until they pass QA.
8) Tier + overlay composition
Use wealth tier as base and overlays as modifiers:
Tier=<10-Village..70-Elite (optional 80/90)>Settlement=<Village|Town|City|Capital>Security=<Open|Guarded|Fortified>Condition=<Worn|Standard|Pristine>
Reference:
references/wealth-tiers-10-70-signals.md
9) In-flight rerender retrofit pattern (when jobs already queued)
When user asks for progression fixes mid-run:
- Patch active rows in queue states (
pending|dispatched|in_progress) with a marker clause. - Verify patch counts by category/tier and status.
- If user asks for spot-checks, frontload one-or-more probe jobs per requested tier.
- Report evidence paths and caveats for already-dispatched rows.
10) Model guidance
- Named/specific NPC references (face/body), Anchor NPC packs, and Anchor Locations: default to grok-imagine-image-pro unless a concrete reason says otherwise.
- Most production renders: default to grok-imagine-image.
gpt-image-2is promising for reference-conditioned scenes and expressions, but treat it as a QA-gated branch; keep attempt counts outside prompts and avoid triptych/contact-sheet wording.- Allow explicit user overrides.