Chapter 19. Wardrobe, Hair and Makeup, Injury, and Time State#

19.1 Consistent identity is not continuous styling#

The same face in the wrong clothes, a wound that switches sides, hair that suddenly dries — any of these breaks the audience out immediately. Identity assets answer who this person is. Look state answers where in the story she currently is. The two must be kept apart.

Wardrobe is not a string of colors in a prompt. It has cut, material, closures, layers, sleeve length, pockets, shoes, jewellery and a state of wear — and those details decide whether it holds across angles.

19.2 Wardrobe IDs and phases#

Each base look holds a stable ID. Story changes are recorded as state overlays rather than inventing a new name each time.

wardrobe:
  id: WD_LINYUN_GREY_SUIT
  owner: CH_LINYUN
  phase: return_to_company
  pieces:
    blazer: charcoal single-breasted, narrow notch lapel, no pocket square
    shirt: cool white, no pattern, top button closed
    trousers: charcoal straight leg
    shoes: black low-heel pointed
    accessories: [PROP_OLD_PEN]
  materials: matte wool suiting, low-sheen cotton shirt
  forbidden: [shiny fabric, gold buttons, skirts, red shoes]

"Grey suit" is not enough to lock an asset. Different models will change the lapel, the buttons and the material.

19.3 Wardrobe phases should serve the character arc#

Early, reveal, confrontation and intimate phases can differ, but the change should avoid the cliché of grey while poor and head-to-toe red once successful. Lin Yun moves from the old grey suit to a better-fitting black one while keeping the restrained silhouette and the old pen — signalling that her power has risen and her core identity has not.

For every styling change, write the story reason, the first appearance, and the change the audience should perceive. Frequent costume changes with no narrative function only add asset cost.

19.4 Overlay states#

One costume can carry overlays: buttons opened, cuffs rolled, rain-soaked, dusty, bloodied, torn.

wardrobe_state:
  base: WD_LINYUN_GREY_SUIT
  state_id: WDSTATE_E007_RESCUE_03
  effective_from: E007_S12
  overrides:
    blazer_button: open
    right_sleeve: dust_at_cuff
    shirt: rain_wet_at_right_shoulder
    shoe: mud_on_left_toe
  caused_by: E007_S09 falls into wet ground at the warehouse side door
  persists_until: E008_SC02 change event

Every state needs a beginning and an end. Cleaning or changing in the next scene requires a visible or plausible interface in time.

19.5 Hair and makeup have a timeline too#

Record parting, length, curl, tie, loose strands, wetness and occlusion. Do not write only "collarbone-length straight hair." Eye makeup after crying, wet hair after rain and night-time fatigue all need states.

Makeup changes should match elapsed time. A character who has just been crying should not have perfect eye makeup in the next shot without a touch-up event. AI tends to beautify automatically, so negative constraints must preserve fatigue and slight imperfection.

19.6 The injury state machine#

An injury records body location, which side, shape, color, severity, how it is covered, and its stage of healing.

injury:
  id: INJ_LINYUN_RIGHT_PALM
  caused_at: E007_S15
  location: right palm, near the base of the thumb
  stage:
    fresh: E007_S15-E008_S04
    bandaged: E008_S05-E012
    healing: E013-E018
  visibility_rules:
    - must appear whenever the palm faces camera
    - a glove may conceal it, but the state persists
  forbidden: [moving to the left hand, vanishing the following day]

Injuries affect action. After a right hand is hurt, raising a document, shaking hands and typing all change. It cannot be treated as a visual sticker.

19.7 Jewellery and carried objects are relationship state#

Rings, necklaces, glasses, pens and phones frequently carry plot. Record who owns them, which side they are worn on, when they change hands, and whether they are concealed.

The old pen is both a styling anchor and an evidence asset. After the storage card is found in E009, its physical state changes; later shots cannot go on showing the unopened version.

19.8 Changing clothes is a continuity node#

A change of costume needs time and a reason: a day has passed, a trip home, an event's dress code, damaged clothing, or the character deliberately changing identity. The change need not be filmed, but the episode ledger must record when it happened.

If E001–E003 all take place on the same afternoon, Lin Yun must not change outfits each episode for visual variety. A stable look also reduces the generation burden and strengthens the memory of the phase.

19.9 The styling reference pack#

For each approved costume, produce front, side, back, seated, arms raised, jacket open and closed, and key lighting versions. A single frontal image cannot specify the back, the cuffs or the lower half.

Important states such as wet clothing, damage and blood get static state references first. Do not let a video model invent the location of damage during movement.

19.10 Color and material shift under different light#

A black suit can lose all separation in low light; ivory can go yellow under warm light. Test costumes under the approved location lighting and record the acceptable range. Material reflectance affects style — glossy silk can produce different highlights in every shot.

Describe costume color against a swatch or reference image, not only with words like charcoal or champagne.

19.11 Propagating look state#

When an injury, stain or accessory changes, the system finds every subsequent shot up to the ending event. Propagation must not depend on the writer's memory.

A shot's generation context loads only the currently effective base costume and its overlays. Older states remain in the history and must not enter the prompt.

19.12 SOP for wardrobe and state#

