botwir3 Mechanic
HALT State
A terminal state where the bot stops executing — triggered by config tampering, execution mismatch, or three consecutive drift periods.
HALT is the bot's last line of defense. Three conditions trigger it: a spec hash mismatch (the config was modified — MANDATE_INTEGRITY_VIOLATION), an execution result that deviates from the gate's projection (something went wrong at the platform level), or three consecutive drift periods (the bot could not find a valid action for three cycles in a row).
A halted bot does nothing. It does not reconnect, retry, or resume. The user must intervene — inspect the cause, resolve it, and restart the bot manually.
HALT is protective. A halted bot with an intact config is a better outcome than a running bot with a broken mandate or a disconnected platform. The design principle: when in doubt, stop.