CI availability

Shipmoor Team

•

August 28, 2026

•

1 min read

Claim Check is not currently supported in self-managed CI. Current machine tokens are scan-scoped, and SHIPMOOR_TOKEN authorizes Scan only.

Do not place an interactive device refresh credential in CI or attempt to run Claim Check with a Scan token. Team and Enterprise managed CI and PR checks are coming soon/contact-only.

Claim Check remains available from an authorized local installation. Free includes five invocations per month, and Pro includes unlimited invocations. User and agent invocations share the same counter; internal Review and Test Evidence composition inside one admitted Claim Check does not consume those separate buckets.

For the supported current CI path, see CI overview and GitHub Actions.

Last updated on August 28, 2026

Was this article helpful?

Your response is saved on this device.

CLI reference

The Shipmoor 0.10.0 claim-check surface: selectors, floor-only mode, acceptance set, agent judge, intent, output, configuration, subcommands, and exit codes.

Privacy & service contacts

How Claim Check keeps source-derived content local by default while using required account, entitlement, and Free allowance service contacts.

Verdicts & exit codes

Understand Claim Check's unconditional local exit-code mapping and the current boundary that self-managed CI supports Scan only.

The intent fidelity judge (BYO-Judge)

For obligations the deterministic floor can't check mechanically, your own coding agent adjudicates. It can only BLOCK by citing a divergence that survives execution, or ABSTAIN by routing to a human. It never passes a check. K=3 samples, 2-of-3 to block, a confidence floor below which the judge steps back, two-phase decomposition then audit, and evidence pointers confirmed by running them for real.

Claim Check overview

Claim Check checks whether a change did what the task asked. A deterministic floor decides READY or BLOCKED; an optional bring-your-own judge can only block or abstain, never pass. When it can't decide something on its own, it hands back a fix packet naming the exact test to write next.