The four checks
What each check reads, when it passes and what it writes.
| Check | Passes when | Reads |
|---|---|---|
check_coverage | Every requirement has at least one evidence topic that survives the pack's profile. | The relationship table in gemma.ditamap and the DITAVAL profile. |
check_currency | Each evidence topic was revised on or after its model version date, or holds only key references whose keys changed in an approved commit after that date. | The prolog <critdates> and model-version, and the version dates in packs/models.yaml. |
check_approval | The last change to each topic merged through a pull request that a code owner approved and didn't author. The agent's account never counts. | The approval index built from Git and GitHub at build time, and CODEOWNERS in dita-corpus. |
check_consistency | Every value resolves from a key, no topic states a fact two ways, and no authority-only key resolves in a public or downstream build. | Key references, key definitions and their audiences, and coverage values marked conflicting. |
What can take a decision
A coverage gap, a stale topic, a missing approval, a literal value and a conflicting statement can each ship with a recorded decision. A leak and an unresolved key can't: they block release until the source is fixed.