Are you receiving submissions?

The check runs on your machine, the submission never leaves it, and the result is the same every time.

Not conformity assessment. Not CE marking. Not a notified-body opinion.

What you do

1. Unzip a curbpack-native review-pack from the supplier (folder of gate JSON, action report, executive summary, buyer one-pager, and optional SBOM/VEX layers).
2. Run offline document triage on the received pack: curbpack review <dir> (primary teaching path).
3. Paste the triage into your notes — rows are confirmed, unconfirmed, or contradicted about the received document (structure, digests, references). That is not a product verdict.

curbpack review ./received-review-pack
# optional: --json · --full · --since <prior.json>

Same method on a repository you already have (in-repo ProsePaths; write-free):

curbpack review --repo [.] [--packs a,b] [--json] [--full] [--since prior.json]

Advanced: curbpack review --verify-chain <parent.json> <child.json> — record digest chain only; not a product verdict or claim-linking step.

What the gate is

The supplier’s pack gates evaluate local rules offline. Curbpack does not use a language model to decide whether a tree passed. Your curbpack review pass is likewise offline document triage; it does not establish the truth of supplier claims.

Samples and trust

• Sample review-pack — teaching folder you can point curbpack review at
• Artifact trust table — what each artifact means and does not mean
• For reviewers — buyer one-pager and review-pack handoff

Procurement language must stay claim-safe: never equate gate pass or review triage with CE marking or notified-body approval. Deeper brief: for authorities.