# Principle packs

Admitted principle packs are the criteria Check applies. Pack identity binds the quote, the run, and the receipt.

A principle pack is an admitted, versioned set of criteria. Check does not invent packs at request time. The pack stack on the quote is the pack stack on the receipt.

## Choose packs before you spend

Agents list packs available to the caller, then pass those references into the quote and the run. Use `inspect_packs` on MCP, `GET /api/check/v1/packs` on REST, or the CLI packs command. Substring filters are for discovery, not for creating new criteria.

## Identity that must not drift

- Quote-bound approval includes pack identity. Approving a different stack requires a new quote.
- Admission is current state: dispatch binds the active admission, verifier digest, and economic ceiling.
- Candidate artifacts from local or BYOK execution are not admitted packs. Candidate does not mean governed.

## What a pack does not do

A pack names what to check. It does not approve spend, waive findings, or publish the deliverable. Human or agent rulings (`accept_concern`, `reject_concern`, `defer`) record a disposition on a finding; they do not re-interpret the pack.

> Today the public managed pilot routes the admitted V01 principles verifier. Additional packs exist in the portfolio; they are not all customer-reachable. See [Check](/docs/check) for the current boundary.