Which document do you want to keep true?

Find the kind of document you keep, and what goes wrong with it. The tool links to its card, and each rule or command to its page in the reference of the release this site pins.

DocumentWhat goes wrongToolRule or command
ADRThe code stops keeping a rule the ADR states; a rule is written so that it can never fail; a code comment cites a decision that was superseded or never written; a superseded ADR still reads as currentspec-guard, spec-graph@assert-* directives under the sentence, run by spec-guard; spec-guard prove; spec-guard cites; live-supersession
SpecificationThe code stops keeping a rule the specification states; a citation names a document or anchor that is not there; a document rests on a decision since retired; open work is handed to a document that can no longer take it; a claim says Implemented and no test stands behind itspec-graph, spec-guardbroken-reference, stale-premise, ghost-handover; @assert-* directives under the sentence; spec-guard claims
Checklist or roadmapA box is ticked with nothing behind it, cites a claim still open, or names a commit git does not havespec-graphunevidenced-completion, premature-completion, unknown-commit
Ledger or status pageA row says done while the claim it cites still leaves work openspec-graphpremature-completion, unknown-commit
RegisterA row's status is a word the register does not know; a row lacks the resolution, citation or commit its status asks for; two rows share a keyspec-graphunknown-register-status, incomplete-register-row, duplicate-key
Measurement protocol, and the figures that rest on itA protocol has no method or no dated result; a claim that asks for a measurement cites no protocol; a figure names no recordspec-graphincomplete-protocol, undated-result, target-without-protocol, unrecorded-figure
Orientation document: CLAUDE.md, AGENTS.md, a READMEIt names a path, a script, a make target or a commit that is not there; the code stops keeping a rule it statesspec-graph, spec-guardmissing-path, missing-command, unknown-commit; @assert-* directives under the sentence
BriefIts contract is incomplete; two rounds meant to run side by side could write the same file; an agent writes a file the brief protects; the round closes with a protected file changed, a box open, or a claim it raises still openspec-brief, spec-harnessspec-brief lint, matrix, schedule, archive; spec-harness guard, audit

What each tool reads

spec-graph reads specifications, ADRs and the references between them with no configuration, including the layouts Spec Kit, OpenSpec and Kiro write (layouts). Its rules for claims, checklists, ledgers, registers, protocols and orientation documents start once its configuration names the files that hold them, as spec-guard claims and spec-guard cites do; a file no configuration names is not held to them. The words in the table - claim, label, ledger, register, protocol, orientation document - are defined in the family's concepts.

One tool is a useful install on its own: spec-guard alone holds code to what its Markdown says, and spec-graph alone holds documents to each other and to the record they cite. Adopting goes from one tool to the whole loop, and the overview's problem-by-problem table names the command for each problem.