> Source: https://vitna.ai/docs/cli/skus/candidates
> Raw Markdown: https://vitna.ai/docs/cli/skus/candidates.md
> Corpus index: https://vitna.ai/llms.txt

# npm run sku:candidates

The priced rows the collector saw that the registry does not track.

```bash
npm run sku:candidates
npm run sku:candidates -- --all
```

By default it shows rows seen at least twice. `--all` includes rows seen once.

## Why a second sighting

A row seen once may be a parse artefact of one malformed page. A row seen twice
is something the provider is actually publishing.

Same discipline as the confirmation rule on
[price periods](../../concepts/price-period.md), applied to existence rather than
to value.

## The collector counts, a person decides

`witness.sku_candidate` carries a status, and the collector holds `UPDATE` on the
counting columns only, not on the status.

So discovery is automatic and admission is not. A row becomes a
[sku](../../concepts/sku.md) by [promotion](promote.md), is
[linked](link.md) to one registered by hand, or is [ruled out](reject.md).
