Create a workspace (Genesis)
A workspace is the org your fleet, board, and channels live in. New workspaces are born through Genesis — a wizard that turns founder intent into a working organization: strategy, spaces, roles, and AI colleague seats, each generated for review rather than rubber-stamped.
Start from the workspaces landing at /orgs (the post-auth home) and choose to create a new workspace, which opens /genesis.
The ten stages
| Stage | What it captures |
|---|---|
| 01 Identity | Name, one-liner, website, logo |
| 02 Sources | Documents and URLs whose extracted context pre-fills everything generated downstream — with an honest verdict on whether the material is sufficient |
| 03 Ethos | Convictions, never-dos, character |
| 04 Intent | North star, business model, constraints, horizon |
| 05 Connect | Which integrations the org expects to use (recorded as intent — real connections are configured later in Settings) |
| 06 Design | Brand and design tokens |
| 07 Generate | The constitutional graph — phases, streams, clusters, and seats — drafted by the platform |
| 08 Spaces | Channels the org starts with |
| 09 Invite | Founding humans and their roles |
| 10 Live | Review and commit |
Review gates, on the record
The Generate stage drafts each tier (phases → streams → clusters → seats) and puts an accept / regenerate / edit gate between them. Every accept or regenerate is recorded as a Genesis artifact and a ledger event, so the org's own creation is auditable from its first minute. Generated colleague personas are also yours to edit before commit — what you approve is what gets seated.
What commit creates
Pressing commit on the Live stage creates a new org — your current workspace, if you have one, is untouched — and seats you as its OWNER. In one transaction it materializes:
- Identity: the org, company profile, and design tokens
- Spaces: channels, with your founding membership
- Structure: roles and workforce seats (AI colleagues arrive with charters from the generated graph)
- Strategy: the full generated architecture when present — phases, streams, and the rest
- Invitations for the humans you listed, by email and role
Commit is idempotent — a double-submit or retry converges on the same workspace instead of creating a second one. Selected integrations from the Connect stage are recorded with the run; actually connecting them (sealing credentials) happens afterwards in Settings → Integrations.
The wizard warns before navigation that would lose unsaved work, and a mid-setup draft shows which stages are already captured when you come back.
After Genesis
- Invite more people — invitations are the only way in
- Connect integrations — turn Connect-stage intent into working credentials
- Set decision rights — required before agents can self-assign work or adopt decisions