# Qubicbox Simulations — Vercel deployment guide

## Current status

The Vercel project is **Strategy**, connected to Qubicbox/Strategy-Game. Application source is on main; the approved catalogue/brand change was merged on 3 November 2026. Vercel reports the production build succeeded, and public routes load at [sim.qubicbox.com](https://sim.qubicbox.com).

A read-only GET to /api/room?route=bootstrap returned HTTP 503 on 3 November 2026. The API source requires DATABASE_URL. Vercel settings and logs were not inspected, so the exact runtime cause is unconfirmed. Build success does not prove room or database availability.

## Public build

The allowlisted output contains:
- / — Qubicbox Simulations catalogue.
- /harvest-exchange/berrynomics/ — Berrynomics shared room.
- /harvest-exchange/tomanomics/ — non-playable concept page.
- /room.html — compatibility route.
- /api/room — hosted room API.

The standalone facilitator page and local JSON state are excluded. Build settings in vercel.json: repository root, npm run build:vercel, output public, Node 20 or later.

## Runtime configuration

The hosted API uses Neon Postgres and requires DATABASE_URL, HL_SETUP_SECRET, and HL_ROOM_ID (defaults to main). The current schema is a room-state JSONB table and login-attempt table; runtime table creation is not a migration system.

For tests, use an isolated staging database and Preview-only variables. Do not use production data. Never place credentials in chat, GitHub, or public build output. The project directive prohibits new paid services without founder approval.

Check Production environment variable names and sanitized function logs to diagnose the 503; do not expose the variable value. Restore gameplay only with an approved database target. Before testing, create or identify a separate staging database and prove write/read/restart behavior there.

## Custom domain

sim.qubicbox.com is attached and serves the catalogue over HTTPS. Namecheap manages DNS. Preserve unrelated records and do not change root-domain nameservers for this subdomain.

## Safe release sequence

1. Develop on a review branch and inspect Vercel Preview.
2. Use isolated staging data for writes and end-to-end tests.
3. Back up and test restore before any production migration.
4. Review security, financial integrity, privacy, and accessibility.
5. Obtain founder approval before production changes.
6. After release, verify the public pages and hosted API separately.