Evaluation guide
Complete a first workflow
Follow a small end-to-end example and verify its result.
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
- Define the boundary to protect: model request, response or tool action. Document the actor, policy and allowed effects before integration.
- Prepare benign, prohibited and sensitive-data fixtures. In the available evaluation interface, compare detector signals with the intended policy decision.
- Check the decision, required masking or approval, and enforcement evidence together. Test timeout behavior before connecting an action that changes data.
Check the result
Check the decision, required masking or approval, and enforcement evidence together. Test timeout behavior before connecting an action that changes data.
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.