​

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

​

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
• Apps, projects, and surfaces
• Living Software
• Usage-Driven Development
• Launch checklist