{
  "sessionId": "cmueb2enk000elliih0x46df0",
  "slug": "the-last-mile",
  "sources": [
    {
      "id": "32beaf2c-f81a-4896-b56a-5f167785b91d",
      "label": "What EverPool is ¶2",
      "title": "What EverPool is — The platform",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## The platform\n\nEverPool is where the games meet the players. It is a live web platform: a player opens it in a browser, signs in, and chooses a game from a library. There is nothing to install. What a player does on EverPool is play, and only that. Play is for entertainment only, with play money. No money changes hands. There is no cash in and no cash out, no deposit, and no prize that has cash value. That is not a detail hidden in the terms of service; the line \"For entertainment only\" sits in the footer of every page on the site, and as of September 2026 it is the whole basis on which the platform operates.\n\nThe games run in the player's browser, but the outcomes do not. When a player takes a spin, opens a pull-tab, or marks a bingo card, the result is decided on the server and written to an audit trail, not calculated on the device in front of them. A player cannot change an outcome by changing something on their screen, because the screen is only showing what the server already decided. This is what people mean when they call the platform server-authoritative, and it is the reason a result on EverPool can be checked after the fact rather than taken on trust.",
      "document": {
        "id": "cmueb1x7h0001lliig8p67o49",
        "title": "What EverPool is",
        "summary": "The document explains EverPool, a browser-based live platform where players play play-money games with server-decided outcomes, detailing game types (finite-pool pull-tabs, real-time bingo, session bingo, and slots) and features like chat and daily credits. It is a conference-session style material describing the platform and its role in the production/verification/distribution chain, including how games are designed, verified, released, and how feedback loops back to studios."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "56345c18-0b32-4eda-a7f9-2ff951656bac",
      "label": "What EverPool is ¶4",
      "title": "What EverPool is — The kinds of game",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "In the library this sits under a tab styled \"Class 2 Bingo\", after the look of Class II bingo, but EverPool is play money and is not Class II gaming or any other regulated category.\n\nSession bingo is a distinct, live, shared format, and it is worth describing carefully because it is not something most platforms offer. In session bingo, players join a shared session and play one bingo game together, in real time, against the same draws at the same moment, rather than each playing a private instance. It is closer to a room of people sitting down to the same game at the same time than to a solitary machine. The session is run and drawn on the server, and every player in it sees the same game unfold. As of September 2026 it is one of the more experimental formats on the platform, and it is the clearest example of EverPool being built for people playing together rather than alone.\n\nSlots are the reel games a player expects, with paylines and bonus rounds, and they too are decided entirely on the server, with the same audit trail behind every spin as everything else.\n\nAcross all of these, the constant is the server-authoritative model. Whether a result comes from a finite pool, a bingo draw, a shared session, or a set of reels, it is decided on the server and left with a record, and none of it is calculated on the player's device.",
      "document": {
        "id": "cmueb1x7h0001lliig8p67o49",
        "title": "What EverPool is",
        "summary": "The document explains EverPool, a browser-based live platform where players play play-money games with server-decided outcomes, detailing game types (finite-pool pull-tabs, real-time bingo, session bingo, and slots) and features like chat and daily credits. It is a conference-session style material describing the platform and its role in the production/verification/distribution chain, including how games are designed, verified, released, and how feedback loops back to studios."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "1d79c1cc-2739-4d36-85d6-976598396f17",
      "label": "What EverPool is ¶5",
      "title": "What EverPool is — Chat, credits, and the daily reset",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## Chat, credits, and the daily reset\n\nEverPool is meant to be a place people play together, not only a shelf of single-player games, and two features carry that. The first is a built-in chat system. Players can talk to one another inside the platform while they play, which matters most in the multiplayer formats, the bingo rooms and session bingo, where other people are genuinely present in the same game at the same time. The chat runs through the platform rather than around it.\n\nThe second is the daily-credits model, which follows directly from the platform being play money for entertainment. Each player has an allowance of play credits that refreshes on a daily reset. A player spends those credits as they play, and when a day's allowance is used up, play pauses until the next reset rather than continuing without limit. Because the credits are play money with no cash value and cannot be topped up with real money, the daily reset is not a paywall; it is a natural daily cap on how much anyone plays, built into the model rather than added on top of it. As of September 2026 the daily allowance resets each morning.",
      "document": {
        "id": "cmueb1x7h0001lliig8p67o49",
        "title": "What EverPool is",
        "summary": "The document explains EverPool, a browser-based live platform where players play play-money games with server-decided outcomes, detailing game types (finite-pool pull-tabs, real-time bingo, session bingo, and slots) and features like chat and daily credits. It is a conference-session style material describing the platform and its role in the production/verification/distribution chain, including how games are designed, verified, released, and how feedback loops back to studios."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "37e6fb66-d69f-457c-ab23-7a8098e0848d",
      "label": "What EverPool is ¶7",
      "title": "What EverPool is — Games you design yourself",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## Games you design yourself\n\nOne of the more unusual things about EverPool is that a game does not have to come from a studio at all. Because the production path behind the platform is a system rather than a hand-built one-off, a person can design their own game through an interface: they describe the game they want, its theme and how it should feel, and the system generates a complete, playable game from that description, instead of it requiring an artist and a mathematician to build by hand. This is the capability the platform's patent-pending work refers to as AI-generated custom game instances, and it is one of the things that most sets EverPool and the system around it apart.\n\nThe part that matters for a talk about distribution, rather than a talk about novelty, is that a game designed this way is held to exactly the same standard as any other. It is not waved through because a person made it themselves. Its mathematics, the pool, the prize structure, and the payback, are verified by Sealed Jars before anyone can play it, the same verification every other game goes through. So designing your own game never means playing an unverified one. A custom game reaches a player the same way a studio's game does: verified first, then released, and removable in one step if something turns out to be wrong. The interface changes who can originate a game. It does not change the bar a game has to clear before a player can open it.",
      "document": {
        "id": "cmueb1x7h0001lliig8p67o49",
        "title": "What EverPool is",
        "summary": "The document explains EverPool, a browser-based live platform where players play play-money games with server-decided outcomes, detailing game types (finite-pool pull-tabs, real-time bingo, session bingo, and slots) and features like chat and daily credits. It is a conference-session style material describing the platform and its role in the production/verification/distribution chain, including how games are designed, verified, released, and how feedback loops back to studios."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "4527eb07-e9c9-4c28-a9eb-4dafc88aca47",
      "label": "What EverPool is ¶8",
      "title": "What EverPool is — Where EverPool sits in the chain",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## Where EverPool sits in the chain\n\nEverPool is one link in a chain that runs, under a single roof, from research all the way to the player and then back again. It helps to see the whole chain before looking at the one link.\n\nIt begins with Gaming Market Research, which produces primary-source market intelligence on prediction markets and charitable gaming: regulatory filings, revenue data, and legislative tracking. It reads the market and the rules from primary sources, and that intelligence informs what is worth building. Homeforge Games and Offphase Games build it. Sealed Jars then verifies it: it checks that a finished build does exactly what its own specification says it does, the pool, the prize structure, and the payback, before anyone downstream is allowed to treat it as real. The Institute for Emerging Gaming Markets researches regulation and compliance and studies how the rules are changing; it does not write those rules and it does not approve anything, so it is not a regulator, and nothing in this session should be read as if it were. EverPool takes the verified build and puts it in front of players. And G³E, the conference you are attending, is how people come to hear about any of it.",
      "document": {
        "id": "cmueb1x7h0001lliig8p67o49",
        "title": "What EverPool is",
        "summary": "The document explains EverPool, a browser-based live platform where players play play-money games with server-decided outcomes, detailing game types (finite-pool pull-tabs, real-time bingo, session bingo, and slots) and features like chat and daily credits. It is a conference-session style material describing the platform and its role in the production/verification/distribution chain, including how games are designed, verified, released, and how feedback loops back to studios."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "38bb8ad3-941d-49c0-a3fe-c8398b2533e4",
      "label": "What EverPool is ¶9",
      "title": "What EverPool is — Where EverPool sits in the chain",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "EverPool takes the verified build and puts it in front of players. And G³E, the conference you are attending, is how people come to hear about any of it.\n\nEverPool's link in that chain is the last mile. It takes from its upstream neighbor, Sealed Jars, a build that has been verified, and it owes its downstream neighbors, the players, a game that opens, runs, and behaves the way it was verified to behave. It also has something to give back up the chain. Because it is the place where real people actually play, EverPool is where the chain finds out whether the games do in practice what they were built and verified to do. That information travels back to the studios, which is how a chain that looks like a straight line from an idea to a player is really a loop. This session follows that last mile in order: what the platform receives, how a verified build becomes a released game, what happens when a problem turns up after release, and what the platform learns and sends back.",
      "document": {
        "id": "cmueb1x7h0001lliig8p67o49",
        "title": "What EverPool is",
        "summary": "The document explains EverPool, a browser-based live platform where players play play-money games with server-decided outcomes, detailing game types (finite-pool pull-tabs, real-time bingo, session bingo, and slots) and features like chat and daily credits. It is a conference-session style material describing the platform and its role in the production/verification/distribution chain, including how games are designed, verified, released, and how feedback loops back to studios."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "d6e78a31-b09d-412b-8962-64cf788acaf0",
      "label": "From verified build to player ¶1",
      "title": "From verified build to player — From verified build to player",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "# From verified build to player\n\n*EverPool, September 2026.*",
      "document": {
        "id": "cmueb23ka0004lliisejoybz2",
        "title": "From verified build to player",
        "summary": "- The document outlines the process by which a game moves from verification to delivery on EverPool, covering the handover, arrival checks, staged release, updates, withdrawals, and post-release handling. \n- It is a policy/documentation piece published by EverPool (dated September 2026) describing how verified builds are managed and released on the platform."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "1dbb06e5-4801-44fc-99a7-27eda170eb1f",
      "label": "From verified build to player ¶2",
      "title": "From verified build to player — The handover",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## The handover\n\nA game reaches EverPool only after Sealed Jars has verified it. What arrives is a complete build: the game itself, and the specification it was verified against, which describes the pool, the prize structure, and the payback that the verification confirmed. The handover is the moment a build stops being the studio's and Sealed Jars' concern and becomes the platform's responsibility, so EverPool does not simply take it on trust.\n\nOn arrival, the platform checks that the thing it received is the thing that was verified. A verified build carries its own identity and a fingerprint of its verified mathematics, and EverPool confirms that the game it is about to host matches that identity and that fingerprint. If they do not line up, the build is not accepted, and nothing goes any further. This check matters because verification and distribution are separate stages run by separate parts of the chain. Sealed Jars can prove a build is correct, but that proof is only worth something to a player if the build the player opens is the same one that was proven. The arrival check is what connects the two, and it is the first thing distribution is responsible for on its own.",
      "document": {
        "id": "cmueb23ka0004lliisejoybz2",
        "title": "From verified build to player",
        "summary": "- The document outlines the process by which a game moves from verification to delivery on EverPool, covering the handover, arrival checks, staged release, updates, withdrawals, and post-release handling. \n- It is a policy/documentation piece published by EverPool (dated September 2026) describing how verified builds are managed and released on the platform."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "4f0cb68e-cb70-4a59-bd27-b856b3ecc3a2",
      "label": "From verified build to player ¶3",
      "title": "From verified build to player — Release",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## Release\n\nAn accepted build is not yet a released game. Releasing it happens in deliberate steps rather than all at once. First the build is staged: it is placed on the platform and prepared, but it is not visible in the library and no player can open it. In that staged state it can be checked in position, running on the real platform exactly as a player would meet it, without any player meeting it yet.\n\nOnly after that does the build become a released game, when it is enabled and appears in the library. Enabling is a specific, gated action, not an automatic consequence of a build arriving. A game opens to players only once its identity and its verification line up and it has been checked in place, and for a new or unusual title that final step is often a controlled release watched together with the studio before the game is opened to everyone. The point of doing it in stages is that each stage can be stopped. A build can sit staged and never be enabled. That is a normal and safe outcome, not a failure, and it is much cheaper to hold a game back before release than to pull it afterward.",
      "document": {
        "id": "cmueb23ka0004lliisejoybz2",
        "title": "From verified build to player",
        "summary": "- The document outlines the process by which a game moves from verification to delivery on EverPool, covering the handover, arrival checks, staged release, updates, withdrawals, and post-release handling. \n- It is a policy/documentation piece published by EverPool (dated September 2026) describing how verified builds are managed and released on the platform."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "46d582d5-60ee-4b99-9d98-2c702ed92c14",
      "label": "From verified build to player ¶4",
      "title": "From verified build to player — Updates and withdrawals",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## Updates and withdrawals\n\nA released game is not frozen. When a game needs to change, the change comes as a new verified build, and it goes through the same handover and the same arrival check as the first one. The platform does not edit a live game in place; it replaces it with a build that has been through verification again. This keeps the same guarantee for an update that applied to the original release, which is that what players are getting is something that was verified and then confirmed to match on arrival.\n\nWithdrawal is the opposite motion, and it is deliberately simple. Pulling a game is a single step: the game is disabled, and it leaves the library and can no longer be opened. Because it is one action rather than a rebuild or a redeployment, it is fast, which is the entire point of designing it that way. A game might be withdrawn because a problem has been found in it, or because it is being retired, or because a studio has asked for it to come down. In every case the platform's ability to remove a game quickly is one of its core responsibilities, and it is independent of anything upstream: EverPool does not need to wait on the studio or on verification to take a live game down.",
      "document": {
        "id": "cmueb23ka0004lliisejoybz2",
        "title": "From verified build to player",
        "summary": "- The document outlines the process by which a game moves from verification to delivery on EverPool, covering the handover, arrival checks, staged release, updates, withdrawals, and post-release handling. \n- It is a policy/documentation piece published by EverPool (dated September 2026) describing how verified builds are managed and released on the platform."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "9feec53c-dc51-4d00-a43c-6c142998dd5b",
      "label": "From verified build to player ¶5",
      "title": "From verified build to player — When something goes wrong after release",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## When something goes wrong after release\n\nMost problems are meant to be caught before a game is ever opened to everyone, which is why release happens in stages and why a new title is often opened first in a controlled way and watched with the studio. In that window the platform and the studio are looking at the real game on the real platform, and if something is wrong, the title is held back and not opened further until it is fixed. When that happens, players never see the problem at all, because the game never reached them. Catching a problem in the controlled window is the ordinary, expected way things go right, even though it does not look dramatic.\n\nIf a problem is instead found in a game that is already live to everyone, the platform's answer is the withdrawal step described above: the game is pulled in one action and stops being playable while the problem is understood. It does not go back up on a promise that it has been fixed. It comes back the same way it arrived the first time, as a new build that has been verified again and that passes the arrival check again, so that a game returning from a problem carries the same proof as a game arriving for the first time. As of September 2026, that is the shape of the platform's response to trouble after release: hold it back before players are affected where possible, pull it in one step where not, and never return it without going back through verification. The chain that put the game in front of a player is the same chain that takes it back if it has to, and it runs in the same order in reverse.",
      "document": {
        "id": "cmueb23ka0004lliisejoybz2",
        "title": "From verified build to player",
        "summary": "- The document outlines the process by which a game moves from verification to delivery on EverPool, covering the handover, arrival checks, staged release, updates, withdrawals, and post-release handling. \n- It is a policy/documentation piece published by EverPool (dated September 2026) describing how verified builds are managed and released on the platform."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "8b0d9afd-f057-4ab0-9b59-27b78b173c10",
      "label": "Distribution and the rules ¶3",
      "title": "Distribution and the rules — Verified is not certified",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## Verified is not certified\n\nThis distinction is the one to get exactly right, and EverPool is careful about it because its own site once was not.\n\nEverPool's games are verified by Sealed Jars. Verification means each game's mathematics, its pool, its prize structure, and its exact payback, are checked against the game's own specification before it goes live, to confirm the game does what it claims to do. That is a fact about the build, it is done for every game, and it travels with the game wherever the game goes.\n\nCertification is a different thing entirely. Certification is a laboratory, in a named jurisdiction, testing a game at deployment against that jurisdiction's own requirements. It is specific to a place and it happens when a real-money operator deploys there. EverPool's games are verified. They are not certified, and EverPool claims nothing beyond verification. Calling a game \"verified\" is a claim the platform can stand behind and show the working for. Calling it \"certified\" would be a claim about a laboratory and a jurisdiction that has not happened, and so it is not a word EverPool uses about its games or their mathematics. Verified is the accurate word, and it is the one used here on purpose.",
      "document": {
        "id": "cmueb26tp0007lliih9w1f6z7",
        "title": "Distribution and the rules",
        "summary": "The document explains EverPool’s status as a play-money, entertainment-only platform, clarifies that it is not a real-money gambling product, and outlines its availability, verification (not certification), and platform responsibilities (disclosure, a daily credits cap, and an audit trail) as of September 2026. It is a company document titled “Distribution and the rules” from EverPool, dated September 2026, describing policies and practices."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "2438b038-1cf5-4bfb-bfc2-c381d7b0a195",
      "label": "Distribution and the rules ¶4",
      "title": "Distribution and the rules — What the platform is responsible for",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## What the platform is responsible for\n\nVerification is upstream, done by Sealed Jars. Distribution carries its own separate responsibilities, and they are the platform's alone.\n\nThe first is disclosure. Every page on the site carries the line that the platform is for entertainment only, so a player is never left to assume they are wagering real money. That statement is not buried; it is on every page, and keeping it there and true is EverPool's responsibility, not the studios' and not verification's.\n\nThe second is the daily-credits cap described earlier. Because each player's play credits are a daily allowance that refreshes on a reset and cannot be topped up with real money, there is a natural daily limit on how much anyone plays, built into the platform. It is not marketed as a protective feature, but it functions as one, and it exists because of how the play-money model is built rather than being added on afterward.\n\nThe third is the record. Every outcome on the platform is decided on the server and written to an audit trail, which means a result is not only fair by design but checkable after the fact. Distribution is responsible for keeping that record, and it is what lets the platform, rather than the player, be the thing that has to answer for an outcome.",
      "document": {
        "id": "cmueb26tp0007lliih9w1f6z7",
        "title": "Distribution and the rules",
        "summary": "The document explains EverPool’s status as a play-money, entertainment-only platform, clarifies that it is not a real-money gambling product, and outlines its availability, verification (not certification), and platform responsibilities (disclosure, a daily credits cap, and an audit trail) as of September 2026. It is a company document titled “Distribution and the rules” from EverPool, dated September 2026, describing policies and practices."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "6d94f115-7aa3-4749-a5ef-c5af370a35ec",
      "label": "Distribution and the rules ¶5",
      "title": "Distribution and the rules — What the platform is responsible for",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "Distribution is responsible for keeping that record, and it is what lets the platform, rather than the player, be the thing that has to answer for an outcome.\n\nAs of September 2026, those are the responsibilities the platform genuinely carries on its own: an honest disclosure on every page, a daily cap that falls out of the play-money model, and an audit trail behind every result. EverPool does not claim more than that, and where a responsibility belongs to a laboratory, a regulator, or a real-money operator, it says so rather than taking the credit for it.",
      "document": {
        "id": "cmueb26tp0007lliih9w1f6z7",
        "title": "Distribution and the rules",
        "summary": "The document explains EverPool’s status as a play-money, entertainment-only platform, clarifies that it is not a real-money gambling product, and outlines its availability, verification (not certification), and platform responsibilities (disclosure, a daily credits cap, and an audit trail) as of September 2026. It is a company document titled “Distribution and the rules” from EverPool, dated September 2026, describing policies and practices."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "1f864f9a-38f9-46a8-b678-1ac9a7552d3b",
      "label": "What the platform learns ¶2",
      "title": "What the platform learns — What gets measured",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## What gets measured\n\nBecause EverPool is where games are actually played, it is where the chain finds out what really happens, as opposed to what was planned. What it measures, it measures in aggregate. It looks at how a game performs against the targets it was verified to hit, so the observed payback and hit rate of a live game can be compared with the specification Sealed Jars checked, and a gap between the two is something worth knowing. It looks at which games get played and how much, so the library can be understood as a whole rather than a list. And it looks at how the multiplayer formats are used, the bingo rooms and session bingo and the chat that runs alongside them, because those only work if enough people are present at once.\n\nNone of this is about individuals. EverPool does not discuss individual players, accounts, or any player's data, here or anywhere. The measurements that matter to the chain are aggregate patterns, the behavior of the library and of formats, not the behavior of any one person, and as of September 2026 that is a firm line rather than a preference.",
      "document": {
        "id": "cmueb2b5w000alliihwlf5rtb",
        "title": "What the platform learns",
        "summary": "- The document explains what EverPool measures on its live platform in aggregate (how games perform against targets, which games and formats are used, and how multiplayer activity looks), while stating it does not consider individual players. \n- It also describes how those measurements feed back up the chain to studios and Gaming Market Research, forming a loop, and notes that EverPool hosts prototypes and experiments with clear labeling and verification."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "4f7f889a-af08-4c35-9082-c3d7b444302c",
      "label": "What the platform learns ¶3",
      "title": "What the platform learns — How it feeds back",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## How it feeds back\n\nWhat the platform learns does not stay on the platform. It travels back up the chain the session opened with. The studios, Homeforge Games and Offphase Games, built the games, and EverPool's aggregate play data goes back to them, showing which of their ideas hold up in front of real people and which do not, and informing what gets built next. Gaming Market Research sits at the front of that chain, reading the market and the rules from primary sources to help decide what is worth building; EverPool supplies the other thing that no filing or revenue figure can, which is how a finished game actually plays once real people have it. So the chain that runs from research through the studios and Sealed Jars to the player is not a one-way street ending at release. It is a loop, and EverPool is the turn in it, the point where a plan becomes evidence and the evidence goes back to the studios who make the next plan. That is the loop this session promised to close, and the platform is what closes it.",
      "document": {
        "id": "cmueb2b5w000alliihwlf5rtb",
        "title": "What the platform learns",
        "summary": "- The document explains what EverPool measures on its live platform in aggregate (how games perform against targets, which games and formats are used, and how multiplayer activity looks), while stating it does not consider individual players. \n- It also describes how those measurements feed back up the chain to studios and Gaming Market Research, forming a loop, and notes that EverPool hosts prototypes and experiments with clear labeling and verification."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    },
    {
      "id": "9bc0c7a7-0dd9-4dde-bcf1-27fcb9f434c4",
      "label": "What the platform learns ¶4",
      "title": "What the platform learns — Prototypes and experiments",
      "source": "EverPool, September 2026",
      "pageNumber": null,
      "text": "## Prototypes and experiments\n\nNot everything on EverPool is a finished product, and the platform is deliberately a place where unfinished things can be tried in front of real players. Some games are prototypes, and some of the technology behind them is experimental. Session bingo, described earlier, is a clear example of a format that is still finding its shape, and Offphase Games' newer, story-led games are the leading edge of what is being tried, with more of them on the way.\n\nA player is not left to guess which is which. An experiment is presented as an experiment, marked as new or as coming, rather than dressed up as a settled part of the library, so a person can tell when they are trying something early. And crucially, being experimental does not lower the bar that matters most: a prototype is still decided on the server, still leaves an audit trail, and still goes through verification before it reaches players, exactly like a finished game. The experiment is in what the game does and how it plays, not in whether its outcomes can be trusted. That is what lets EverPool be both the shop floor and the test bench at once: it can put a new idea in front of people without giving up the guarantee that makes anything on the platform worth playing in the first place.",
      "document": {
        "id": "cmueb2b5w000alliihwlf5rtb",
        "title": "What the platform learns",
        "summary": "- The document explains what EverPool measures on its live platform in aggregate (how games perform against targets, which games and formats are used, and how multiplayer activity looks), while stating it does not consider individual players. \n- It also describes how those measurements feed back up the chain to studios and Gaming Market Research, forming a loop, and notes that EverPool hosts prototypes and experiments with clear labeling and verification."
      },
      "knowledgeBank": {
        "slug": "everpool",
        "name": "EverPool"
      }
    }
  ]
}