Keep the meaning clear.
“Payments above $5,000 need Finance approval” is a rule a business can review, own and explain.
Make your business rules part of the action.
Write your rules in plain English and put them in the path of connected workflows and AI agents. Hold an action when a requirement is missing, and bring in the right person when approval is needed.
Connected workflowAI agent action
Held for review
Schedule a $7,450 supplier payment
The payment is above the $5,000 approval limit. Finance needs to review it before it can proceed.
Approve supplier paymentsVersion 2 · Finance controls
RW
Ryan WalkerFinance reviewer · Approval needed
Payment has not been scheduled
A policy cannot protect the business if the workflow never checks it.
Your people and agents can commit money, share information and make promises in seconds. Put the relevant checks before those actions, so the business has a chance to catch a missing approval or an unmet requirement while it can still make a difference.
Start with the rules your business already understands.
Write what should happen in plain English, or import an existing policy document. Review the statements before publishing, then choose the agents and connected workflows where the rules belong.
Plain-English rules, with a version and a clear place in the business.
Published · v2
Payments above $5,000 require Finance approval before execution.
Applied only where explicitly attached.Reuse rules where they belong.
Organize rules into groups such as Finance controls, then attach them to the relevant agents. See where each rule is used before changing it.
Choose what is governed.
A rule saved in the library starts unattached. Connect it deliberately to the work it should check.
Let your rules evolve without losing why an earlier decision was allowed.
A new requirement should change the next action without rewriting yesterday’s record. Publish a new version with the reason for the change, and keep earlier actions linked to the exact rules they used.
See who changed a rule, when it changed and which agents use it. Review conflicts before publication. If you restore an earlier rule, it becomes a new version with its own history.
Here, version 2 adds independent verification when a supplier’s bank details change. Version 1 remains available to explain decisions made before that requirement existed.
RulesAcme Dynamics · Agents portal
Approve supplier payments
Version 2Rule
Payments above $5,000 need Finance approval. If a supplier’s bank details have changed, verify them independently before payment.
- Status
- Active
- Created by
- Logan Hayes
- Where it is used
- Finance controls · 3 agents
Changes are checked against the rules on affected agents before publication.
Give the reviewer the full picture before the action goes ahead.
A supplier payment needs more than a yes or no. Bring the amount, agreement, required checks and responsible reviewer into one record, so approval is based on the work behind the request.
ApprovalsAcme Dynamics · Agents portal
Awaiting approval
Finance approval is still needed.
The agent requested a $7,450 supplier payment. The invoice matches the agreement and the bank details have been verified, but the amount needs Ryan’s approval.
Supplier invoiceSigned agreementBank verification
- Requested action
- Schedule supplier payment
- Rule applied
- Approve supplier payments · v2
- Invoice and agreement
- $7,450 · Amounts match
- Bank details
- Independently verified
- Finance approval
- Waiting for Ryan Walker
The connected workflow is held before the payment is scheduled.
Proceed when the checks pass.
Work within the rules can move ahead without an unnecessary approval request.
Hold what needs a decision.
Keep a governed action waiting for required evidence or an authorized reviewer.
Stop what the rules prohibit.
An approval does not cancel other restrictions. A prohibited action stays blocked.
Give auditors the record behind the rule.
When a reviewer asks why a payment was allowed, connect the amount, rule version, supporting evidence, approval and tool outcome in one scoped packet.
Your team can spend less time collecting screenshots and asking who remembers the decision. The auditor can trace what happened, who signed off and what the record does or does not establish.
Explore audit readinessSupplier payment review
22 September · Fixed snapshot
- Agent
- Payment coordinator
- Period
- 22 September, 09:00–10:00
- Purpose
- Review the $7,450 supplier payment
- Snapshot
- Rules, attachments and events at export
Later rule changes do not rewrite this snapshot. Evidence supports review within the stated scope.
Knowing as fast as doing.
For the actions that matter most, the doing waits for the knowing.
Keep the business context close to the decision and put the check in the action’s path. Your people and agents can move with the evidence, authority and accountability the work deserves.
Give your agents business contextClear rules, with clear answers.
Can we write rules in plain English?
Yes. Write the requirement in ordinary language or import an existing policy document. Review the extracted statements and their supported checks before publication. Your business decides what is published and where it applies.
Does saving a rule apply it to every agent?
No. Rules created in the agent library start unattached. Attach a rule directly to an agent or organize it into a group and attach that group. The record shows which groups and agents use it.
Why keep different versions of a rule?
Rules change as your business learns. Each published version keeps the statement, author and reason for the change, while earlier action records retain the version used at the time. Restoring an earlier rule publishes a new version rather than replacing the history.
Which actions can be held before they happen?
Actions can be held when their connected execution path passes through the required check and honors its result. The supported workflows, action types and integrations are agreed during setup. Connecting a source, registering an agent or using MCP does not by itself intercept every action.
What happens when someone approves an action?
The approval records that person’s decision for the specific request. The workflow must still satisfy the remaining rules and checks before execution. A separate outcome records what the connected tool actually did.
Can the system stop an action it only learns about afterward?
No. An action observed after it happened can be investigated and explained, but cannot be stopped retroactively. Prevention requires the check to sit in the action path before execution.
How does this help with audits?
A scoped packet brings together the agent, exact rule version, evidence, approval and recorded outcome. Auditors can trace how the control was applied, and your team spends less time rebuilding the history. The record supports review within its coverage; it is not a certification or a guarantee that every external action was captured.