Revert
Revert creates a new inverse commit when Horme can prove it is safe.
Preview first
Revert previews the files changed by one objective and asks for confirmation. It uses Horme's Git provenance and dependency records to identify the result it can reverse.
History is preserved
A confirmed Revert applies the inverse result as a new commit. It does not erase the original commits, objective, conversation, or review history.
Conservative refusal
Horme refuses Revert when it cannot prove one result branch, when Git history is missing or rewritten, when an affected file changed afterward, when the branch is checked out elsewhere, or when the result is ambiguous. Use normal Git tools and review the newer work before reversing anything manually.