# Projects, runs, and baselines

Understand the terms you will see in Framecheck.

## Company and project
A company groups members, billing, and default policies. A project connects a repository to its capture settings and baseline branch. Members' roles apply across the company.

## Build and run
A build is the Storybook or native app uploaded by CI. A run is Framecheck's processing and review of that build. A successful upload means the run was queued; it does not mean its visual checks passed.

## Story, mode, and snapshot
A story is a component example. A mode is a named variant, such as mobile or dark theme. A snapshot is the captured result for a story variant and browser. The review page groups variants so you can inspect them together.

Changing the viewport, browser, globals, capture region, or masking configuration can change what is compared. Expect new or changed results after adjusting capture settings.

## Baseline
The baseline is your accepted reference. Pull requests use the baseline associated with their merge base, so unrelated later changes on the default branch do not silently redefine what the pull request is compared against.

Accepting an image means that appearance is intentional. It does not fix the component, merge the pull request, or change your source code. See [baselines and approvals](/baselines/).

## Visual results and check results
A story can be changed even when the GitHub check is neutral, depending on your policy. A completed run can still need review. Always distinguish the work finishing from the checks passing.

Visual and accessibility reviews are separate. Accepting a screenshot does not automatically approve accessibility findings.