> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genieforge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How GenieForge works

> The Living Software loop: blueprint, project runtime, portal, operator AI, signals, and versioned change.

# How GenieForge works

GenieForge is a **Living Software** platform. You describe an app; GenieForge assembles it from production-tested building blocks the AI can understand and change safely over time.

## The loop

```mermaid theme={null}
flowchart LR
  builder[You in Build mode]
  blueprint[App blueprint]
  project[Project runtime]
  portal[Customer portal]
  signals[Signals and feedback]
  builder -->|plans and versions| blueprint
  blueprint -->|same recipe| project
  project --> portal
  portal -->|usage| signals
  signals -->|what to build next| builder
```

| Stage    | What happens                                                                    |
| -------- | ------------------------------------------------------------------------------- |
| Build    | You and the AI shape the shared **blueprint**: data, tools, pages, forms, roles |
| Operate  | Each **project** runs that blueprint with its own database, files, and users    |
| Observe  | **Signals**, Feedback, Chats, and **Executions** show what really happened      |
| Learn    | **Evals**, views, and credit usage help you see patterns                        |
| Evolve   | Back in Build: plans, versions, rollback                                        |
| Remember | **Build Rules**, App Documentation, and optional memories keep intent           |

## Blueprint vs project

* **App (blueprint):** the recipe shared across every workspace of that app.
* **Project:** an isolated runtime (its own data and files). Use one project per client, or staging vs live-style boundaries.

Building changes the recipe. Customer data stays in the project unless you deliberately seed or import it.

## Build vs Chat

* **Build mode** designs and changes the software (usually through a plan you approve).
* **Chat mode** (including the portal) uses what already exists. End users should not redesign the app from the portal.

## A concrete picture

A coaching practice describes a program. GenieForge creates clients, check-in forms, a coach dashboard, role-specific portal access, weekly email digests, a companion agent for clients, secure files, and signals when something is missing. When clients use it, friction returns to the builder as structured signals for the next version, under permissions and version history.

## Where to go next

* [Build your first app](/getting-started/build-your-first-app)
* [Apps, projects, and surfaces](/getting-started/apps-projects-and-surfaces)
* [Living Software](/concepts/living-software)
* [Usage-Driven Development](/concepts/usage-driven-development)
* [Launch checklist](/getting-started/launch-checklist)