Powered by ARBITER Email Gate
Prepare and Send a Customer Follow-Up
See AI prepare a customer message, surface the risk, ask for approval, act once, and return proof without keeping permanent email access.
AI Action Gate
Before AI does something real, ARBITER checks whether that exact action should be allowed.
When integrated into a workflow, ARBITER Gate sits between an AI request and a real action. It checks what is being requested, the rules that apply, whether a person must approve it, what limits apply, and what should be recorded before anything important happens.
request → rules → approval if required → limited permission → final check → action → verified record
The doctrine
Context is not permission.
A recommendation is not approval. Approval applies only to the action and limits you can see. Before anything runs, ARBITER checks those details again, then records what actually happened.
Why the category matters
Providers change. The authority boundary should not.
Models can research, draft, reason, and propose. The Gate answers a different question: may this exact actor perform this exact action against this exact target under the current policy and authority state?
The control loop
Seven controls for sensitive actions.
- 01AI proposes an exact action
- 02ARBITER checks current policy and state
- 03A person approves the exact action if policy requires it
- 04A limited, expiring permission is issued
- 05The action is checked again before it runs
- 06The constrained action runs
- 07The outcome is recorded and authority is consumed, expires, or is revoked
Working reference proofs
Start with the action you recognize.
Each public example leads with work a client can recognize. The smaller ARBITER label identifies the control behind it. Demo results are synthetic examples, not proof that every outside system is already connected.
Powered by ARBITER System Action Gate
Run a System Action Safely
See one exact system action limited to one sandbox, one approved command, and one short execution window instead of opening an unrestricted terminal.
Powered by ARBITER File Action Gate
Update a File Without Losing Control
See one file change limited to the approved path, operation, size, and content while neighboring files and broad storage access remain out of bounds.
Powered by ARBITER Support Access Gate
Inspect a Customer Issue Without Taking Over
See a short, read-only support session limited to one site and device group while configuration changes and permanent access remain blocked.
Powered by ARBITER Network Change Gate
Make a Controlled Network Change
See one network change bound to the exact site, devices, validation check, and rollback plan before any adapter is allowed to act.
Where this helps
One permission pattern. Many business workflows.
Start with one workflow where a mistake would cost time, money, trust, or access. Each implementation still has to qualify its own identity, adapter, credentials, policy, approval, one-time authority, evidence, rollback, and incident path; the provider can change without changing that contract.
- customer messages
- exact system actions
- file updates and publication
- remote support sessions
- network changes
- customer follow-up
- payment-intent creation
- connected API actions
Add another controlled workflow
Controlled Workflow Add-On — $149/month.
Add one named ARBITER-controlled workflow to an eligible Centaur workspace. The recurring license covers the rules, approval steps, limited permissions, activity history, expiration, and ongoing maintenance. Connections to outside systems are set up and tested separately before use.
Workflow license includes
- → one named action and target
- → deterministic policy and current-state checks
- → human approval path when required
- → short-lived limited permission
- → execution-time revalidation
- → constrained adapter boundary
- → allow, deny, hold, expiration, cancellation, repeat attempts, and outcome evidence
- → reviewable action record and emergency-stop plan
For business owners
Use AI to reduce busywork while keeping configured consequential actions behind explicit authority boundaries rather than permanent model permission.
Discuss the first workflowFor technical teams and integrators
Add reusable approval rules, limited permissions, and a reviewable action record around important actions that touch systems, providers, network devices, support workflows, or business records.
Review developer contract