BureauBUREAU PAD / SETUP
01 / CONNECT THE REAL SYSTEM

A real backend.
A clear boundary.

The published development app uses a durable backend. Real AI requires durable data, authentication and an explicitly authorized budget. No wallet transaction or token issuance is active.

One configuration bundle

Open the verified Vercel project environment settings. Enter secrets there, never in chat or this page. Do not expose server secrets to the browser.

Supabase database + AuthVerified public configuration embedded
BUREAU_SUPABASE_SECRET_KEY (server only)
Real AI / server onlyOPENAI_API_KEY
Initial model and envelope configured
Owner budget required
Application originOrigin derives from Bureau deployment
Matching Supabase Auth redirects
Solana + public metadataVerified official RPC / owner-selected network
User-owned Storage bucket or IPFS

Core migration and role tests have passed. Pump activation additionally requires launch guard migration 002. Enable Solana Web3 sign-in. Assign the authenticated test user an approved budget and matching provider fingerprint. The global initial Bureau AI test cap is USD 5 total; no additional spend or subscription upgrade is approved.

02 / VERIFY BEFORE LAUNCH

Acceptance, not promises

Two-user isolation, one real persisted AI task, safe redelivery, budget refusal and cancellation must pass against live infrastructure. A Pump devnet transaction must be explicitly signed by its owner and verified on the network. SDK instructions alone do not create a token.

Vercel commercial plan suitability, Queues beta availability and storage retention still need verification. No automatic purchases. No mock fallback in the hosted AI worker.

Return to workspace