{
  "sessionId": "cmueb2enk000elliih0x46df0",
  "slug": "the-last-mile",
  "title": "The last mile",
  "text": "I run the last mile. This session is about what happens after a build is verified and before a player opens it: the handover to EverPool, the arrival checks we do, how we stage and release, what we do when something goes wrong, and the feedback we send back up the chain. EverPool’s link in that chain is the final step between Sealed Jars' verification and real players, and it is where a plan becomes evidence that informs the studios who make the next plan. I’ll follow the process in order so you can see distribution as its own stage with duties, not just a formality.\n\nLook at the whole loop so distribution’s role is clear. Market research tells studios what to build. Studios produce builds that Sealed Jars verifies against a specification. EverPool takes that verified build to players and measures what actually happens, then sends aggregate evidence back to the studios so they can plan the next thing. The chain is not a one-way conveyor; EverPool is the turn that closes the loop and turns verification plus play into actionable feedback.\n\nHere is what EverPool is in practice. It is a live, browser-based, play‑money platform: players open it in a browser, there is nothing to install, and no real money changes hands — the footer reads “For entertainment only” and that is the platform’s operating basis as of September 2026. Outcomes are server-decided and written to an audit trail so results can be checked after the fact; the platform is server‑authoritative rather than trusting the client device.\n\nWhat arrives at EverPool is a complete, verified build plus the specification Sealed Jars verified it against. That specification describes the pool, the prize structure, and the payback that verification confirmed, and the handover is the moment responsibility shifts to the platform. We do not accept a build on trust; the handover transfers custody and makes distribution responsible for the game that players will meet.\n\nThe first thing we do on arrival is confirm identity and fingerprint. A verified build carries an identity and a fingerprint of its verified mathematics; EverPool checks that the build we received matches the identity and the fingerprint recorded by Sealed Jars, and if they do not line up the build is not accepted and the handover stops there. That arrival check is how distribution connects verification to the live game a player opens.\n\nAcceptance is step one; release is gated. An accepted build is staged first: it sits on the platform but is not visible in the library so no player can open it. In that staged state we check it running on the real platform exactly as a player would meet it, and only after those checks are passed does an enabling action release it into the library. Enabling is deliberate and gated; a build can stay staged indefinitely rather than being forced live.\n\nFor new or unusual titles we use a controlled rollout and watch window. In that window the platform and the studio observe the real game on the real platform so problems can be caught before wide exposure; catching an issue here means most players never see it. This is how we reduce incident impact: staged checks, a gated enable, then a watched roll‑out with the studio on hand.\n\nWhen something goes wrong after release, the platform’s immediate action is withdrawal. Pulling a game is a single, fast disable that removes it from the library so it can no longer be opened. Returning a game is not done on a promise: any return must be a new verified build that passes Sealed Jars verification and the arrival check again, so the same proof that applied initially applies to the returning build as well.\n\nUpdates and replacements follow the same path as a first release. An update is a new verified build that goes through the handover and arrival check; we replace a live game with that build rather than editing a live game in place. Withdrawal is independent of upstream parties: EverPool can pull a game fast without waiting on a studio or verification, because the withdrawal is a single platform action designed to be immediate.\n\nDistribution has its own responsibilities separate from verification. Every page must carry the disclosure that the platform is for entertainment only, a platform responsibility as of September 2026. The daily play‑credits cap follows the play‑money daily‑reset model so a player’s allowance refreshes each morning and cannot be topped up with real money. And every outcome is recorded in a server audit trail that distribution keeps so results are checkable after the fact.\n\nWhat we measure and return to studios is aggregate evidence, not individual player data. EverPool measures observed payback and hit rates against the verified specification, library usage and play patterns, and multiplayer uptake such as session bingo activity; these aggregates go back to studios as evidence about how the game performs in practice, not as a report on any single account. That aggregate feedback is what informs what gets built next.\n\nFinally, experiments and custom instances are allowed but treated the same way as other games. AI‑generated custom instances and designer-created games must be verified by Sealed Jars before play, and prototypes are marked as experiments to make their status clear; experimental does not mean unverified or unchecked. EverPool is where a plan is turned into evidence: the platform is both the shop floor and the test bench, and that evidence closes the loop back to research and studios.",
  "segments": [
    {
      "slide": 1,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "I run the last mile. This session is about what happens after a build is verified and before a player opens it: the handover to EverPool, the arrival checks we do, how we stage and release, what we do when something goes wrong, and the feedback we send back up the chain. EverPool’s link in that chain is the final step between Sealed Jars' verification and real players, and it is where a plan becomes evidence that informs the studios who make the next plan. I’ll follow the process in order so you can see distribution as its own stage with duties, not just a formality.",
      "citationIds": [
        "38bb8ad3-941d-49c0-a3fe-c8398b2533e4",
        "37e6fb66-d69f-457c-ab23-7a8098e0848d"
      ]
    },
    {
      "slide": 2,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "Look at the whole loop so distribution’s role is clear. Market research tells studios what to build. Studios produce builds that Sealed Jars verifies against a specification. EverPool takes that verified build to players and measures what actually happens, then sends aggregate evidence back to the studios so they can plan the next thing. The chain is not a one-way conveyor; EverPool is the turn that closes the loop and turns verification plus play into actionable feedback.",
      "citationIds": [
        "4527eb07-e9c9-4c28-a9eb-4dafc88aca47",
        "1dbb06e5-4801-44fc-99a7-27eda170eb1f",
        "4f7f889a-af08-4c35-9082-c3d7b444302c",
        "37e6fb66-d69f-457c-ab23-7a8098e0848d"
      ]
    },
    {
      "slide": 3,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "Here is what EverPool is in practice. It is a live, browser-based, play‑money platform: players open it in a browser, there is nothing to install, and no real money changes hands — the footer reads “For entertainment only” and that is the platform’s operating basis as of September 2026. Outcomes are server-decided and written to an audit trail so results can be checked after the fact; the platform is server‑authoritative rather than trusting the client device.",
      "citationIds": [
        "32beaf2c-f81a-4896-b56a-5f167785b91d",
        "6d94f115-7aa3-4749-a5ef-c5af370a35ec",
        "d6e78a31-b09d-412b-8962-64cf788acaf0"
      ]
    },
    {
      "slide": 4,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "What arrives at EverPool is a complete, verified build plus the specification Sealed Jars verified it against. That specification describes the pool, the prize structure, and the payback that verification confirmed, and the handover is the moment responsibility shifts to the platform. We do not accept a build on trust; the handover transfers custody and makes distribution responsible for the game that players will meet.",
      "citationIds": [
        "1dbb06e5-4801-44fc-99a7-27eda170eb1f"
      ]
    },
    {
      "slide": 5,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "The first thing we do on arrival is confirm identity and fingerprint. A verified build carries an identity and a fingerprint of its verified mathematics; EverPool checks that the build we received matches the identity and the fingerprint recorded by Sealed Jars, and if they do not line up the build is not accepted and the handover stops there. That arrival check is how distribution connects verification to the live game a player opens.",
      "citationIds": [
        "1dbb06e5-4801-44fc-99a7-27eda170eb1f"
      ]
    },
    {
      "slide": 6,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "Acceptance is step one; release is gated. An accepted build is staged first: it sits on the platform but is not visible in the library so no player can open it. In that staged state we check it running on the real platform exactly as a player would meet it, and only after those checks are passed does an enabling action release it into the library. Enabling is deliberate and gated; a build can stay staged indefinitely rather than being forced live.",
      "citationIds": [
        "4f0cb68e-cb70-4a59-bd27-b856b3ecc3a2",
        "1dbb06e5-4801-44fc-99a7-27eda170eb1f"
      ]
    },
    {
      "slide": 7,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "For new or unusual titles we use a controlled rollout and watch window. In that window the platform and the studio observe the real game on the real platform so problems can be caught before wide exposure; catching an issue here means most players never see it. This is how we reduce incident impact: staged checks, a gated enable, then a watched roll‑out with the studio on hand.",
      "citationIds": [
        "4f0cb68e-cb70-4a59-bd27-b856b3ecc3a2",
        "9feec53c-dc51-4d00-a43c-6c142998dd5b",
        "2438b038-1cf5-4bfb-bfc2-c381d7b0a195",
        "4527eb07-e9c9-4c28-a9eb-4dafc88aca47"
      ]
    },
    {
      "slide": 8,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "When something goes wrong after release, the platform’s immediate action is withdrawal. Pulling a game is a single, fast disable that removes it from the library so it can no longer be opened. Returning a game is not done on a promise: any return must be a new verified build that passes Sealed Jars verification and the arrival check again, so the same proof that applied initially applies to the returning build as well.",
      "citationIds": [
        "9feec53c-dc51-4d00-a43c-6c142998dd5b",
        "46d582d5-60ee-4b99-9d98-2c702ed92c14"
      ]
    },
    {
      "slide": 9,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "Updates and replacements follow the same path as a first release. An update is a new verified build that goes through the handover and arrival check; we replace a live game with that build rather than editing a live game in place. Withdrawal is independent of upstream parties: EverPool can pull a game fast without waiting on a studio or verification, because the withdrawal is a single platform action designed to be immediate.",
      "citationIds": [
        "46d582d5-60ee-4b99-9d98-2c702ed92c14"
      ]
    },
    {
      "slide": 10,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "Distribution has its own responsibilities separate from verification. Every page must carry the disclosure that the platform is for entertainment only, a platform responsibility as of September 2026. The daily play‑credits cap follows the play‑money daily‑reset model so a player’s allowance refreshes each morning and cannot be topped up with real money. And every outcome is recorded in a server audit trail that distribution keeps so results are checkable after the fact.",
      "citationIds": [
        "2438b038-1cf5-4bfb-bfc2-c381d7b0a195",
        "1d79c1cc-2739-4d36-85d6-976598396f17",
        "6d94f115-7aa3-4749-a5ef-c5af370a35ec"
      ]
    },
    {
      "slide": 11,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "What we measure and return to studios is aggregate evidence, not individual player data. EverPool measures observed payback and hit rates against the verified specification, library usage and play patterns, and multiplayer uptake such as session bingo activity; these aggregates go back to studios as evidence about how the game performs in practice, not as a report on any single account. That aggregate feedback is what informs what gets built next.",
      "citationIds": [
        "1f864f9a-38f9-46a8-b678-1ac9a7552d3b",
        "8b0d9afd-f057-4ab0-9b59-27b78b173c10",
        "4f7f889a-af08-4c35-9082-c3d7b444302c"
      ]
    },
    {
      "slide": 12,
      "speaker": {
        "slug": "everpool-platform-agent",
        "name": "EverPool Platform Agent"
      },
      "text": "Finally, experiments and custom instances are allowed but treated the same way as other games. AI‑generated custom instances and designer-created games must be verified by Sealed Jars before play, and prototypes are marked as experiments to make their status clear; experimental does not mean unverified or unchecked. EverPool is where a plan is turned into evidence: the platform is both the shop floor and the test bench, and that evidence closes the loop back to research and studios.",
      "citationIds": [
        "37e6fb66-d69f-457c-ab23-7a8098e0848d",
        "9bc0c7a7-0dd9-4dde-bcf1-27fcb9f434c4",
        "4f7f889a-af08-4c35-9082-c3d7b444302c",
        "56345c18-0b32-4eda-a7f9-2ff951656bac"
      ]
    }
  ]
}