# packs/ — the record of what was cut

One directory per source pack, holding the **manifest and its views** for a cut that
actually shipped:

```
packs/<pack>/
  fred_kits.json     # the manifest — every sample, where it came from, its grade + tags
  fred_kits.md       # the report: per-track probe verdicts, tempo, per-kit tables
  fred_kits.tidal    # the cheat sheet — paste-ready, `n` index of every sample
  kitcheck.md        # the audit
```

The audio itself lives under a **staging root**, symlinked into Dirt-Samples, never
here — this is provenance, not a copy. Where that root is, is per-pack: kits cut from
someone else's stems are staged beside their source (`Samples/Fred/output/<kit>/`, via
`--samples-root`) so the pack stays one movable, deletable thing, while ParVagues' own
kits sit directly under `Samples/<kit>/`. Either way the bank name is the directory
name, so `s "<kit>"` does not care which. The manifest is the record; `.md` and
`.tidal` are views of it and can be rebuilt at any time with:

```bash
python3 -m engine.stempack --report-only --out packs/<pack>
```

Keeping the manifest is what makes a cut auditable months later: which stem a loop came
from, at what tempo, graded how, and what CLAP heard in it.
