Skip to main content

User guide · Chapter 9 of 12

The gate, reviews and approvals

How ODIN's gate checks each agent action, what it refuses, how code reviews and the Decision Audit work, and how approvals keep a person in charge.

On this page

Friday morning one of Acme's agents tries something it should not. This is where ODIN earns its keep.

What does the gate do?

Before each edit, commit or command in Claude Code, the ODIN plugin asks ODIN whether it may run. If the project has rule cards the agent has not read, the gate names them and the agent reads them first. Data leaving the company is refused. A message sent outside the company is held for a person to approve. If ODIN cannot be reached, the action goes ahead and you are told it was not checked.

What happens when an agent damages something?

ODIN's watch notices when an action empties a file or cuts a tracked file to almost nothing. Your administrators get an email, the miss appears on the Monitoring page, and ODIN learns a gate rule so the same action is stopped next time. The file can be restored from git.

How are code reviews done?

ODIN reviews merge requests on GitLab and GitHub against the project's rules, requirements and history. Each finding cites the rule it comes from, and findings are posted after a person approves them.

What is the Decision Audit?

A scored, explained judgement of a change or an idea: a merge request, a requirement, a deployment. It names its factors, how sure it is, and what would change its mind. Your team's feedback improves it.

Questions

Can the gate block my work by mistake?

The gate asks rather than blocks when it is unsure, and every refusal says why and what to read. You can pause ODIN for a while if you need to (see Tips and quick commands).

Is the gate on in ChatGPT or Claude's apps?

The gate runs where the ODIN plugin runs, in Claude Code. Other agents still answer from ODIN and record their tool calls on ODIN's server.