Docs

Checks catalog

All 37 core checks in one table: what each refuses, where it first runs, and which gate it implements.

All checks

Filter by where a check first runs, or by whether it implements a generic gate or exists only because of how Vinaya works. Each name links to the check's full entry. How the rings work is in Gates.

First runs
Kind

37 of 37 checks

CheckRefusesFirst runsImplements
brief-shapeA PR/brief report missing Vinaya’s required sectionsCommitVinaya-specific
pr-report-densityReport content that breaks Vinaya’s density and shape rulesCommitVinaya-specific
doc-coverageA code change without the documentation its doc-owner policy requiresCommitEvidence completeness
doc-coverage-pushThe same obligation, with push semanticsCommitEvidence completeness
pr-premise-reassertA Premise: pin the current repository no longer satisfiesCommitIntent freshness
single-plan-prConcurrent PRs on the same legacy tranche planCommitVinaya-specific
no-disk-stateA file that stores live execution status on diskCommitVinaya-specific
exec-bitsA staged executable without mode 100755CommitContract validity
ci-shard-coverageA CLI test missing from the CI shard listsCommitVinaya-specific
changeset-coverageA change to shipped packages without a Changesets entryCommitEvidence completeness
quoted-commandA quoted command or config line its cited file no longer containsPushEvidence freshness
coherenceA task branch, tranche, Issue and forge state that disagreePushVinaya-specific
dispatch-readinessDispatch of a task whose Issue, dependencies, conflicts or facts are not readyPushVinaya-specific
registry-gatesA gate registry, hooks, workflows and doctrine that disagreePushVinaya-specific
branch-topologyA task branch with no row in its tranche’s topologyPushVinaya-specific
dead-branch-pushA push to a branch whose pull request is already closed or mergedPushTerminal completeness
first-push-dispatchA first push that does not come from a dispatched taskPushVinaya-specific
reader-resolvable-proseUnresolvable references or undefined coined terms in reader-facing prosePushContract validity
retired-vocabularyTerms Vinaya has retiredPushVinaya-specific
doctrine-portabilityDoctrine references that depend on machine-local or author-only pathsPushVinaya-specific
doctrine-no-proceduresCommand sequences inside doctrinePushVinaya-specific
doc-claimsAn AEG:CLAIM marker its cited file no longer supportsPushEvidence freshness
workspace-escapeA file reference that escapes its workspace package or resolves nowherePushContract validity
main-branch-refusalA commit or a push on the default branchCommitEffect safety
token-collection-wiredUsage collection that is configured but not producing eventsPushTraceability
closes-nA task PR that does not close its own Issue with valid linkagePull requestVinaya-specific
surface-scopeA beyond-Surface path missing from the authoritative beyond-Surface record (no protected-path rule yet)Pull requestScope
test-planA test plan whose required results are missing or not bound to the headPull requestEvidence completeness
evidence-freshEvidence whose head, tree or result no longer matches the candidatePull requestEvidence freshness
review-gateMissing, stale, superseded or unauthorized Code and Security verdictsPull requestReview validity
principal-test-plan-waitMerge while a [principal] test-plan item is unticked for the current headPull requestAuthorization and Decision validity
body-bare-digitsBare digits in narrative PR prosePull requestVinaya-specific
issue-title-grammarA task Issue title outside Vinaya’s grammarIssue writeVinaya-specific
issue-objectives-numberingMalformed objective numberingIssue writeVinaya-specific
issue-parts-coverageA Part that cites no valid objectiveIssue writeVinaya-specific
issue-surface-globsInvalid or unresolvable Surface globsIssue writeVinaya-specific
issue-milestone-attachOn edit, a task Issue whose Milestone is not the one its tranche label resolves to (not checked on create)Issue writeVinaya-specific