Frame the decision.
You provide a question, an audience, optional context, and an alternative to compare. Foundate uses those inputs—not secret audience data—to frame an exploratory exercise.
Foundate is built to widen your thinking.
Not to tell you it can predict the world.
You provide a question, an audience, optional context, and an alternative to compare. Foundate uses those inputs—not secret audience data—to frame an exploratory exercise.
The agent creates four or six explicitly fictional personas with different priorities and concerns. These are creative lenses, not digital twins of real people or a statistically representative sample.
A language model simulates a moderated discussion. Personas challenge the proposal, react to each other, and consider an alternative. All voices come from one underlying model, so their apparent agreement is not independent evidence.
The agent synthesizes tensions, assumptions, option trade-offs, and a concrete experiment. Ask follow-up questions to examine the result. Export a Markdown brief or revisit saved sessions on this browser.
No. Foundate is an independent project by James He. It is inspired by social simulation, but does not use or reproduce the proprietary systems, datasets, research validation, or enterprise services of Artificial Societies.
Foundate follows a three-stage workflow: plan a diverse fictional room, simulate a discussion, and synthesize a decision brief. Each stage uses the preceding result. It can then answer follow-up questions using the brief. It cannot take external actions, independently verify facts, or run a real-world experiment.
The default backend uses Google Gemini 4 Argon through RouterHub. The site owner can select another RouterHub Chat Completions-compatible model in the server configuration. The sample run is prewritten and clearly labeled; it makes no AI calls.
Completed briefs are saved locally in this browser when you enable “Save on this device.” You can delete them from the studio. Temporary server session data enables the three-step workflow. Accounts are optional and support email/password or verified Solana message signatures. Accounts do not sync briefs between devices; private SQLite storage holds account identity only.