shipmoor claim-check maps each local verdict directly to an exit code:
| Verdict | Exit code |
|---|---|
READY | 0 |
READY_WITH_GAPS | 0 |
BLOCKED | 1 |
INCONCLUSIVE | 1 |
No flag or configuration key softens this mapping. BLOCKED and INCONCLUSIVE are not tooling failures; they are Claim Check outcomes.
Free allowance admission
Free includes five Claim Check invocations per month, and Pro is unlimited. On Free, one allowance is consumed after authentication, argument parsing, target/config resolution, and non-execution subcommand classification, but before engine or runner work.
Once admitted, the invocation counts even if the verdict is BLOCKED or INCONCLUSIVE, or later work is canceled or fails. Running Claim Check again consumes another unit. Internal Review and Test Evidence composition does not consume those separate counters.
claim-check init is setup-only and does not consume an allowance. The resolve and probes execution paths do consume one Claim Check invocation.
Current CI boundary
Self-managed CI currently supports Scan only with a scan-scoped SHIPMOOR_TOKEN. Claim Check is not currently supported in self-managed CI, so do not place an interactive device credential in a workflow or treat a Scan token as Claim Check authorization.
See CI availability and Plans & tiers.