Stopping an action requires running in the same path that executes it. A check that reads the result afterwards can only record what already happened.
Akka Verify runs guardrails inline in the transactional path. The check finishes before a response is emitted or a tool call is made, and the action, the verdict and the audit entry are written in one transaction.
A check runs either outside the request path or inside it. Outside, the check receives a copy of what the agent did. The check can score the response, raise an alert, and open a ticket. The action it is scoring has already executed.
Inside, the check holds the request while it runs. The agent proposes an action, the guardrail returns a decision, and the runtime acts on that decision before anything reaches a customer or a system of record.
A check in the request path runs before the response, so its duration is added to the response. The latency cost is why each control chooses its own mode.
Compliance owns the policy matrix that makes the choice. A control that must prevent an outcome runs inline. A control that only has to be evidenced runs against the interaction log after the fact. Inline checks and after-the-fact checks produce the same evidence record. Only the inline check can change what happens.
The runtime treats an unavailable check as a failed check, so the action does not execute. A guardrail that fails open is a guardrail that stops enforcing under exactly the load that makes enforcement matter.
The paused run holds its state and releases its resources. Other work continues, and the held run resumes at the step where it stopped once the decision arrives, whether that takes a minute or three days.
Compliance owns the policy matrix, and the runtime enforces it. Engineers do not hand-code the decision, so a change to policy does not require a change to application code.
The proposed action, the policy that refused it, the verdict, and the time. The record is written in the same transaction as the refusal, so an auditor reads the decision itself. A missing result would leave the auditor inferring one.
Evaluation and evidence work against agents built on other frameworks. Inline enforcement requires the runtime to sit in the execution path, which means the agent runs on Akka.
Evaluation, inline enforcement, and the evidence record an auditor reads.
The classification decides which controls a system has to enforce.
Financial actions are regulated, irreversible, and time-critical.
