How to use these docs

These docs teach briefing and verification, not coding. For what GenieForge is, start with 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
Brief and verify	Describe outcomes clearly; Preview as each role; fix gaps in Build	Writing better prompts
Operate and trust	Invite users, watch signals, ship safely	Preview as a role, Launch checklist

GenieForge vocabulary

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.

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.