Shipmoor docs
Community CLI, agent skills, CI integrations, and the Pro console — every Shipmoor product surface in one place.
Featured Topics
View all →Attestation artifacts
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.
Read more →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.
Read more →CI integration
Wire shipmoor claim-check into CI. The exit code maps BLOCKED and INCONCLUSIVE to a non-zero code unconditionally, so the real per-team choice is floor-only versus full judge-enabled mode in the blocking step, not whether to gate at all. Covers GitHub Actions, generic CI, the VSA artifact, an optional advisory judge step, and Test Evidence composition.
Read more →Browse by Category
Account & Billing
4 articlesComprehensive guides and tutorials for Account & Billing.
View all articles →Agent Skills
4 articlesWrap Codex, Claude Code, and Cursor with Shipmoor skills and harness hooks.
View all articles →CI & Automation
3 articlesComprehensive guides and tutorials for CI & Automation.
View all articles →Claim Check
11 articlesComprehensive guides and tutorials for Claim Check.
Community CLI
5 articlesThe free local scanner — commands, configuration, scan inputs, and output formats.
Getting Started
4 articlesOrientation, install paths, and the right Shipmoor surface for your team.
View all articles →Reference
7 articlesRule catalogue, exit codes, SARIF schema, configuration reference, and APIs.
View all articles →Test Evidence
5 articlesComprehensive guides and tutorials for Test Evidence.
Recently Updated
Attestation artifacts
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.
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.
CI integration
Wire shipmoor claim-check into CI. The exit code maps BLOCKED and INCONCLUSIVE to a non-zero code unconditionally, so the real per-team choice is floor-only versus full judge-enabled mode in the blocking step, not whether to gate at all. Covers GitHub Actions, generic CI, the VSA artifact, an optional advisory judge step, and Test Evidence composition.