Claim Check

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

Troubleshoot Claim Check account authorization, Free allowances, acceptance sets, agent commands, judge failures, and local exit behavior.

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.

The four Claim Check verdicts, READY, READY WITH GAPS, BLOCKED, and INCONCLUSIVE, and exactly how they're fused from the floor's binary signal and the judge's opinion. Includes a full worked example of the fix packet: fixes, route_to_human, and author_checks.

Where intent comes from on shipmoor claim-check: --intent-ticket outranks --intent-prompt outranks the acceptance file's own goal key. How agreement across sources sets confidence, the wider ticket, session, prompt, and manual precedence on claim-check resolve, and what changes for an acceptance set committed before this model.

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

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

Sign in, write a small acceptance set by hand with shipmoor claim-check init, run your first check with a one-line --intent-prompt, and read a real READY verdict and a real BLOCKED one, in about five minutes.

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.

Current CI support for Claim Check: local interactive use is available, while self-managed CI currently supports Scan only with SHIPMOOR_TOKEN.

Claim Check runs several evidence producers concurrently and records every outcome as a content-addressed attestation on disk. The VSA (Verification Summary Attestation) is the one binding output; a trace sidecar is additive only. How the fix packet's evidence pointers relate to the VSA's per-item dispositions.