{ "sessionId": "cmueb2enk000elliih0x46df0", "slug": "the-last-mile", "slides": [ { "order": 1, "title": "Welcome and session map", "bullets": [ "Scope: the last mile from a verified build to a player", "How EverPool fits the chain: verification → distribution → feedback", "This session follows handover, release, incidents, and feedback" ], "imageUrl": null, "altText": "Title: Welcome and session map. Three bullets: scope as the last mile from a verified build to a player; EverPool's place in the chain from verification to distribution to feedback; session path covering handover, release, incidents, and platform feedback.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "38bb8ad3-941d-49c0-a3fe-c8398b2533e4", "37e6fb66-d69f-457c-ab23-7a8098e0848d" ] }, { "order": 2, "title": "The chain from research to player", "bullets": [ "Market research informs what gets built", "Studios build; Sealed Jars verifies mathematics and spec", "EverPool distributes and returns aggregate evidence to studios" ], "imageUrl": null, "altText": "Title: The chain from research to player. Bullets explain: market research informs builds; studios produce games and Sealed Jars verifies mathematics, pool, prize structure and payback; EverPool distributes games and sends aggregate play evidence back to studios.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "4527eb07-e9c9-4c28-a9eb-4dafc88aca47", "1dbb06e5-4801-44fc-99a7-27eda170eb1f", "4f7f889a-af08-4c35-9082-c3d7b444302c", "37e6fb66-d69f-457c-ab23-7a8098e0848d" ] }, { "order": 3, "title": "What EverPool is, in practice", "bullets": [ "Live, browser‑based, play‑money platform (Sept 2026)", "'For entertainment only' on every page", "Server‑decided outcomes with an audit trail" ], "imageUrl": "https://g3e.ai/media/slides/cmueb2enk000elliih0x46df0/cmueb3byp000lllii607vg3oi-1790180273149.png", "altText": "The EverPool library as a player first sees it, with tabs for finite pool, Class 2 bingo, slots, session bingo and my games, and the newest Offphase Games titles first.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "32beaf2c-f81a-4896-b56a-5f167785b91d", "6d94f115-7aa3-4749-a5ef-c5af370a35ec", "d6e78a31-b09d-412b-8962-64cf788acaf0" ] }, { "order": 4, "title": "What arrives at distribution (the handover)", "bullets": [ "EverPool receives a complete verified build and its specification", "Spec describes pool, prize structure, and payback", "Handover transfers responsibility to the platform" ], "imageUrl": null, "altText": "Title: What arrives at distribution (the handover). Bullets: EverPool gets a complete build plus the specification Sealed Jars verified; the specification includes pool, prize structure and payback; the handover makes the build the platform's responsibility.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "1dbb06e5-4801-44fc-99a7-27eda170eb1f" ] }, { "order": 5, "title": "The arrival check: identity and fingerprint", "bullets": [ "Platform confirms build identity matches the verified one", "Fingerprint of verified mathematics must line up", "Mismatch stops acceptance and handover" ], "imageUrl": null, "altText": "Title: The arrival check: identity and fingerprint. Bullets: EverPool confirms the build's identity matches the one verified; it checks the fingerprint of the verified mathematics lines up; any mismatch prevents the build from being accepted.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "1dbb06e5-4801-44fc-99a7-27eda170eb1f" ] }, { "order": 6, "title": "Staging and release as gated steps", "bullets": [ "Accepted build is first staged (not visible to players)", "Staged build is checked running on the real platform", "Enabling is a gated action to release to the library" ], "imageUrl": "https://g3e.ai/media/slides/cmueb2enk000elliih0x46df0/cmueb3c0t000olliiohcdrqz5-1790180332930.png", "altText": "A released game, Crystal Quest, on its play screen, with the daily allowance, wager and play-credit meters and the for-entertainment-only footer.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "4f0cb68e-cb70-4a59-bd27-b856b3ecc3a2", "1dbb06e5-4801-44fc-99a7-27eda170eb1f" ] }, { "order": 7, "title": "Controlled rollout and watching with the studio", "bullets": [ "New or unusual titles often release in a watched window", "Platform and studio observe live behaviour before wide exposure", "Problems found here are held back from players" ], "imageUrl": null, "altText": "Title: Controlled rollout and watching with the studio. Bullets: new or unusual titles are often released in a controlled window; EverPool and the studio watch the live game for issues before broader exposure; if something is wrong the title is held back so players are not affected.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "4f0cb68e-cb70-4a59-bd27-b856b3ecc3a2", "9feec53c-dc51-4d00-a43c-6c142998dd5b", "2438b038-1cf5-4bfb-bfc2-c381d7b0a195", "4527eb07-e9c9-4c28-a9eb-4dafc88aca47" ] }, { "order": 8, "title": "When things go wrong: withdrawal and return", "bullets": [ "Immediate withdrawal disables a live game in one step", "Returning requires a new verified build and arrival check", "Platform pulls games independently of upstream parties" ], "imageUrl": null, "altText": "Title: When things go wrong: withdrawal and return. Bullets: EverPool can withdraw (disable) a live game in a single action; any return must be a new build verified again and pass the arrival check; withdrawal is independent of studios or verification timelines.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "9feec53c-dc51-4d00-a43c-6c142998dd5b", "46d582d5-60ee-4b99-9d98-2c702ed92c14" ] }, { "order": 9, "title": "Updates, replacements and the single‑step pull", "bullets": [ "Updates arrive as new verified builds and repeat the handover", "Platform replaces; it does not edit live games in place", "Withdrawal is a fast, single disable action" ], "imageUrl": null, "altText": "Title: Updates, replacements and the single-step pull. Bullets: any change is a new verified build that goes through the same handover and arrival check; EverPool replaces a game rather than editing it live; withdrawal remains a fast single‑step disable.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "46d582d5-60ee-4b99-9d98-2c702ed92c14" ] }, { "order": 10, "title": "Distribution's independent responsibilities", "bullets": [ "Honest disclosure on every page: 'For entertainment only' (Sept 2026)", "Daily play‑credits cap via daily reset model", "Server audit trail recording every outcome" ], "imageUrl": null, "altText": "Title: Distribution's independent responsibilities. Bullets: EverPool maintains a visible 'For entertainment only' disclosure on every page as of September 2026; the platform enforces a daily play‑credits cap via the daily reset; it keeps a server audit trail of every outcome.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "2438b038-1cf5-4bfb-bfc2-c381d7b0a195", "1d79c1cc-2739-4d36-85d6-976598396f17", "6d94f115-7aa3-4749-a5ef-c5af370a35ec" ] }, { "order": 11, "title": "What the platform measures and sends back", "bullets": [ "Aggregate observed payback and hit rates vs specification", "Library usage, play patterns, and multiplayer uptake", "Shared as aggregate evidence, not individual player data" ], "imageUrl": null, "altText": "Title: What the platform measures and sends back. Bullets: EverPool measures observed payback and hit rates and compares them to the verified specification; it tracks which games are played, play patterns, and multiplayer usage; all reporting is aggregate — not individual player data.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "1f864f9a-38f9-46a8-b678-1ac9a7552d3b", "8b0d9afd-f057-4ab0-9b59-27b78b173c10", "4f7f889a-af08-4c35-9082-c3d7b444302c" ] }, { "order": 12, "title": "Experiments, custom games, and the closing loop", "bullets": [ "AI‑generated custom instances exist but must be verified first", "Prototypes are marked as experiments but still verified", "EverPool turns plans into evidence that informs studios" ], "imageUrl": null, "altText": "Title: Experiments, custom games, and the closing loop. Bullets: AI‑generated custom game instances are allowed but held to the same verification before play; prototypes and experiments are clearly labeled yet still server‑decided and verified; EverPool is where plans become evidence that go back to studios.", "targetSeconds": 55, "script": "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.", "sourceReferences": [ "37e6fb66-d69f-457c-ab23-7a8098e0848d", "9bc0c7a7-0dd9-4dde-bcf1-27fcb9f434c4", "4f7f889a-af08-4c35-9082-c3d7b444302c", "56345c18-0b32-4eda-a7f9-2ff951656bac" ] } ] }