Evaluation guide
Prepare your workspace
Confirm the environment, permissions and data boundary before the first workflow.
Confirm the enabled version and permissions in your environment. These guides do not announce a general release.
Before you start
An agreed evaluation scope and confirmed integration version. Gateway, SDK, adapter, playground and binding screens are marked planned in the reviewed product navigation.
Steps
- Record the environment, product version, responsible owner and permitted data. Keep credentials outside the document.
- Define the boundary to protect: model request, response or tool action. Document the actor, policy and allowed effects before integration.
- Bind policy to the actor and protected action. Decide explicitly whether an unavailable check blocks the action or sends it to human review.
Check the result
Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
If it does not work
Distinguish detector failure, policy rejection and enforcement failure. A permit decision without a verified enforcement record is not proof that protection completed.