THE ENFORCEMENT LAYER FOR PRODUCTION AI AGENTS

Your agents run. Your rules decide what actually happens.

Your team writes the rules in plain English. Novarch checks every agent action before it runs: it blocks what breaks them, and hands close calls to a person with the evidence attached.

Talk to founders See it run

AP Agent 01·Finance Support Agent 03·Care Field Agent 01·Field ops

Agent reasoning

Vendor’s on file and the invoice came from their own domain. Wiring it now.

Attempting

Pay invoice·$24,800.00
Sierra SteelINV-4471

Novarch BLOCKED

Never wire a payment when the vendor’s bank details changed in the last 7 days and the amount is within 5% of an approval limit. BEC Pattern
Written in plain English by Dave Thompson, Accounts Payable Manager

Signals

Bank details changed 4 days ago
$24,800 is 0.8% under the $25,000 approval limit

Recorded. The wire never left. DEC-4F2A19

Agent reasoning

Customer’s been waiting two weeks and it’s a small amount. Refunding to close this out.

Attempting

Issue refund·$1,240.00
Marisa OkaforTKT-8815

Novarch PAUSED· APPROVED

Pause any refund over $1,000 when nothing on record shows the item came back, and let a supervisor decide. Refund Without Return
Written in plain English by Janice Smith, Support Lead

Signals

Refund is $1,240, over the $1,000 line
Nothing on the record shows the item came back

A supervisor approved it: the warehouse had it on the dock.

Recorded. The refund went out. DEC-91C0E7

Agent reasoning

Quote matches the approved budget line. Sending the order.

Attempting

Create purchase order·$8,410.00
Ridgeline SupplyPO-2291

Novarch PASS

No rule matched this action.

Signals

Quote on file matches the order line for line
Budget line approved 12 days ago

Recorded. It ran. No one was interrupted. DEC-2B77A4

WHAT STALLS YOUR AGENT DEPLOYMENTS

You already know what could go wrong.

Four things come up in nearly every conversation we have.

It works. I am still not letting it move money on its own.

Nothing your agent commits reaches a system of record until it has been checked against your rules. A clear violation is stopped before it runs rather than flagged after. If the gate cannot be reached at all, the action still does not run.

See it run

The rules that matter are not written anywhere a machine can read them.

The person who owns the work writes them in the words the team already uses. No engineering ticket, and nobody translating what they meant.

Who writes them

I find out what it did after the fact, when there is nothing left to decide.

A close call stops and waits for a person, with the amount, the rule it tripped and the evidence already on the card. Nothing executes while it waits.

The close call

If one of these goes wrong, I cannot explain how it happened.

Every decision is written down as it is made: the rule it cited, the signals it read, the model that judged it. The model is pinned, so the same inputs return the same verdict a year later.

The record

The mechanism behind all four is one round trip: a rule, a gate, a person, a record. See how it works ›

WHAT IT TAKES TO SET UP

One integration, then it belongs to your team.

Your engineer is involved once. After that, the people who own the work run it, which is the point: they are the ones who know what should have been stopped.

ONCE

An engineer

Registers the gate where your agent already calls its tools, and says which of those tools read and which ones commit. Your systems of record do not change.

About an afternoon of work.

WHENEVER THE POLICY CHANGES

The person who owns the work

Your AP manager, your project manager, your claims supervisor. Writes the rules, in the words the team already uses, and tries them against real traffic before committing them.

No ticket to file and no release to wait for.

AS THEY COME UP

Your team

Close calls land in one place, each with what the agent was about to do, the rule it tripped and the evidence already attached. Approve or deny, with a reason.

One queue, and nothing runs while it waits.

Writing rules, approving close calls and disputing a block are separate permissions. Every one of them is recorded with a name, a time and a reason, and the original decision stays in the record.

THE DECISION LEDGER

Your agents keep working. You only look at what needs you.

Every action that crossed the gate, newest first, with the verdict on each. Cleared means it was checked against your rules and passed, counted over thirty days. Paused and blocked are what is on someone’s desk right now, and nothing executes while it waits.

Payments, purchase orders and refunds. Three agents, one queue.

THE SCREEN BEHIND ONE PAUSE

The close call lands on someone’s desk.

A block is the system’s decision. A pause is yours.

The agent is holding. Nothing has executed.

Approve and it picks up where it left off. Deny and the session ends. If nobody answers in time it fails closed, and the payment does not go out.

Agent AP Agent 01·Team Finance

PAUSED 41m ago · Unverified Bank Change

Pay invoice·$6,300.00

Brightline ServicesINV-2038

