For builders

Install, init, and check—green gates in your repo in under ten minutes.

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

Install hub: docs/getting-started/install.md · stuck? troubleshooting. Install pin v0.5.3; Action pin @v0.5.2.

Pick one of three ways in:

Write then check

Build curb outlines via pathway → assistant proposes A and B → you pick → cite-check → you confirm (TTY or --i-am-human) → check.

After pack confirm, Curbpack builds a local pack→rule map that steers drafting—not a legal oracle. Depth: docs/getting-started/pathway.md.

Windows (PowerShell)

irm https://raw.githubusercontent.com/afelin/curbpack/v0.5.3/scripts/install.ps1 | iex

macOS / Linux

curl -fsSL https://raw.githubusercontent.com/afelin/curbpack/v0.5.3/scripts/install.sh | sh

Then the same ladder:

curbpack doctor
curbpack demo
cd /path/to/your/product
curbpack init
curbpack check
curbpack share              # optional --bundle
# human when ready: curbpack attest → proof/index.html
curbpack drift              # optional checklist (exit 0)

Default pack is house-policy. Optional warm-start suggests checklists; drafts never replace check. Install pin v0.5.3; Action @v0.5.2. After PATH loss: curbpack doctor --repair (local only).

Bring docs then check

cd /path/to/your/product
curbpack init
# place existing policies on pack paths, e.g.:
#   SECURITY.md
#   .well-known/security.txt
curbpack check

No portal PDF ingest — files in the repo only. Names above match the house-policy pack.

CI (check alone)

- uses: afelin/curbpack@v0.5.2
  with:
    heal: "true"

Drop-in example: repo examples/workflows/curbpack-check.yml. Action runners = Linux/macOS only; local Windows CLI is supported separately.

What you get

Artifact	When	What it is
Gate report	Every `check`	JSON + markdown findings—structural evidence
Review pack	`share` or `prepare-release`	Layered reports for human review
Buyer one-pager	After green + `share`	Supplier evidence summary HTML
Attest capsule	Human `attest`	Git Notes hash bind—unsigned ≠ verified

Teaching sample: samples/onepager.html

How to interpret results

Exit 0 — gates passed on this tree; for human review, not certification
Exit 1 — findings remain or operational error
Exit 2 — usage / environment
Unsigned attest — not cryptographically verified

Daily loop

curbpack check
# red: curbpack check --heal && curbpack ask .github/curbpack/cache/latest_failure.json --propose
# green handoff: curbpack share
# human: curbpack attest  → optional proof/index.html

curb is a short alias for curbpack (same binary) — available only after install. Action pin stays @v0.5.2; CLI install pin is v0.5.3.

On red: heal, then ask propose, then re-check — never invent green. On green: share is the handoff recipe (check → context-pack → buyer-questions → prepare-release). After attest, open local proof/index.html vs the evidence pointer — still not conformity assessment.

Human pathway guide: docs/getting-started/pathway.md. Recipes: 60-second paths. Go deeper: white paper · how it works.

Works with assistants — run the CLI, then curbpack export --context-pack. Optional thin MCP: repo examples/mcp. Contract: docs/assistant-loop.md.