- What does KLA do when an agent tries to act?
- KLA evaluates the action against your policy before the tool runs. The result is allow, warn, require approval, or block. Actions that need approval wait in the Decision Desk for the person responsible.
- What happens while an action waits for approval?
- The tool does not run. The reviewer sees the request, the rule that applied, and the supporting context on one screen. Approval releases the action and rejection stops it. Both outcomes are recorded.
- Which agents can KLA govern?
- Agents you run through KLA Runtime, and agents in your existing stack. Teams add the KLA Node.js or Python SDK, and KLA checks each consequential tool call before it runs. OpenTelemetry adds a record of what the agent did.
- What if an approved action still produces poor work?
- KLA samples completed work for quality review by someone who did not approve it, and the reviewer records a verdict and a reason. When incorrect verdicts push quality below your target, a Finding opens, an owner tracks the fix in a Remediation Plan, and later samples show whether it worked.
- Who writes the policies?
- Your team defines the allowed operations, destinations, and approval requirements in Policy Builder.
- What evidence does KLA keep?
- Each action, the rule that applied, the reviewer’s decision, the tool result, and any quality verdict. The record shows what happened and who decided. Quality review shows whether the work was right. Evidence Room exports a Sealed Evidence Bundle when an auditor or supervisor asks.
- Can an auditor check a bundle without access to KLA?
- Yes. The export ships with a standalone verifier that checks the bundle with no network access. To confirm the bundle came from KLA, the auditor pins its keys against a key fingerprint KLA publishes.
- How long does it take to reach production?
- The SAFR Production Sprint runs four weeks on one workflow. It ends with a verified evidence bundle and a documented production decision.
- What happens after the four weeks?
- A positive production decision defines your subscription. Your controls, quality review, and evidence record keep running as releases and models change, and the next workflow runs on the same platform.
- Where does KLA run, and with which models?
- KLA runs as a managed service or on your own Kubernetes cluster. Your agents use the model provider you choose: OpenAI, Azure OpenAI, Anthropic, or a model you host behind an OpenAI-compatible endpoint.
- What does the first session cover?
- Thirty minutes on one workflow: the agent, the systems it touches, the approval owner, and the evidence you need.