How KLA works
Check the policy before the tool call.
An agent requests a payment. KLA evaluates the amount against your operating rule. The connected execution path can proceed, pause for review or stop before it reaches the payment tool.
Every strand is one agent action.
Agents call tools, send email, move money, and change records.
Each action meets your policy first.
KLA checks every action against the active policy before the tool runs.
- When
- action is
payments.transferand amount is above €1,000,000 - Then
- Hold for two approvals
- Reviewers
- Compliance officer L2, then MLRO. Two different people.
- Due
- Within 2 hours
Some actions wait for a person.
The rule names the reviewer. Higher risk goes to a higher level, and the largest amounts need two different people.
- No requests waiting. New ones arrive in a few seconds.
Every decision is sealed.
Every outcome, blocked actions included, is written to the evidence chain. Each record's hash covers the record before it.
The hashes are SHA-256 digests computed in your browser.
Follow one case from start to finish.
A Journey links everything an agent did on one case: each action, its policy outcome, who approved it, and the sealed record.
- Journey
- Onboarding Halden Logistics
- Process
- Business onboarding
- Agent
- Onboarding agent
Connect one operation, then test its failure paths.
A checkpoint needs to stop or hold the operation. Telemetry reports what happened; enforcement requires the tool call to respect the decision.
Confirm the supported integration, supplied policy context, reviewer permissions and captured events. Coverage follows that connected action path. Include unavailable dependencies, rejected approvals and tool failures in the evaluation.
Review supported integration paths- 1
Define the action and its policy
Identify the operation, the context it needs, the applicable rule and the person responsible for exceptions.
- 2
Connect the execution boundary
Place the supported integration at the tool call or operation that must respect the policy decision.
- 3
Apply the decision
Permit, warn, hold for an authorized reviewer or block the action according to the policy outcome.
- 4
Review the connected record
Inspect the request, applicable policy, human decision and resulting action in the execution record.
Open the detail your next review needs.
Resolve a waiting request, investigate an executed action or inspect an evidence sample. Each surface answers a different question about the workflow.
Lineage Explorer
Follow the action through its recorded decisions and outcome.
Explore Lineage ExplorerBring one agent and the tools it uses.
We can map the policy checks, review steps and evidence needed for an evaluation.