Operator Command Center Lite

This compares backend public config against the Command Center authoring state. It does not read coordinates, secrets, environment files, provider keys, wallets, or private evidence.

This workbench is proof and planning only. It previews public-safe operator changes without publishing live payments, signing wallets, changing DNS, or touching coordinate material.

Prototype ledger only. Real money, BB ownership, NFT ownership, refunds, and account identity must be reconciled against payment processors, wallet/indexer records, and an append-only server ledger.

Backend sync is read-only and uses local mock records only.

Reputation is an advisory community-quality signal only. It does not grant coordinate access, treasury authority, wallet permissions, payment privileges, or final expedition control.

Challenge runs are public-safe completion records. They can feed player history, BB utility preview, and reputation review, but do not process real payments, treasury moves, wallet transfers, or coordinate access.

Planning map only. Production storage should use role-based access, append-only ledgers for money/BB events, provider reconciliation, backups, audit logs, and no secret coordinate fields in the DAPP database.

Backend schema sync is read-only and admin-gated. Use the local server URL for live sync.

Ledger summary is calculated from append-only mock events. It does not custody money, BB, wallets, or treasury assets.

Admin roles control Command Center actions only. They do not grant coordinate-vault access, wallet private keys, treasury authority, or payment secrets.

AI may draft broadly, but publishing stays gated by page type. Reveal pages, BB/token pages, payment pages, expedition pages, NFTs, press pages, and anything implying private proof require operator approval.

Export downloads these public-safe settings as JSON for backup or migration. Import brings in a JSON pack of public-safe money variables. Store payment secrets, wallet keys, contract owners, treasury controls, and API keys outside the DAPP.

No local checkout test has been run in this browser session.

No live Stripe key, webhook secret, customer ID, card number, or environment secret belongs in this DAPP. Use Stripe CLI and test-mode dashboard records only when real integration begins.

Current persistence is local JSON. Production migration should move records to managed database tables, then prove backup, restore, rollback, and coordinate exclusion.

Draft copy here is a launch planning map only. Attorney-reviewed final pages are required before live subscriptions, paid Archive fees, NFTs, token utility, or expedition participation offers.

Export downloads the current games, challenges, clues, timers, costs, rewards, and status settings as JSON. Import brings in a public-safe JSON challenge pack. Coordinates and private evidence stay out of game definitions.

Analytics here are public-safe operating signals from prototype records. Production analytics should use event streams, privacy rules, consent, and reconciled ledgers.

These controls define what real accounts must support before launch. They do not store credentials, session secrets, payment credentials, or private user evidence.

Provider decisions document external systems only. Stripe, auth, hosting, analytics, storage, and database choices are evidence records here; live secrets, private keys, treasury controls, and environment values stay outside this DAPP.

Lifecycle controls define account states and permissions. They do not store credentials, identity documents, billing secrets, or private evidence.

Reconciliation matches DAPP activity to provider records, wallet/indexer records, and append-only ledgers. This app must not hold private keys, signing authority, live provider secrets, or treasury custody.

These are review queues only. They do not process charges, issue refunds, sign transactions, move BB, or custody assets.

Deployment hardening is a launch checklist only. It does not deploy, change hosting, read environment secrets, process payments, sign wallets, or access coordinate material.

Runbook records are launch planning evidence. They do not deploy, change DNS, read environment secrets, or access coordinate material.

This gate tells us what is still mock, what is production-ready, and what needs operator approval before launch. It performs no live payments, wallet signing, hosting changes, legal claims, or coordinate access.

Diff preview compares public-safe browser state against backend config. It summarizes changed sections only; it does not read coordinate vaults, secrets, wallets, or payment credentials.