Ghost
A check on an agent's own steps: n ghosts redo the same step of the model, one hunter says what the majority did, and a step that loses the vote is asked about, stopped or replaced.
n ghosts and one hunter
Garage → Agents → Ghost. With the Ghost on, each step of the model (or only the steps that act: check every step, or acting steps) is redone by n ghosts, 1 to 5, 3 by default. The hunter compares them and says whether the agent is with the majority. The hunter is the same model, another model of the catalogue, or JEV when an agent of the tron has it. It needs runtime 0.25.0: the deploy says so otherwise.
When the agent is outvoted
Ask (the step waits for a person: Proceed with the agent, Use the majority, or Stop), Stop, or Use the majority. On a tie the agent loses by default; you can make it win. If the ghosts themselves fail, the step proceeds or stops, as you choose.
Deciding
A decision is asked in the chat, on the tron's Ghost & checks page, from the Tron API (POST /v1/actions/:id/decide) and on the bridges that have Ghost decisions on and are not public: buttons on Telegram, Discord and Slack, a reply command (approve, majority, stop with the id) on the others. Only an allowed id decides. The first decision counts; a second one is told it was already decided.
Deadlines
A question waits 24 hours by default (1 to 168). Halfway, the bridges get a reminder. At the deadline it expires and the turn stops, with the reason.
Said against done
After every turn the platform compares what the final answer claims to have done with what was actually called, written and decided: verified, mismatch or unverifiable. A mismatch is an event and shows under the turn; the Ghost & checks page filters on it. An optional judge (the same model) reads the claims, at one call per turn that makes some.
What it costs
Every ghost and the hunter are model calls: the Garage warns about it, and Usage shows them apart (Ghost, Hunter, Judge) from the agent's own calls.
A company's rule
Organization → Settings → Ghost policy: owners and admins can require the Ghost on agents with effects, a minimum number of ghosts, the mildest allowed answer to an outvote, and the hunters allowed. A Ghost saved below it is a 422 ghost_policy_violated, and so is the deploy of a company tron that breaks it.