Public Go-Live Board

This reads generated launch artifacts only. It does not read raw coordinates, service secrets, payment card data, or private member records.

This panel shows which public-facing lanes are ready, still short, and backed by implementation artifacts.

This panel folds the generated build check into the public go-live decision. It cannot deploy, approve go-live, enable live billing, or expose coordinate material.

This probe reads public health, saved records, billing audit, payment help, and message setup endpoints. It never reads secret values, card data, passwords, wallet keys, or raw coordinates.

This snapshot turns the probe into a founder-readable view: what was checked, what is saved, and what should happen before public go-live.

Use this after every pushed checkpoint. It records that source, host, the public page, and saved launch signals point to the same version.

This reads the saved release-check packet. It does not create a Git tag, trigger Render, enable live Stripe, approve public go-live, or expose coordinate material.

This panel keeps the first sales focused on memberships and Archive review credits while credits, supporter briefing tiers, collectibles, and the Public Help Path stay public-safe. It does not send member messages, create checkout sessions, mutate services, launch value claims, or access coordinates.

This runway follows the same order visitors experience: start, chat, play, research, support, and campaigns. It keeps the prioritized public spine and Public Help Path visible without revealing coordinates, selling treasure access, sending messages, or making value or expedition-access promises.