> For the complete documentation index, see [llms.txt](https://whitepaper.gamegpt.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.gamegpt.gg/02-platform-overview.md).

# Platform Overview

GameGPT is two products and a pipeline between them.

* **The Builder** is the supply side. Creators describe a game, the engine generates it, they tune it in the workspace and submit it for review.
* **The Arcade** is the demand side. Players find, play and compete in published games, for free or for prizes.
* **The publishing pipeline** sits in the middle. Every game that reaches players has been reviewed by a person, scanned, signed and sandboxed.

The Builder generates supply, the Arcade generates demand, and the economy (credits, subscriptions, tournaments, rewards) moves value between the two. The sections below cover each in turn.

## Security model

Generated code running in front of real players has to be trustworthy. GameGPT treats that as a platform feature, not an afterthought:

* **Human review.** Every submitted game goes into a moderation queue. A reviewer reads the actual game code and approves, rejects or requests changes. Every decision is recorded with notes in an audit trail. Nothing reaches players without passing a person.
* **Static safety scan.** Before publication the game code is scanned for anything that could reach outside the game (network calls, storage access, escaping the page). Games that fail do not publish.
* **Signed, immutable publication.** On approval the game is bundled with a locked-down runtime and a strict content security policy, uploaded to an immutable location, and described by a manifest that is cryptographically signed. The Arcade verifies that signature on its servers and again in the player's browser before a game loads. A tampered or unsigned game cannot reach a player from either direction.
* **Sandboxed play.** Games run in a fully isolated frame with no network, no storage and no access to the page around them. They talk to the Arcade only through a narrow message bridge (ready, score, game over, replay).
* **Verified scores.** Each play session gets a one-time secret; score submissions must present it. That is how a leaderboard score earns its "verified" status, and it is the foundation tournaments are built on.
* **Auditable money.** Every credit or reward movement is a row in an append-only ledger with idempotency keys, so balances are auditable and double-charges are structurally impossible.