Problem/Motivation

Varbase ships AI agents that interact with user input and generate content, but every new Varbase site starts with zero AI safety controls. No PII detection, no liability guardrails, no XSS / prompt-injection blocking, no AI logging, no observability. Enterprise Varbase clients require GDPR coverage, liability control, security hardening, and compliance audit trails site builders must hand-wire every guardrail rule and set retention policies manually.

Proposed resolution

Initialize a varbase_ai_safety recipe that bundles a complete AI safety stack via the recipes: chain plus direct module install:

Result: 14 guardrail rules across 3 sets, AI logging enabled with prompt_logging: true and prompt_logging_max_age: 90, observability ready for compliance reports out of the box.

Remaining tasks

  • ✅ File an issue about this project
  • ✅ Addition/Change/Update/Fix to this project
  • ✅ Testing to ensure no regression
  • ➖ Automated unit/functional testing coverage
  • ➖ Developer Documentation support on feature change/addition
  • ➖ User Guide Documentation support on feature change/addition
  • ➖ UX/UI designer responsibilities
  • ➖ Accessibility and Readability
  • ✅ Code review from 1 Varbase core team member
  • ✅ Full testing and approval
  • ✅ Credit contributors
  • ✅ Review with the product owner
  • ✅ Update Release Notes
  • ❌ Release varbase-11.0.0-beta1, varbase_starter-beta1, varbase_ai_safety-1.0.0-alpha1

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • feat: #3589351 Initialize Varbase AI Safety recipe

Comments

rajab natshah created an issue. See original summary.

rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Version: » 1.0.x-dev

rajab natshah’s picture

Assigned: rajab natshah » josebc
Status: Active » Needs review
rajab natshah’s picture

rajab natshah’s picture

Assigned: josebc » Unassigned
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

rajab natshah’s picture

Issue summary: View changes

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

rajab natshah’s picture