Interview Bank

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

D2 The Script Agent: Turning a Single Sentence Into Structured Data — Character Cards, Scenes, and Shots

• To keep character definitions consistent across many episodes, where do you store that state and how do you use it?多集内容要保持人物设定一致，你会把这份设定放在哪、怎么用？

  Common in ChinaCommon overseasIntermediate#state-management#consistency

  How to reason about it · think before answering

  1. The crux is that models have no memory. Answering just concatenate previous episodes into the context invites a fatal follow-up: context grows linearly with episode count, so by episode five you pay repeatedly for four full episodes, and the model may still miss details.
  2. Break it down by separating what is invariant across episodes from what is recomputed each time. Invariant: the world, each character's appearance, personality, voice id, and a few hard rules. Recomputed: scenes and shots. Extract the invariant part into its own file and load it verbatim before generating each episode.
  3. Add the commonly missed point: the fields in that file are not only lore, they are downstream input parameters. Appearance text goes straight into image prompts, the voice id goes straight into the speech API. Keeping them beside the name means consistency is solved in one file rather than restated in three places.
  4. Choose the storage boundary by write frequency: the profile is written once and read many times, while the shot list is rewritten on every run. Mixing lifetimes in one file makes it impossible to rerun one episode without disturbing the others.
  5. Conclusion and cost: the profile itself can drift. Change a character's appearance mid-season and previously generated assets no longer match, so version the profile and include that version in the asset cache key — editing the profile then invalidates exactly the affected assets. That is only possible because it lives on its own.
  6. Likely follow-up: should you use a vector store? Usually not. Cross-episode canon is small, structured, and must be injected in full; retrieval risks dropping the one line that matters. Retrieval fits large corpora where only a few relevant items are needed.

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

  1. 这题的题眼是「模型没有记忆」。答成「把前一集的输出拼进上下文」的人会被追问到崩——上下文会随集数线性膨胀，第五集时你在为前四集的全文反复付费，而且模型仍然可能漏读。
  2. 怎么拆：先分辨哪些是「跨集不变」的，哪些是「每集重算」的。不变的是世界观、人物外貌、性格、音色与几条硬规则；每集重算的是场景与分镜。把不变的那部分抽成单独的档案文件，每一集生成前原样读进去。
  3. 接着说一个容易被忽略的点：档案里的字段不只是设定，还是**下游的输入参数**。外貌描述要原样进图像提示词，音色 id 要原样进语音接口。所以它们必须和名字放在同一份档案里，一致性问题才是在一个文件里解决的，而不是散在三处各写一遍。
  4. 存放位置的判据是写入频率：档案一次生成、多次读取，分镜每跑一次就重写。生命周期不同的数据放同一个文件，你就没法只重跑一集而不动其他集。按写入频率切分文件，是这类流水线最省事的一条习惯。
  5. 结论与代价：档案本身也会漂——中途改了人物外貌，之前生成的资产就对不上了。所以档案要有版本，且资产的缓存键要包含档案版本，改档案等于让相关资产失效。这条也是把它单独存放才做得到的。
  6. 可预期的追问：那要不要上向量库做检索？多数情况下不需要。跨集共享的设定是**有限的、结构化的、必须全量注入的**，检索反而可能漏掉关键一条。检索适合的是「素材库很大且只需要相关几条」的场景。

  Key points

  • Models are stateless; cross-episode consistency comes from an external profile, not from stuffing prior episodes into context
  • Split by invariant versus recomputed: world and character profiles persist, scenes and shots are regenerated per episode
  • Appearance text and voice id are downstream input parameters, so they belong beside the character's name
  • Split files by write frequency — a read-mostly profile versus a rewritten shot list — or you cannot rerun one episode alone
  • Version the profile and fold that version into the asset cache key so edits invalidate exactly the affected assets

  答题要点

  • 模型没有记忆，跨集一致性靠外部档案而不是把前几集拼进上下文
  • 按「跨集不变」与「每集重算」切分：世界观与人物卡是档案，场景与分镜每集重来
  • 档案里的外貌与音色 id 同时是下游的输入参数，所以必须和名字放在一起
  • 按写入频率切分文件，档案读多写少，分镜每次重写，混在一起就没法只重跑一集
  • 档案要有版本并进资产缓存键，改设定才能精确地让相关资产失效

