Skip to main content
On this page

Use this page to define the controls shared by every specialized agent. To compare the five agents and choose one for a specific outcome, start with Meet the agents.

One policy layer for every agent#

Flow diagram
ObserveRecommendExecute1Approved data andevents2Specialized agent3Commercial, risk,and operationalpolicies4Action authority5Insight and trace6Human or systemdecision7Bounded action8Outcome measurement
Result or outcome

Every implementation must define:

  • the data and events the agent can read;
  • the providers, markets, methods, and transactions it can affect;
  • commercial commitments, risk rules, eligibility requirements, and technical constraints;
  • whether an output is observational, advisory, approval-gated, or executable;
  • timeouts, static fallbacks, rollback conditions, and incident ownership;
  • the metrics and evaluation period used to decide whether exposure can increase.

Roll out progressively#

StageWhat changesRequired evidence
ObserveThe agent analyzes historical or live data without changing an operation.Data completeness and reproducible reasoning
ShadowThe agent records the decision it would make while the existing behavior remains active.Agreement between predicted and observed outcomes
Controlled exposureAn approved share of eligible activity follows the agent.Guardrail health and statistically useful outcome comparison
ActiveThe agent operates within the approved policy and traffic boundary.Continuous monitoring, traceability, and a tested rollback path

Operational agents can use an equivalent progression: observe, recommend, approval-gated action, and bounded automation.

Integrate without inventing a public contract#

When DEUNA owns the relevant payment or operational surface, supported agents can run within that flow. When your system remains the executor, consume only the decision or file interface agreed for your account. Do not infer a public endpoint from a dashboard or marketing example; your DEUNA Technical Account Manager confirms the supported contract, authentication, latency, and failure behavior.

Continue#