Interview Bank

Build an AI Short-Drama Production Pipeline With Agents in 14 Days

D3 Character Consistency: Character Sheets, Reference Images, and Style Locking — Keeping the Same Person the Same Person in Every Shot

• Where does the character consistency problem in image generation come from, and what engineering mitigations exist, with what trade-offs?生成模型的角色一致性问题是怎么来的？工程上有哪几种缓解手段，代价分别是什么？

  Common in ChinaCommon overseasBasic#image-generation#consistency

  How to reason about it · think before answering

  1. The differentiator is your first sentence. Saying 'the prompt wasn't detailed enough' reads as a user, not an engineer; the answer they want is that each request is an independent sample with no memory across calls.
  2. Follow the mechanism: a prompt only constrains the degrees of freedom you actually wrote down, and everything unwritten gets re-sampled — while face recognizability lives exactly in the details text cannot exhaust.
  3. Present the mitigations in three layers by what each one actually locks: a prompt template locks style and framing at near-zero cost; a fixed seed locks reproducibility for one identical prompt and stops helping the moment the prompt changes; a reference image locks the face, but only one per request, so two faces in one frame cannot both be locked.
  4. The trade-off discussion is where candidates separate: using a reference image means you must first produce a base image, which forces a human 'pick the reference sheet' step into an otherwise unattended pipeline.
  5. Volunteer the counter-intuitive rule: every derived image must reference the same base image, never the previous one. Chaining references accumulates drift, and by the fifth image it is a different person.
  6. Expect the follow-up: what if consistency still fails? The answer is cinematography — split two-character frames into reverse-angle singles and push secondary characters to wider shots, working around the API's limits with shot design.

  分析过程 · 先想清楚再作答

  1. 这题的区分度在第一句。答「提示词写得不够细」就掉到了使用者视角；面试官想听的是「模型每次请求都是独立采样、没有跨请求记忆」这个机制层面的原因。
  2. 顺着机制往下推就有了完整答案：提示词只约束了你写出来的那些自由度，没写的部分每次重新掷一遍；而人脸的辨识度恰好集中在脸型、眼距、鼻梁这些你没法用文字穷尽的细节上。
  3. 手段按「锁得住什么」分三层说，不要混在一起：提示词模板锁风格与构图，成本几乎为零；随机种子锁同一提示词的可复现性，换提示词即失效；参考图锁人脸，但每次请求只能带一张，双人同框锁不了两个人。
  4. 代价这一段才是拉开差距的地方：参考图要求你先有一张基准图，于是流程里必须插入一次「定妆并由人挑一张」的环节，这是整条自动化流水线上少数值得保留的人工卡点。
  5. 还要主动说一个反直觉的做法：派生图必须都参考同一张基准图，不能参考上一张。参考上一张会让偏差逐张累积，第五张已经不是同一个人了。
  6. 可以预期的追问：一致性做不到怎么兜底？答案是改镜头语言——把双人同框拆成正反打的单人镜头、次要角色用更远的景别，用拍法回避接口能力的边界。

  Key points

  • The root cause is that each request is an independent sample with no cross-request memory, so unconstrained degrees of freedom get re-rolled
  • A prompt template locks style and framing at near-zero cost but cannot lock facial detail
  • A fixed seed locks reproducibility for one identical prompt and stops helping once the prompt changes
  • A reference image locks the face, but you must first produce a base image and only one reference is allowed per request
  • Derive every variant from the same base image rather than chaining off the previous one, or drift accumulates image by image

  答题要点

  • 根因是模型每次请求独立采样、没有跨请求记忆，提示词没约束到的自由度会被重新掷一遍
  • 提示词模板锁风格与构图，成本几乎为零，但锁不住五官
  • 随机种子锁的是同一提示词的可复现性，提示词一变就失效
  • 参考图锁人脸，代价是必须先有基准图，且每次请求只能带一张，双人同框锁不了两个人
  • 派生图统一参考同一张基准图，不要链式参考上一张，否则偏差会逐张累积
