These written rules decide PASS or FAIL. A broken blocking rule fails the gate; a non-blocking rule only warns. Saved in this browser and used by Evaluate. Export as YAML to enforce the same rules in CI.
Start from a pack
Support bot
Customer-facing answers drawn from a help centre or policy
Strict on private data and invented policy, relaxed on style. 6 rules.
RAG, strict
Retrieval-augmented answers that must stay inside the retrieved passages
High grounding bar, citations required, consistency checked. 5 rules.
Structured output
Answers consumed by code: JSON from an extraction or classification step
Exact checks only. Nothing here depends on a model judge, so the result is identical on every run. 4 rules.
Safety first
Open-ended assistants where tone and data leaks matter more than grounding
Blocks toxicity, personal data and secrets; warns on canned refusals. 4 rules.
Try it (warnings only)
First experiments: see every signal without anything failing hard
Every rule is a warning, so the gate passes unless an exact secret or personal-data check trips. 4 rules.
Packs are starting points with defaults chosen by the author, not calibrated thresholds. Check them against your own examples.
Active rules
Add a rule
Share of claims the source text supports.