# X_PIN_RAISE_UNSTATED

## Means

a ratchet pin in `scripts/lib/*-pins.ts` is higher than at `origin/main`'s tip with no `why:` on the row

## Typical cause

a pin raised to make a guard green, in silence — `secret-compare` 53 → 63, `node-import-pins` 3 → 12, `proto-index-pins` 1 → 9 all happened with nothing on the row. `budget-raises`' rule for routes, applied to every pins table and to the ratchets kept inside scripts (`DOC_COMMAND_PINS`, `README_FENCE_BACKLOG`, each app's `expectedRed`); the `why:` must be one `origin/main` did not already have for that row, since the old sentence was written for the old number; a table new since the base is stated by a `why:` in its header

## Fix

add `// why: <the reason these sites cannot be fixed yet>` on the row or directly above it, or fix the new sites and lower the row back. Then `bun run pin-raises`

[CLI and verify](/error-codes#cli-and-verify)