• Does fixing the random seed solve character consistency? What does a seed actually lock?固定随机种子能解决角色一致性吗？它到底锁住了什么？

  Common in ChinaCommon overseasIntermediate#image-generation#reproducibility

  How to reason about it · think before answering

  1. This is a yes/no trap dressed as a concept question; answering 'yes' ends it. The hinge is 'what does it actually lock' — they are testing whether you separate reproducibility from consistency.
  2. Define it first: a seed is the random starting point of sampling. With the model, prompt and other parameters unchanged, the same seed returns the same image, so what it locks is reproducibility.
  3. Then explain why that is not enough here: every shot has a different prompt because action, scene and shot size all change. Change the prompt and the sampling path changes with it, so the same seed yields a different person. A seed is a reproducibility switch, not a consistency switch.
  4. Do not dismiss it though. It earns its place twice: single-variable debugging, where you change one word and watch the image move; and stacked with a reference image, where the reference holds the face and the seed holds the remaining degrees of freedom so a whole set looks shot on the same day.
  5. One production note: for a seed to actually reproduce anything, turn the prompt optimizer off. It defaults to on, rewrites your prompt server-side, and you never see the rewrite — which destroys reproducibility.
  6. Expect the follow-up: is seed semantics the same across vendors? No guarantee — switching vendor or even model version can make the same seed produce something else, which is one more reason to keep a provider abstraction layer.

  分析过程 · 先想清楚再作答

  1. 这是一道判断题伪装成的概念题，答「能」直接出局。题眼是「到底锁住了什么」——面试官在测你有没有把复现和一致这两件事分开。
  2. 先给定义：seed 是采样的随机起点。在模型、提示词、其余参数都不变的前提下，同一个 seed 会给出同一张图，所以它锁住的是**可复现性**。
  3. 再说为什么在短剧场景里不够用：每一镜的提示词天然不同，动作、场景、景别都在变。提示词一变，采样路径就换了，同一个 seed 出来的是完全不同的人。所以 seed 是复现开关，不是一致性开关。
  4. 但不要把它说成没用。它在两个地方非常值钱：调试时做单变量对照，只改一个词看画面怎么变；以及跟参考图叠加使用，参考图管脸，seed 管其余自由度的采样起点，两者一起才让整组图像同一天在同一个棚里拍的。
  5. 生产视角补一句：想让 seed 真的可复现，必须把提示词优化开关关掉。那个开关默认是开的，它会在服务端改写你的提示词，改写结果你看不到，可复现性也就没了。
  6. 可以预期的追问：那不同厂商的 seed 语义一样吗？答案是不保证，换厂商甚至换模型版本都可能让同一个 seed 出别的图，所以 seed 不能作为跨厂商的一致性依据——这也是要有一层 provider 抽象的原因之一。

  Key points

  • No. A seed locks reproducibility: same model, same prompt, same other parameters plus same seed returns the same image
  • Every shot in a drama has a different prompt, and a changed prompt voids the seed, so it is not a consistency mechanism
  • Its real value is single-variable debugging, and stacking with a reference image — the reference holds the face, the seed holds the rest
  • For a seed to reproduce anything you must disable the server-side prompt optimizer, which is on by default and rewrites your input
  • Seed semantics do not carry across vendors or model versions, so a seed cannot underpin cross-provider consistency

  答题要点

  • 不能。seed 锁的是可复现性：模型、提示词与其余参数都不变时，同一个 seed 给出同一张图
  • 短剧每一镜的提示词天然不同，提示词一变 seed 就失效，所以它不是一致性手段
  • 它真正的用处是单变量调试，以及与参考图叠加——参考图管脸，seed 管其余自由度的采样起点
  • 要让 seed 可复现，必须关掉服务端的提示词优化开关，它默认开启且会改写你的输入
  • seed 语义不跨厂商也不跨模型版本，不能作为跨 provider 的一致性依据
