/01 Teardown
We study one process first and write up what we find. You keep the document.
- signed manifest
- named approver
- spend limit
- sealed record
- export in open formats
We deploy AI agents on your work.Then we run them.
Surehand starts with a teardown, a written study of one of your processes. Then we put an agent to work on it and run it for you. Each action goes through Gatehouse, the software Surehand built to check and record what agents do.
- 01Teardown
- 02Deployment
- 03Operation
We are a small operator-run firm that deploys and runs governed agents for clients. Each agent acts inside a manifest your team signs, so your reviewers can check each action.
No customer names on this site. The cases are composites and the screens are simulated, and each is labelled.
One Gatehouse run
How you know what the agent did.
Gatehouse is a product of Surehand, the control plane each deployment runs on. It checks each action against the signed manifest, the rules file your team signs, before it runs. Hard calls go to a named approver, and the record is sealed. Below is one simulated run, the same one the Gatehouse site shows.
14:31:52run opened, policy checkchained · sha-256PASS
14:31:58invoice matched, INV-40218chained · sha-256PASS
14:31:58read, match, draft, schedulechained · sha-256PASS
14:32:00payment held, rule bank-detail-changechained · sha-256HELD
ap-lead · asked with the evidence
- invoice INV-40218 · 2,400.00
- bank detail · previous
- bank detail · first seen today
declined · ap-lead · 14:32:19
14:32:19declined by AP lead, supplier did not confirm the changechained · sha-256DECLINED
14:32:19record sealedchained · sha-256SEALED
CHAINED BY SHA-256 · EXPORTS IN OPEN FORMATS
What we do
Three services, and the product they run on.
/02 Deployment
We write the manifest, the rules file, with your team. You sign it, and the agent runs on Gatehouse under it.
/03 Operation
We run what we deploy. A held action goes to your named approver, and the record stays yours.
/04 Gatehouse
A product of Surehand, and the control plane each deployment runs on. It checks each action before it runs and seals the record.
The first step
Book a teardown
One process, measured before anything is built.
The teardown measures the volume and the exception rate of one process. You keep the document, even if it says not to automate yet.
Book a teardownTEARDOWNONE PROCESS
VOLUMEmeasured on your process
EXCEPTION RATEmeasured on your process
HOLDSwhere a person decides
VERDICTmay be that automation is not worth it yet
Sample layout. No figures.
Deployments
Three composite cases.
Client work with names and figures changed. All three run on Gatehouse.
Claims triage at a regional TPA
First-pass document checks and routing on incoming claims. Low-confidence files wait for a named claims handler.
W/01 on the Gatehouse site
Invoice matching for a distributor
Three-way matching across purchase orders, receipts and invoices, with a spend limit on each run.
W/02 on the Gatehouse site
Policy answers with named escalation
Policy questions answered from the policy library only, each with its clause cited. Anything below the confidence threshold goes to a named support lead.
W/03 on the Gatehouse siteGatehouse capabilities
The eight capabilities of Gatehouse.
Each row opens that capability on the Gatehouse platform page, so you can send a reviewer only the part they need.
- P/01Policy engineYour rules, in one signed file.
- E/02Runtime enforcementEach action is checked before it runs. Anything the manifest does not name is refused.
- R/03RecordEach run is saved to the audit trail, chained by SHA-256.
- A/04ApprovalsHard calls wait for a named approver. Overriding a block takes two names.
- S/05Spend controlsA limit on what a run may spend or commit.
- L/06Least privilegeThe agent gets only the access the manifest names.
- C/07Continuous evaluationApprover decisions become labelled examples, and later changes are tested against them.
- X/08Data portabilityThe trail, policy history and examples export in open formats.
MANIFEST V14SIGNED
SCOPEaccounts-payable
ROLEap-agent
LIMITautopay 250.00
APPROVERap-lead
RULEbank-detail-change: hold
DEFAULTrefuse
Simulated. Manifest v14 from the run above.
If we part ways
What stays yours.
These four things are yours to keep. Each one links to where you can see it.
The manifest
One signed file per deployment, with its version history.
The record
Each run, hold and decision, in order. Editing one breaks the chain in view.
The examples
Each correction your approver made, saved as a labelled example.
The teardown
The teardown document from the first step, whatever its verdict.
Before you sign
Four questions buyers ask before they sign.
Each answer links to the page that shows how it works.
What stops it doing something we cannot undo?
OUR ANSWEREach run has a scope and a spend limit before it starts. An action outside the scope is refused before it runs. An amount over the limit is held for a named approver, and both are recorded.
What happens when it is wrong?
OUR ANSWERA rule in the manifest holds the action, and one named approver gets it with the evidence gathered. Their decision is saved with their name.
Who owns it once you leave?
OUR ANSWERYou do. The manifest is one signed file you hold. The audit trail, policy history and labelled examples export in open formats and read without Gatehouse.
You have no SOC 2. Why would security sign off?
OUR ANSWERNo SOC 2, no ISO 27001 today. We sign an NDA and DPA first. We answer your questionnaire in writing, usually inside two business days. You get the signed manifest and a record your team can check.
Articles
Notes on AI agents at work.
Short articles on cost, approvals, spend limits and audit trails.
What does Surehand do?
Surehand deploys and runs governed AI agents for clients. Each deployment runs on Gatehouse, the control plane we built. It adds a signed manifest, a named approver for hard calls and a sealed record of each run.
What is Gatehouse?
Gatehouse is the control plane for enterprise AI agents, and a product of Surehand. It checks each action against a signed manifest before it runs, sends the hard calls to a named approver and seals the record. Gatehouse on this site
What is a teardown?
You bring one process, and we measure its volume and exception rate. You keep the written document, whether or not we go further.
What happens when the agent is unsure?
The action is held, and it goes to a named approver with the evidence gathered. It waits there until they decide, and the decision is saved with their name.
What happens at the spend limit?
An action that would go over the limit is held and goes to a named approver with the evidence gathered. The hold and the decision are saved in the record.
Start here
Bring one process.
Tell us what comes in, who handles it and where it goes wrong. A person replies, usually inside two business days.
support@surehand.io