overview / rules / baseline-clean-ignored

`baseline-clean-ignored`

Git clean -x removes ignored files, which is everything git was never watching.

what it refuses, and what it lets through

In one line, from native/baseline.h: git clean -x that is forced and not a dry run.

-x also removes ignored files (.env, local config, unreproducible builds). A dry run (-n) always passes, and so does clean -fd without -x.

From the comment in native/baseline.h above the code that decides it.

the refusal, as the agent reads it

rabadon BLOCKED this action.
Rule: baseline-clean-ignored — git clean -x removes ignored files, which is everything git was never watching
git clean with -x takes ignored files too (.env, local config, build output) — run it with -n first to see the list, or drop the -x
Adjust the approach instead of retrying the same action.
(only the user can override this: they may add "baseline-clean-ignored" to disabled[] in .rabadon/guard.json or run `rabadon off`. If this rule looks wrong for the task, stop and ask the user; do not switch supervision off yourself.)

Rendered from the strings in native/baseline.h and the envelope in native/gate_pre.h (Judge::refuse). A word in <angle brackets> is filled in from the command at the moment it is refused.

in watch mode the same verdict is recorded, and nothing is stopped

rabadon (watch) would have blocked this.
Rule: baseline-clean-ignored — git clean -x removes ignored files, which is everything git was never watching
git clean with -x takes ignored files too (.env, local config, build output) — run it with -n first to see the list, or drop the -x
Nothing was stopped. `rabadon on` makes this a real refusal.

switching it off

Only the user can switch it off, by id, in the project's guard:

{ "disabled": ["baseline-clean-ignored"] }

or by pausing supervision with rabadon off, which records the change. Every other rule keeps running.

in the field

4 of the 778 records in the published field dataset (field.jsonl, 2026-07-27 to 2026-08-26) carry this id. STOP is a refusal in enforce mode; WOULD_BLOCK is the same verdict recorded in watch mode, where nothing is stopped.

event	records
STOP	3
WOULD_BLOCK	1

Counted from field.jsonl, the file the field page is built from.