Interlock
Sign in Request access
Authorization for AI agents

Before an AI agent acts,
Interlock decides whether it should.

Interlock intercepts consequential agent actions before execution, applies policy, routes exceptions to the right human, and records exactly what was authorised.

Beforeexecution, not after
Fail-closedwhen policy cannot answer
Nameddecisions, never anonymous
Agent intentbilling-agent
01
Proposed action
refund · $4 200 · 12 customers
02
Interlock intercepts
before the tool call reaches the world
03
Policy check
refund_limit v4 · class money · irreversible
Allowed
executes, still recorded
Human decides
approve · edit · deny
Blocked
refused, with a reason
Interlock  /  Overview Live
Autonomous actions
94.2%
completed without a human · was 91.8%
Human disagreement
7.4%
of what reached a human
Reviewer capacity
62%
Escalations
$4 200 credit · 12 customers
→ M. Kovach · never opened
Interception
7 min
03:12–03:19 · 2 refused
Outcome after execution
Not observed
unknown by design
The missing layer

Agents can decide what to do.
That is not the same as being allowed to do it.

Model reasoning determines what an agent wants to do. Interlock determines whether that action is authorised — and if it is not, who decides instead.

Without Interlock

01Agent decides to act
02Tool call
03The action has happened

The first time a human sees it, the money has already left.

With Interlock

01Agent decides to act
02Interlock intercepts · policy · scope · reversibility
03A human decides, if the policy says one must
04Authorised action, with evidence

Nothing consequential happens without someone answerable for it.

How Interlock works

Four stages between intent and execution.

01

Intercept

The agent's tool call is captured before it reaches the outside world.

POST /refunds
held
02

Evaluate

Policy, scope, decision class and reversibility are resolved for this exact request.

refund_limit v4
irreversible · external
03

Decide

Allowed automatically, routed to a named human, or refused with a stated reason.

approve · edit · deny · hand over
04

Record

The decision and the exact card shown at that moment are written once, and never rewritten.

29.08 02:58 · L. Arslanova
immutable
A real decision

This is the screen a reviewer actually sees.

Not a marketing abstraction. The card carries everything needed to decide, and nothing that would decide for you.

Interlock  /  Decision queue Live
IrreversibleExternal customer decision by 03:19 · 1 h 14 min left
Refund $4 200 to 12 customers
Agent
billing-agent
issue_refund
Policy
refund_limit v4
threshold $500
Scope
12 customers
$4 200 total
Reversibility
Irreversible
money that has left
Fourth refund from this agent within an hour
Shown because the pattern matters, not because the policy forbids it.
Approve Edit Deny Hand over last four digits of the amount to approve
The human loop

Human decisions refine policy.
They are not graded by it.

When a reviewer and the policy would have differed, Interlock records the divergence and returns it to the rule. It does not decide who was right.

Decision queue

A reviewer denies a $180 refund — the customer's third that week.

24 Aug · L. Arslanova
denied a $180 refund
the rule would have approved it
Audit log

The divergence is written once, with the exact card shown at the time.

aud-0291 · immutable
Denied · out of policy
a later revocation is a second record
Rules

A draft is derived, runs in shadow, and waits for someone to switch it on.

refund_under_500_single_customer
21 of 23 agreement
needs a second condition first
Shadow mode

A rule proves itself before it can change anything.

Drafts see every intercepted action and record what they would have decided. They influence nothing until a named person promotes them.

Rule in shadowDerived fromAgreementStatus
refund_under_500_single_customer 23 decisions · 4 reviewers 21 of 23 Ready to decide
plan_change_outside_billing_window 18 decisions · 2 reviewers 18 of 18 Ready to decide
pii_export_under_2000_rows 9 decisions · 3 reviewers 7 of 9 Not enough data

Open Rules → Eighteen of eighteen is not proof that a rule is right — it can also mean the hard cases never arrived. Interlock says so on the screen rather than promoting the rule for you.

Reversibility

Reversible and irreversible actions are not the same problem.

Irreversible marks the action, not the amount. Money that has left cannot be pulled back, while an export or a plan change is undone inside its window.

Reversible
Plan change for 1 customer
undone inside the billing window
Export 1 840 records
revocable while the transfer is queued

Revocation can stop what has not happened yet.

Irreversible
Refund $4 200 to 12 customers
the money has left for an external system
Delete 3 user records
no compensating action restores them
Stronger confirmation
4200 last four digits, typed from the card

Not a gimmick — it makes an irreversible approval impossible to give by reflex.

Fail-closed

Failure should change the system state —
not disappear into a log.

When Interlock cannot answer, agents are stopped rather than let through, and the refusal carries the reason that caused it.

Interception down

Agents are stopped, not running unchecked

Every action outside policy is refused with “interception unavailable” as the stated reason.

Connection lost

The queue is not updating

Decisions already sent are safe. What is uncertain is what arrived after the connection dropped.

No competent reviewer

It becomes a refusal

Named honestly, rather than left waiting for a person who is not there. It is not called an escalation when there is no one to escalate to.

Not found

This request no longer exists

Decided elsewhere, withdrawn, or expired fail-closed. Links outlive requests by design.

Immutable evidence

Every consequential decision leaves evidence.

A record is written once. A later revocation is a second record; the first is never rewritten. Retained seven years.

Open the audit log →

Interlock  /  Audit log Live
TimeAgentActionRisk What was shownDecisionWhoRule
Unknown by design

Interlock does not invent certainty.

It knows the decision was sent. It does not know how the execution ended. An approved refund may have failed in billing and is still counted here as approved.

Until outcomes come back into the log, a “share of correct decisions” would be invented — so there is none.

Outcome after execution
Not observed
unknown by design

Interlock stands before the action, not after it. Execution results never return to the log, so the product does not claim them.

The product

Five surfaces, one chain of custody.

Where it applies

Actions worth stopping.

Payments & refunds
issue_refund · issue_credit
Irreversible once the money leaves. Amount limits and named approval.
Data export
export_records · pii_export
Scope and destination, not row count alone.
Account changes
update_plan · change_owner
Reversible inside a window; still recorded under a name.
Infrastructure operations
delete_records · rotate_keys
Fail-closed by default; no silent continuation.
Support automation
support-agent actions
High volume, low value — handled by policy, not by people.
Enterprise agent fleets
many agents, one policy
One decision class per reviewer, one owner per rule.
Governance

Who answers for what.

Decision class

A money reviewer cannot decide a data action. Misrouted requests are handed over, never declined silently.

Amount limits

Above the limit the request goes to the duty lead — separate from the rule threshold.

Escalation

Named, not “the next shift”. An escalation without a name is not an escalation.

Handover

Open requests cross shifts with their timers intact. Nothing is closed or re-queued by the change of shift.

Rule ownership

Whoever promotes a rule becomes its author — not the reviewers whose decisions produced it.

Immutable records

Written once, retained seven years, never rewritten by a later decision.

Get started

Give AI agents authority
without giving up control.

Interlock gives agentic systems a decision layer before consequential actions become real.