# Workspace and Experiments

The workspace layer groups simulation work into projects and experiments. Use
it when a design produces multiple runs, notes, result tables, or comparison
artifacts.

## Projects

A project is the user-facing container for a design effort. It can own
libraries, experiments, and generated outputs.

Use a project when:

- several cells belong to the same design effort
- you need repeatable experiment folders
- results should be compared across runs
- notes and metadata matter as much as the netlist

## Experiments

An experiment stores one simulation campaign: inputs, results, notes, and
derived analysis.

Good experiment names describe the question being answered:

- `inverter_nominal_delay`
- `nand2_pvt_sweep`
- `opamp_phase_margin_vs_cc`
- `sense_amp_mc_offset`

## Relationship to User Guide Flow

The workspace layer does not replace the LCV and simulation APIs. It wraps
them:

```text
Project
  Library/Cell/View source
  Experiment
    SimTask inputs
    SimResult outputs
    measurement/spec reports
    notes
```

Start without a workspace for small examples. Add projects and experiments
when the number of runs or artifacts becomes difficult to track manually.