> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bravenlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> The one-page cheat sheet — every core term in Braven, defined once.

If you read nothing else, read this page. Every other page in these docs uses these terms exactly as defined here.

## The hierarchy

```
Company
  └── Project
        └── Experiment
              ├── Files            (raw data)
              ├── Config           (input parameters)
              ├── Summary          (output metrics)
              ├── Series / Figures (plottable data)
              └── Device(s)        (optional — what was physically measured)
```

## Core terms

<ResponseField name="Company" type="tenant / visibility boundary">
  The organization you belong to. Everything you can see in Braven is scoped to a company you're a member of. There's no cross-company visibility — "shared" always means "shared with your company," never public.
</ResponseField>

<ResponseField name="Project" type="grouping of experiments">
  A named bucket of Experiments inside a Company — typically one measurement campaign, product line, or workstream. Every company member can see every project; there's no separate project membership to manage.
</ResponseField>

<ResponseField name="Experiment" type="one unit of lab work">
  Uploaded data files plus everything derived from them — metadata, pipeline runs, plots, notes. Named from the uploaded file (or folder) at ingestion. This is the page you open to look at one piece of work.
</ResponseField>

<ResponseField name="Run" type="one execution of a Pipeline">
  A single time a Pipeline processed an Experiment. A Run writes its Config, Summary, Series, and Figures **all at once, at the end** — nothing streams in while it's still running. Re-running a pipeline **replaces** the previous Run's output for that experiment; it doesn't append to it.
</ResponseField>

<ResponseField name="Pipeline" type="a Python script Braven runs for you">
  A script you write once (or generate) that runs automatically against every new Experiment's files. See [Write a pipeline script](/guides/write-a-pipeline-script).
</ResponseField>

<ResponseField name="Config" type="input metadata">
  Small key–value settings a Run was given (temperature, voltage, sample ID, …). Shown as columns/filters in the Experiments list.
</ResponseField>

<ResponseField name="Summary" type="output metadata">
  Small key–value results a Run produced (slope, gain, threshold, …). Same shape as Config, opposite direction — inputs vs. outputs.
</ResponseField>

<ResponseField name="Series" type="plottable measurement data">
  A named set of numeric traces (x/y arrays) an Experiment produces — the thing that ends up as an interactive chart. See [Series vs. Figures](/concepts/data-model) for how this differs from a Figure.
</ResponseField>

<ResponseField name="Figure" type="an uploaded matplotlib plot">
  A matplotlib figure your pipeline script uploaded with `braven.upload(fig, name)`. Braven keeps the rendered PNG **and** tries to auto-extract an interactive version of its line/scatter data — see [Series vs. Figures](/concepts/data-model).
</ResponseField>

<ResponseField name="Device" type="the physical thing being measured">
  A sensor, board, or setup identified by a stable key (serial number, MAC address, or anything unique you choose). An Experiment can be tagged to one or more Devices. See [Devices](/concepts/devices).
</ResponseField>

<ResponseField name="Watcher" type="the desktop/OneDrive sync agent">
  A background agent that watches a folder and uploads new files as Experiments automatically — no code required. See [Ingest data](/guides/ingest-data).
</ResponseField>

<ResponseField name="Analysis" type="cross-experiment comparison view">
  The project tab where you combine Series and Figures **from multiple experiments** onto shared charts — the place you go to compare runs. See [Analyze and compare](/guides/analyze-and-compare).
</ResponseField>

<ResponseField name="Report" type="a saved analysis, made shareable">
  An Analysis arrangement you've saved and can share with teammates or export. See [Reports](/guides/reports).
</ResponseField>

## Quick reference table

| Term             | Scope                                          | Where you see it                             |
| ---------------- | ---------------------------------------------- | -------------------------------------------- |
| Company          | Tenant                                         | Implicit — everything you're logged into     |
| Project          | Grouping of experiments                        | Project switcher, top of every page          |
| Experiment       | One dataset                                    | Experiments tab                              |
| Run              | One pipeline execution                         | Experiment detail → Pipeline tab             |
| Config / Summary | Small scalar metadata                          | Experiment detail, Experiments list columns  |
| Series           | Plottable data (classifier or `plot_series()`) | Experiment detail, Analysis tab              |
| Figure           | Uploaded matplotlib plot                       | Experiment detail → Images tab, Analysis tab |
| Device           | Physical thing measured                        | Devices tab, experiment detail               |
| Analysis         | Cross-experiment comparison                    | Analysis tab                                 |
| Report           | Saved, shareable analysis                      | Reports tab                                  |