{
  "sessionId": "cmud566df000emviiz7ttpktm",
  "slug": "generate-then-control",
  "slides": [
    {
      "order": 1,
      "title": "Opening example — the Tidebreak sea‑dragon",
      "bullets": [
        "Concrete asset: turquoise/blue dragon head with gold frame and jewels",
        "Settled image + animation atlas served from the public package",
        "Responsibility: generation supplied look; controlled tools delivered media"
      ],
      "imageUrl": null,
      "altText": "Introduces the Tidebreak sea-dragon wild symbol: a turquoise and blue dragon head framed in gold with jeweled ornament and a bright eye. Notes that both a settled image and an animation atlas are served from the public Tidebreak game package. States that generation proposed the appearance while controlled production supplied the delivered media.",
      "targetSeconds": 45,
      "script": "I'll start with the concrete example we'll follow: Tidebreak's rebuilt sea‑dragon wild symbol — a turquoise and blue dragon head, framed in gold with jeweled ornament and a bright eye. Both its settled image and an animation atlas were served from the game's public package and we inspected those hosted files to confirm they match the production outputs. In production terms, generation proposed the look; controlled tools delivered the media that the game consumes.",
      "sourceReferences": [
        "55a6f660-294a-4edf-a9a8-9c291ab89b79",
        "909e0b53-17af-4922-9450-de745bc6bf97",
        "56850297-b289-4d2d-a321-4d83e1804aab"
      ]
    },
    {
      "order": 2,
      "title": "What the generative half produced",
      "bullets": [
        "Generation supplied the painted master with ornament and color",
        "It produced a candidate image, not a finished delivery asset",
        "Responsibility: visual richness and design proposals"
      ],
      "imageUrl": null,
      "altText": "Explains that the generative half produced a painted master image carrying decorative detail, turquoise scales, blue jewels and gold framing. Emphasizes that this was a candidate illustration to explore appearance, not the final delivered asset.",
      "targetSeconds": 50,
      "script": "The generative half supplied the painted master: a detailed illustration carrying ornament, jewels, color choices, and a transparent surround — in other words, a candidate image rather than a finished delivery asset. Generation gave us the visual richness and the proposal that we would carry into the pipeline, not the final packaged media.",
      "sourceReferences": [
        "56850297-b289-4d2d-a321-4d83e1804aab",
        "a1bc00bb-a883-450d-af79-bb3901ee21f4"
      ]
    },
    {
      "order": 3,
      "title": "Why the painted master is not a full‑round sculpt",
      "bullets": [
        "The painting carries surface richness but not unseen anatomy",
        "It was intended as relief art, not an all-around creature model",
        "Responsibility: generation supplies face; controlled tools supply depth"
      ],
      "imageUrl": null,
      "altText": "Clarifies the distinction between a painted relief source and a full-round sculpt. Notes the painted master did not need to invent the dragon's unseen back or full anatomy because the intended delivery was a relief emblem.",
      "targetSeconds": 40,
      "script": "That painted master is not a full‑round sculpt. The image contains surface richness but did not need to invent an unseen back or full anatomy because the intended delivery was a relief emblem, not a freely viewable creature model. Treating the painting as relief art keeps expectations aligned when we move into modeling and rendering.",
      "sourceReferences": [
        "70b54bdb-bdd5-4220-b9a6-0b4ea70b0f2d",
        "56850297-b289-4d2d-a321-4d83e1804aab",
        "6de3baeb-9453-45de-8307-a9f6851bb319"
      ]
    },
    {
      "order": 4,
      "title": "Into the deterministic tool — Blender relief rendering",
      "bullets": [
        "Blender produced a textured solid relief with backing and depth",
        "Scene authored with cameras, lights, and repeatable motion",
        "Responsibility: deterministic tool supplies geometry and frames"
      ],
      "imageUrl": null,
      "altText": "Describes how the painted image became a textured solid relief in Blender, with a backing, visible depth, controlled orientation, and moving illumination. Emphasizes a repeatable relationship among emblem, camera, and lights to produce frames.",
      "targetSeconds": 60,
      "script": "We then moved into a deterministic tool: Blender rendered the painting as a textured solid relief with a backing and visible depth, and the scene included cameras, lights, and authored motion to produce repeatable frames. That controlled scene is what produced the animation frames, not a sequence of newly generated pictures.",
      "sourceReferences": [
        "a26a9e33-dfdc-49fa-b67d-0c02dce3e7ca",
        "06495c6a-2e04-4222-847b-2fa8f13d7be0",
        "21c01cdd-a4ce-42bf-ae95-ced92484bfbc",
        "bcb7a3d6-0b6e-42b4-a843-d5ee8ac87625",
        "909e0b53-17af-4922-9450-de745bc6bf97"
      ]
    },
    {
      "order": 5,
      "title": "What the deterministic half guarantees and what it cannot",
      "bullets": [
        "Guarantees: explicit geometry, materials, cameras, lights, frames",
        "Testable outputs: dimensions, transparency, animation frames",
        "Cannot guarantee subjective qualities like 'feels substantial'"
      ],
      "imageUrl": null,
      "altText": "Lists objective guarantees of the controlled toolchain—geometry, materials, cameras, lights, and authored motion—and testable outputs such as dimensions and transparency survival. Notes subjective qualities like perceived substance require human inspection.",
      "targetSeconds": 55,
      "script": "What the deterministic half guarantees are explicit, testable things: geometry, materials, cameras, lights, and authored frames that can be checked for presence, dimensions, transparency, and frame content. What it cannot guarantee are subjective qualities like whether the symbol \"feels substantial\" — those still require human review and taste judgments.",
      "sourceReferences": [
        "bcb7a3d6-0b6e-42b4-a843-d5ee8ac87625",
        "6de3baeb-9453-45de-8307-a9f6851bb319",
        "c935645b-e544-44f5-ba9b-2ba151b20878"
      ]
    },
    {
      "order": 6,
      "title": "Why we drive Blender rather than only using it interactively",
      "bullets": [
        "Driving automates repeatable scene construction and exports",
        "It keeps set-wide consistency and makes revisions tractable",
        "Responsibility: controlled production enforces repeatable specs"
      ],
      "imageUrl": null,
      "altText": "Explains the difference between driving Blender (repeatable scene construction and rendering) and using it interactively. States that driving preserves consistency across related assets and makes revisions easier while still requiring human direction for taste.",
      "targetSeconds": 50,
      "script": "We drive Blender rather than only using it interactively because automation produces consistent scene construction across many related assets and makes revisions tractable; both manual and driven workflows can produce excellent results, but driving enforces repeatability for a set. The recorded scenes and saved Blender files separate production representation from delivery so we can regenerate outputs without treating a single exported image as the sole source.",
      "sourceReferences": [
        "c3286bed-45f4-4a80-96e9-b6260b5212c0",
        "b3ea1d44-5cf9-494d-a954-edbb2da91e80",
        "e4264fc9-3bd0-4240-ad92-c6d1c890921c"
      ]
    },
    {
      "order": 7,
      "title": "Costs and limits of automation",
      "bullets": [
        "Setup cost: building repeatable scene processes",
        "Brittleness: changed inputs or tools can break assumptions",
        "False confidence: automation doesn't replace review"
      ],
      "imageUrl": null,
      "altText": "Covers the costs of automation: initial setup effort, brittleness to changed sources or tool behavior, and the danger of false confidence where automation repeats a bad choice. Notes repeatable instructions don't promise identical bytes everywhere.",
      "targetSeconds": 55,
      "script": "Automation carries costs and limits: setup effort to express cameras, materials, and motion; brittleness when inputs or tools change; and false confidence if you assume automation replaces review. Repeatable instructions also do not promise identical output bytes across every renderer, hardware, or software revision.",
      "sourceReferences": [
        "b9949217-0026-428e-bac1-4458f5d4f4d0",
        "d2ea2353-f7c9-4bda-8ec1-373c13a1d2f0",
        "d64cf90c-f047-48c6-8fa0-0bb7374ca05b",
        "06495c6a-2e04-4222-847b-2fa8f13d7be0"
      ]
    },
    {
      "order": 8,
      "title": "When generation fails the properties we must control",
      "bullets": [
        "Failure modes: detail without hierarchy reduces readability",
        "Identity drift across frames breaks symbol continuity",
        "Responsibility: control properties that would break identity"
      ],
      "imageUrl": null,
      "altText": "Identifies recurring generation failures: excessive detail without hierarchy that harms readability at working size, identity drift during motion, and confusing candidate images for finished assets. Emphasizes assigning control to properties that would break identity or readability.",
      "targetSeconds": 55,
      "script": "Generation can fail the properties we must control. Common failures include excessive detail without visual hierarchy that reduces readability at working size, and identity drift across frames that breaks symbol continuity. Those failures motivate taking identity, readability, and timing under explicit control rather than leaving them to unconstrained generation.",
      "sourceReferences": [
        "6de3baeb-9453-45de-8307-a9f6851bb319",
        "bcb7a3d6-0b6e-42b4-a843-d5ee8ac87625",
        "d741a87f-ced8-4cb1-876e-ba44ffbbcc20",
        "a26a9e33-dfdc-49fa-b67d-0c02dce3e7ca"
      ]
    },
    {
      "order": 9,
      "title": "The handoff rule — how we decide the split",
      "bullets": [
        "Rule: generation proposes appearance; control risky properties",
        "Control when failure would break identity, timing, or integration",
        "Responsibility split is an explicit engineering decision"
      ],
      "imageUrl": null,
      "altText": "States the session's rule: let generation propose appearance, and give explicit control to any property whose failure would break identity, readability, timing, or integration. Notes this is an engineering decision and independent of where computation runs.",
      "targetSeconds": 50,
      "script": "Here's the simple handoff rule we use: let generation propose appearance; give explicit control to any property whose failure would break identity, readability, timing, or integration. This is an engineering decision about responsibility and verification, not a statement that generation can never meet a constraint.",
      "sourceReferences": [
        "a26a9e33-dfdc-49fa-b67d-0c02dce3e7ca",
        "56850297-b289-4d2d-a321-4d83e1804aab",
        "d64cf90c-f047-48c6-8fa0-0bb7374ca05b"
      ]
    },
    {
      "order": 10,
      "title": "Practical pairing: settled image and animation atlas",
      "bullets": [
        "Produce settled image and frames from the same authored scene",
        "Keeps opening pose and motion visually related on delivery",
        "Responsibility: controlled renders produce both media formats"
      ],
      "imageUrl": null,
      "altText": "Explains the practical benefit of producing a settled still and an animation atlas from the same authored scene so the opening pose and motion remain visually related. Notes the shipped deliverable is WebP media produced from Blender renders.",
      "targetSeconds": 40,
      "script": "Practically, we produce a settled image and the animation atlas from the same authored scene so the opening pose and the motion frames remain visually related; that avoids a visual jump between still and motion assets. For Tidebreak, the frames are actual Blender renders and the settled image is drawn from the same opening pose.",
      "sourceReferences": [
        "21c01cdd-a4ce-42bf-ae95-ced92484bfbc",
        "a26a9e33-dfdc-49fa-b67d-0c02dce3e7ca",
        "909e0b53-17af-4922-9450-de745bc6bf97",
        "bcb7a3d6-0b6e-42b4-a843-d5ee8ac87625",
        "06495c6a-2e04-4222-847b-2fa8f13d7be0"
      ]
    },
    {
      "order": 11,
      "title": "When to regenerate vs fix downstream",
      "bullets": [
        "Fix downstream when design is sound but technical change needed",
        "Regenerate when silhouette, identity, or composition is wrong",
        "Decisions are reviewed, not automatic"
      ],
      "imageUrl": null,
      "altText": "Describes when production should fix downstream versus regenerate. If framing, format, or continuity are the issues, downstream fixes are appropriate. If the asset's silhouette or identity is wrong, regeneration or a new candidate is needed. Emphasizes human review.",
      "targetSeconds": 40,
      "script": "When should we regenerate versus fixing downstream? We fix downstream when the design is sound and only technical or framing changes are needed. We regenerate when the asset's silhouette, identity, or composition is wrong — that decision is reviewed, not automatic.",
      "sourceReferences": [
        "e4264fc9-3bd0-4240-ad92-c6d1c890921c",
        "06495c6a-2e04-4222-847b-2fa8f13d7be0",
        "6de3baeb-9453-45de-8307-a9f6851bb319"
      ]
    },
    {
      "order": 12,
      "title": "Closing takeaway — hybrid split as an engineering decision",
      "bullets": [
        "Hybrid split defines which properties must be guaranteed",
        "Tooling choices are separate from where computation runs",
        "Verify at delivery; automation eases repeatability, not taste"
      ],
      "imageUrl": null,
      "altText": "Summarizes the core message: the hybrid split is an engineering decision about which properties to guarantee in delivery, not a technology loyalty. Notes that the handoff is independent of execution location and that verification at the point that matters is required.",
      "targetSeconds": 55,
      "script": "To close: the hybrid split is an explicit engineering decision about which properties must be guaranteed at delivery, not a compromise between technologies. Tooling choices are independent of where computation runs, and verification must happen at the point that matters — the delivered media and the running game. Automation eases repeatability; it does not replace review or taste.",
      "sourceReferences": [
        "56850297-b289-4d2d-a321-4d83e1804aab",
        "d64cf90c-f047-48c6-8fa0-0bb7374ca05b",
        "c935645b-e544-44f5-ba9b-2ba151b20878",
        "a26a9e33-dfdc-49fa-b67d-0c02dce3e7ca",
        "bcb7a3d6-0b6e-42b4-a843-d5ee8ac87625",
        "b9949217-0026-428e-bac1-4458f5d4f4d0"
      ]
    }
  ]
}