Arcoverse Creator Console

Standard motion keeps console review readable while preserving the same public route context.

This compares saved public config against the Creator Console draft state. It does not read coordinates, secrets, environment files, provider keys, private accounts, or private evidence.

This board tracks the public-facing matrix blocks only: shell, motion, World Gate, globe reveal, and public Atlas cards. It excludes coordinates, vault data, private evidence, private accounts, and provider secrets.

This board tracks the public flow after the spine: Archive review, chat/community, memberships and credits, Bullseye campaigns, future expedition briefings, Navigator, and Creator Console. It excludes coordinates, vault data, private evidence, live payments, and provider secrets.

This workbench previews founder changes, build continuity, revenue offers, and Navigator handoffs without publishing live payments, signing assets, changing DNS, or touching coordinate material.

Preview ledger only. Real money, Campaign Credits, collectibles, refunds, and account identity must reconcile against payment processors, provider records, and an append-only server ledger.

Saved-record sync is read-only here and uses local preview records only.

Reputation is an advisory community-quality signal only. It does not grant coordinate access, payment privileges, private-record access, or final expedition control.

Challenge runs are public completion records. They can feed player history, Campaign Credit preview, and reputation review, but do not process real payments, 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, Campaign Credits, private accounts, or assets.

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

AI may draft broadly, but publishing stays gated by page type. Reveal pages, Campaign Credit pages, payment pages, expedition pages, collectibles, press pages, and anything implying private proof require founder approval.

Export downloads these public offer settings as JSON for backup or migration. Import brings in a JSON pack of money variables. Store payment secrets, private keys, custody 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. Live checkout, webhook, refund, tax, and portal actions stay behind Render/provider gates and exact operator approvals.

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

Open Legal Policy Review Board

Draft copy here is a launch planning map only. Attorney-reviewed final pages are required before live subscriptions, paid Archive fees, collectibles, Campaign Credits, or future expedition campaign backing.

Export downloads the current games, challenges, clues, timers, costs, rewards, and status settings as JSON. Import brings in a public 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, custody 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 and append-only ledgers. This app must not hold private keys, signing authority, live provider secrets, or custody assets.

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

Deployment hardening is a launch checklist only. It does not deploy, change hosting, read environment secrets, process payments, sign assets, 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 founder approval before launch. It performs no live payments, asset 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, private accounts, or payment credentials.

Reveal ordering stays public-safe: campaign labels, return targets, and motion state can change here without exposing coordinates, private evidence, or operator-only route details.