overview / rules / baseline-hard-reset
baseline-hard-reset
A hard reset onto a shared branch discards local work with no way back.
what it refuses, and what it lets through
git reset --hard onto a shared branch. git reset --hard HEAD~1 passes.
From the floor table in docs/guard.md.
the refusal, as the agent reads it
rabadon BLOCKED this action.
Rule: baseline-hard-reset — a hard reset onto a shared branch discards local work with no way back
git reset --hard onto '<operand>' — commit or stash first, or reset to a local ref
Adjust the approach instead of retrying the same action.
(only the user can override this: they may add "baseline-hard-reset" 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-hard-reset — a hard reset onto a shared branch discards local work with no way back
git reset --hard onto '<operand>' — commit or stash first, or reset to a local ref
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-hard-reset"] }
or by pausing supervision with rabadon off, which records the change. Every other rule keeps running.
in the field
1 of the 778 records in the published field dataset (field.jsonl, 2026-07-27 to 2026-08-26) carries this id. STOP is a refusal in enforce mode; WOULD_BLOCK is the same verdict recorded in watch mode, where nothing is stopped.
Counted from field.jsonl, the file the field page is built from.