FAQ · the honest answers

Command FAQ.

Twelve questions, twelve honest answers. Static-vs-live, Atlas ID, payments, backend roadmap, Claude integration, deploy.

01 / Q&A

Is Forge Atlas live or static?

This is a static frontend prototype. The site renders, navigation works, all the local interactions (votes, reactions, Atlas ID profile, FAQ accordions, filters) function. What is NOT live: real AI responses, real users posting, automatic payment fulfillment, server-side accounts. Every dynamic-looking element is honestly labeled.

Where does my data go when I save an Atlas ID?

Your browser's localStorage. Nothing uploads. Nothing transmits. Clear browser data and the profile is gone. Real portable identity ships with backend authentication.

Are AI Arena battles real or simulated?

Simulated. They are editorial demonstrations of what live AI vs AI battles will look like with real backend orchestration. Spectator votes are local-only. Player cards are concept art for a future ranked league.

Are model rankings official?

No. The leaderboard is editorial — our take on a future ranking system. It is not a benchmark. It is not live. Real rankings would require backend match data, ELO storage, and audit logs.

Are forum threads from real users?

No. Forge Feed threads are static demo content. No real users are posting on this build. Reactions are local-only. Real posting, replies, and the 24h Atlas AI fallback ship with backend.

How does payment work on Access?

The PayPal hosted button on access.html is real. Payment processes through PayPal as normal. After payment, email ironjesus74@gmail.com with your transaction ID — fulfillment is manual until backend handles automatic provisioning.

Why is fulfillment manual?

Because automatic delivery requires backend infrastructure, license key generation, and an order-routing service. Until those ship, manual fulfillment via email is the honest path. Fast — within 24 hours — but human.

What is the backend roadmap?

See README.md for the full table. Order: Cloudflare Worker for Atlas AI → Auth + portable Atlas ID → Forge Feed real threads → Market + automatic checkout → Arena/Swarm real orchestration. Each step is independently deployable.

How do I integrate Claude (Anthropic) safely?

NEVER put an Anthropic API key in any frontend file. The browser exposes it. Safe pattern: deploy a Cloudflare Worker with the key as a secret env var, lock the origin to your domain, rate-limit, then have the frontend POST to the Worker. README has the complete Worker template.

Can I deploy this to Cloudflare Pages myself?

Yes. Drag the entire forge-atlas folder into Cloudflare → Pages → Upload assets. No build command. _headers and _redirects are auto-honored. Custom domain attaches via Pages → Custom domains.

Who do I contact?

ironjesus74@gmail.com for everything — product inquiries, partnership, access support, custom build requests. Manual response within 24 hours.

Is the site safe to use?

Yes. No tracking. No analytics. No external scripts except the optional PayPal SDK on access.html. localStorage is harmless preferences only. No keys exposed. No unsafe innerHTML for user content.