Skip to main content
A classification evaluates an event. Your integration applies the result before the protected action or content is consumed.

​
Read the decision

Check prediction and the optional governance.action. A malicious prediction or a governance action of block is a would-block decision. Governance can block an event whose prediction is BENIGN. The returned score and threshold are diagnostic fields. Route on the verdict and applicable governance decision. Use outcomes for additional malicious-result detail.

​
Apply the result

Choose Shadow or Warn explicitly when observing. Python and Go use a Block fallback when the response and local configuration omit a mode. Framework adapters resolve their own override first, then the client setting, then an optional response mode, then Block. Current classify responses omit mode. SDK results preserve explicit local choices. Java examples choose a mode explicitly.

​
Handle a failed check

An API, network, timeout, or cancellation error leaves the event without a verdict. Choose whether that boundary stops or continues when classification fails. Deep Agents allows execution on classification errors by default. Set failOpen: false in TypeScript or fail_open: False in Python when execution requires a completed check. The LiteLLM starter uses unreachable_fallback: fail_open. Check each integration guide for its error policy.

​
Enable blocking

Start with observation and verify connected boundaries. Review would-block findings, choose the error policy, then enable Block on the intended boundary. Repeat verification after changing the mode. For streaming output, buffer and classify content before delivery when blocking must prevent exposure. Checks cover the paths connected to Silmaril. Route every protected operation through those paths.