{
  "sessionId": "cmu6eyapu0014kkiitemx513c",
  "slug": "verifying-generated-game-math",
  "slides": [
    {
      "order": 1,
      "title": "Definitions: RTP and volatility",
      "bullets": [
        "RTP: long‑run proportion of wagers returned to players",
        "Computed from the paytable and symbol probabilities",
        "Volatility: spread of individual outcomes around that mean"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'Definitions: RTP and volatility'. Three terse bullets define RTP as the long-run proportion of wagers returned, state it is computed from the paytable and symbol probabilities, and define volatility as the spread of individual outcomes around that average.",
      "targetSeconds": 60,
      "script": "I start with definitions so we share terms. Return to player, or RTP, is the long‑run proportion of total wagers a game pays back; that is a sourced definition of RTP. Saying this is a fact, not an opinion. Volatility describes how widely individual outcomes vary around that long‑run mean; that is the sourced definition of volatility. Explanation: in practical checks we treat RTP as the average outcome over many plays and volatility as the spread around that average. Those are the two quantities I will use for verification and simulation.",
      "sourceReferences": [
        "b5ecef5a-1e34-4fe0-8427-439f07b28f09"
      ]
    },
    {
      "order": 2,
      "title": "Compute RTP analytically",
      "bullets": [
        "RTP = sum over outcomes of (p(outcome) × payout)",
        "Outcome probabilities come from paytable and reel strips",
        "Analytic RTP is the baseline for verification"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'Compute RTP analytically'. Three bullets: formula-style statement that RTP equals the sum over outcomes of probability times payout, that probabilities come from paytable and reel strips, and that analytic RTP is the verification baseline.",
      "targetSeconds": 90,
      "script": "Next I show how to compute RTP analytically. The RTP is computed from the paytable and symbol probabilities; this is the sourced method for getting the long‑run figure. The analytic formula is the sum over all outcomes of the outcome probability times the payout; this is the standard computation and follows from the definition. Outcome probabilities come from the paytable together with the reel strips or other symbol distributions that define how likely each combination is; that connection is part of the same sourced description. Explanation: you build a model of every distinct outcome, assign each a probability from the strips, multiply by its payout, and sum. The number you get is the analytic RTP and it is the baseline number we will verify against with simulation.",
      "sourceReferences": [
        "05a56370-0264-4c36-a862-bd718bd0ff20",
        "b5ecef5a-1e34-4fe0-8427-439f07b28f09"
      ]
    },
    {
      "order": 3,
      "title": "Simulate and compare",
      "bullets": [
        "Run a large Monte Carlo of plays to get empirical RTP",
        "Compare empirical RTP to analytic RTP; expect close agreement",
        "Large discrepancy indicates an error in analysis or simulator"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'Simulate and compare'. Three bullets instruct to run a Monte Carlo to obtain empirical RTP, compare it to the analytic RTP expecting close agreement, and note that a large discrepancy signals an error in either the analysis or the simulator.",
      "targetSeconds": 90,
      "script": "Now the practical check: simulate and compare. The placeholder verification method is to run a large Monte Carlo of plays to get an empirical RTP, and then compare that empirical number to the analytic RTP computed from the paytable and strips; that procedure is described in the source and is the practical check we use. Explanation: if the simulator and the analytic model are both correct, the empirical RTP should be close to the analytic RTP within sampling error. If you see a large discrepancy, treat that as evidence of an error in either the analytic model or the simulator; the source explicitly states this as the diagnostic rule. In other words, simulation is a tool to confirm implementation fidelity to the specification.",
      "sourceReferences": [
        "05a56370-0264-4c36-a862-bd718bd0ff20"
      ]
    },
    {
      "order": 4,
      "title": "What simulation cannot tell you",
      "bullets": [
        "Simulation shows the game matches its specification",
        "It cannot show whether the specification is appropriate",
        "Appropriateness is a design and regulatory judgment"
      ],
      "imageUrl": null,
      "altText": "Slide titled 'What simulation cannot tell you'. Three bullets state that simulation confirms the game matches its specification, that it cannot determine whether the specification is appropriate, and that appropriateness remains a design and regulatory judgment.",
      "targetSeconds": 60,
      "script": "Finally, what simulation cannot tell you. Simulation can confirm that a game matches its own specification, but it cannot show whether that specification is appropriate; that limitation is stated in the source. Explanation: simulation verifies correspondence between implementation and spec, not the policy, design, or regulatory adequacy of the spec itself. Determining appropriateness is a separate design or regulatory judgment and is outside what simulation alone can prove.",
      "sourceReferences": [
        "59cb82dc-a5f2-484a-8f27-b83da38ee2dd"
      ]
    }
  ]
}