How it works
Security actions follow customer-defined policy. A generated explanation does not change a rule, grant an exception or authorise access to evidence.
Policy and control
Deterministic detection and policy provide an inspectable decision path. Any separately configured model service needs its own approved task, data boundary and access controls.
Deployment and operations
Define the permitted role of assistance before connecting a model service. Keep policy changes and evidence approvals within their existing authorised workflows.
How to read this
| Review | Product context | Operating decision |
|---|---|---|
| Policy | Customer-defined rules and actions | Assign policy ownership |
| Records | Decisions with policy references | Define review access |
| Deployment | Supported clients and data paths | Validate configuration |