First, define a small number of wardrobe phases along the character arc. Second, build complete pieces and materials for each. Third, generate multi-angle references. Fourth, test under location lighting. Fifth, establish hair, makeup, injury, stain and accessory states. Sixth, define cause, start, end and effect on action for each state. Seventh, record change and cleaning events. Eighth, propagate automatically to later shots and spot-check by hand.

19.13 Fault tree#

Symptom: the face is consistent and the clothes change every shot. The costume has only a color description, with no cut, pieces or multi-angle reference.

Symptom: the wound switches sides or disappears. Location, start/end and propagation rules are missing. Build an injury ID and state machine.

Symptom: the character becomes immaculate the moment she cries. Model beautification is overriding story state. Add post-crying hair and makeup references and negative constraints.

Symptom: a costume change damages the character. The styling chased a visual upgrade without retaining the identity anchors. Connect phase changes to the character arc.

Symptom: later action ignores the injury. The wound is only an image sticker with no effect on action. Write the restriction into the performance context.

19.14 Checklist, exercises and deliverables#

Check that costumes have stable IDs; that pieces and materials are explicit; that phase changes have story reasons; that states have a start, an end and a cause; that injuries affect action; that jewellery handoffs are recorded; that location lighting was tested; and that nothing changes costume inside one continuous stretch of time.

Exercise one: expand "black suit" into a generatable asset card. Exercise two: build wetness and stain states for a rescue in the rain. Exercise three: write a ten-episode state and action-impact record for a right-hand injury. Exercise four: delete one costume change with no narrative function and calculate the assets saved.

Deliverables for this chapter: the wardrobe registry, the multi-angle costume pack, the phase chart, wardrobe states, hair and makeup states, the injury ledger, the accessory handoff table, and the costume change event table.

19.15 Compose base looks and overlays in layers#

A grey suit is a base asset. Opened buttons, a soaked right shoulder, dusty cuffs and blood on the chest are overlay states. Do not define a fresh costume for every combination, or asset count grows exponentially and you can no longer tell whether a change came from a costume change or from a story event. Compile the generation context as base look plus current overlays plus body state.

Figure 19-1 The asset library does not duplicate a character for wet, muddy and bandaged variants. It layers the base look, environmental overlays and body state, and visibility rules compile only what this shot can actually see. Approved states continue propagating into later shots.

The same state is visible to different degrees at different shot sizes: a close-up on hands must show the bandage wrapping precisely, while a distant rear wide needs only the silhouette of wet clothing. Not visible does not mean ended. Shot context is therefore a projection of the state ledger, not a second, independent set of facts.

Overlays have an order. Rain changes hair and fabric tone first; a fall then adds mud; removing the jacket removes the jacket's wet marks while the shirt's state persists; only a cleaning event ends a stain. The system needs conflict rules: blood on a shirt being hidden by a closed jacket does not delete it, and a wound covered by a bandage keeps healing underneath.

look_context:
  base: WD_LINYUN_GREY_SUIT@v04
  overlays:
    - wet_right_shoulder_40_percent
    - mud_left_cuff_light
  body_state:
    injury_right_palm: bandaged_day_2
  visibility:
    shirt_front: partly_occluded_by_jacket
  ends_only_on: [change_event, cleaning_event, healing_event]

19.16 The look matrix and batch checking#

Generate a look matrix by episode, scene and character, with time along one axis and wardrobe, hair, makeup, injuries, stains and carried objects along the other. Discontinuities inside a continuous stretch show up as color immediately; changes across days get checked for a change, cleaning or treatment event. The matrix finds season-scale problems far more easily than reading prompts shot by shot.

Key states also deserve contact sheets: the four nodes of a wound appearing, worsening, scabbing and recovering side by side; wet hair drying gradually from exterior to interior; makeup moving from intact to tear-streaked. The reviewer is not demanding that each cell look copy-pasted — they are judging whether the direction, speed and position of the change are plausible.

Locking the look matrix for the first ten episodes before batch generation lets you compute which asset combinations you genuinely need. A banquet gown appearing for three seconds that changes no relationship may not justify a full multi-angle asset set. A suit running across eight episodes justifies investment in seated, rear and special-lighting tests.

19.17 Impact analysis for styling changes#

A client asking to make Lin Yun's suit red affects the character color arc, her differentiation from Lin Wei, contrast against the boardroom background, skin reflectance, existing keyframes, video, posters and acquisition creatives. A change request must list dependencies and rework cost first; recoloring one image locally and declaring the season done is not a change.

Small changes can also become identity risks. Changing a fringe affects forehead and face-shape recognition. Swapping earrings can destroy a feature used to distinguish characters. A different heel height changes relative heights in group shots. The styling owner assesses narrative, identity, spatial and generation impact, then decides from which episode the new version takes effect.

Old versions are not overwritten; they enter a retired state. Published episodes keep referencing the historical version and new shots reference the new one. If a version boundary falls inside one scene with no costume change in the story, the system should block it rather than explaining a continuity error as a style upgrade.

A note on sources#

Character consistency tutorials usually concentrate on the face and a fixed costume. This chapter splits wardrobe into base assets and time state, so that rain, wounds, stains and story phases can be inherited by the system instead of being redescribed in every shot.