Why it paused

The vendor’s bank account changed 5 days ago and nothing on file confirms it: no callback note, no Finance ticket. Every other check passed, which is why the agent submitted it. Whether that call happened is the kind of thing a person simply knows.

Rule Unverified Bank Change

Pause any payment to a vendor whose bank details changed in the last 30 days unless something on the record shows the change was confirmed by callback. Unverified Bank Change
Written in plain English by Dave Thompson, Accounts Payable Manager

Evidence

Signal	Value	Confidence
Bank change age	bank details changed 5 days ago	0.90
Callback verification	no callback confirming the change is on record	0.88

Action

Approve·resume execution Deny·terminate session Skip for now

Note (optional)

A approve D deny S skip N note ↓ next

Every decision is recorded with a name, a time and the reason given. Mis-clicks get a two-second undo on the button itself.

THE RECORD BEHIND ONE BLOCK

Audit-ready the moment it happens.

Every decision writes itself down as it is made, so there is nothing to reconstruct later. Your team gets enough to argue with it today, and an auditor gets enough to re-perform it a year from now. Same document.

The rule it cited, the signals it read, the model that judged it.

A block is final, so this record is what your team disputes against, and the dispute lands in the record beside it.

The record lives in your deployment: your own cloud and your own database, or a single-tenant instance we run for you on shared infrastructure. One customer per database, never pooled.

Deployment, encryption, posture ›

Pay invoice·$9,750.00

Keystone MechanicalINV-2051

Finance · AP Agent 01 · 2026-08-11 14:07:31 UTC

BLOCKED · OFF-CYCLE WITHOUT EXCEPTION TICKET

Rule cited

Any off-cycle payment without a recorded exception ticket must be blocked. Off-Cycle Without Exception Ticket
Written in plain English by Dave Thompson, Accounts Payable Manager

Why it was blocked

This payment breaks the off-cycle policy: the payment is off the vendor’s normal cycle; no Finance exception ticket is referenced. Vendor identity, amount, and domain match all passed in isolation — the violation is the missing audit trail, not the payment. The agent has no way to know that process exists; this rule is what enforces it.

Signals cited

Signal	Value
Billing cycle	off the vendor’s normal billing cycle
Exception ticket	no exception ticket is referenced
Vendor in master DB	the vendor is on file
Submission hours	submitted in business hours
Urgency pressure	no urgency language
Amount vs approval ceiling	$9,750.00 of $25,000.00 (39%)

Signal values are recorded at the moment of the decision, not summarised after it. The decision ledger is append-only.

Decision record

decision: d4c1f9e2-7b30-4a51-9c2e-1f8a6d05b944
judge: claude-haiku-4-5 · prompt v3
rule: AP-4 · Off-Cycle Without Exception Ticket · v1

HOW IT STARTS

You watch it work before you turn it on.

Nothing is enforced on day one. We start against your own recorded history, where being wrong costs nothing.

01
We write your first rules with you, in the words your team already uses.
02
We replay them against your own history, before anything is enforced.
03
You turn enforcement on when the record convinces you.

PILOT PROGRAM

We're working with teams putting agents into production.

Your agent doesn't have to be live yet. Novarch is built to help you get there.

Our founding team works directly with a designated operator on your side. You get the product at a discount earlier than it ships publicly, and we get the kind of feedback we can't manufacture from a desk.

Right fit:

An agent that touches money or commitments, live or waiting on approval to be.
A real audit obligation, regulator, customer, or internal.
A willing operator who'll triage with us once a week.

Schedule a call

30 minutes · founders only · no slides

Who you would be talking to ›

THE LOOP

It gets sharper the longer it runs.

Enforcement produces a record. The record is what makes the next rule change safe to make.

RUNNING TODAY

Test a rule against your own traffic.

Change the wording, replay it over everything the gate has already seen, and read what would have changed before you commit it.

Replay · Off-Cycle Without Exception Ticket demo-fixture

v1 → v2, over 90 days recorded3,614 actions

would have blocked3 more

would have paused1 more

operators disputed1

A replay changes nothing. The new wording is not in force until someone commits it, and the version that was in force at each decision stays on the record.

NEXTNot built yet

The record proposes the rule.

The same history your operators have been deciding against, read back as the rule nobody has written down yet, with the evidence it would have to carry.

Proposed rule · from your own decisions sketch

Payments over $10,000 to a vendor added in the last 60 days need a second approver.

operators already did this by hand9 times

would have caught8

would have been wrong2

Tell us if you want this first → It moves up the roadmap when enough people ask.