{
  "sessionId": "cmu6ey9zx0010kkiilcddmcbi",
  "slug": "certifying-generative-games",
  "slides": [
    {
      "order": 1,
      "title": "Fictional ESGC certification workflow (summary)",
      "bullets": [
        "Submit rules, paytable, source or build, and PAR sheet",
        "Independent lab verifies behavior, RNG, and RTP within 0.1%",
        "PLACEHOLDER fictional example used for demonstration"
      ],
      "imageUrl": null,
      "altText": "Slide title: Fictional ESGC certification workflow (summary). Three bullets: 1) Suppliers submit game rules, paytable, source code or compiled build, and a PAR sheet. 2) An independent test laboratory verifies that the game behaves as documented, the random number generator passes statistical tests, and that the theoretical return to player (RTP) in the PAR sheet matches the lab's calculation within a tolerance of 0.1 percentage points. 3) A note that this is a placeholder fictional example for demonstration.",
      "targetSeconds": 60,
      "script": "I will describe a fictional certification workflow used as our worked example. Under this workflow, a supplier submits a game package containing the game rules, the paytable, the source code or compiled build, and a mathematical description called the PAR sheet. An independent test laboratory then verifies the game behaves as documented, that the random number generator passes statistical tests, and that the theoretical return to player in the PAR sheet matches the lab's calculation within 0.1 percentage points. I note up front that this is a placeholder, fictional example prepared for demonstration.",
      "sourceReferences": [
        "0d163b21-78c1-4180-8899-40c7ac4caff8",
        "a263b013-e235-456d-9298-53a22a9f549d"
      ]
    },
    {
      "order": 2,
      "title": "Implicit assumption: logic fixed at submission",
      "bullets": [
        "Any post‑certification change to game logic requires resubmission",
        "Cosmetic artwork may follow a lighter notification process",
        "Explanation: these are the ESGC change‑control assumptions"
      ],
      "imageUrl": null,
      "altText": "Slide title: Implicit assumption: logic fixed at submission. Three bullets: 1) Any post-certification change to game logic requires resubmission. 2) Cosmetic artwork changes may be approved via a lighter notification process if supplier attests no effect on outcomes or paytables. 3) An explanation label stating these are the change-control assumptions under the ESGC model.",
      "targetSeconds": 80,
      "script": "I will state the workflow's change-control assumption. In the ESGC model, any post-certification change to game logic requires resubmission to the laboratory, while purely cosmetic artwork changes may follow a lighter notification process if the supplier attests outcomes and paytables are unaffected. Explanation: these procedures imply the certification process assumes game logic is fixed at submission; that is an interpretive statement about the workflow, not an assertion of regulatory law.",
      "sourceReferences": [
        "34e89f01-28fc-4e84-a5f2-bc990bb6c351"
      ]
    },
    {
      "order": 3,
      "title": "Where generative pipelines conflict with assumptions",
      "bullets": [
        "Generated artwork: cosmetic or outcome‑affecting?",
        "Should we certify a pipeline instead of a single build?",
        "Who is accountable if an autonomous system proposes a paytable?"
      ],
      "imageUrl": null,
      "altText": "Slide title: Where generative pipelines conflict with assumptions. Three bullets: 1) A question whether generated artwork counts as cosmetic or affects outcomes. 2) A question whether certification should cover a generative pipeline rather than a single compiled build. 3) A question who is accountable when an autonomous system proposes a paytable. These are presented as unresolved issues identified by ESGC staff.",
      "targetSeconds": 70,
      "script": "I will identify where generative development conflicts with that fixed-logic assumption. ESGC staff outline three unresolved issues: whether generated artwork should be treated as cosmetic or as outcome-affecting, whether a regulator can certify a development pipeline instead of a single build, and who is accountable when an autonomous system proposes a paytable. Explanation: these are listed by the fictional ESGC as open questions rather than answered requirements.",
      "sourceReferences": [
        "01aea77a-341d-4a08-92d5-8f9db3ffc0ff"
      ]
    },
    {
      "order": 4,
      "title": "Accountability and evidentiary expectations (proposal)",
      "bullets": [
        "A licensed human or entity should remain accountable for certified games",
        "Suppliers using autonomous development should keep audit logs, prompts, versions",
        "Memo does not assert generated mathematics is riskier than human math"
      ],
      "imageUrl": null,
      "altText": "Slide title: Accountability and evidentiary expectations (proposal). Three bullets: 1) The proposal that a licensed human or entity remain accountable for every certified game, and that the supplier name a responsible officer who signs submissions. 2) The expectation that suppliers using autonomous development keep audit logs of agent actions, retain prompts and model versions, and be able to reproduce certified builds from those records. 3) A note that the memo does not take a position that generated game mathematics is inherently riskier than hand-written mathematics.",
      "targetSeconds": 80,
      "script": "I will summarize a proposed accountability position from a fictional memo. The memo proposes that a licensed human or legal entity must remain accountable for every certified game and that the supplier must name a responsible officer who signs the submission. The memo further suggests suppliers using autonomous development retain audit logs of agent actions, preserve prompts and model versions, and keep records sufficient to reproduce any certified build from those artifacts. I note the memo explicitly does not assert that generated mathematics is inherently riskier than hand-written mathematics; it records no cited study supporting either claim. Explanation: these are the memo's proposed evidentiary expectations and stated limits, not regulatory determinations by an actual authority.",
      "sourceReferences": [
        "399b59c3-0b68-4c5f-a280-ab8be5873173",
        "65227732-f94a-472d-8ed8-e513b57a69aa",
        "9d6d749b-c0c4-4f47-bf2c-31516b988a9c"
      ]
    },
    {
      "order": 5,
      "title": "Unresolved questions to take away",
      "bullets": [
        "Treatment of generated content (artwork vs outcome)",
        "Certify pipelines vs certify single builds",
        "Assignment of accountability for autonomous outputs"
      ],
      "imageUrl": null,
      "altText": "Slide title: Unresolved questions to take away. Three bullets listing open questions: 1) How to treat generated content — is generated artwork purely cosmetic or outcome-affecting? 2) Whether regulators should certify an entire generative pipeline rather than a single build. 3) How accountability is assigned when outputs originate from autonomous systems. A final note that these are identified as unresolved in the ESGC example rather than answered.",
      "targetSeconds": 70,
      "script": "I will close with the unresolved questions to take away. The fictional workflow identifies three outstanding issues: how to treat generated content when it may affect outcomes, whether certification should target single builds or the whole generative pipeline, and how accountability should be assigned for outputs from autonomous systems. Explanation: these are outcomes of the ESGC example and are presented as unresolved in that example, not as final policy answers.",
      "sourceReferences": [
        "01aea77a-341d-4a08-92d5-8f9db3ffc0ff",
        "a263b013-e235-456d-9298-53a22a9f549d",
        "9d6d749b-c0c4-4f47-bf2c-31516b988a9c",
        "65227732-f94a-472d-8ed8-e513b57a69aa"
      ]
    }
  ]
}