{
  "sessionId": "cmud8nw8p000hebiiwur4l735",
  "slug": "governing-what-nobody-has-certified",
  "slides": [
    {
      "order": 1,
      "title": "Governing what nobody has certified yet",
      "bullets": [
        "Scope: United States regimes only",
        "Sources: IEGM documents (Sept 2026) and cited rules [S6, S12]",
        "Session frames gaps, not fixes"
      ],
      "imageUrl": null,
      "altText": "Title slide reading 'Governing what nobody has certified yet'. Bullets state scope is United States regimes only; sources are IEGM documents dated September 2026 and cited rules [S6, S12]; session will identify gaps without proposing fixes.",
      "targetSeconds": 30,
      "script": "Welcome. I am an AI presenter from the Institute for Emerging Gaming Markets. This session is titled Governing what nobody has certified yet. Scope: United States regimes only. All materials and claims I will cite come from IEGM documents dated September 2026 and the cited rules. I will identify what the rules say and how they might be read, and where the texts go quiet. I do not attempt to fill those silences.",
      "sourceReferences": [
        "73b8ebf0-b92a-4c6e-81a9-47578448b77e",
        "405b5d64-9dbf-481e-b7ed-959fa3f27335"
      ]
    },
    {
      "order": 2,
      "title": "Why generative games matter",
      "bullets": [
        "Generative systems produce content at time of play",
        "That runtime content challenges fixed‑build assumptions",
        "Grounding: IEGM explanation of runtime content [S6]"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'Why generative games matter' with bullets: generative systems produce content at time of play; runtime content challenges fixed-build assumptions; grounding citation to IEGM [S6].",
      "targetSeconds": 45,
      "script": "Why generative games matter. I mean a generative system as one that produces content or behavior at the time of play rather than selecting it from a set fixed beforehand. Generative systems produce content at runtime and therefore challenge assumptions embedded in existing certification regimes, as IEGM explains. I will stick to what the texts say and where they leave questions open.",
      "sourceReferences": [
        "73b8ebf0-b92a-4c6e-81a9-47578448b77e",
        "246fedb6-1022-47c5-be7b-2644de6debf7"
      ]
    },
    {
      "order": 3,
      "title": "Today's certification baseline",
      "bullets": [
        "Primary references: Nevada Reg. 14 (Feb 2026)",
        "Federal Class II standards: 25 C.F.R. part 547",
        "IEGM’s September 2026 summary describes requirements [S13]"
      ],
      "imageUrl": null,
      "altText": "Slide listing the two primary reference regimes: Nevada Regulation 14 revised February 2026 and federal Class II standards at 25 C.F.R. part 547. Notes IEGM Sept 2026 summary [S13].",
      "targetSeconds": 50,
      "script": "Today's certification baseline. The two primary reference regimes for this session are Nevada Gaming Commission Regulation 14, revised February 2026, and the federal Class II minimum technical standards at 25 C.F.R. part 547. IEGM's September 2026 summary describes how those regimes operate as the baseline for certification today.",
      "sourceReferences": [
        "e6e01a63-b4ab-4269-aabe-3416e2784f80",
        "405b5d64-9dbf-481e-b7ed-959fa3f27335"
      ]
    },
    {
      "order": 4,
      "title": "Key feature: approval before play (Nevada)",
      "bullets": [
        "Rule says: administrative approval required before offering play (Nevada)",
        "How it might be read: presumes an identifiable, stable submission [S15]"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'Key feature: approval before play (Nevada)'. Bullet quotes that Nevada requires administrative approval before offering a gaming device for play, and explains this presumes an identifiable, stable submission. Cites [S15].",
      "targetSeconds": 60,
      "script": "Key procedural feature in Nevada: approval before play. The rule says that a manufacturer or distributor shall not distribute, and a licensee shall not offer for play, unless the device has received administrative approval from the Chair or Commission or is authorized for a field test; these provisions are in Nevada Regulation 14, revised February 2026. How it might be read: this presumes the thing to be approved is identifiable and stable at the time of submission.",
      "sourceReferences": [
        "69c7ae75-a8bc-4f82-a714-3ede7bbbea92"
      ]
    },
    {
      "order": 5,
      "title": "Key feature: submission‑testing‑finding (Federal)",
      "bullets": [
        "Rule says: Part 547 requires lab testing and tribal finding",
        "How it might be read: any modification re‑opens the process [S16]"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'Key feature: submission-testing-finding (Federal)'. Bullets state Part 547 requires submission to a testing laboratory and a tribal finding, and this implies changes re-open the process. Cites [S16].",
      "targetSeconds": 60,
      "script": "Key procedural feature in the federal Class II regime: submission, testing, and finding. The rule says part 547 requires that no tribal gaming regulatory authority permit use of a Class II gaming system or any modification thereto unless it has been submitted to a testing laboratory, tested against the part, reported on, and then a tribal finding made. How it might be read: any change re‑opens the process, and the rule assumes discrete, reportable modification events.",
      "sourceReferences": [
        "32dd179a-f235-42a7-9c4d-836507d2f183"
      ]
    },
    {
      "order": 6,
      "title": "Artifact binding: hashes and IDs today",
      "bullets": [
        "Nevada 14.400 requires SHA1 signatures for files",
        "Part 547 requires verification methodology (hash examples)",
        "Certification ties to a specific, stable artifact [S11,S19]"
      ],
      "imageUrl": null,
      "altText": "Slide 'Artifact binding: hashes and IDs today' noting Nevada 14.400's SHA1 requirement and Part 547's verification methodology. States certification attaches to a specific, stable artifact. Cites [S11, S19].",
      "targetSeconds": 50,
      "script": "Artifact binding: hashes and IDs today. The rule says Nevada Regulation 14.400 requires reporting the SHA1 signature of applicable files as they would appear post‑installation, and part 547 requires a verification methodology, with hashing formulas given as illustration. How it might be read: certification attaches to a specific, stable artifact identified by a value that changes when the artifact changes.",
      "sourceReferences": [
        "05aa12cc-a50d-4a7c-b70b-b787608d2fed",
        "584e2359-11f5-47ef-863b-29fcda1a9597",
        "6346a3c5-9816-4030-9ed6-61e852896cae"
      ]
    },
    {
      "order": 7,
      "title": "Rule fixing the shape of a play",
      "bullets": [
        "Nevada 14.040(3): all outcomes must be available at play start",
        "14.040(1)(b): outcome determined 'solely' by chance/skill [S14,S17]"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'Rule fixing the shape of a play' quoting Nevada 14.040(3) that all possible outcomes must be available at play initiation and 14.040(1)(b) that outcome be determined solely by chance or skill. Cites [S14, S17].",
      "targetSeconds": 60,
      "script": "Rule fixing the shape of a play. The rule says Nevada 14.040(3) requires that all possible game outcomes be available upon initiation of each play, and 14.040(1)(b) requires that outcome be determined solely by chance, skill, or a combination. How it might be read: these provisions presume outcomes are enumerable and fixed at play initiation; a runtime‑composed artifact raises a textual question the rule does not settle.",
      "sourceReferences": [
        "6346a3c5-9816-4030-9ed6-61e852896cae",
        "b3511d42-24fb-42a7-8f0b-fe3a3d1b7e0a",
        "5c089e1f-dad6-4568-80d6-f6a4792dae46"
      ]
    },
    {
      "order": 8,
      "title": "Assumption 1 — Content produced at runtime",
      "bullets": [
        "Assumption: presentation shipped in the build, not composed at play",
        "Tension: text treats artistic vs material elements differently [S2,S4]"
      ],
      "imageUrl": null,
      "altText": "Slide 'Assumption 1 — Content produced at runtime' stating the assumption that presentation is shipped in the build, and noting tension in rule text about artistic versus material elements, citing Nevada provisions. Sources [S2, S4].",
      "targetSeconds": 60,
      "script": "Assumption 1 — Content produced at runtime. The assumption is that presentation and content are shipped in the build rather than composed at play. Nevada's text draws a line: changes to software used for artistic attributes are excluded from modification unless such elements are material to gameplay [Regulation 14.010(25)(e)] and Nevada requires outcomes be available at play initiation. How this reads creates tension about whether runtime‑composed artifacts count as outcomes or mere artistic attributes; the text is silent on mixed cases.",
      "sourceReferences": [
        "335f733a-2fc6-4498-a1cc-bece3f73f742",
        "5c089e1f-dad6-4568-80d6-f6a4792dae46"
      ]
    },
    {
      "order": 9,
      "title": "Where that assumption goes quiet — materiality test missing",
      "bullets": [
        "Rule says artistic elements excluded unless 'material to game play' (Nevada)",
        "Rule does not publish a test for when generated content is material [S1,S17]"
      ],
      "imageUrl": null,
      "altText": "Slide explaining NV excludes artistic elements unless they are material to gameplay, but provides no published test for when generated runtime content is 'material.' Cites [S1, S17].",
      "targetSeconds": 55,
      "script": "Where that assumption goes quiet — materiality test missing. The rule says Nevada excludes artistic elements from modification unless they are material to game play because they are necessary for the player to understand the game or outcome. What the rule does not do is publish a test for when generated presentation is material, especially when composition happens during play. IEGM records that as unresolved rather than offering a resolution.",
      "sourceReferences": [
        "66fe72e9-6abe-4dcb-9cfd-408df2d3796a",
        "b3511d42-24fb-42a7-8f0b-fe3a3d1b7e0a",
        "335f733a-2fc6-4498-a1cc-bece3f73f742"
      ]
    },
    {
      "order": 10,
      "title": "Assumption 2 — A build, not a pipeline",
      "bullets": [
        "Assumption: product is a single build with stable components",
        "Model‑updated or remotely served components break that assumption [S11]"
      ],
      "imageUrl": null,
      "altText": "Slide 'Assumption 2 — A build, not a pipeline' stating certification presumes a single build; model-updated or remotely served components do not present that stable artifact. Cites [S11].",
      "targetSeconds": 60,
      "script": "Assumption 2 — A build, not a pipeline. The assumption is that certification treats the product as a single build with stable components. Nevada and part 547 require identification and verification methods that presuppose a component to hash and compare, and testing that the examined source produced materially identical software to production. Model‑updated or remotely served components break that assumption because the deployed behavior may diverge without a discrete changed artifact to rehash.",
      "sourceReferences": [
        "05aa12cc-a50d-4a7c-b70b-b787608d2fed",
        "6346a3c5-9816-4030-9ed6-61e852896cae",
        "584e2359-11f5-47ef-863b-29fcda1a9597"
      ]
    },
    {
      "order": 11,
      "title": "Where that assumption goes quiet — unit of certification",
      "bullets": [
        "Open question: certify process, bounds on outputs, or each output?",
        "IEGM labels this unresolved (Sept 2026) [S1,S5]"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'Where that assumption goes quiet — unit of certification' posing the open question whether the unit is the process, output bounds, or each output, and noting IEGM labels it unresolved. Cites [S1, S5].",
      "targetSeconds": 50,
      "script": "Where that assumption goes quiet — unit of certification. The open question here is the unit of certification: should it be the generating process, bounds on its outputs, or each output individually? IEGM examined candidate answers but labels this unresolved as of September 2026; the Institute does not favor one approach over another.",
      "sourceReferences": [
        "66fe72e9-6abe-4dcb-9cfd-408df2d3796a",
        "54228b40-6651-441a-a892-f5c1749bad60",
        "73b8ebf0-b92a-4c6e-81a9-47578448b77e"
      ]
    },
    {
      "order": 12,
      "title": "Assumption 3 — Named human accountability",
      "bullets": [
        "Regimes locate accountability in named attestants (labs, manufacturers)",
        "Text is silent on disclosing design origin if machine‑proposed [S3]"
      ],
      "imageUrl": null,
      "altText": "Slide 'Assumption 3 — Named human accountability' noting regimes expect named parties (laboratories, manufacturers) to attest, and the rules do not require disclosure of whether design was proposed by an autonomous system. Cites [S3].",
      "targetSeconds": 55,
      "script": "Assumption 3 — Named human accountability. The assumption is that regimes locate accountability in named parties who attest. Nevada requires a laboratory statement signed under penalty of perjury and manufacturer attestations, and Part 547 places the conforming finding with the tribal authority. The texts are silent about requiring disclosure of whether a design was generated by an autonomous system; IEGM has not identified a requirement that asks that question as of September 2026.",
      "sourceReferences": [
        "fb457f6b-8876-4bd3-aa42-d5d00c395782",
        "83164478-98c3-4c81-b5fb-64126113953d"
      ]
    },
    {
      "order": 13,
      "title": "Open accountability questions",
      "bullets": [
        "Must origin‑of‑design be disclosed? Unresolved",
        "What would a lab examine if behavior derives from model weights? Unresolved",
        "Who is accountable when no person chose parameters? Unresolved [S5,S8]"
      ],
      "imageUrl": null,
      "altText": "Slide listing unresolved accountability questions: disclosure of design origin, what labs would examine when behavior derives from model weights, and who is accountable when no person chose parameters. All labeled unresolved by IEGM. Cites [S5, S8].",
      "targetSeconds": 55,
      "script": "Open accountability questions. These are unresolved in IEGM's review: whether origin‑of‑design must be disclosed; what a laboratory would examine when behavior derives from model weights rather than readable source code; and who is accountable when no person chose parameters. IEGM lists each of these as unresolved and separates disclosure, testing, and approval as distinct questions.",
      "sourceReferences": [
        "54228b40-6651-441a-a892-f5c1749bad60",
        "246fedb6-1022-47c5-be7b-2644de6debf7"
      ]
    },
    {
      "order": 14,
      "title": "Other unresolved technical questions",
      "bullets": [
        "When does continuous change become a 'modification'? Unresolved",
        "Can statistical assurance substitute for deterministic verification? Unresolved",
        "What happens to a certificate when a model changes? Unresolved [S1,S7]"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'Other unresolved technical questions' summarizing open issues: threshold for continuous change becoming a modification; whether statistical assurance can substitute for deterministic verification; certificate validity when models change. Each marked unresolved per IEGM. Cites [S1, S7].",
      "targetSeconds": 55,
      "script": "Other unresolved technical questions. IEGM also records as unresolved whether continuous change should be treated as a stream of modifications or as a single approved process; whether statistical assurance can substitute for deterministic verification; and what happens to a certificate when the model behind it changes. These remain open in United States regimes as of September 2026.",
      "sourceReferences": [
        "66fe72e9-6abe-4dcb-9cfd-408df2d3796a",
        "3ba6bfda-db6f-4b55-8013-9db1a1649b4b",
        "a83f1d1b-2017-4ecf-a589-cf1aa2882651",
        "0509f87a-2729-4959-9578-edf1c26c05e6"
      ]
    },
    {
      "order": 15,
      "title": "Takeaways and what to do with the silence",
      "bullets": [
        "Name three assumptions generative systems violate",
        "Identify genuinely open questions IEGM lists as unresolved",
        "IEGM's role: identify gaps, not answer them (Sept 2026) [S6,S5]"
      ],
      "imageUrl": null,
      "altText": "Final slide 'Takeaways and what to do with the silence' listing three actions: name the three assumptions violated by generative systems, identify the IEGM‑listed unresolved questions, and note IEGM stops at gap identification rather than answering. Cites [S6, S5].",
      "targetSeconds": 60,
      "script": "Takeaways and what to do with the silence. First: name the three specific assumptions generative systems violate — content shipped in the build, a single build as the unit of certification, and named human origin requiring accountability. Second: identify the genuinely open questions IEGM lists as unresolved, including unit of certification, materiality of generated presentation, origin disclosure, what labs examine, continuous change versus modification, statistical versus deterministic assurance, and certificate validity when models change. Third: IEGM's role is to identify gaps, not to answer them; these remain open as of September 2026. Thank you.",
      "sourceReferences": [
        "73b8ebf0-b92a-4c6e-81a9-47578448b77e",
        "54228b40-6651-441a-a892-f5c1749bad60",
        "246fedb6-1022-47c5-be7b-2644de6debf7",
        "05aa12cc-a50d-4a7c-b70b-b787608d2fed",
        "fb457f6b-8876-4bd3-aa42-d5d00c395782",
        "66fe72e9-6abe-4dcb-9cfd-408df2d3796a",
        "335f733a-2fc6-4498-a1cc-bece3f73f742",
        "a83f1d1b-2017-4ecf-a589-cf1aa2882651",
        "3ba6bfda-db6f-4b55-8013-9db1a1649b4b",
        "0509f87a-2729-4959-9578-edf1c26c05e6"
      ]
    }
  ]
}