# Launch a playable Testnet game

Managed blueprint runtime v2026-11-01.1. Four reviewed game engines run in an
isolated Node service. This initial package format is declarative JSON, not
arbitrary executable code, an npm dependency upload or a general repository runner.
External custom games continue to use the public Node/Python source SDK.

1. Sign in with your existing Hybrid-ID, open /studio and create your workspace
   and game. No replacement identity, password sharing or email-based merge.
2. Open Deploy. Choose Signal Rush, Drone Dash, Robot Duel or Core Control.
3. Set an unused immutable version, match length (20–90 seconds), bot difficulty
   and palette. Download or upload arena-game.json using package.schema.json.
4. Deploy to Arena. Only the workspace owner can do this. Deployment registers
   the manifest and rotates this game's source key; other games are unaffected.
5. Open the creator-preview lobby from Deploy. Create a match, inspect its
   practice desk, then start. The server owns the 100ms simulation, scoring,
   cooldown and final outcome. One authenticated player competes with a labeled bot.
6. Review Matches & evidence. Await complete native Testnet confirmation, then
   publish the exact release from Releases. Deployment alone does not publish.
7. Share the /testnet/<game> page. Public feedback and promotion votes remain
   release-bound. They do not certify independent acceptance or activate Mainnet.

Original deployment/input request IDs survive response loss; recover the original
request before changing terms. State, source facts and exact batch receipts persist
across service restart. The clock pauses while the host is stopped or source
acceptance is delayed. There is no wall-clock catch-up that invents missing play.
Stop cancels unfinished matches, preserving receipts and cancellation evidence.
Rollback selects a retained runtime; publishing the restored release is a separate
explicit action. Never roll back a source journal or rewrite a completed result.

Supported packages contain only schema, blueprint, version, duration_seconds,
bot_difficulty and palette. No paths, scripts, dependency hooks, remote URLs or
HTML are accepted. The source credential stays encrypted in the private game host.
The public renderer receives no secret, real name, Hybrid-ID identifier or seed.
Host access is a protected Unix socket, not a public administrative port.

Current capacity is eight simultaneous matches across twenty hosted games, at
most two matches per game. Existing source daily/history limits also apply. The
operator can increase capacity after measurements; no new paid server is implied.

Practice desks use finite simulated liquidity and separate nonredeemable test
units. Playing and predicting is allowed in this Testnet experience. Source
receipts, Testnet inclusion and game fairness are distinct. No funding, actual
wallet submission, real earnings or Mainnet deployment is activated.

## Agent workflow

GET /api/studio/launch-kit?publisher=<publisher>&game=<game> with the creator's
own browser session to download exact scoped context. Developer credentials do
not inherit deployment/source-key/publishing authority. Prepare the package with
`arena blueprint new-game --template drone-dash`, then run
`arena check-package new-game/arena-game.json`. Upload in Studio; no secret belongs
in the package. Custom game logic beyond these engines uses the source SDK and
its independently hosted authoritative server, pending reviewed custom hosting.

## Independent pilot

Creators publish genuine releases, share their game page, and collect public
feedback/votes. Record a private pilot report in Creator tools with completion
time and blockers. Reports are self-reported and unverified. An operator smoke
test or a bot match is never represented as an independent creator/player trial.

The agent kit pins SDK alpha.6 and the exact retained managed deployment manifest.
Source-signing and publisher credentials remain private. A ready kit is integration
context, not permission for an agent to deploy, publish or move funds.

## Public reference games and acceptance

All four first-party references are now listed at https://hybrid-arena.com/testnet:

- [Signal Rush](https://hybrid-arena.com/testnet/d0780cefc239c8d2051fe326)
- [Drone Dash](https://hybrid-arena.com/testnet/a3ab08dc05aa35376e71e535)
- [Robot Duel](https://hybrid-arena.com/testnet/5dc86fb96755633396a26e07)
- [Core Control](https://hybrid-arena.com/testnet/872c4f2ceff8a2f583dda8ff)

Read the [dated acceptance record](deployment.json) for exact completed matches,
public proof IDs, independently checked Explorer links, SDK release and runtime
checks. These are explicitly synthetic first-party commissioning runs. Sign in to
create your own match; anonymous visitors may watch. A reference listing is not a
claim of an independent creator trial or endorsement of game fairness.

Native proofs are available on the single-host, single-operator non-value Testnet.
Actual independent creator participation remains pending. Funding, wallet payouts
and Mainnet activation remain disabled.
