Game Catalog Readiness¶

Swarm Hosts keeps every supported game definition in the internal catalog, but only games marked as public-ready appear on public launch surfaces. Readiness metadata makes that choice explicit instead of relying on route-specific allowlists.

Each catalog game carries these fields:

Field	Meaning
public_ready	Whether the game may appear on public launch surfaces.
validation_status	The current support state for launch readiness.
requires_credentials	Whether launch needs user account credentials, such as Steam credentials.
requires_license	Whether launch needs a user-provided server token, license key, or similar entitlement.
readiness_notes	Short operator-facing explanation for the current state.

Statuses¶

Status	Meaning
flagship	Primary public experience with the strongest current validation and product support.
validated	Allowed on public launch surfaces after focused deployment validation.
needs_validation	Catalog definition exists, but current live validation is not strong enough for public launch.
credential_gated	Launch depends on user-provided account credentials, server tokens, or license keys.
needs_repair	Known image, config, or runtime issue must be fixed before launch.
hidden	Intentionally hidden from public launch while retained for internal use or existing deployments.

A game is public-launchable only when public_ready is true, validation_status is flagship or validated, and neither credential nor license gating is set.