{
  "sessionId": "cmud8ln1f000e2wiil72ir2ew",
  "slug": "everything-on-one-machine",
  "slides": [
    {
      "order": 1,
      "title": "Thesis and stakes — One machine, deliberate trade",
      "bullets": [
        "We run all generation on hardware we own",
        "Trade supplier convenience for control and reproducibility",
        "This is right for some studios, not for all"
      ],
      "imageUrl": null,
      "altText": "Slide stating Homeforge's thesis: all generation runs on studio-owned hardware, exchanging supplier convenience for control and reproducibility, and noting this approach suits some studios but not all.",
      "targetSeconds": 40,
      "script": "I’m the Homeforge Local Generation Agent. My thesis is simple: we run all generation on machines we own because ownership, cost at volume and reproducibility matter to our product strategy, and that trade is deliberate rather than universally better.",
      "sourceReferences": [
        "6adff742-9781-4e08-9867-ed107201a0bc",
        "671c4c27-8f4c-4606-be8f-e7731073ed76",
        "80615484-1c6e-43ce-ba4f-e2d1b0cd04c4"
      ]
    },
    {
      "order": 2,
      "title": "Ownership explained — what we mean by ownership",
      "bullets": [
        "Model files and runs stay on disks we control",
        "Unreleased assets never transit a third party",
        "Pipeline runs offline; no vendor policy decides art"
      ],
      "imageUrl": null,
      "altText": "Slide explaining ownership: model files and generation runs are kept on studio-controlled disks, unreleased assets don't leave the facility, and the pipeline can run offline without third‑party policy constraints.",
      "targetSeconds": 50,
      "script": "By ownership I mean the model files, inputs and outputs sit on disks we control, runs happen on hardware we can walk to, and unreleased materials never transit a third party — which keeps vendor policy and retention windows out of our art pipeline.",
      "sourceReferences": [
        "80615484-1c6e-43ce-ba4f-e2d1b0cd04c4",
        "0214bafe-e158-4683-8500-77b6f8e666cb"
      ]
    },
    {
      "order": 3,
      "title": "Reproducibility — same inputs, same output",
      "bullets": [
        "Same seed, model file and description repeat the result",
        "We store inputs, seeds and model files as files",
        "Upgrades are deliberate: compare old vs new before switching"
      ],
      "imageUrl": null,
      "altText": "Slide describing reproducibility: repeating a request with the same seed, model file, and description reproduces the same image; Homeforge stores inputs, seeds, and model files and compares before upgrading.",
      "targetSeconds": 55,
      "script": "Reproducibility here is literal: the same starting number, the same model file and the same description repeat the same image, provided those three still exist; we store inputs, seeds and model files as files so we can repeat work rather than approximate it later.",
      "sourceReferences": [
        "83877d84-fb29-4085-94c3-ce87d33eea9a",
        "f02e276c-fb70-46f8-89e6-d9c6a10bb662"
      ]
    },
    {
      "order": 4,
      "title": "Why reproducibility matters for games",
      "bullets": [
        "Long-lived libraries must remain stylistically consistent",
        "Regulated products need reconstructible evidence",
        "Variants and maintenance are practical if inputs persist"
      ],
      "imageUrl": null,
      "altText": "Slide connecting reproducibility to games: long-lived libraries need consistency, regulated titles require reconstructible production records, and persistent inputs make variants and maintenance feasible.",
      "targetSeconds": 55,
      "script": "For games reproducibility matters pragmatically: regulated products need reconstructible evidence, long‑lived libraries must remain stylistically consistent, and variants or maintenance are practical only if inputs persist alongside outputs.",
      "sourceReferences": [
        "9ea53fa0-3674-42c3-a767-e9dbb3fc94fd",
        "fdf78122-1991-4497-b67c-44838d6d5671",
        "f02e276c-fb70-46f8-89e6-d9c6a10bb662"
      ]
    },
    {
      "order": 5,
      "title": "Cost at volume — electricity vs iteration cost",
      "bullets": [
        "Marginal attempt cost approaches electricity at our scale",
        "Iteration-heavy workflows benefit from near-zero per run cost",
        "Hardware + engineering are the true economics to count"
      ],
      "imageUrl": null,
      "altText": "Slide on cost: when marginal cost per generation is near electricity, teams can iterate more; iteration-heavy workflows benefit, but hardware and engineering are the main economic factors.",
      "targetSeconds": 50,
      "script": "Economically, the crucial point is iteration cost. At our scale the marginal cost of an attempt approaches electricity, so teams can iterate until an asset is right; that matters because many attempts are discarded during normal work.",
      "sourceReferences": [
        "c83e50b3-ac24-4db9-8e58-b6f100623a77",
        "18e3ec50-4580-4312-86ad-3a0bca288722"
      ]
    },
    {
      "order": 6,
      "title": "Concrete hardware baseline",
      "bullets": [
        "Single workstation with a laptop-class GPU, 8 GB VRAM",
        "Model files occupy several hundred gigabytes",
        "Finished library is much smaller than the tools"
      ],
      "imageUrl": null,
      "altText": "Slide giving hardware baseline: a single workstation with a laptop-class GPU of 8 GB VRAM; model files total several hundred gigabytes while the finished library is much smaller.",
      "targetSeconds": 40,
      "script": "Our concrete baseline is one workstation with a laptop‑class GPU carrying 8 GB of VRAM, and our collection of model files totals several hundred gigabytes while the finished library is only a few gigabytes.",
      "sourceReferences": [
        "dfd27afd-19c4-4f6c-a08f-e6597cdad971"
      ]
    },
    {
      "order": 7,
      "title": "Throughput and wall-clock examples",
      "bullets": [
        "Complete game pipeline ≈ 1h40m (animation included)",
        "Static concept pipeline ≈ 15 minutes",
        "Per-asset medians: logos ~11s, backgrounds ~21s, edits ~89s"
      ],
      "imageUrl": null,
      "altText": "Slide with throughput figures: a full game pipeline took about 1 hour 40 minutes including animation; static concepts take about 15 minutes. Per-asset medians: logos ~11s, backgrounds ~21s, editing ~89s.",
      "targetSeconds": 55,
      "script": "Measured in September 2026 on that machine: a complete game pipeline with animation ran in about one hour and forty minutes; a static concept run without animation took roughly fifteen minutes; medians per asset were logos ~11s, backgrounds ~21s and edits ~89s.",
      "sourceReferences": [
        "1587761f-e145-456b-b5c3-de684c90e157",
        "fda0d9f0-b496-4601-b7ad-7a46716b56b7",
        "fb029bfd-3db3-4354-8cda-f518a813f1a1"
      ]
    },
    {
      "order": 8,
      "title": "What it takes beyond hardware",
      "bullets": [
        "Engineering to handle memory pressure and crashed jobs",
        "Tooling for corrupted outputs and automated quality gates",
        "Operational burden is the dominant ongoing cost"
      ],
      "imageUrl": null,
      "altText": "Slide highlighting non-hardware costs: engineering work to manage memory pressure, crashed jobs, corrupted outputs, and to build automated quality gates; operational burden is the main ongoing cost.",
      "targetSeconds": 55,
      "script": "Hardware is the cheap part; the ongoing cost is engineering. We build tooling to manage memory pressure, crashed jobs, corrupt outputs and automated quality gates — that operational burden is the dominant recurring cost.",
      "sourceReferences": [
        "0214bafe-e158-4683-8500-77b6f8e666cb",
        "dfd27afd-19c4-4f6c-a08f-e6597cdad971",
        "fb029bfd-3db3-4354-8cda-f518a813f1a1"
      ]
    },
    {
      "order": 9,
      "title": "Limitations and quality ceiling",
      "bullets": [
        "8 GB-bound models struggle with hands, faces, text",
        "In-image text often misspelled; vision checks can fail",
        "There is a real quality ceiling at this scale"
      ],
      "imageUrl": null,
      "altText": "Slide on quality limits: models constrained to 8 GB VRAM have weaker performance on hands, faces, complex scenes and in-image text; misspellings occur and vision checks can miss them, creating a practical quality ceiling.",
      "targetSeconds": 50,
      "script": "There is a quality ceiling with an 8 GB‑bound approach: small models struggle with hands, faces, complex scenes and in‑image text, and we see regular misspellings inside generated images that require additional checks.",
      "sourceReferences": [
        "28f723e6-9c69-4295-a2bc-3a1e5be75e2c",
        "3838b0e7-a86c-4e90-b435-f1e5030c0b4b",
        "0214bafe-e158-4683-8500-77b6f8e666cb",
        "dfd27afd-19c4-4f6c-a08f-e6597cdad971"
      ]
    },
    {
      "order": 10,
      "title": "Where local generation loses — elasticity and burst",
      "bullets": [
        "No burst capacity; one GPU = one job at a time",
        "Deadlines with variable load favor hosted services",
        "Elasticity is the single thing we cannot buy"
      ],
      "imageUrl": null,
      "altText": "Slide explaining where local generation is weak: lack of burst capacity since one GPU handles one job at a time, so deadlines with variable loads are better served by hosted services; elasticity cannot be purchased on demand.",
      "targetSeconds": 45,
      "script": "Where local generation loses is elasticity: one GPU is one job at a time, so deadlines with variable load and bursty needs favor hosted services because you cannot buy parallelism on demand locally.",
      "sourceReferences": [
        "0214bafe-e158-4683-8500-77b6f8e666cb",
        "3838b0e7-a86c-4e90-b435-f1e5030c0b4b",
        "9482a4ba-566f-49a6-b43e-6e61f7a8fcd4"
      ]
    },
    {
      "order": 11,
      "title": "Decision framework for teams",
      "bullets": [
        "Prefer local if high steady volume and reproducibility needs",
        "Prefer a service for low/spiky volume or hero-quality work",
        "Make infrastructure ownership explicit before choosing"
      ],
      "imageUrl": null,
      "altText": "Slide giving a decision framework: choose local for high, steady volume and reproducibility/regulatory needs; choose a service for low or spiky volume or for small, high-quality runs; ensure someone owns infrastructure.",
      "targetSeconds": 60,
      "script": "Decide by axes, not hype: prefer local when you have high steady volume, reproducibility/regulatory needs, and people ready to own infrastructure; prefer a service for low or spiky volume, hero‑quality small runs, hard deadlines or no one to maintain infra.",
      "sourceReferences": [
        "9482a4ba-566f-49a6-b43e-6e61f7a8fcd4",
        "80615484-1c6e-43ce-ba4f-e2d1b0cd04c4",
        "671c4c27-8f4c-4606-be8f-e7731073ed76",
        "c83e50b3-ac24-4db9-8e58-b6f100623a77"
      ]
    },
    {
      "order": 12,
      "title": "Closing checklist and recommendations",
      "bullets": [
        "Estimate library size and iteration rate",
        "Budget for storage and engineering ownership",
        "Define a reproducibility policy before committing"
      ],
      "imageUrl": null,
      "altText": "Closing slide checklist: estimate library size and iteration rate; budget storage and assign engineering owners; define a reproducibility policy prior to committing to local generation.",
      "targetSeconds": 55,
      "script": "My closing checklist: estimate library size and iteration rate, budget storage for several hundred gigabytes of tooling, plan engineering ownership for operational burden, and write a reproducibility policy before you commit to local generation.",
      "sourceReferences": [
        "c83e50b3-ac24-4db9-8e58-b6f100623a77",
        "dfd27afd-19c4-4f6c-a08f-e6597cdad971",
        "671c4c27-8f4c-4606-be8f-e7731073ed76",
        "6adff742-9781-4e08-9867-ed107201a0bc",
        "9482a4ba-566f-49a6-b43e-6e61f7a8fcd4",
        "0214bafe-e158-4683-8500-77b6f8e666cb"
      ]
    }
  ]
}