{
  "sessionId": "cmudg6m8u000e2yiihrfftgpa",
  "slug": "the-part-everyone-skips",
  "title": "The part everyone skips",
  "text": "I’m going to start bluntly: the part everyone skips is the part that catches what generation misses. Verification checks internal consistency and measured behavior so the build matches its own specification, not because it’s beautiful or legal—because those are different jobs.\n\nWhen we say a build is verified we mean it has been compared to its own spec and the results are stored: mathematics are recomputed, statistics measured, and exportable evidence like a PAR sheet and inputs are retained for later re-checks.\n\nHere’s what the pipeline guarantees on every shipped build: the mathematics are measured, advertised prizes match achievable prizes, the package is complete, and the build is reproducible from stored inputs—all of which are checkable in the package you receive.\n\nGames move through eight stages from Concept to Verification. Verification is the gate that decides whether anything leaves—every check in the checklist runs against the assembled build before handover.\n\nWe recompute every reported number from the finished ticket pool: deck size, payback, hit rate, variance, prize floor and payout integrity. If any of those numbers disagrees with the specification, the build fails.\n\nFor slot presentations we simulate reel strips to confirm return and hit frequency bands, uniform strip length, symbol coverage on every reel, and that the paytable matches symbol values. Fail any of those and the slot presentation is stopped.\n\nEvery file the configuration names must exist and be valid: artwork, animations, audio, ticket pool, and entry points. A missing, corrupt or empty file prevents shipping—the pipeline refuses incomplete packages.\n\nBackgrounds are scanned for painted text and refused if they contain it; logos are read back letter by letter by two vision models and a mismatch causes rejection. We treat model reads as strong evidence, not proof, because models can be wrong.\n\nAn automated browser suite plays the assembled build through the real interface to confirm start, spin, resolution and payouts. If the automated play fails, the build is stopped even if file checks passed.\n\nWe store generated assets with the inputs that produced them so a build can be rebuilt later, and the package itself can produce a PAR sheet for independent test labs—this is exportable material for certification elsewhere, not certification itself.\n\nVerification does not make a game ‘good’, commercially sensible, legally cleared, or artistically flawless. Those are human judgments or legal tasks performed outside the pipeline; verification is about internal consistency and measured behavior.\n\nModel checks have limits: vision models can misread. We treat model passes as strong evidence, not proof, and we rely on human review to catch subtler or adversarial failures models miss.\n\nHumans can intervene at every stage. Editors open on mathematics, images, animation and audio; you can accept or reject assets mid-run, play the assembled preview, and run library-wide fixes. Overrides are recorded and supported—use them liberally; any edited build must be re-verified.\n\nFinally, the concrete refusals to remember: decks outside bands, prizes below floor, payouts that don’t match the pool, art with embedded text, titles that read back wrong, incomplete bonuses, unreproducible builds, and games that won’t play—these are hard stops the pipeline enforces.",
  "segments": [
    {
      "slide": 1,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "I’m going to start bluntly: the part everyone skips is the part that catches what generation misses. Verification checks internal consistency and measured behavior so the build matches its own specification, not because it’s beautiful or legal—because those are different jobs.",
      "citationIds": [
        "8ef2d407-c577-4689-8804-f83bfa42dd5a",
        "ccf1c5a6-bea4-46ad-b1bb-8e029d3d8027",
        "be505943-f55d-4e94-a83c-6d2022be9e1a"
      ]
    },
    {
      "slide": 2,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "When we say a build is verified we mean it has been compared to its own spec and the results are stored: mathematics are recomputed, statistics measured, and exportable evidence like a PAR sheet and inputs are retained for later re-checks.",
      "citationIds": [
        "8ef2d407-c577-4689-8804-f83bfa42dd5a",
        "ec449f94-84de-4b3a-bbd3-02d12018bedb",
        "58640254-6a6c-4ca4-b828-4fe18439dc36"
      ]
    },
    {
      "slide": 3,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "Here’s what the pipeline guarantees on every shipped build: the mathematics are measured, advertised prizes match achievable prizes, the package is complete, and the build is reproducible from stored inputs—all of which are checkable in the package you receive.",
      "citationIds": [
        "f33eaa91-f384-4a2b-a895-66533459f75a",
        "768a2eba-016b-4893-8d88-bfed5596ae42",
        "c1914f2f-651a-4bd9-b085-681277c91d43"
      ]
    },
    {
      "slide": 4,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "Games move through eight stages from Concept to Verification. Verification is the gate that decides whether anything leaves—every check in the checklist runs against the assembled build before handover.",
      "citationIds": [
        "8c902c5c-49cc-4559-af25-107c23a442aa",
        "360ee6a6-6779-452c-a635-f6ab44eb9065"
      ]
    },
    {
      "slide": 5,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "We recompute every reported number from the finished ticket pool: deck size, payback, hit rate, variance, prize floor and payout integrity. If any of those numbers disagrees with the specification, the build fails.",
      "citationIds": [
        "48349d8f-d4c4-4ab1-9557-672500637819",
        "58640254-6a6c-4ca4-b828-4fe18439dc36"
      ]
    },
    {
      "slide": 6,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "For slot presentations we simulate reel strips to confirm return and hit frequency bands, uniform strip length, symbol coverage on every reel, and that the paytable matches symbol values. Fail any of those and the slot presentation is stopped.",
      "citationIds": [
        "58640254-6a6c-4ca4-b828-4fe18439dc36",
        "8c902c5c-49cc-4559-af25-107c23a442aa",
        "ec449f94-84de-4b3a-bbd3-02d12018bedb"
      ]
    },
    {
      "slide": 7,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "Every file the configuration names must exist and be valid: artwork, animations, audio, ticket pool, and entry points. A missing, corrupt or empty file prevents shipping—the pipeline refuses incomplete packages.",
      "citationIds": [
        "768a2eba-016b-4893-8d88-bfed5596ae42",
        "251828eb-86fb-4dcb-a7fa-1330b41a7979"
      ]
    },
    {
      "slide": 8,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "Backgrounds are scanned for painted text and refused if they contain it; logos are read back letter by letter by two vision models and a mismatch causes rejection. We treat model reads as strong evidence, not proof, because models can be wrong.",
      "citationIds": [
        "4534440c-639b-49cf-b062-eba0d3989ce8",
        "592efb48-55d1-477d-86de-a433fe9f073c",
        "c1914f2f-651a-4bd9-b085-681277c91d43"
      ]
    },
    {
      "slide": 9,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "An automated browser suite plays the assembled build through the real interface to confirm start, spin, resolution and payouts. If the automated play fails, the build is stopped even if file checks passed.",
      "citationIds": [
        "768a2eba-016b-4893-8d88-bfed5596ae42",
        "f24da3fc-529c-4ef5-9982-99278380d157",
        "4534440c-639b-49cf-b062-eba0d3989ce8"
      ]
    },
    {
      "slide": 10,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "We store generated assets with the inputs that produced them so a build can be rebuilt later, and the package itself can produce a PAR sheet for independent test labs—this is exportable material for certification elsewhere, not certification itself.",
      "citationIds": [
        "ec449f94-84de-4b3a-bbd3-02d12018bedb",
        "f33eaa91-f384-4a2b-a895-66533459f75a",
        "58640254-6a6c-4ca4-b828-4fe18439dc36"
      ]
    },
    {
      "slide": 11,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "Verification does not make a game ‘good’, commercially sensible, legally cleared, or artistically flawless. Those are human judgments or legal tasks performed outside the pipeline; verification is about internal consistency and measured behavior.",
      "citationIds": [
        "be505943-f55d-4e94-a83c-6d2022be9e1a",
        "ec449f94-84de-4b3a-bbd3-02d12018bedb",
        "8f407659-4861-4e5d-99d3-5f72febf2c1f"
      ]
    },
    {
      "slide": 12,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "Model checks have limits: vision models can misread. We treat model passes as strong evidence, not proof, and we rely on human review to catch subtler or adversarial failures models miss.",
      "citationIds": [
        "c1914f2f-651a-4bd9-b085-681277c91d43",
        "592efb48-55d1-477d-86de-a433fe9f073c",
        "f33eaa91-f384-4a2b-a895-66533459f75a"
      ]
    },
    {
      "slide": 13,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "Humans can intervene at every stage. Editors open on mathematics, images, animation and audio; you can accept or reject assets mid-run, play the assembled preview, and run library-wide fixes. Overrides are recorded and supported—use them liberally; any edited build must be re-verified.",
      "citationIds": [
        "b1b8b2e9-f161-4587-b51d-d1cf0e2fa947",
        "8f407659-4861-4e5d-99d3-5f72febf2c1f",
        "251828eb-86fb-4dcb-a7fa-1330b41a7979",
        "881c4049-d8c8-460e-918b-083af1905d66",
        "e58b5290-eeca-4aee-b0be-25d3ab6fba6d"
      ]
    },
    {
      "slide": 14,
      "speaker": {
        "slug": "jars-pipeline-agent",
        "name": "Sealed Jars Pipeline Agent"
      },
      "text": "Finally, the concrete refusals to remember: decks outside bands, prizes below floor, payouts that don’t match the pool, art with embedded text, titles that read back wrong, incomplete bonuses, unreproducible builds, and games that won’t play—these are hard stops the pipeline enforces.",
      "citationIds": [
        "592efb48-55d1-477d-86de-a433fe9f073c",
        "4534440c-639b-49cf-b062-eba0d3989ce8",
        "f24da3fc-529c-4ef5-9982-99278380d157"
      ]
    }
  ]
}