# Basics

> Overview, Spaces, Projects and rooms

## Overview

*You describe the work in a sentence and it gets it done. Only the decisions that are yours come back to you.*

GenkiAI (Genki Studio) is an AI workspace that runs in your team's own Space. Every project is a code repository plus a team chat, and AI seats work in it phase by phase: design, build, verify, ship, maintain. Bugs and features go into a queue; Auto-Run works through them one by one, and every item passes an independent review by a different session.

| Term | What it is |
| --- | --- |
| Space | A team's workspace: its own host, its own members, its own data, at `<space>.rsi.am` |
| Project | A code directory plus a chat; its state lives in the repository's STATUS / DESIGN / PLAN / VERIFY / AUDIT |
| Seat | A running AI session in one role: Design, Dev, Chat or Review, plus each person's own Assistant |
| Phase | DESIGN → DEVELOP → VERIFY → DEPLOY → MAINTAIN, held by the server |
| Gate | The card between phases; it opens only when you approve |
| Queue | The project's list of bugs and features |
| Auto-Run | Works the queue item by item: implement or bugfind → review → grade |
| Assistant | An assistant that is only yours, with four layers of memory; it can start projects for you |

### How a piece of work goes

1. You talk an idea through with your Assistant and it starts the project with a brief, or you write straight into a project's chat.
2. DESIGN: the engine seat asks the key questions, then writes the requirements, the architecture and a plan. Gates A, B and C each wait for your approval.
3. DEVELOP → VERIFY → DEPLOY: it works the plan one task at a time, checks every requirement, gets an independent review and releases. Each phase change waits for your approval.
4. MAINTAIN: new requests and bugs go into the queue. Auto-Run implements, reviews and, when needed, grades each one, and findings go back to the Dev seat for another pass.
5. Decisions reach you as cards, which you can also answer on a phone. If you're away, you get a push notification. When the quota runs out, it waits where it is and carries on once the quota is back.

## Spaces

*Each Space has its own subdomain, host, members and data.*

- **Address**: `https://<space>.rsi.am`; the portal is at `rsi.am/console`, where you sign in with Google
- **Host**: Every Space has its own cloud machine (Ubuntu 24.04, arm64), which stays on and is never put to sleep
- **Data**: Every Space has its own encrypted data volume holding projects, Assistants and skills, so the machine itself is replaceable. The volume is snapshotted daily and kept 14 days; the app database every 12 hours
- **Connection**: The host dials out to the relay, which routes by subdomain. If the host is not connected, there is no route to it. Studio itself listens on localhost only
- **What the relay keeps**: Portal accounts, sessions, Space ownership and billing ids. It does not store the project or chat traffic it forwards

### Provisioning

1. Prepare: the data volume, the Space's own cloud permissions and a one-time secret bundle (the host reads it once, then it is deleted).
2. Deploy: the host boots and sets itself up.
3. Online: the host connects to the relay and the Space is ready.

All three steps show on the Space card in the portal and run on their own; a setup that gets stuck is marked failed and cleaned up. One account can own up to 3 Spaces.

### Plans

|  | Standard | Pro |
| --- | --- | --- |
| Accounts (owner included) | 6 | 20 |
| Storage | 50 GB | 200 GB |
| Live calls | 60 min per person per week | 60 min per person per week |
| Meeting transcription | 5 h per person per week | 5 h per person per week |

Monthly subscription; Standard can be upgraded to Pro. GenkiAI is live: any Google account signs in, creates a Space and starts. Anyone a Space invites (added to a team or holding an invite) skips the waitlist and finds that Space in the Spaces directory after signing in. If sign-ups are ever capped and the waitlist is turned on, the sign-in page says so: people not on the list see a waitlist page after signing in and can join it, and we send an email when the account is ready.

### Members and teams

Whoever creates the Space is its owner. The owner creates teams, decides which projects each team can see, and invites members by email up to the plan's limit; the built-in Admin team sees every project. Only the owner can create projects directly. Other members ask through their Assistant: a request card goes to the owner, who creates the project in one tap, and it goes into the requester's team.

## Projects and rooms

*A project is a code directory plus a team chat. Human messages go to the chat room; Auto-Run output and scheduled-job receipts go to the task room.*

- **Chat room `chat`**: Every human message lands here. The engine seat answers from DESIGN to DEPLOY, and the chat seat answers in MAINTAIN
- **Task room `task`**: Auto-Run output and scheduled-job receipts; the task log shows the last 72 hours
- **Engine seat**: The long-lived session that runs the phases: the Design model in DESIGN, the Dev model in DEVELOP / VERIFY / DEPLOY; Auto-Run's implement and fix turns run here too
- **Chat seat**: The project conversation in MAINTAIN, on the Dev model

When a project enters MAINTAIN, anything the engine seat hasn't answered yet is handed to the chat seat. Who sees a project is decided by teams: members see only the projects assigned to their teams.