> ## 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 to use these docs

> How to read GenieForge docs: model the product, brief and verify, then operate. Not a coding manual.

# How to use these docs

These docs teach briefing and verification, not coding. For what GenieForge is, start with [What GenieForge is](/getting-started/what-genieforge-is).

## Three layers

| Layer                 | Your job                                                            | Start with                                                                                               |
| --------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| **Model**             | Understand blueprint vs project, Build vs Chat, and the evolve loop | [How GenieForge works](/getting-started/how-genieforge-works)                                            |
| **Brief and verify**  | Describe outcomes clearly; Preview as each role; fix gaps in Build  | [Writing better prompts](/getting-started/writing-better-prompts)                                        |
| **Operate and trust** | Invite users, watch signals, ship safely                            | [Preview as a role](/users-and-access/preview-as), [Launch checklist](/getting-started/launch-checklist) |

## GenieForge vocabulary

```mermaid theme={null}
%%{init: {"flowchart": {"curve": "basis", "htmlLabels": true}}}%%
flowchart TB
  app("App"):::root
  subgraph recipeGroup["Shared recipe"]
    direction TB
    blueprint("Blueprint"):::recipe
    screens("Screens, logic, and roles"):::recipe
    blueprint --> screens
  end
  subgraph projectGroup["One project"]
    direction TB
    projects("Projects"):::runtime
    pdata("Data and files"):::runtime
    chats("Chats and executions"):::runtime
    signals("Signals"):::observe
    endUsers("End users"):::live
    projects --> pdata
    projects --> chats
    projects --> signals
    projects --> endUsers
  end
  app --> blueprint
  app --> projects
  classDef root fill:#E2E8F0,stroke:#475569,color:#0F172A,stroke-width:2px
  classDef recipe fill:#DDD6FE,stroke:#6D28D9,color:#4C1D95,stroke-width:2px
  classDef runtime fill:#99F6E4,stroke:#0F766E,color:#134E4A,stroke-width:2px
  classDef live fill:#A7F3D0,stroke:#047857,color:#064E3B,stroke-width:2px
  classDef observe fill:#FDE68A,stroke:#B45309,color:#78350F,stroke-width:2px
  style recipeGroup fill:#F5F3FF,stroke:#C4B5FD,color:#4C1D95
  style projectGroup fill:#F0FDFA,stroke:#5EEAD4,color:#134E4A
```

| Term                  | Meaning                                                                     |
| --------------------- | --------------------------------------------------------------------------- |
| **App / blueprint**   | The shared recipe GenieForge maintains for your product                     |
| **Project**           | One isolated runtime of that app (its own data, files, chats, signals)      |
| **Preview as**        | Try a role’s experience without inviting a real person                      |
| **Access**            | App Blueprint map of who can reach what                                     |
| **Signals**           | Usage evidence you review before the next Build                             |
| **Publish / version** | Ship a draft; customers see the published blueprint until you publish again |

Labels like Tools, Forms, and Pages under **App Blueprint** are how GenieForge stores the recipe. Treat them as recognition aids, not a shopping list. Fuller map: [Apps, projects, and surfaces](/getting-started/apps-projects-and-surfaces).

## What to expect on a page

* **Operate pages** show how to brief, Preview, invite, or ship.
* **“What’s in an app” pages** explain sidebar labels you may see while reviewing Access or export.
* **Tutorials** walk a scenario: brief → plan → verify role journeys.

If you need low-level authoring detail, that is for the builder AI in Build mode, not for you to implement by hand.

In the app, a **Help** control on a page or settings section lists what to look for there and links the matching articles.

## Related

* [Build your first app](/getting-started/build-your-first-app)
* [How building works](/building/how-building-works)
* [Getting help](/account/getting-help)