• How would you design the cache key for reusing generated assets so that you save money without serving the wrong asset?生成类资产要做复用，缓存键你会怎么设计，才能既省钱又不会串戏？

  Common in ChinaCommon overseasDeep dive#caching#cost#image-generation

  How to reason about it · think before answering

  1. This question is about two kinds of cache error with wildly asymmetric cost. A miss only costs money; a wrong hit puts last episode's prop into this one. The first is a number, the second is a content incident.
  2. The derivation is one sentence: the key must be computed from every input that changes the artifact, and nothing else. Include something irrelevant, like the output path, and one directory refactor invalidates everything and you pay again; omit something relevant, like the prompt, and a changed description silently serves the old image.
  3. Concretely, hash the asset kind, the owning entity id, the variant name, the full prompt, the reference image identity and the seed. Take a short digest as the id, and store those fields verbatim in the metadata so any artifact can be reproduced.
  4. Then name the boundaries yourself: does the model id and version belong in the key? Yes. What if the style template changes? It is part of the prompt, so it invalidates everything by construction — which is why templates should carry a version number, letting you choose the blast radius.
  5. One more production note: never cache failed generations, or you will faithfully reuse an empty result that safety review rejected. Cache hits also belong in the cost ledger, flagged as hits, otherwise you cannot report how much caching saved.
  6. Expect the follow-up: should the cache expire? Content assets usually should not expire on time; invalidate explicitly by version instead, because a time-based expiry regenerates a whole episode at the least convenient moment.

  分析过程 · 先想清楚再作答

  1. 这题考的是缓存的两类错误，而且两类的代价完全不对称。少命中只是多花钱，错命中会把上一集的道具塞进这一集——前者可量化，后者是内容事故。
  2. 推导链只有一句：**键必须由所有会改变产物的输入算出来，一项不多一项不少。** 多算了不该算的（比如输出路径），改一次目录结构缓存全部失效，白花一遍钱；少算了该算的（比如提示词），换了描述还命中老图，就是串戏。
  3. 落到这个场景，参与哈希的是：资产类别、归属对象、变体名、完整提示词、参考图标识、随机种子。用 sha1 之类取个短摘要当 id，元数据里再把这几项原样存一份，出问题能照着复现。
  4. 然后主动把边界说清楚，这是加分项：模型 id 与版本要不要进键？要。风格模板改了怎么办？它是提示词的一部分，进键之后天然全部失效——所以模板要谨慎改，或者给它一个版本号，让你能决定失效的范围。
  5. 生产视角还有一条：失败的生成不要写进缓存，否则你会稳定复用一张被审核拦下的空结果。命中缓存的那条路径也要记台账并标成命中，不然你算不出缓存到底省了多少钱。
  6. 可以预期的追问：缓存要不要过期？答案是内容型资产通常不设时间过期，而是靠版本号显式失效；时间过期会在你毫无预期的时候让一整集重新生成一遍。

  Key points

  • Derive the key from everything that changes the artifact: asset kind, owner id, variant, full prompt, reference image identity, seed, plus model id and version
  • Keep output paths and filenames out of the key, or one directory refactor invalidates the whole cache and you pay twice
  • Omitting inputs like the prompt causes wrong hits, which are content incidents and far costlier than misses
  • Store the hashed fields verbatim in metadata so any artifact is reproducible, and never cache failed generations
  • Record cache hits in the cost ledger flagged as hits, and invalidate explicitly by version rather than by time

  答题要点

  • 键由所有会改变产物的输入算出：资产类别、归属对象、变体名、完整提示词、参考图标识、随机种子，再加模型 id 与版本
  • 不要把输出路径或文件名放进键，改目录结构会让缓存整体失效，白付一遍钱
  • 少算提示词这类输入会导致错命中，那是内容事故，代价远高于少命中
  • 元数据里原样保存参与哈希的各项，出问题能复现；失败的生成不写缓存
  • 命中缓存也要记台账并标成命中，否则算不出缓存省了多少；失效靠显式版本号而不是时间过期