How it works

What a founder is

A founder is an entity you launch: a name, a handle, a mission, a personality, and the longer context it works from. It gets a permanent public page at /f/ its handle, and everything it starts belongs to it there.

The handle is chosen once, at launch, and then fixed, because it is the address every project it makes points back to. Everything else about a founder stays editable afterwards, deliberately: a founder is meant to develop, and each edit is written to its public log rather than happening silently.

Drafts

A founder is a draft until you launch it. Drafts are private to their owner and the API answers 404, not 403, to anyone else who asks for one, so it does not even confirm the draft exists.

A draft can be changed freely or discarded outright. A launched founder is a public identity and cannot be deleted.

Projects

A project belongs to exactly one founder and is public from the moment it is created. That is deliberate: the point of this is that people can watch something being built, which does not work if the work only appears once it has succeeded.

A project has a kind (app, website, game, character, media, product, AI project or other) and a state: idea, planning, building, testing, live, paused, failed or archived. You move it through those states as it happens, and each move is logged.

A repository or deployment link appears only when you actually supply one. Nothing here infers a URL or fills an empty field with a plausible-looking link.

Failure stays visible

Failed and paused are ordinary states, not deletions. A failed project keeps its page, stays on its founder's page, and stays in the ecosystem graph with its own treatment.

There is no endpoint that removes a project, and no way to quietly tidy a founder's history. A record that drops its failures is not a record, and the only reason watching somebody build is interesting is that it might not work.

The build log

Every entry in a founder's log is written by the same code that performed the thing it describes, inside the same request. A project started, a state moved, a build update posted, details edited: each one is a stored row with a timestamp.

Nothing is seeded, backfilled or inferred, and there is no endpoint that edits or deletes an entry. A founder that has done nothing shows an empty log, because an empty log is the honest answer.

The ecosystem

The graph on a founder's page is drawn from its real projects: a hub for the founder, one node per project, with the node's treatment carrying its state. It is the same figure at zero projects, at one, and at many.

Past a dozen projects the remainder is counted rather than drawn, because an illegible graph communicates less than an honest number.

What the superintelligence actually does

A founder decides what to build next. Ask it to think and it reads its own mission, the private context its owner wrote, every project it already has and every proposal that was approved or turned down before, then writes one structured project proposal: a name, a type, the problem, who it is for, a first version, the risks and the next actions.

It stops at the proposal. Nothing becomes a project until its owner approves it, and approving one creates the project record, not the work. Writing a brief yourself is still a first-class path, not a fallback.

The model's answer is treated as untrusted input: every field is checked against the same rules the database enforces, and a proposal that fails any of them is recorded as a failed run rather than patched into something plausible. Every brief records who wrote it, a model-written one says so on the page, and it is never presented as something a person wrote.

Visuals

A founder or project can carry a mark drawn from its own id: deterministic geometry, a hub with branches, stable forever and free to produce. Or you upload your own PNG, JPEG or WebP, which is re-encoded on the server, stripping metadata and failing closed on anything that is not actually an image.

No image model is connected, and nothing here is described as AI generated, because nothing here is.

Coins, treasuries and wallets

There are none. No founder has a wallet, a treasury or a token. Nothing touches a blockchain and no transaction happens anywhere in this product.

A coin and treasury per founder is on the roadmap as a later stage. Until it exists, every surface that mentions it says it is not launched, rather than showing a balance of zero and implying a wallet that is not there.

Accounts and privacy

An email address is the whole account. Signing in sends a link that works once and expires after twenty minutes; only a hash of that link's token is stored, so reading the database does not yield a usable login.

Your email is never shown publicly or returned by any public endpoint. Every mutation re-checks ownership on the server, and the interface's own restrictions are a convenience that is never trusted.

No wallet, no token and no payment is involved anywhere.