Why was the refund declined?
The request exceeded the agent’s approval limit. A human reviewer declined the exception.
- Control
- Refund policy · version 2.8
- Intervention
- Human decision recorded
- Sources
- Gateway · Policy · Approval · CRM
Arkna prepares the activity, controls, source references and human decisions from one AI workflow into a record another person can check.
The request exceeded the agent’s approval limit. A human reviewer declined the exception.
Open the sequence, the control that applied and the intervention. You do not assemble a new account afterwards.
Engineering, risk and audit work from the same record. They do not need the same interface or vocabulary.
Source references stay with the record so reviewers can understand where each event came from.
Follow observed events, sources, exceptions and interventions. Open a run when something looks wrong, with its context still attached.
Prepare a readable record with source references, integrity checks and the capture statement kept alongside the activity.
Arkna brings activity from the services behind an AI deployment into one ordered record for operations, risk and audit.
See how sources connect →Choose the path that fits the review question, available source data and architecture.
Observe requests and responses that pass through an agreed gateway. Useful when the interaction boundary is the central review question.
Available for scopingEmit selected application events with richer workflow context. It remains a cooperative source and can only report what the integration sends.
Available for scopingReuse existing OpenTelemetry or compatible traces where they already describe the workflow. Coverage depends on the instrumentation in place.
Available for scopingBring one workflow. We map the connected sources, the reader and the first question the record should answer. A larger implementation comes after.