Core concepts - FlowPilot

These are the terms used throughout the FlowPilot docs. Each one gets a one-line definition here and links to the page that covers it in depth.

Vocabulary

Term	What it is	Learn more
Workspace	Your organization. One workspace maps to one Clerk organization.	Workspaces and apps
App	A platform target (for example your iOS or Android app) that owns its flows, placements, and experiments. Identified by an App ID.	Workspaces and apps
Flow	An ordered set of screens plus logic. A flow has versions.	Flows
Screen	One full-screen step in a flow. Holds a layout of components.	Your first screen
Component	A UI primitive such as text, button, image, or input.	Components
Block	A curated preset made of several components, ready to drop in.	Blocks
Variable	Typed flow state. Either a constant or supplied by the SDK at runtime.	Variables
Action	What happens on an interaction, such as navigate, setVariable, or closeFlow.	Interactions and actions
Zone / Persistent UI	A navigation bar, footer, or overlay that persists across screens.	Persistent UI zones
Placement	A named trigger the SDK resolves, for example `onboarding`.	Placements
Experiment / Variant	An A/B test on a placement. Each variant points at a flow version.	Experiments
Resolve	The SDK asking the backend “what flow, if any, for this placement and user?”	SDK REST API

Read top to bottom, the terms nest:

A workspace contains one or more apps.
An app owns flows, placements, and experiments.
A flow is built from screens, each holding components (and blocks, which are groups of components).
Variables and actions add logic. Zones add UI that persists across screens.
A placement is what your app asks about at runtime. A resolve turns that request into a flow, optionally split by an experiment.