Make authority specific.
Set the operation, resource, actor, budget and expiry. Delegation can narrow the original permission.
AGENT AUTHORITY, MADE EXPLICIT
Give agents
room to work.
Keep control.
When an instruction changes, your agent’s authority should change with it. RuleEvo checks permission before admission and keeps external outcomes in view.
Private prototype · Bounded integrations · Seeking a first design partner
AUTHORITY RECORDILLUSTRATION / 01
Allowed operation
drive.folder.createResource boundaryDedicated test folder
External spend$0.00
Decision pointBefore admission
Permission checkedAuthority active
Owner withdraws instructionEpoch changes
Future admission deniedOutcome recorded separately
Already admitted work may still complete.
Explicit authority.
Observable outcomes.
Observable outcomes.
THE MOMENT THAT MATTERS“Stop” needs an execution boundary.
“Stop” needs an execution boundary.
And a record of what happened next.
Useful control sits where an integrated agent is about to act. A revoked instruction should block future admission. A completed write should stay completed. An uncertain result should stay uncertain until checked.
THE CONTROL LOOPPermission is a process.
Permission is a process.
Not a permanent pass.
One bounded workflow, from the owner’s instruction to the provider’s observed outcome.
Check where work begins.
Recheck authority before claiming execution. Stable request keys prevent duplicate accounting; adapters handle external effects.
Keep outcomes honest.
Withdraw future authority. Separate blocked, completed and unresolved work. Read back ambiguous writes before retrying.
TRY AN ILLUSTRATIONChange the instruction.
Change the instruction.
See the next decision.
This is a local simulation. It does not call RuleEvo, Google Drive or another provider.
InstructionActive
Next action admissionAllowed in this illustration
Previously completed folderStill completed
Authority is available for the next protected admission. External completion is a separate fact.
WHAT EXISTS TODAYBuilt. Tested.
Built. Tested.
Still a bounded pilot.
Product tests establish specific behavior. They do not establish customer demand, production certification or control over every agent.
Synthetic provider cases
Separate documents, reports and simulated-bookings services exercised withdrawal, outages, retries, unknown outcomes and a real reports-provider redeployment.
All services share the same owner/operator. No commercial bookings or payments.Real Drive sandbox checks
Restricted folder creation tested with actual Google Drive metadata readbacks, including duplicate prevention, withdrawal and a deliberately lost response.
The connected agent executes the write. Observations are bridge-recorded, not Google-signed.Control applies to the route you integrate.
Direct credentials can bypass an adapter. Withdrawal cannot undo admitted or completed effects. Unknown work needs reconciliation.
Customer-specific access, measured costs, security review and a supported deployment arrangement come before production use.
Prototype tests completed October 17, 2026. Evidence walkthrough available during discovery.
DESIGN-PARTNER OFFERStart with one
Start with one
meaningful action.
For teams building agents that write to business systems. Bring a real control problem and a technical owner. We’ll scope a harmless sandbox before customer data or production work.
- One workflow and an explicit execution boundary
- Withdrawal, retry and uncertain-outcome acceptance tests
- A shared review of evidence, effort and operating cost
Proposed experiment. No instant checkout or automatic renewal.
ONE-MONTH PILOT
$199USD
Includes 50,000 unique authorized action prechecks
Additional authorized actions$0.001 each
Denied requests & idempotent retriesNo added usage fee
Usage ceiling agreed before starting. Onboarding, integration engineering, provider/model fees and applicable taxes are separate. Proposed ongoing support: two hours, scheduled by agreement. Commercial billing is not enabled.
Discuss the pilot Scope, acceptance, access, payment and service terms require agreement first.BEFORE YOU ASK
A few clear answers.
Does this make every AI agent pass through RuleEvo?
No. RuleEvo controls admission only for workflows integrated with its execution boundary. It is not a universal agent gateway or a mandatory toll.
Can withdrawal undo a completed action?
No. Work admitted before withdrawal may still complete. Recovery, refunds or undo operations are separate provider-specific processes.
Which integration can I test first?
The current real adapter is restricted to creating generated folders inside one dedicated Google Drive test folder. Google access stays with the connected agent. Existing files, sharing, deletion and production writes are outside the initial sandbox offer.
Is this a production service or security certification?
This is a private prototype seeking design partners. Product tests are not independent security review, production certification, an uptime guarantee or a promise about third-party outcomes.
What counts toward the usage price?
Unique authorized action prechecks are the proposed unit. Denials, status reads, commits and retries with the same idempotency key do not add usage units. The first 50,000 are included in the proposed $199 month; a 100,000-action month would be $249 before separate services or applicable taxes.
LET’S TEST THE IMPORTANT PARTWhat should your agent
What should your agent
stop doing when you say stop?
Tell Mohamad which tool action you want to control, your current workaround, and who owns the integration. No credentials or sensitive customer data, please.
Email the founderOpens your email app · maximosyos@gmail.com
Mohamad Rawass · Beirut, Lebanon