Integration patterns
These are the most common ways to set up Averment. All of them use handlers so you have full control over what happens for each outcome.
1. Agent feedback loop
Averment acts as an independent control layer for AI actions. It runs in real time, without human involvement, and gives consistent, predictable results.
Use this when an AI agent is taking actions autonomously. Instead of blocking and stopping, you let the agent respond to the outcome and adjust its behavior.
js
The agent does not just get blocked. It gets feedback it can act on.
2. Operator review
Averment sends decisions to humans when needed, ensuring oversight for high-risk operations.
Use this when high-risk actions need a human to approve before anything happens. The action is paused and routed to an operator.
js
3. Hybrid control (Recommended)
Use this when you want both automation and human oversight. For example, you might allow both
allow and caution to proceed, use an AI feedback loop for review, and route block to an operator for review.js
4. Multi-system orchestration
Use this when Averment sits at the center of multiple services or pipelines. Every system routes decisions through Averment and gets consistent enforcement everywhere.
Common mistakes
| Mistake | Effect |
|---|---|
| Treating Averment as logging only | No enforcement, unsafe actions can still execute |
| Hard-coding logic instead of using policies | Requires code changes for every rule update |
| Ignoring feedback loops in AI systems | Agents may continue risky actions without correction |
Next steps
See real-world examples of Averment across different use cases and industries.
Examples
Example code for AI agents, authentication, fintech, healthcare, DevOps, and BYOLLM.