# Model inventory

In-repo **catalog of open-weight revisions** reserved (or nominated) for the lab.
Weight blobs live on the **VAULT HD** at `D:\vault\coulomb\freedom-intelligence\` —
see `docs/backup-storage-policy.md`.

## Layout

```text
inventory/
├── README.md                 # this file
├── schema.yaml               # field reference (v0.2+)
├── collection-policy.md      # approval and eligibility (R/S/W tiers)
└── catalog/
    └── *.yaml                # one file per model revision
```

## What each catalog entry contains

| Section | Purpose |
| ------- | ------- |
| **Identity** | `id`, `name`, `org`, `status`, `tags`, `tier-*` |
| **source** | HF/org URLs, revision pin |
| **profile** | Use cases, sweet spots, anti-patterns, **original_source** link |
| **swot** | Compact strengths / weaknesses / opportunities / threats |
| **license / size / hardware_class** | Retention and run guidance |
| **collection** | Approval, NAS path, brief refs |

Operators should be able to open one YAML and decide *whether* and *why* to pull
or serve a model without reading the whole research tree.

## Status values

`candidate` → `approved` → `collecting` → `collected` → `verified`  
also: `superseded` | `evicted` | `rejected`

## Tiers

| Tag | Meaning |
| --- | ------- |
| `tier-r` | Runnable spine (current lab hardware) |
| `tier-s` | Strategic capability (may be beyond run envelope) |
| `tier-w` | Watch / optional |

## Adding an entry

1. Confirm eligibility in `collection-policy.md`.
2. Create `catalog/{org}__{name}__….yaml` from `schema.yaml` **including `profile` + `swot`**.
3. Set `profile.original_source` to the canonical card/release URL.
4. Set `status: candidate` (or `approved` if signed off).
5. After download: `collected` / `verified` + `collection.storage_path`.

## Related

- Collection plan: `research/2026-07-24-nas-strategic-collection-plan.md`
- Strategic NAS decision: `docs/decisions/2026-07-24-nas-strategic-reserve.md`