D14 A Five-Episode Season: Batch Production, Portfolio Packaging, and a Short-Drama Pipeline Interview Deep Dive

• How do you keep characters and visual style consistent across many generated episodes, and what breaks at a hundred episodes?多集连续生成时，人物与画风的跨集一致性你是怎么保证的？如果要做一百集会遇到什么新问题？

  Common in ChinaCommon overseasIntermediate#consistency#prompt-assembly

  How to reason about it · think before answering

  1. The discriminator is whether you rely on discipline or on structure. Writing the prompt the same way every time drifts by episode five, because every copy is another chance for a human edit.
  2. The right shape makes inconsistency structurally impossible: keep one archive (character cards with appearance and voice id, style tokens, scene list) and enforce one rule, that every shot's prompt is assembled from the archive plus that shot's description, never hand-written.
  3. Then turn the rule into decidable checks: are all characters in the archive, did any voice id change across episodes, is the appearance fragment verbatim from the archive, does every shot carry the style tokens, and does each episode's hook match the next one's pick-up. These five inspect inputs only; picture quality belongs to the automated review pass, and the two are complementary.
  4. At a hundred episodes three new problems appear. First the archive itself evolves as characters restyle and new ones appear, so it needs versions and each episode must record which version it used, or you cannot explain why episode thirty differs from episode ten.
  5. Second, the hook chain gets long and manual maintenance fails, so hook validation has to be a hard gate before the run starts. Third, the asset library bloats, so reference sheets need an index and deduplication or one character accumulates dozens of contradictory base images.
  6. Expect the follow-up: does consistency fight variety? Separate the layers. The archive locks identity traits such as appearance, voice and style, while randomness lives in camera movement, framing and lighting. Locking the wrong layer gives you a hundred identical episodes.

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

  1. 这题的区分度在于你是靠自律还是靠结构。答「每次都把提示词写得一样」的人做到第五集就会漂，因为每复制一次提示词就多一次人为改动的机会。
  2. 正确形态是把一致性变成结构上做不到不一致：建一份唯一的档案（人物卡含外貌与音色、风格词、场景表），再立一条硬规矩——每一镜的提示词只能由「档案加本镜描述」拼出来，不允许手写。
  3. 然后把这条规矩做成可判定的检查：角色是不是都在档案里、音色跨集有没有变、外貌片段是不是逐字来自档案、风格词每一镜有没有带上、集间钩子有没有首尾相接。注意这五条只看输入不看画面——画面质量是机器审片的职责，两道检查互补，谁也替代不了谁。
  4. 一百集会冒出三类新问题。第一是档案本身会演化：人物换了造型、加了新角色，需要给档案做版本，并记录每一集用的是哪个版本，否则回头没法解释第三十集为什么和第十集不一样。
  5. 第二是钩子链变长之后容易断，人工维护五条还行、维护九十九条一定出错，得让钩子校验成为开跑前的硬闸门。第三是资产库膨胀，定妆图与参考图要有索引与去重，否则同一个角色会攒出几十张互相矛盾的基准图。
  6. 可预期的追问是「一致性和多样性冲突吗」。答案是把两者分开：档案锁死的是身份特征（外貌、音色、风格），随机性留给运镜、构图与光线——锁错层就会得到一百集一模一样的片子。

  Key points

  • Rely on structure: one archive plus a rule that prompts may only be assembled from it
  • Five decidable input-only checks: cast membership, voice stability, verbatim appearance, style tokens, hook chain
  • Input checks complement automated picture review; neither replaces the other
  • At scale add archive versioning, a hard pre-run hook gate, and an indexed deduplicated asset library
  • Lock identity traits in the archive and leave randomness to camera, framing and lighting

  答题要点

  • 靠结构不靠自律：唯一档案加一条硬规矩，提示词只能从档案拼出来
  • 五条只看输入的可判定检查：角色、音色、外貌逐字、风格词、集间钩子
  • 输入检查与机器审片互补，一个查有没有漂，一个查画面好不好
  • 上百集会新增三类问题：档案要版本化、钩子校验要变成硬闸门、资产库要索引去重
  • 档案锁身份特征，随机性留给运镜构图光线，锁错层会一百集雷同