configlisted

# Choose what to enforce Let me pick, check by check, what did-you-check enforces in this repo. **Everything starts on.** Turning something off is a decision written into `.check.toml`, so it shows up in the pull request and the team can see it. **Reply in whatever language I am writing to you in,** and write config comments in that language. ## 1. Read the current state Read `.check.toml` at the repo root. Take the `disabled_rules` line if there is one. **That line is the only thing this command changes.** Leave every other key and comment exactly as it is. Check the environment too. If `NGG_DONE`, `NGG_TESTGUARD`, `NGG_GUARD` or `NGG_JUDGE` is `0`, that switch turns a whole gate off regardless of the file. Say so. ## 2. Show every item One table with five columns: **Gate, Name, Blocks, Source, On/Off.** Use these rows and copy the Source text as written. **Never drop the Source column.** It is the reason this command exists: I should see where a rule comes from before I switch it off. A table without it is not the table this command promises. | Gate | Name | Blocks | Source | |---|---|---|---| | Evidence | `R0` | Answering about this repo's state without running a tool | Reduce hallucinations | | Evidence | `R1` | Asserting a file's state without looking | Reduce hallucinations | | Evidence | `R2a` | Ending on "this needs to be verified" without running a tool | Reduce hallucinations, "Allow Claude to say I don't know" (deferring what could be checked is not the sa