botwir3 Mechanic
Mandate Integrity Violation
A HALT condition triggered when the runtime detects that the strategy configuration file has been modified since compilation.
MANDATE_INTEGRITY_VIOLATION fires when the spec hash check fails. The runtime recomputes the SHA-256 hash of the current config and finds it does not match the stored hash from compile time. Something changed.
The bot enters HALT immediately. It does not attempt to execute under the modified config. It does not try to identify what changed. The hash mismatch is sufficient — the mandate is no longer intact, and the bot stops.
To resume, the user either restores the original config file (if the modification was unintentional) or recompiles in the builder (if the modification was intentional). A recompile produces a new spec hash, and the bot restarts with the new mandate.