It is a permanent identifier for a game independent of its name, domain, owner or publisher. Future transfers to a separate company won't require renaming the original project.

First create a browser edition in Game Builder. Initialize source from that immutable edition. Save changes with revision locking, then send the reviewed source to the build queue. A successful compile is not a game QA certificate; inspect the ZIP and test it on target devices before publishing.

Rules add collectible score bonuses, limited health recovery, hazard shields and score milestone rewards. Each rule has strict allowed values. No model-generated JavaScript runs on the VPS. Saving rules affects future builds only; published versions remain unchanged. This is a bounded game-authoring feature, not free-form game code generation.

This initial release checks the application, database and local storage. External uptime checks, multiplayer metrics, player crash analytics, resource alerts and incident response tooling are tracked as future requirements.

Upload a trusted signed ZIP. The server verifies its Ed25519 signature, file hashes and approved source paths. A separate VPS update agent rebuilds, smoke-tests, backs up the database, activates and checks the application. If activation fails it attempts application rollback. No SSH commands are needed for routine code updates.

Limits: Engine infrastructure, dependencies, arbitrary scripts and database migrations cannot be updated by this code-only channel. Those require a separately reviewed infrastructure upgrade. Recovery from major outages may still require VPS access.