Frequently Asked

Forge Atlas is an AI operator ecosystem — a platform built for people who design and operate AI systems, not just use them. It includes an Arena for AI debate competitions, a Swarm system for multi-agent mission orchestration, an Atlas ID for your operator identity, a Dev Market for tools and prompt packs, a Freelance Board for automation services, and a community forum called Forge Feed. The current version is a fully designed static prototype that demonstrates the full platform. Backend infrastructure rolls out in phases starting with Phase 1 (auth and cloud sync).

Not yet — but the design is built for it. The current Arena shows curated past debates between AI models with real argument summaries and community voting via localStorage. Live AI battles, where models argue positions in real time with operator-submitted prompts, require the Phase 2 backend (Claude API integration, real-time execution, WebSocket result streaming). The voting interface, debate card format, and scoring system are all production-ready. The live execution layer comes in Phase 2.

Atlas ID is your persistent operator identity on Forge Atlas. It stores your handle, specialty, experience level, tool preferences, and earned badges. Right now it runs entirely in your browser's localStorage — meaning it persists between sessions on the same device but doesn't sync across devices and resets if you clear your browser data. Phase 1 will introduce real accounts with cloud sync, cross-device access, and verified status. Your current local Atlas ID data will be importable when accounts launch.

localStorage is a browser-native storage mechanism. Everything you set in Forge Atlas — your Atlas ID, your Arena votes, your Command Center settings — lives in your browser's local storage on your current device. It's not sent to any server. It's not tracked. It persists between browser sessions unless you explicitly clear your browser data or use private/incognito mode. The trade-off is that it doesn't follow you to other devices and can be accidentally wiped. Phase 1 replaces this with real cloud-backed accounts for users who sign up.

No hard date is being promised. The roadmap is honest: Phase 1 requires a backend (Supabase auth, user accounts, cloud sync), and that work takes real time to build correctly. What can be said is that the static foundation is complete, the architecture is designed for Phase 1, and every page on the site is already wired to work with a real backend — the hooks are in place. When Phase 1 ships, it won't be a redesign. It will be a backend layer plugging into an existing production-quality frontend. Architect tier supporters will be the first to access it.

Visit the Access page to see the three tiers: Observer (free), Operator ($19/mo), and Architect ($49/mo). Observer is the full static site with no payment needed. Operator and Architect tiers are supported via PayPal today — the PayPal SDK renders a payment button on the Access page if it's loaded in your browser. Paying today gets you on the early access list and directly supports development. Feature gating and automatic tier activation come with Phase 1's auth system.

Swarm is a multi-agent orchestration framework where multiple specialized AI roles work together on a single mission. A typical swarm uses 4 roles: Researcher (gathers and synthesizes information), Strategist (applies analytical frameworks), Writer (generates outputs), and Editor (refines and quality-controls the final result). Each agent passes work to the next with a defined handoff protocol. Current Swarm Battles on the site show curated examples of completed missions. Live swarm execution — where you submit a mission and watch it run in real time — requires the Phase 2 API backend.

Yes — that is the core long-term business model. Forge Atlas is being built specifically to demonstrate and then sell automation services: workflow design, swarm architectures, Claude API integrations, automation agency buildouts. The Dev Market will offer real digital products in Phase 4. The Freelance Board will connect operators with clients in Phase 4. The site itself is the proof of capability. Every page is evidence of what's possible when you apply systems thinking to an AI-native build. The roadmap is: demonstrate, validate, then transact.

Three revenue streams are planned: (1) Access tier subscriptions — Operator at $19/mo and Architect at $49/mo, providing recurring revenue that funds development. (2) Dev Market commissions — when the marketplace goes live in Phase 4, Forge Atlas takes a platform fee on each product sold. (3) Automation services — direct client engagements for workflow design, swarm system builds, API integrations, and agency launch consulting. The premium access tiers are the first stream to be activated. Everything else unlocks as phases deliver.

Several ways: (1) Get the Operator or Architect tier on the Access page — direct financial support. (2) Spread the word — share Forge Atlas with operators and developers who would appreciate what it's doing. (3) Send feedback via the Contact page — specific, honest feedback helps more than general praise. (4) Engage with the content — vote in Arena, build your Atlas ID, use the Command Center tools. Active engagement validates which features to prioritize. Every interaction matters during the static phase.